/srv/irclogs.ubuntu.com/2022/09/25/#ubuntu-mate.txt

moshebug confirmed by another friend08:26
alkisgIt's possible that lightdm requires one of the missing stanzas, while other DMs do not require it. 14:31
alkisgYou could check which line makes the difference (starting from mate.desktop, changing Exec=i3), or you could directly file a bug against lightdm14:31
mosheI've looked at that already14:35
alkisgAnd you found the line?14:36
moshedidn't find anything obviously missing eyeballing i3.desktop against mate.desktop and jw.desktop14:36
alkisgDoes it work if you start with mate.desktop and change just the Exec line to i3?14:37
moshealso, it's exactly the same file I had in 20.04 and lightdm has only received 2 minor updates since then14:37
alkisgI just tried apt install i3 in jammy-mate and it worked fine for me14:38
alkisgI selected it from the login screen and I'm now seeing the first configuration dialog14:38
moshewas the background of t he lightdm entries garbled ?14:40
alkisgno14:41
moshenot even sure if  that's related tbh, I haven't messed about with that yet14:42
moshehttps://paste.debian.net/plainh/c6aa72d614:42
mosheis your i3.desktop file the same ?14:42
moshethis is what 22.04 dropped in/usr/shar/xsessions after nuking and reinstalling i314:43
mosheoh wait I might have done a forced reinstall14:43
moshebut I do remember my friend's file being the same 14:43
moshepurged, removed the files myself, reinstalled i3, nothing was put back into /usr/share/xsessions now lightdm can only find mate14:48
alkisgi3 installs i3-wm which has the session file15:01
alkisgIf i3-wm is missing for you, something is wrong15:01
moshethe packages are installed15:02
alkisgMy i3.desktop is termbin.com/2wyi15:02
mosheit's i3.desktop that didn't get put back in15:02
alkisgUse `sudo dpkg -V` to discover if you manually deleted files that you shouldn't have15:02
alkisgFor example if you rm /usr/share/xsessions/i3.desktop, and then you apt install --reinstall i3, you're causing issues15:03
alkisgAs that file is shipped by i3-wm, not by i3, so reinstalling i3 won't put it back15:03
moshenot what I did15:03
mosheuninstalled, purged, nuked the files, reinstalled15:03
alkisgWhat's the output of sudo dpkg -V15:04
moshestill running but so far nothing except ??5?????? c /etc/gnome/defaults.list15:04
alkisgLet it run. And you're saying you have no files in /usr/share/xsessions now?15:07
moshea handful of files, most I don't recognize, and it's complaining about those 2 .desktop files15:07
mosheyes15:07
moshereinstalling i3 didn't put them back in15:07
alkisgRun this: dpkg -S /usr/share/xsessions15:07
alkisgi3-wm, mate-session-manager15:08
alkisgThese are the packages that you need to reinstall to get the desktop files back15:08
alkisgNot i3, not mate15:08
alkisgsudo apt install --reinstall i3-wm15:08
alkisgAlso put the output of dpkg -V to pastebin15:08
alkisgSince the files that you don't recongnize might be importatnt15:08
alkisgs/importatnt/important/15:09
moshewell I killed it to run the other command15:10
mosheand I fail to see how uninstalling i3 an following that up with an autoremove, to then install i3 and i3status, wouldn't put the files back in15:11
mosheand yet forcing a reinstall of i3-wm did put them back in15:11
moshesame content as what I pasted earlier15:12
alkisgIt's what I'm trying to explain about package management15:12
alkisgWhen you uninstall or reinstall a metapackage, it doesn't automatically reinstall all its dependencies15:12
mosheautoremove15:13
alkisgSo for example if you ever apt purge --auto-remove mate-desktop and then reinstall it, you completely break your installation15:13
alkisgAs all the programs that depend on mate-desktop get removed by they don't automatically get back15:14
alkisgFor me to help more, I'll need the output of `sudo dpkg -V` and `sudo dpkg -l`15:14
mosheanyway I'm going to log out and back in, see if that changed anything. If that did, then we still have a problem because the same thing happened on a clean install a few months ago, and inside a vm last night.15:14
alkisgIn any case this isn't a development channel15:14
alkisgSo you can't report bugs here, you can only get volunteer help15:15
alkisgSo even if you are able to reproduce the issue in a clean installation (I wasn't, it worked fine for me), the next step is to report the bug15:15
moshenope, fails and falls back to i315:15
mosheI have already15:15
moshe*falls back to mate15:16
alkisg> For me to help more, I'll need the output of sudo dpkg -V and sudo dpkg -l15:16
mosheI'm running them15:16
alkisgYou may even test with a live cd if you wish15:16
alkisgapt install i3 in the live session15:16
alkisgBtw if you reported the bug, you may mention it here so that it helps with the discussion15:18
mosheI did it just as you started asking questions15:20
mosheI assumed it was why you were asking15:20
moshehttps://bugs.launchpad.net/ubuntu-mate/+bug/199077115:21
mosheas for the output you asked for https://paste.debian.net/plainh/ab2de20615:22
alkisgNo dpkg -l output there16:06
alkisgYou may run `dpkg -S filename` for the affected files16:06
alkisgIt will show the affected package. By reinstalling it, you'll fix the dpkg -V issues16:07
moshehalf of the dpkg -V output is on purpose16:07
moshethe other half I have absolutely no clue, I don't go around and nuke files willy-nilly so I can only assume they're leftovers from the previous install16:08
alkisgInstallations and upgrades can't cause that dpkg -V output; in any case I've mentioned how to fix it16:10
mosheI'll look into it16:11

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!