[00:00] Agreed. [14:41] Eickmeyer: The qjackctl systray/notifier item is messed up again. The icon doesn't display, and the menu either... [14:41] How did that happen?!? [14:42] I guess we need to add more of it's functionality to controls [14:42] I would guess either Rui has changed something or xfce has. [14:42] ... or the lib that both rely on has [14:43] Strange. I don't see any problems on my end. Did you remember to select "enable system tray icon"? [14:44] https://i.imgur.com/CEu7Zm5.png [14:44] That triangle is qjackctl [14:45] I don't see that here. Can't reproduce. I have the standard qjackctl icon. [14:45] this is 19.10 BTW [14:45] Same. [14:46] hm. I didn't change the icon theme [14:46] I literally just tried it myself without issue. You /might/ have to go into qt5ct and select an icon theme. [14:46] (it might not be selected) [14:47] If that's the case, I'll fix the defaults file. [14:48] That didn't change anything and besides the menu doesn't work either [14:49] Yeah, then there's something weird on your end. I can't reproduce. [14:50] maybe after a reboot... [14:53] The system I'm on is a fresh install. [14:53] This too [14:55] Yuck, something new... some of the icons fade to BG colour if they have no mouse over. [14:55] Again, that's weird. I can't reproduce that. [14:56] So I set up a second panel (on right display) and add items. Some of them can't be seen till I mouse over then they show. [14:57] I thought maybe they went dark so I changed the panel BG colour... but no they fade [14:57] I do know xfce4-pulseaudio-plugin has a strange bug where it won't show the proper volume level until you mouseover it, but I can't see any issues on the other side. [14:57] Try adding "Directory menu" to your panel. [14:59] The audio indicator? it seems fine here. The mute or on off button to the side of the level control is... ugly or out of place or something [15:01] Ok, for the directory menu, I can see the problem with the dark icon, but once the menu is open no issues whatsoever. That's just a side-effect of having a dark panel with that icon theme. THe indicator icons have zero issues. [15:01] Not ideal, but there's nothing we can do about it. [15:02] I know it is a design choice, but really, I need to see the icon before I get to it not after... how else do I know where it is? [15:03] Can probably file a bug against the papirus icon theme. [15:03] It is not just dark, I tried making the panel background a light grey and the icon is still just as hard to see. [15:04] Oh hey, that sweird... problem solved [15:04] O_o [15:04] * Eickmeyer blames xfce 4.14 now. [15:04] when I changed the background back to None (use system theme) the problem went away [15:05] ¯\_(ツ)_/¯ [15:06] I can see my icons now. [15:06] \o/ [15:06] reboot to see if qjackctl behaves nicer [15:09] Hmm, the qjackctl icon is right, but it still has no left click menu [15:09] Yeah, I can't reproduce that. Very odd. [15:15] re lsp plugins - lsp-plugins-ladspa.so gives undefines symbol [15:16] There are a whole pile of vst errors too. [15:17] That's reallly weird. I can't reproduce that. [15:18] https://paste.ubuntu.com/p/tFDGxRBqbR/ [15:18] basically that is what showed up in Ardour in the plugin scan [15:19] Again, very odd. I'm not seeing that at all. [15:20] I've used Ardour and lsp-plugins several times over the past few days. [15:21] It only scans plugins if you ask it to. there are no errors on sedcond start (they are probably already blacklisted :) [15:23] Ok, looking at that those plugins aren't meant to be run outside of a plugin host or the standalone clients. [15:23] So, expected. [15:23] the carla rack does show up inside so that is ok. [15:24] Yes, as it should. [15:25] My clue is that not every LSP plugin was having difficulty in your log. Just the select few. I mean, it's about 90 plugins in total. [15:26] Ya, but none of the ladspa versions show up at all in the plugin selector. [15:26] Screw the ladspa versions. Am I right? [15:26] Those are just there for lmms as far as I'm concerned. [15:26] jsut want to see if they work in lmms [15:26] ok [15:28] I see no lsp plugins in lmms [15:29] no errors either [15:29] Hmmmm..... [15:29] I'd bug report that to the developer. I worked with him on the packaging, and it doesn't build outside of any defaults. [15:30] I can't check to reproduce right now, though. [15:30] can you run qtracktor? [15:31] I have blank menus [15:35] qtracktor runs fine, no blank menus. [15:35] I am going to remove and reinstall it. [15:35] it sounds like the same problem as for qjackctl [15:36] Yeah. Seems like the qt problems I was having (the reason I included qt5ct was to circumvent these problems). [15:37] kdenlive is fine [15:38] kdenlive uses the KDE Frameworks, so not much surprise there. [15:38] reinstalling qtracktor does not grab any extra libs... [15:39] still bad. It is like the items are there but I can't see them. [15:39] Did you run qt5ct? [15:40] I'm just curious. [15:40] I did... but I did not make any changes [15:40] Ok, try to make a change and see what it does. [15:41] I can see menus [15:41] Oh I can hear myself type too... (just added a qtracktor track [15:42] Ok, so that tells me qt5ct is the problem. *sigh* [15:42] Might be something I need to work on in the seed. [15:42] still no menu for qjcakctl indicator. [15:42] And -default-settings. [15:42] Xfce might have to be restarted (or qjackctl) to get the menu for that. [15:43] qt5ct doesn't make changes to running apps, unfortunately. [15:43] I started qjackctl after and the change did show up in the running qtractor [15:47] Ok, that tells me theres things that still need to be tweaked. I'll try to fix that today. Could you do a bug report against ubuntustudio-default-settings and add ubuntustudio-meta to it? Just do it from https://launchpad.net/ubuntu/+source/ubuntustudio-default-settings [15:48] I might be removing qt5ct from the seed. [15:48] I changed the theme from windows to Fusion [15:49] Default theme for qt5ct should be gtk2. [15:49] style sorry [15:49] The style, I mean. [15:49] There are only two styles: windows and fusion [15:51] Make sure that qt5-style-plugins is installed (maybe I omitted that from the seed). [15:51] not there [15:52] Ok, there's the bug. File the bug against meta then, it's not a default-settings issue. I know what needs to be done. [15:52] https://launchpad.net/ubuntu/+source/ubuntustudio-meta [15:52] I forgot to include that package. [15:53] Much easier bug to fix than -default-settings. [15:54] What should I label the bug? [15:56] https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1845857 [15:56] Launchpad bug 1845857 in ubuntustudio-meta (Ubuntu) "qt5-style-plugins is missing" [Undecided,New] [15:56] That works. [15:56] I'll fix later today. [15:59] whenever [16:04] there is still no alsa-tools icon [16:05] That's a known bug in hicolor, I thought. [16:06] could be, but we could either add our own icon or... file a bug with the right package ... and maybe supply an icon. [16:07] alsa-tools should include the icon [16:08] Agreed, but it doesn't. Having our own icon would work too. [16:08] huh, alsa tools does not supply the desktop files either [16:08] Where do those come from? [16:09] cd /usr/share/Applications [16:10] oops... wrong window [16:10] Yes I remember now. they changed the icons [16:10] Ah. [16:11] but did not change the desktop files to match. [16:11] dpkg -S tells you which package provided a particular file. [16:11] alsa-tools-gui [16:11] Ok, so they didn't fix that bug. [16:12] I am not sure where upstream would be for that [16:12] but it probably wasn't fixed because upstream hasn't [16:19] we could add one anyway... It seems to me it ends up being used as sort of a default for other packages as well [16:20] Hmmm.... should the icon go in -icon-theme or -menu? [16:22] we added /usr/share/pixmaps/ffado.xpm at some point. I think it could be removed [16:22] ffado mixer has it's own icon now [16:23] OK, we could remove that. [16:24] If we want this to change before 19.10 final, we need bug reports, though. [16:25] that file doesnt have to be removed right now. but adding alsa-tools would be good which package do we want to bug? [16:25] -menu would make sense [16:25] (to me) [16:26] we don't install -menu :) [16:26] where did we move that to? [16:27] Uh... we do install menu. I have it installed right now. [16:27] sudo apt search ubuntustudio-menu shows it installed. [16:28] Go ahead and file it against -menu. It probably just needs a symlink. [16:28] To the alsa-tools ico. [16:29] *icon [16:37] there is no alsa-tools icon but that could be a symlink to almost any utility icon emblem-system for example. [16:39] like a setup icon [16:39] I'll see what I can find. [16:46] preferences-activities, utilities-tweak-tool I am not sure which packages these came from but there shouold be a generic setup icon that would work that comes with the basic icon set all ubuntu flavours use [16:50] the hicolor package only installs directories :P [16:55] I'm notiing a lot of it comes from the elementary icon themes. There should be more, though. [16:55] I'll keep investigating. [19:45] OvenWerks: I just pushed and uploaded a fix for the icons and for the missing qt5-style-plugins. Awaiting release team approval since we're after beta freeze. [19:45] I don't see why they wouldn't approve it [19:46] Especially considering the bug fixes. [19:49] Eickmeyer: ok [19:50] Normally nothing is said about any tweaks to flavour packages... [19:51] But something that keeps menu from showing is a hard bug anyway. [19:52] Exactly. I honestly can't believe I omitted that package from the seed. [19:53] I also have a FFe/Sync Request for obs-studio which is a version newer in Sid, surprisingly. [19:54] Vorlon had already mentioned it was a sensible request, so it'll probably get the green light. [19:54] cool [20:07] there has been another spin... [20:08] Yeah, but this stuff isn't going to land in it. [20:09] It has to be approved by the release team. [20:20] I know [20:20] might be other stuff [20:29] Eickmeyer: if you see drmacro on line, I would like to take to him. I have some more ideas (did some more reading) [20:30] OvenWerks: Ok, I'll keep an eye out. [20:39] OvenWerks: Unrelated, new systemd dropped and broke Ubiquity: bug 184573 [20:39] bug 184573 in nautilus (Ubuntu) "nautilus crashed with SIGSEGV" [Medium,Invalid] https://launchpad.net/bugs/184573 [20:39] Oops, wrong bug. [20:39] * OvenWerks gave up on Nautilus long ago. [20:40] OvenWerks: bug 1845730 [20:40] bug 1845730 in ubiquity (Ubuntu) "ubiquity crashed with FileNotFoundError in _execute_child(): [Errno 2] No such file or directory: '/sbin/udevadm': '/sbin/udevadm'" [Critical,Confirmed] https://launchpad.net/bugs/1845730 [20:40] I accidentally a digit. [20:40] systemd... does that mean we need to check if we still have memlock? [20:41] No, that bug is fixed and not likely to regress. [20:41] I guess we should check that anyway [20:41] Basically, the Ubiquity installer is broken. So, new images won't install until that bug is fixed. [20:41] ok [20:42] we had two people do upgrades from 19.04 to 19.10 that failed BTW [20:42] Yeah, not sure why. [20:43] I am wondering if ubuntustudio-backports was enabled [20:43] and if that could cause it [20:43] That's a possiblity, in which case ppa-purge needs to be used to get rid of it and downgrade the packages to the repo version. [20:44] That's what I had to do. I successfully upgraded an install with it. [20:44] but only after ppa-purge. [20:46] might be worthwhile having a wiki page to point to for upgrades with a step by step [20:47] It's already in the Backports PPA release notes as well as the PPA page itself. [20:47] !ubuntustudio-backports [20:47] The Ubuntu Studio Backports PPA is required for users of Ubuntu Studio to receive LTS support for Ubuntu Studio 18.04, and for #ubuntustudio to support users of Ubuntu 18.04 LTS and its flavors using !jack. For more info, see https://help.ubuntu.com/community/UbuntuStudio/BackportsPPA, !ubuntustudio-controls, and !ubuntustudio-installer [20:47] I can also add it to the release notes. [20:48] when doing an upgrade I would be looking for documentation on upgrading rather than PPAs [20:50] Then it'll be in the release notes. That said, because it's beta, they are already warned that there are likely to be issues. [20:51] :)