[09:54] <lighterowl> hey there, xubunters. I've upgraded my system from 18.04 to 19.10, and changing Xfce themes in "Appearance" doesn't work anymore - only "Greybird" changes anything despite there being more on the list. .xsession-errors contains a lot of "Unable to locate theme engine in module_path: "xfce"" (the theme engine differs depending on the style) messages - is there something that maybe got uninstalled
[09:54] <lighterowl> during the upgrade? thanks in advance!
[10:15] <astraljava> Hey guys, what is the current method to specifying which monitor should the panel(s) be displayed on? I found some instructions via google, but none seem to be currently valid anymore.
[10:18] <JackFrost> lighterowl: A lot of stuff went from being GTK2 to GTK3 (well, Xfce did) so my guess is that you are selecting GTK2 themes (with a missing theme engine) and thus it wouldn't really affect much.
[10:20] <lighterowl> JackFrost: I see, thanks!
[10:21] <JackFrost> lighterowl: There's themes such as Numix, Arc, etc in the archive, I know of several themes to make it look like various Windows releases too! :P
[10:21] <JackFrost> 'apt-cache search gtk-theme' might help.
[10:22] <lighterowl> JackFrost: I'm not that much into looks. :) I'm actually fine with Greybird, but thought that maybe something was off in the system.
[10:22] <JackFrost> Greybird just got a nice 'dark' version, looks pretty shiny.
[10:23] <lighterowl> astraljava: PPM on panel -> panel submenu -> panel preferences -> output
[10:23] <lighterowl> JackFrost: yes, that's the one I'm currently using. like it very much so far.
[10:27] <astraljava> lighterowl: Right, got it. Didn't realize that dialog is dynamic, meaning that option is not even presented without multiple monitors being active. I see it now that I set the external display active again.
[10:28] <lighterowl> oooooooooooooh
[10:29] <lighterowl> had no idea it was dynamic. I have my 3 monitors connected almost all the time at work. :P
[10:36] <astraljava> Yeah, I will jump quite frequently between only laptop to having at least one external setups. Now I shouldn't have much problems as I could set panels constantly staying on the laptop's screen. Thanks!
[10:37] <lighterowl> :)
[12:39] <kathy> can somebody help a noobish person? I accidentaly chose a wrong setting for my screen, and now all i get, once I've logged in to my user, is a black screen with a dancing "input not support".
[12:40] <gnrp> kathy: Did you just create a new account or is there data on it?
[12:41] <gnrp> I mean, the easiest thing might be to delete all the user data and create a new one...
[12:41] <gnrp> otherwise, where did you change the screen setting?
[12:41] <diogenes_> or not to delete anything just make a new user.
[12:41] <kathy> I've been using it for quite a while. I know I could rescue most of the data, but not the most recent bookmarks etc.
[12:42] <kathy> I changed it in "Settings" "monitor" on the menu
[12:43] <gnrp> diogenes_: Or that. But then the username is already taken
[12:44] <kathy> I could always choose a nickname, of course - but that wouldn't rescue my latest data :(
[12:44] <diogenes_> kathy, it's easy to transfer data from one account to another one.
[12:44] <gnrp> kathy: (maybe wait for somebody more competent to reply, like diogenes_, but what I would do): Log in as administrator, then go into the home directory of your old account
[12:45] <gnrp> and then move the .local, .cache and .config files away (e.g. renaming them in local, cache and config)
[12:45] <kathy> Never done that before - how does that work?
[12:45] <diogenes_> kathy, alt+ctrl+f1
[12:45] <gnrp> and then you log in with your regular user and step-by-step copy the data from these directories back to the real .local, .cache and .config. You start with the obvious ones (like the chrome directory does not contain the screen settings pretty sure)
[12:47] <gnrp> but there might be somebody who can tell you which file contains exactly the setting you want
[12:48] <kathy11> Sorry everybody, noobish person made anoobish mistake ;)
[12:48] <gnrp> `grep` tells me that it might be the .config/xfce4/xfconf/xfce-perchannel-xml/displays.xml file. So maybe try moving that file away first and then try logging in, otherwise go on as I said
[12:48] <gnrp> kathy11: What was it?^^
[12:51] <kathy11> gnrp: sorry, locked myself accidentally out, missed a bunch of your explanation. You lost me after the "ctrl-alt-f1" bit
[12:51] <kathy11> and yes, freenode changed my name too
[12:52] <gnrp> ah, ok
[12:53] <gnrp> 13:45 <gnrp> and then you log in with your regular user and step-by-step copy the data from these directories back to the real .local, .cache and .config. You start with the obvious ones (like the chrome directory does not contain the screen settings pretty sure)
[12:53] <gnrp> 13:47 <gnrp> but there might be somebody who can tell you which file contains exactly the setting you want
[12:53] <gnrp> 13:48 <gnrp> `grep` tells me that it might be the .config/xfce4/xfconf/xfce-perchannel-xml/displays.xml file. So maybe try moving that file away first and then try logging in, otherwise go on as I said
[12:53] <gnrp> ah, no, you were in there already
[12:54] <gnrp> you should also be able to start a guest session, then open a terminal, type `su kathy` (or replace kathy by whatever your username is on your system). Then you enter the password of your user
[12:54] <gnrp> and then you type `thunar` and a file explorer with the permission of your user should open, and you can manipulate files
[12:56] <kathy11> ok thanks, I'll try that!(y)
[12:57] <gnrp> and as I said, I would try first moving away tgh e.config/xfce4/xfconf/xfce-perchannel-xml/displays.xml file and then log in with your regular user again
[13:01] <kathy11> ok, I'll try that first. Bye for now.
[13:36] <lighterowl> huh
[13:36] <lighterowl> she's been gone for a long time.
[13:42] <gnrp> lighterowl: Hmmmm...
[13:42] <lighterowl> yeah.
[13:42] <lighterowl> are you thinking what I'm thinking
[16:47] <st-gourichon-fid> Hi. In Xubuntu 18.04 I attach custom keyboard shortcuts to "multimedia" keys and they work.  In Xubuntu 19.10 I can define some, but pressing them has no effect.  Is it a known fact?
[16:50] <st-gourichon-fid> (On an unrelated note, I observe from time to time that window decorations disappear then reappear but windows get shifted bottom right a little.  I guess xfwm4 crashed and was relaunched.)
[17:13] <lighterowl> st-gourichon-fid: is that global or specific to a particular application? if you launch xev, does the window receive the proper keyboard events?
[17:40] <st-gourichon-fid> Keys work in applications, only shortcut keys are ignored.
[17:42] <st-gourichon-fid> Oh, yes, it's not a matter of "my media keys don't work".  Most things works very well, I isolated the issue being: xfce4-keyboard-settings allows to attach shortcut to media keys (e.g. XF86AudioPlayPause) but pressing them has no result.  Regular keys work (both tested with "xmessage foo").
[17:44] <st-gourichon-fid> Correlating xfsettingsd activity (observed using strace) with keyboard activity (regular shortcut and media keys shortcut) suggests that xfsettingsd does *not* receive media keys events.
[17:45] <lighterowl> huh.
[17:46] <st-gourichon-fid> When I say "keys work in applications", more precisely: gmusicbrowser with MPrisv2 plugins receives and processes media keys: I can start/stop music go to previous/next with the keys.
[17:48] <st-gourichon-fid> Testing with xev... with normal keys, xev receives KeyPress KeyRelease events. With media keys, xev receives FocusOut FocusIn KeymapNotify events.
[17:48] <brainwash> st-gourichon-fid: maybe something to do with the pulseaudio panel plugin?
[17:49] <brainwash> st-gourichon-fid: that one maps multimedia keys
[17:49] <st-gourichon-fid> Volume up/down also work out-of-the-box. xfsettingsd does not receives them, but they trigger correct volume change and visible notification.
[17:50] <st-gourichon-fid> brainwash: okay I check that.
[17:50] <st-gourichon-fid> I guess you mean /usr/lib/x86_64-linux-gnu/xfce4/panel/plugins/libpulseaudio-plugin.so
[17:50] <st-gourichon-fid> Yes that process receives volums events.
[17:51] <st-gourichon-fid> It reacts to PlayPause and other music-related events, though with less activity.
[17:52] <st-gourichon-fid> So, I guess libpulseaudio-plugin.so captures media keys in 19.10, preventing xfsettingsd to process them. In 18.04 xfsettingsd could process them.
[17:53] <st-gourichon-fid> Thanks lighterowl brainwash for hints.  Not yet fixed, but this helps.
[17:54] <st-gourichon-fid>  /usr/share/doc/xfce4-pulseaudio-plugin/README says " It can optionally handle multimedia keys for controlling the audio volume."
[17:54] <st-gourichon-fid> But it should probably not grab other media keys.  That might be the bug.
[17:54] <brainwash> I suggest checking the Xfce bug tracker
[17:54] <brainwash> and open a new report if needed
[17:55] <st-gourichon-fid> brainwash, will do that (not right now) -- am in Paris, have to go to the commuter's train for fear of not being able to join home tonight because of strike affecting transportation...
[17:56] <st-gourichon-fid> Summary: since xfce4-keyboard-settings *allows* to defines key shortcuts using media keys (interactively) but these shortcut do not *actually* work, there is definitely a bug.
[17:58] <st-gourichon-fid> Hmm, not sure what to type to filter. https://bugzilla.xfce.org/buglist.cgi?quicksearch=xfce4-pulseaudio-plugin&list_id=53398 too broad. https://bugzilla.xfce.org/buglist.cgi?quicksearch=shortcut%20media%20keys&list_id=53400 only one irrelevant answer.
[17:58] <st-gourichon-fid> I might be more productive digging into source.
[18:01] <brainwash> st-gourichon-fid: maybe this https://bugzilla.xfce.org/show_bug.cgi?id=12334
[18:02] <st-gourichon-fid> Found  https://github.com/xfce-mirror/xfce4-pulseaudio-plugin/blob/cbb5acc2085dc82f32ba45244f5d799321806718/panel-plugin/pulseaudio-plugin.c#L512 and following
[18:03] <st-gourichon-fid> brainwash, interesting. I'll try removing xfce4-pulseaudio-plugin and using xfce4-volumed-pulse instead.
[18:04] <brainwash> st-gourichon-fid: that report is from 2015 though
[18:05] <st-gourichon-fid> Well, it works.
[18:06] <st-gourichon-fid> But I lose the icon to see volume and change interactively in the tray.
[18:06] <brainwash> wasn't sure if xfce4-volumed-pulse is still packaged, but it is
[18:06] <st-gourichon-fid> There must be another way.
[18:07] <brainwash> it does not provide a panel indicator
[18:07] <brainwash> back then indicator-sound from ubuntu's Unity DE was used
[18:08] <st-gourichon-fid> There is now an option. The bug https://bugzilla.xfce.org/show_bug.cgi?id=12334 marked wontfix was fixed apparently.
[18:08] <st-gourichon-fid> See https://github.com/xfce-mirror/xfce4-pulseaudio-plugin/blob/cbb5acc2085dc82f32ba45244f5d799321806718/panel-plugin/pulseaudio-plugin.c#L393
[18:09] <st-gourichon-fid> I have to find the correct channel
[18:09] <st-gourichon-fid> for a xfconf-query line
[18:11] <st-gourichon-fid> Oh it can be set in the GUI.
[18:13] <st-gourichon-fid> Mmh not sure it's the correct one.
[18:13] <st-gourichon-fid> Anyway I have enough hints.
[18:13] <st-gourichon-fid> Will try to keep you informed.
[18:14] <st-gourichon-fid> There is still a bug: xfce4-keyboard-settings allows to define shortcut involving media keys, but they are ignored when libpulseaudio-plugin is active, and the innocent user does not know that.
[18:14] <st-gourichon-fid> So, the out-of-the-box behavior breaks the principle of least surprise.
[18:15] <st-gourichon-fid> And I doubt it's the job of xfce4-keyboard-settings to see if libpulseaudio-plugin is active as tell the user "warning, the shortcut you define will be ignored..." or things like that. :-/
[18:15] <st-gourichon-fid> Anyway, good evening.