=== brainwash_ is now known as brainwash [04:28] thankfully i fixed something so i only have two things to find out, ones super simple so im gonna type it in here [04:31] i might sound dumb with this but whats the second session on my login screen? [04:31] one says XFCE4 Session and ones just Xubuntu-Desktop [04:32] i read the XFCE4-session is just a raw barebones version of XFCE4 and xubuntu-desktop which im on now is what i can customize and all? [04:32] is there a way i can delete that extra session? [05:07] anyone on? [12:02] hey diogenes_ I've finaly managed to work around the issue when the icon position resets on login/reboot [12:02] misko_, and what was it? [12:04] I remove the write permission of .config/xfce/desktop on logout/shutdown/reboot and change them back to 755 on login [12:04] https://forum.xfce.org/viewtopic.php?pid=49764#p49764 [12:04] oh ok i see, i just never use icons on desktop that's why i didn't even have a vlue that such bug can exist :) [12:07] The first script runs on startup. The second I use for logout/shutdown. That bug is here for a long long time :) [12:16] Preety nice application http://xlunch.org/ but it will run under xfdesktop in desktop mode. This is great for openbox. [13:59] I have a following problem with Xubuntu Bionic... [14:00] when the computer first boots up, it suspends fine [14:00] however, if I try suspending it afterwards, it won't [14:01] I get desktop notification by DBus and PowerManager (i think) saying something about "suspend or shutdown already in progress" [14:02] not only that I can't suspend, but the computer won't shutdown either [14:02] Xfce logs out and it just stays at login screen [14:10] the only way to shut it down is to go to console and either login and use poweroff command (I believe sometimes this doesn't work too) or hit ctrl-alt-del [14:15] and after it executes the manual shutdown sequence, THEN the machine goes to suspend [14:15] powers off only after I bring it out of suspend [14:15] what gives? [14:17] HalfWord: I recall reading about this issue on launchpad [14:19] there are some bugreports, but it seems no solution so far... [14:20] it's hard to pinpoint the culprit... is it dbus, systemd, kernel, some power management components...? [14:21] bug 1441253 [14:21] bug 1441253 in systemd (Ubuntu) "hanging suspend job prevents shutdown" [Undecided,Won't fix] https://launchpad.net/bugs/1441253 [14:23] I could've suspected it would be systemd... damn that piece of bloatware [14:23] I've never had problems like that before systemd :( [14:24] I would temporary disable xfce4-powermanger and/or light-locker, and see if this issue still occurs [14:26] tnx, I've now disabled the suspend timer in the xfce4-powermanager, will see how it fares... [14:26] also, there may be some hint in "journalctl" [14:28] tnx, haven't checked that yet, only dmesg and syslog but no clues there... [14:30] I guess The Monster's log might have some [14:31] https://bugs.freedesktop.org/show_bug.cgi?id=82670 [14:31] Freedesktop bug 82670 in general "logind fails to suspend anymore after random number of suspends" [Normal,Resolved: worksforme] [14:32] ohhh [14:32] https://devtalk.nvidia.com/default/topic/1025478/linux/cannot-suspend-after-some-time-of-idle/ [14:32] this one has an interesting comment [14:32] "It seems that this issue was closely related to lightdm and light-locker. light-locker switches VT to lightdm's one and suspend action is going on in parallel. Seems nvidia cannot handle this correctly." [14:33] great [14:33] that's probably it, I have a nvidia card [14:34] and you use the nvidia driver? or the open source one? [14:35] nvidia driver [14:35] there are quite some issues with the closed source one in 18.04 iirc [14:35] ok [14:35] I've switched to the closed binary one because I had some issued [14:35] issues* [14:35] the last link shows problems identical to mine [14:36] so that's it... perhaps I should switch back to nouveau [14:37] if possible, I suggest that you add that info to the linked launchpad report [14:38] but I had problems with some applications, the whole window content would flash and disappear and reappear... so it wasn't very usable [14:38] perhaps I should try with another card... an ATI one... [14:38] keep the nvidia driver and use another screen locker then? [14:39] that seems like a good option [14:39] which one might I try? [14:40] xscreensaver probably, but it's not fancy looking compared to light-locker [14:40] there are various other minimal locker also [14:41] ugh... I've used xscreensaver for years and been sooo happy when I finally switched to a more modern one like light-locker ;) [14:43] maybe mate-screensaver [14:43] I haven't tried that one yet [14:44] one would have to add it manually to /usr/bin/xflock4 [14:44] xflock4 being a simple script that just calls the locker [14:45] so, mate-screensaver has to run on session start, and xflock4 would need to run "mate-screensaver-command --lock" [14:45] same for gnome-screensaver, but that may be in a bad shape [14:45] gnome abandoned it years ago [14:46] well, I've just returned to good ol' xscreensaver ;) [14:46] we'll see how it goes [14:46] ok [14:47] thanks again, I hope this will help [14:48] you're welcome [14:49] at least xscreensaver has one advantage... it's fast, accepts the password even before the screen wakes up :) [14:50] I'll try to suspend this bucket of bolts now... if I succeed, I'll timeout ;) [14:50] see you guys [17:41] Hmm. I just logged in after fresh bootup and my system tray has two wifi icons. They appear to be linked to the same app, but the wifi signal strength indicator looks slightly different [17:41] I just removed one :) [17:41] Bish bosh [17:46] cheets, that's a known bug, sometimes tray icons (Network and Redshift in my case) get duplicated [17:47] you can restart your panel "xfce4-panel -r" or hide those icons in the Notification Area (then expand arrow would be displayed instead) === benoliver999_ is now known as benoliver999 [23:17] since today's packet upgrades i get loads of these errors: https://paste.ubuntu.com/p/xBsxQKXHSn/ on xubuntu 18.10 [23:18] and this seems to bring a series of problems, onboard is not working properly anymore, but also pulseaudio cannot start most of the time [23:20] also .xsession-errors is full of these "AT-SPI: Could not obtain desktop path or name" === Spass_ is now known as Spass