[09:49] Hello. I had a problem in 17.04 and now that I reinstalled 17.10 the problem came back again, and I don't remember how I had solved it previously [09:50] My dns gets slow, seems like more specifically in apt [09:50] when using italian sources [09:50] the browser is fine, websites load instantly, but apt stays there for 30 seconds at 0% before starting. [09:50] I seem to recall it was a DNS problem but I'm actually unsure. [09:58] well, it's not the DNS at least ping works fine === vincenzo is now known as vincenzoml === JanC is now known as Guest66311 === JanC_ is now known as JanC === lotuspsychje_ is now known as lotuspsychje [18:32] hey! my indicators are not showing even though the extension is installed and running. any ideas? thanks! [18:35] Soul_Sample: got the same thing here [18:35] Soul_Sample: think its being worked on still [18:36] a lot of issues with extensions. i upgraded from 17.04 gnome and everything worked well there, now I can't enable half of the extensions and tracker absolutely kills my system on every reboot for a couple of minutes even though everything is indexed [18:36] Soul_Sample: both indicators & dash to dock show in gnome-tweak-tool enabled here [18:36] lotuspsychje: did you notice there is a SECOND extension tweaker? [18:37] Soul_Sample: did you upgrade to 17.10 or clean install? [18:37] it was an upgrade [18:37] Soul_Sample: its not recommended to upgrade yet [18:37] Soul_Sample: still in development [18:37] well yeah, but I figured if something breaks I'll reinstall. I don't want to reinstall for one extension on/off switch &/()= [18:38] Soul_Sample: knotifier indicators addon is what you talk about right? [18:38] this installation went through so much that I'm kind of surprised it still works. Yeah, knotifier, but I also tried topicons, no luck [18:39] Soul_Sample: thats the fork their working on, so i guess we have to be patient in this stage [18:39] i'm okay with that. just wanted to check if there's some quick fix [18:39] everything I run is in development, I live on the edge :D [18:40] but I will probably reinstall for 18.04, it's way overdue [18:40] i found 17.10 clean very stable myself already [18:40] im gonna help bug out intil 18.04 [18:41] I actually have to move to a clean home folder, there's hundreds of redundant files everywhere. I installed this as 16.04 unity, upgraded it to kde neon, downgraded back to 16.04, upgraded to 16.10>17.04 mate, back to unity, switched to gnome, upgraded to 17.10. and IT STILL BOOTS [18:42] Soul_Sample: you could dig around dconf-editor perhaps, thats where i found dash to dock tweaks [18:42] Soul_Sample: thats asking for issues lol [18:42] ubuntu Dock doesn't show up at all, but luckily Dash to dock worked as soon as I reinstalled it [18:43] It's actually impressive, 8.10 fell apart for every little thing, driver update, random upgrade, wrong version of a conf file. Feels like it's invincible now [18:44] I remember spending whole nights trying to type out xorg.conf manually to make my second display work [18:44] and then drivers would update and overwrite the xorg.conf :D [18:44] for proper helping 17.10 i would recommend clean install [18:45] you never know what old leftovers can confuse system [18:45] also not very helpful to add a !bug this way [18:45] well you have the exact same issue and yours was a clean install! [18:47] and i have placed some bus to help out [18:47] *bugs [19:26] :https://bugs.launchpad.net/ubuntu/artful . Should I raise them there? [19:26] 20:24 < alias_neo> I find it hard to believe they haven't been raised so is there somewhe [19:26] well that didn't work [19:27] alias_neo: explain the whole story please? [19:27] So I'm running Arty on my new Ryzen build because it's got a late enough kernel that I can even boot. [19:27] I installed the nightly from 4 or 5 nights ago [19:27] okay and your issue is? [19:28] I apt update a couple of times a day, and I have a couple of issues; [19:28] alias_neo: can you hastebin them to channel? [19:28] I'm not sure what you mean? You want me to write up the issue in a hastebin? [19:29] no, the putput of errors of apt update [19:29] output [19:29] there's no errors in apt update [19:29] the reference to apt update was meaning that I keep it up to date, apologies [19:29] (and apt upgrade too of course) [19:29] ok whats your couple of issues? [19:30] alias_neo: you should be using full-upgrade, mot just upgrade [19:30] So, the first is that I set scale to 200% because I'm on a 4K monitor, after a reboot the shell is unscaled and I have to go into display, click 100% and apply, and then it goes back to 200% and scales. [19:31] ducasse: Thanks, I was not aware [19:31] The second issue is that if my machine sleeps, I come back to a broken lock screen with a white background, and if I log in all my windows are gone. [19:31] by sleep I mean screen-off, not suspend [19:32] bug 1717272 [19:32] bug 1717272 in gnome-control-center (Ubuntu) "HiDPI settings reset on logout" [Undecided,New] https://launchpad.net/bugs/1717272 [19:32] Hmm, is search case sensitive? Because I searched several variations on "hi-dpi" and "scaling" [19:33] Ok, so that's one down, as it's already raised [19:33] it was opened 4 hours ago [19:33] nice find brainwash [19:34] What's the best way to add some weight to it? Simple click that it affects me? [19:34] is your second issue really triggered by turning off the screen? [19:35] I guess so alias_neo [19:35] not by turning it off, when it turns itself off [19:35] as in screen-off session locked, I forget the term for it [19:35] when I'm afk [19:35] did you try to manually lock the session? [19:36] No, I'll try now, one moment [19:37] I'm guessing that one just answered itself [19:37] not only is everything closed, my scaling reset itself back to 100% [19:38] the first issue was filed against gnome-control-center, and a new version is available in -proposed [19:40] Hmm, my ression just crashed and hte system rebooted [19:40] apologies if I missed any reponses [19:40] alias_neo: first issue was filed against gnome-control-center, and a new version is available in -proposed [19:41] there may be other gnome packages in -proposed also [19:41] Just enabling it as we speak [19:42] is there any harm in just installed all proposed updates? [19:42] hard to tell [19:43] I mean, what's the best way to keep track of updates to the pre-realease? [19:43] keep track? [19:43] Anyway, not to worry, I'm here to report bugs if needed [19:44] so the second issue, do we think it needs raising? [19:44] certainly it does [19:44] Ok, then I shall do so [19:45] please check the system log (journalctl) for hints [19:45] conversely, is there something I can do to indicate a bug appears to be fixed, a la the first one? [19:45] (assuming I reboot now and it proves to be fixed) [19:45] then you add a comment to the bug report [19:46] Great, then I'll reboot and see if the gnome-control-center update fixed the scaling and report that. [19:46] brb [19:46] ok [19:50] Ok, the gnome-control-center update does not appear to have resolved the issue [19:51] did you install any other gnome related updates? [19:51] I installed the "additional" and any others that started with gnome-* [19:52] ok [19:52] that's valuable information also [19:52] Where does it see which version this was supposedly fix in? [19:52] s/see/say/ [19:52] alias_neo: wich kernel are you on plz? [19:52] !info linux-image-generic [19:52] linux-image-generic (source: linux-meta): Generic Linux kernel image. In component main, is optional. Version 4.12.0.13.14 (artful), package size 2 kB, installed size 13 kB [19:53] lotuspsychje: 4.13.0-041300-generic [19:54] Installing linux-image-generic meta as we speak [19:54] I'm not sure it'll boot though, 4.13 is the only one I've had success with on this Ryzen machine [19:55] ah [19:56] I@m happy to try boot into it now it's installed [19:56] alias_neo: I mean you should add to the report that you've tested with gnome packages from -proposed also [19:56] that's valuable information [19:56] brainwash: Sure thing [19:57] the lock screen issue may be related to xorg vs wayland session [19:57] did you test with both? [19:58] brainwash: isnt that still worked on? [19:58] I don't have the session switcher on my login screen for some reason. I'm pretty sure though Xorg didn't work at all. I may have to test that if I recall incorrectly [19:58] brainwash: last time i checked, xorg was still default [19:59] I have no clue [19:59] running a minimal system since long [19:59] first i had xorg and Xwayland, then wayland dissapeared [19:59] think its still work in progress [19:59] How do I confirm which I'm on? [20:00] I assume the wayland option is hidden when a closed source gpu driver is used [20:00] Ah yes, I'm on Nvidia drivers [20:00] but on the other hand.. gnome did add support for the nvidia driver recently I think [20:01] this new tech :D [20:01] I've been quite happily running some ML/CUDA stuffo n the Nvidia driver here though. [20:02] well, either way you should check system and session logs [20:03] this will tell you why your session is closed unexpectedly [20:04] This any use: https://hastebin.com/yiboterebi.vbs ? [20:07] it probably is [20:08] lotuspsychje: What should I look out for if the kernel you suggested boots? [20:09] alias_neo: just wanted to know for info [20:09] ok [20:09] alias_neo: if you fill bug, mention kernel too ok [20:09] will do :d [20:10] just going to reboot and try that 4.12 kernel [20:10] in fact, let me grab another machine for irc, logging in with irssi every time is getting irksome, plus HiDPI works on the other machine running Xenial :D === alias_neo is now known as alias_neo_1 [20:11] alias_neo_1: maybe bug 1697882 [20:11] bug 1697882 in gdm "GDM should not allow X11 sessions when NVIDIA's KMS is enabled" [Medium,Incomplete] https://launchpad.net/bugs/1697882 [20:12] but it should be fixed anyway [20:13] hmm, my log suggests kms isn't enabled? [20:13] or am I misinterpreting it [20:15] that's true [20:15] catting that modeset module says N on my machine [20:16] let me turn it on and reboot and test [20:17] I would run "ubuntu-bug gdm3" to help filing a new bug report [20:18] at this point I'm a bit distracted [20:18] can't pay much attention right now [20:19] no problem [20:48] I switcihed to Wayland, that fixed the scaling bug, but the machine doesn't wake at all from locked session with Wayland [20:49] how do I get the log for this session since I'll have to forcefully power cycle the box? === brainwash_ is now known as brainwash [23:39] ‎ I'm recieving the error owncloud: relocation error: /opt/ownCloud/qt-5.6.2/lib/x86_64-linux-gnu/libQt5OpenGL.so.5: symbol _ZTV26QOpenGLSharedResourceGuard, version Qt_5_PRIVATE_API not defined in file libQt5Gui.so.5 with link time reference in Kubuntu. It is preventing the owncloud-client from running. Just happened with an update of Artful 17.10 today [23:40] Unfortunately I have no idea why and Google was no help. Other clients on other machines work fine.