[03:27] hey guys, when i install some snap like... sudo snap install wavebox [03:27] wavebox does not appear in the apps menus [03:28] or gnome apps [03:35] snap apps dont appear in gnome apps with wayland [08:03] reading alot of mouse lag bugs on gnome/wayland both ubuntu and fedora [08:03] https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1718653 [08:03] Launchpad bug 1718653 in gnome-shell (Ubuntu) "Windows buttons gone on specific programs" [Undecided,Confirmed] [08:04] lets hope that gets solved in final [08:15] How do I show the top panel on both screens when using a laptop and an additional display? In the moment it is shown on the notebook only. [08:17] eh, I test 17.10beta with gnome [08:22] passt: does screen settings show both screens? [08:23] passt: only have 1 screen here, but cant find any settings there [08:29] yes, both screens are shown in the display settings and I don't mirror the screen [08:30] passt: how about the Fn + F(screen) key does that do something usefull when switch? [08:39] I don't understand what you want me to do? [09:36] problem is solved. After I setup the external screen as the only screen and then set it back to expand desktop to each screen, the external screen kept the top panel. [10:32] Virtualbox seamless mode doesn't work as expected. When I switch to seamless mode with win7 as the guest and maximize a window, the window isn't shown fully maximized. The window of the program covers the size of the area which it had before I started to maximize it. [10:32] Does anybody know this behaviour in ubuntu with virtualbox before or is it a bug in the beta version? [10:33] Btw when I resize the program window with the mouse, It is shown correctly. [15:25] hi! how do i get a wayland session in artful? in both virtualbox and on a laptop with some radeon 5xxx igp i can't select it on the login screen === ghostcube_ is now known as ghostcube [16:25] hey guys, can anyone help me understanding what's causing my fresh install to hang/freeze when I try to shut it down or restart? I've enabled the debug shell as per a recommendation on stack overflow and extracted my dmesg before the last REISUB. http://termbin.com/8lf0 [16:28] dchotas: looks like a fault in the wifi kernel driver [16:29] I've looked around for drivers for this specific wireless card and up untill fairly recently, it wasn't supported natively and I've seen some thread on stack overflow where people download backports for 4.4 and compile just the ath10k driver. [16:29] dchotas: starting at 46.333111 looks like there's some problem with the pcie bus/hardware comms [16:29] But the driver is supported now [16:29] the card, I mean [16:29] [ 29.852463] pcieport 0000:00:1c.5: AER: Multiple Corrected error received: id=00e5 [16:30] TJ-: I not so strong in driver/firmware related issues, what would be a good place to start? [16:32] the card is a Qualcomm Atheros QCA9377 [16:33] dchotas: it could be caused by problems in the Mobo firmware. I see you've got kernel commandline "acpi=force" - that is very unusual and if needed points to a problem [16:33] dchotas: why is that needed? [16:34] I just blindly follower a stack overflow thread when I was searching for 'ubuntu restart/shutdown hanging' without specifying the underlying issue [16:34] I'll remove that, thanks for the reminder [16:35] dchotas: also at the start I notice the MTRR couldn't build an optimum set. [16:35] I could give this a try [16:35] although I'd had to figure out to to compile it for my specific card and put it in the right place [16:35] https://github.com/kvalo/ath10k-firmware [16:36] s/had/have [16:36] dchotas: you might try with "noaer" instead for those, but I'm not clear if they're related to the driver bugs later [16:39] dchotas: does it happen if you prevent the Wifi from associating? [16:39] You mean not letting the card connect to any network? [16:41] I'll try that, brb. [16:45] dchotas: looks like it's something to do with hardware-offload of the TX A-MPDU aggregation. So could be the firmware on the device. any later firmwares available? See https://www.kernel.org/doc/html/latest/driver-api/80211/mac80211-advanced.html#tx-a-mpdu-aggregation [16:49] TJ-: Simply trying to disable Wifi while it is connect will cause the settings UI to crash and force close. Also after restarting with airplane mode `on` the freeze didn't happen. [16:49] dchotas: which does seem to confirm it [16:51] dchotas: I'd first try to find a newer wifi firmware because it seems to be a firmware issue, in that the ath10k_pci driver asks it to stop the ba session and will callback to the kernel's 80211 syb-system when the firmware says done. But what is happening is the callback never happens so the kernel gets stuck and you see those stack traces for the stuck threads [16:51] Sorry, got logged out for some reason, might've missed somethign you said. [16:52] Hmm, I should probably give the firmwares on that ath10k repo a spin. [16:52] Can I just backup the existing .bin file and dump the other one in it's place? [16:53] dchotas_: that crash may be fixed in gnome-control-center 1:3.26.1-0ubuntu1 which should be in updates sometime today [16:53] jbicha: thanks for the heasds up! === dchotas_ is now known as dchotas [17:05] TJ-: Apparently the files on that github as exactly the same as the ones I have in /lib/ [17:06] dchotas: might be worth filing a bug on kernel bugzilla