[00:34] bluesabre, seems like not only Polish translation is affected, we now know more about this issue - https://bugs.launchpad.net/menulibre/+bug/1793406 [00:34] Launchpad bug 1793406 in MenuLibre "Cut off launcher name and description in Polish translation" [Undecided,Confirmed] [00:34] Russian is also affected === brainwash_ is now known as brainwash [10:04] bluesabre: do you think that bug 1550444 is a duplicate of bug 1374887? [10:04] bug 1550444 in parole (Ubuntu) "Parole media player segfaults when seeking forward in a video file" [High,Confirmed] https://launchpad.net/bugs/1550444 [10:04] bug 1374887 in parole (Ubuntu) "parole crashed with SIGSEGV in parole_provider_player_get_stream_position()" [Undecided,Fix released] https://launchpad.net/bugs/1374887 [10:05] 32bit etc. [12:45] ochosi: I think that the fix for https://github.com/shimmerproject/elementary-xfce/issues/71 needs to be done for the 16/22/24 variants also [12:45] otherwise the mono style icon is used in whiskermenu or the classic application menu [12:47] which is not correct, right? [12:51] fix works for 16 [12:52] I guess because there is no panel/16/blueman.png for -dark [12:53] but a panel/24/blueman.png still overrides a apps/24/blueman.png [12:53] same for 22 [12:56] this affects whiskermenu which shows 24px sized app icons in xubuntu [14:49] ochosi: the reason why I even looked into this -> https://i.imgur.com/GmMqRaz.png [14:51] not because of the mono style icon, but because of the lack of resizing [19:34] brainwash: about that font bug: it affects most of Xfce and the only reasonable fix involves convincing GNOME that they should add another parameter to a deprecated API in order to support third party desktops. in other words it's about as likely as convincing them to go back to gnome-panel. i don't know where to start with that. opening an xfce bug probably won't help :( [19:39] ali1234: and there is nothing that could be done via xubuntu-default-settings, right? [19:39] no, because the apps don't look at that [19:40] actually i can't remember... do you ship gnome settings? [19:41] gsettings? https://git.launchpad.net/xubuntu-default-settings/tree/debian/xubuntu-default-settings.gsettings-override [19:41] yes, i think so [19:42] so you could set /org/gnome/desktop/interface/monospace-font-name [19:42] to match whatever it is in xfconf [19:44] i'm not sure that aps will be able to see it though, unless gnome-settings-daemon is running as well [19:44] because apps that try to follow the gnome setting just make a dbus call [19:44] brainwash: i'm not sure in which contexts the "blueman" icon is actually used [19:44] if it's just for the application's desktop file/launcher, then ofc that's easily fixable [19:45] and yeah, i could amend the 16px version in -dark [19:45] but then again, i'd prefer to know the contexts beforehands [19:45] blueman.png for app launcher and (mono style) blueman.png for the tray icon in the panel [19:45] those two conflict [19:46] blueman icons is one of the two things i had to hack to get my desktop looking right (the other was battery icons) [19:47] actually with statusnotifier plugin you can switch to symbolic [19:47] so that problem should be mostly gone [19:47] (if you use that plugin, that is) [19:48] ok [19:48] i have never seen that checkbox do anything [19:48] your icon theme needs to support it [19:48] but panel/22/blueman.png and panel/24/blueman.png are still in -dark [19:48] as elementary-xfce supplies a "blueman-symbolic" icon it has an effect [19:48] you would need to remove those [19:48] yes, because so far we haven't had a single release with the symbolic feature [19:48] ah! [19:49] well, 18.10 will be the first, correct? [19:49] yup [19:49] cool [19:49] and until the next LTS we have some time to figure this out ;) [19:50] having that 16px version in -dark would help already [19:50] yeah, with certain menus it would [19:50] but with small panels it wouldn't :/ [19:50] small as in 16px? [19:51] small as in <22px or so [19:52] i don't remember when the panel switches to 16px anymore [19:52] but there is a scaling logic i added so the "best" icon size is chosen [19:52] anyway, bbabl [19:52] cya [19:55] ali1234: would it be worth to test if overriding the monospace font via gsettings helps? [19:55] i just looked it up and it does help - i have a workaround in my dotfiles [19:56] ohh nice [19:56] the issue is that if user changes the xfce setting, then the gnome one won't match [19:56] i'm not sure if they match by default, but if not they should [19:56] not much can be done about that [19:56] https://github.com/ali1234/dotfiles/blob/bd661f14e2ff27a7e648ad1b43e69204241e45e0/install.sh#L44 [19:57] just running that command on a default xfce install is enough to override the setting in gnome apps that use it [19:58] i have to have 9.5 pt font because of the weird font rendering in 18.04 :( [19:58] I assume that hacking that command into xfce4-settings won't be accepted, or? [19:58] dconf write [19:59] it might do but the issue is it's supposed to be desktop private [19:59] this is where that deprecated API comes into play [20:00] the desktop reads its private settings and turns them into xsettings and sends those to the app. that's cross desktop. but there is only an xsetting for "font" and not "monospace font" [20:02] but there are only two option left: a hack or doing nothing [20:03] well, making it at least match by default would be better than nothing [20:03] if it doesn't already [20:03] you don't seem to be in the mood to argue with the gnome devs :) [20:06] dconf read /org/gnome/desktop/interface/monospace-font-name [20:06] returns nothing [20:07] it wont if nothing has been set [20:07] you have to do something else, i forget what it is [20:07] I expected a "default" value [20:07] it's probably just "monospace", but which size? [20:07] no, the defaults aren't shown by dconf - it only prints something if the user has set a custom value [20:08] if you install the dconf-editor you can see the defaults [20:08] Xfce reports "monospace regular 10" [20:09] yes i think that is the default [20:10] dconf-editor tells me it's "monospace 11" [20:11] ah yes, that's the default mismatch :) [20:12] from dconf manpage "This tool operates on dconf directly, without using gsettings schema information." and gsettings schema is where the default values are [20:14] okay. so, it should be set to "monospace 10" in the gsettings.override (xubuntu-default-settings)? [20:14] sounds about right. i don't know the technical details of how that stuff works [20:15] I'm just wondering if that would help [20:15] even if it works [20:15] 10 vs 11 [20:16] its very noticable (especially if you set xfce to 9.5 so that fonts are the same size as they were in 16.04) [20:17] that is only one use case though [20:20] ali1234: will you add gsettings.override suggestion to your report? [20:22] i already mentioned the defaults under 2. [20:31] ali1234: https://paste.ubuntu.com/p/ZG9w4CCZrf/ [21:01] ondondil: looking good re custom action shortcuts [21:06] ondondil: the unique IDs could be made a bit more meaningful, like "search-files-3" instead of "3-3" [21:06] maybe even without the -3 [21:07] but that's for bluesabre to decide [21:09] I think after all these changes in xubuntu-default-settings it will need some good testing [21:09] before 18.10 [21:18] I weren't sure what to put there so I just wrote those numbers [21:19] And I just noticed that someone forgot to edit description field here https://git.launchpad.net/xubuntu-default-settings/tree/etc/xdg/xdg-xubuntu/Thunar/uca.xml.in#n31 [22:17] ondondil: not quite [22:17] see https://git.xfce.org/xfce/thunar/tree/plugins/thunar-uca/uca.xml.in [22:17] it is just an example uca [22:22] xubuntu's uca.xml.in is missing https://git.xfce.org/xfce/thunar/commit/plugins/thunar-uca/uca.xml.in?id=be7c64b6ece15d96b16f3ca097070195ebe5629d