[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
Please include at least this patch on the package. It allows setting Suspend as the action but does nothing if the user hasn't explicitly done that. ** Patch added: "Patch that keeps the defaults unchanged but allows the setting in the config file" https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1852911/+attachment/5463625/+files/upower-suspend-defaults-unchanged.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported Status in Upower: New Status in upower package in Ubuntu: Triaged Bug description: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1852911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
You may also want to consider just having Suspend be a fallback option before PowerOff. These days users are much more likely to have a laptop that suspends properly and prefer that to happen and just quickly grab a charger and continue instead of having their computer do a full poweroff. ** Patch added: "Patch to make Suspend a fallback option before PowerOff" https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1852911/+attachment/5463642/+files/upower-suspend.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported Status in Upower: New Status in upower package in Ubuntu: Triaged Bug description: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1852911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852911] [NEW] CriticalPowerAction=Suspend should be supported
Public bug reported: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported Status in upower package in Ubuntu: New Bug description: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1852911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
Upstream seems to be ignoring the user's wishes. Would Ubuntu be willing to take the patch? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported Status in Upower: Unknown Status in upower package in Ubuntu: Triaged Bug description: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1852911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
By the way the actual discussion seems to be this one: https://gitlab.freedesktop.org/upower/upower/issues/59 And this is the unmerged PR with the simple patch: https://gitlab.freedesktop.org/upower/upower/merge_requests/11 ** Bug watch added: gitlab.freedesktop.org/upower/upower/issues #59 https://gitlab.freedesktop.org/upower/upower/issues/59 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported Status in Upower: Unknown Status in upower package in Ubuntu: Triaged Bug description: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1852911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
I've once again lost my open session because upower has decided a shutdown is a sensible thing to do instead of just suspending and allowing me to just find a charger. Please consider this an actual bug and not just a "Wishlist" item. It's something that deeply frustrates users continuously. Orderly shutdowns are a relic of the past. Suspend or just dieing from lack of battery are both much better options for a laptop. That upstream has decided to force this behavior is unfortunate but the patches are simple enough. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported Status in Upower: New Status in upower package in Ubuntu: Triaged Bug description: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1852911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal
Hi Daniel. I can't even reproduce it in 18.04 anymore. I tried: - Booting 18.04.2 from a usb disk - The 18.04 GNOME Wayland session (what I'm trying now to avoid a bunch of other bugs) - The 18.04 default Ubuntu Xorg session all of them seem to be showing reasonable <1% gnome-shell CPU usage when showing just a gnome-terminal running top. Don't know what fixed it but it does seem fixed. I can live boot 18.10 if that's useful or even 19.04 if there are images for that already somewhere. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal Status in gnome-shell package in Ubuntu: Incomplete Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 220263]
I'm also using Ubuntu 18.04 but using the vanilla GNOME session (that uses Wayland) with the dark Adwaita theme selected. Could you please test with that to see if you get the same result? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/220263 Title: Bad Firefox integration with dark themes Status in Mozilla Firefox: Fix Released Status in XULRunner: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme. Now I see all the input boxes and buttons filled with grey colour. This happened even with Firefox 2, but I solved that problem with a quick guide under the comment "firefox fix" by Proton at the bottom of this page: http://www.gnome- look.org/content/show.php/Grey+Neu?content=60824 In Firefox 3 I can't correct this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/220263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 220263]
I have "Use System Colors" unchecked, `widget.content.gtk-theme- override` set to `Adwaita` and the Light theme selected. And yet even then the Ctrl-F input has white text over white background. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/220263 Title: Bad Firefox integration with dark themes Status in Mozilla Firefox: Fix Released Status in XULRunner: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme. Now I see all the input boxes and buttons filled with grey colour. This happened even with Firefox 2, but I solved that problem with a quick guide under the comment "firefox fix" by Proton at the bottom of this page: http://www.gnome- look.org/content/show.php/Grey+Neu?content=60824 In Firefox 3 I can't correct this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/220263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820743] [NEW] Pulseaudio is sometimes broken after resume from suspend
Public bug reported: Sometimes when resuming from suspend pulseaudio is broken and only the dummy output is available. After "pulseaudio -k" audio again works. Here's what I found in the logs: $ journalctl --since "1 day ago" | grep pulseaudio Mar 17 19:40:51 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 17 21:29:49 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 18 09:01:13 coulson pulseaudio[9869]: [alsa-sink-ALC293 Analog] alsa-sink.c: snd_pcm_mmap_begin: File descriptor in bad state Mar 18 09:06:25 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 18 09:32:40 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 18 09:47:36 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 18 18:16:42 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. --- Here I ran pulseaudio -k --- Mar 18 19:08:13 coulson pulseaudio[26606]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Mar 18 19:08:13 coulson pulseaudio[26612]: [pulseaudio] pid.c: Daemon already running. Mar 18 19:08:13 coulson pulseaudio[26614]: [pulseaudio] pid.c: Daemon already running. Mar 18 19:08:13 coulson pulseaudio[26616]: [pulseaudio] pid.c: Daemon already running. The "Failed to create sink input" seems to happen on every resume but only some times does it actually break. Don't know if the ofono message is related or not. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr 26606 F pulseaudio CurrentDesktop: GNOME Date: Mon Mar 18 19:11:09 2019 InstallationDate: Installed on 2018-05-31 (291 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1820743 Title: Pulseaudio is sometimes broken after resume from suspend Status in pulseaudio package in Ubuntu: New Bug description: Sometimes when resuming from suspend pulseaudio is broken and only the dummy output is available. After "pulseaudio -k" audio again works. Here's what I found in the logs: $ journalctl --since "1 day ago" | grep pulseaudio Mar 17 19:40:51 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 17 21:29:49 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 18 09:01:13 coulson pulseaudio[9869]: [alsa-sink-ALC293 Analog] alsa-sink.c: snd_pcm_mmap_begin: File descriptor in bad state Mar 18 09:06:25 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 18 09:32:40 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 18 09:47:36 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Mar 18 18:16:42 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. --- Here I ran pulseaudio -k --- Mar 18 19:08:13 coulson pulseaudio[26606]: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Mar 18 19:08:13 coulson pulseaudio[26612]: [pulseaudio] pid.c: Daemon already running. Mar 18 19:08:13 coulson pulseaudio[26614]: [pulseaudio] pid.c: Daemon already run
[Desktop-packages] [Bug 1866250] [NEW] nautilus crashes under wayland when trying to unmount an external drive
Public bug reported: I can 100% reliably crash nautilus when running under a sway session. The steps to reproduce it are simple: 1. Connect an external drive and mount it by browsing to it in nautilus 2. Open a terminal and cd into the drive mount 3. Press the unmount icon for the drive in nautilus At this point nautilus 100% reliably crashes. It will not crash if the drive is not being used. Looking at the backtrace it seems it is somehow trying to do X calls when running under wayland. Here's the trace: (gdb) bt #0 0x in () #1 0x77eb3393 in g_hash_table_lookup_node (hash_return=, key=0x60, hash_table=0x561e8000) at ../../../glib/ghash.c:473 #2 0x77eb3393 in g_hash_table_lookup (hash_table=0x561e8000, key=key@entry=0x60) at ../../../glib/ghash.c:1509 #3 0x776d35b8 in lookup_cached_xatom (atom=0x60, display=0x561b1040 [GdkWaylandDisplay]) at ../../../../../gdk/x11/gdkproperty-x11.c:76 #4 0x776d35b8 in lookup_cached_xatom (atom=0x60, display=0x561b1040 [GdkWaylandDisplay]) at ../../../../../gdk/x11/gdkproperty-x11.c:67 #5 0x776d35b8 in gdk_x11_atom_to_xatom_for_display (atom=0x60, display=0x561b1040 [GdkWaylandDisplay]) at ../../../../../gdk/x11/gdkproperty-x11.c:109 #6 0x776d35b8 in gdk_x11_atom_to_xatom_for_display (display=0x561b1040 [GdkWaylandDisplay], atom=0x60) at ../../../../../gdk/x11/gdkproperty-x11.c:96 #7 0x77b3fc8d in _gtk_mount_operation_lookup_context_get (display=0x561b1040 [GdkWaylandDisplay]) at ../../../../gtk/gtkmountoperation-x11.c:534 #8 0x779cf800 in update_process_list_store (processes=0x569ce670, list_store=, mount_operation=) at ../../../../gtk/gtkmountoperation.c:1286 #9 0x779cf800 in gtk_mount_operation_show_processes_do_gtk (choices=0x0, processes=0x569ce670, message=0x56930a90 "", op=) at ../../../../gtk/gtkmountoperation.c:1679 #10 0x779cf800 in gtk_mount_operation_show_processes (op=, message=message@entry=0x567dfac0 "Volume is busy\nOne or more applications are keeping the volume busy.", processes=processes@entry=0x569ce670, choices=choices@entry=0x56578420) at ../../../../gtk/gtkmountoperation.c:1704 #11 0x77329b5b in _g_cclosure_marshal_VOID__STRING_BOXED_BOXEDv (closure=0x569572e0, return_value=, instance=, args=, marshal_data=, n_params=, param_types=0x569e27f0) at ../../../gio/gmarshal-internal.c:2059 #12 0x7725c936 in _g_closure_invoke_va (closure=0x569572e0, return_value=0x0, instance=0x569d32d0, args=0x7fffd1f8, n_params=3, param_types=0x569e27f0) at ../../../gobject/gclosure.c:873 #13 0x7727936c in g_signal_emit_valist (instance=instance@entry=0x569d32d0, signal_id=signal_id@entry=566, detail=detail@entry=0, var_args=var_args@entry=0x7fffd1f8) at ../../../gobject/gsignal.c:3306 #14 0x77279fa9 in g_signal_emit_by_name (instance=0x569d32d0, detailed_signal=0x7fffdae3a1d2 "show-processes") at ../../../gobject/gsignal.c:3493 #15 0x7fffdae33fa8 in () at /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so #16 0x7fffdae385a8 in () at /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so #17 0x7616c81e in ffi_call_unix64 () at ../src/x86/unix64.S:76 #18 0x7616c1ef in ffi_call (cif=cif@entry=0x7fffd660, fn=fn@entry=0x7fffdae38530, rvalue=, avalue=avalue@entry=0x7fffd570) at ../src/x86/ffi64.c:525 Python Exception There is no member named v_pointer.: #22 0x772783ea in #23 0x7fffdae2d7e5 in () at /usr/lib/x86_64-linux-gnu/gio/modules/libgioremote-volume-monitor.so #27 0x772799b3 in (instance=instance@entry=0x562b6f70, signal_id=, detail=detail@entry=0) at ../../../gobject/gsignal.c:3453 #24 0x7725c6e2 in g_closure_invoke (closure=0x557441a0, return_value=0x0, n_param_values=4, param_values=0x7fffdbe0, invocation_hint=0x7fffdb60) at ../../../gobject/gclosure.c:810 #25 0x7726fcc6 in signal_emit_unlocked_R (node=node@entry=0x557441d0, detail=detail@entry=0, instance=instance@entry=0x562b6f70, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffdbe0) at ../../../gobject/gsignal.c:3679 #26 0x77279327 in g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7fffdde0) at ../../../gobject/gsignal.c:3397 #28 0x773bc638 in on_signal_received (connection=, sender_name=0x7fffe4014460 ":1.39", object_path=, interface_name=, signal_name=0x7fffe401b220 "MountOpShowProcesses", parameters=0x569d7670, user_data=0x55a52610) at ../../../gio/gdbusproxy.c:924 #29 0x773ab118 in emit_signal_instance_in_idle_cb (data=0x7fffe401fe60) at ../../../gio/gdbusconnection.c:3747 #30 0x77ec571e in g_main_dispatch (context=0x55745480) at ../../../glib/gmain.c:3
[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
I don't know what automation concluded that a fix was released but what happened instead is that upstream has once again refused to address this and just closed the bug reports. I suggest Ubuntu just ship the patch in its packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported Status in Upower: Fix Released Status in upower package in Ubuntu: Triaged Bug description: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1852911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
I've attached a patch already. I've been running for over a year now with no issues. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported Status in Upower: New Status in upower package in Ubuntu: Triaged Bug description: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1852911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
I've been running patched upower for a year and a half now. It has saved me in a few occasions. By far the most common scenario is that I've forgotten to plugin and it just suspends and I reconnect it and get going again. Shutdown is just useless, you still lose your work so might as well let the power fail completely. Ubuntu should just ship the patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported Status in Upower: New Status in upower package in Ubuntu: Triaged Bug description: The action to take when the battery is critical can only be one of the following: # Possible values are: # PowerOff # Hibernate # HybridSleep Adding Suspend to that list makes perfect sense. My laptop is currently powering off on low power which is useless as I'll be losing my work anyway. Might as well suspend and allow me to notice that and connect a charger. If the thinking is that suspend uses power I can set a high enough threshold to give me some margin. The failovers are: # If HybridSleep isn't available, Hibernate will be used # If Hibernate isn't available, PowerOff will be used I'd argue Suspend should actually come before PowerOff in that list. For most laptop users having their computer suspend because they didn't notice the battery was running out is very easy to fix and takes no time. They'll just connect the charger. If however the computer needs to be completely rebooted, not only does that take a lot more time it will very likely cause lost work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: upower 0.99.10-1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 17 14:32:13 2019 InstallationDate: Installed on 2019-05-09 (191 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1852911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573728] Re: Files opened with gedit on command line no longer open within the existing gedit session
Just moved to Ubuntu 18.04 and can confirm the issue and it does seem to be something related to the window manager. I can confirm this only happens with a maximized window and in 16.04 it would happen with gnome but not Unity. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1573728 Title: Files opened with gedit on command line no longer open within the existing gedit session Status in gedit package in Ubuntu: Confirmed Bug description: Prior to my update today to Ubuntu 16.04, I could open a file using gedit on the command line and it would open in the gedit window i already have open. After updating to 16.04 when I open a file with say `gedit /tmp/myleakycode.c` it opens in a new window. Oddly, as I was writing this bug report it's now working I expect it to, where opening files on the CLI adds to my existing session. I'll follow up if I find some pattern as to what triggers this. I am running Ubuntu Gnome 16.04 with the 4.4.0-21-generic kernel, gedit 3.18.3, terminator 0.98 to open the files. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 22 12:54:04 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1573728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573728] Re: Files opened with gedit on command line no longer open within the existing gedit session
It doesn't seem to be about maximization but about window location. If any part of the gedit window is against the screen edge or over it a new window opens. If the whole gedit window is fully within the screen and not against any borders it opens in the existing window. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1573728 Title: Files opened with gedit on command line no longer open within the existing gedit session Status in gedit package in Ubuntu: Confirmed Bug description: Prior to my update today to Ubuntu 16.04, I could open a file using gedit on the command line and it would open in the gedit window i already have open. After updating to 16.04 when I open a file with say `gedit /tmp/myleakycode.c` it opens in a new window. Oddly, as I was writing this bug report it's now working I expect it to, where opening files on the CLI adds to my existing session. I'll follow up if I find some pattern as to what triggers this. I am running Ubuntu Gnome 16.04 with the 4.4.0-21-generic kernel, gedit 3.18.3, terminator 0.98 to open the files. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 22 12:54:04 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1573728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1651685] Re: Highlight active tab
This is extremely annoying and still an issue with 18.04. I've tried fiddling with CSS settings bug can't get anything to apply to gedit for some reason. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1651685 Title: Highlight active tab Status in gedit package in Ubuntu: Confirmed Bug description: Currently, when multiple files are open in gedit, there is no way to tell which tab is active (other than the very hint of shadow around the tab). It is very difficult to see which one is active. Please see the attached image, it is very difficult to see which tab is active. gedit: 3.18.3-0ubuntu4 500 ubuntu: 16.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1651685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1651685] Re: Highlight active tab
Note that this is a problem specifically with Ambiance. With Adwaita the selected tab has a decent highlight -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1651685 Title: Highlight active tab Status in gedit package in Ubuntu: Confirmed Bug description: Currently, when multiple files are open in gedit, there is no way to tell which tab is active (other than the very hint of shadow around the tab). It is very difficult to see which one is active. Please see the attached image, it is very difficult to see which tab is active. gedit: 3.18.3-0ubuntu4 500 ubuntu: 16.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1651685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772192] [NEW] Missing setting to disable touchpad
Public bug reported: There is no longer an option to disable the touchpad. On Thinkpads with a Trackpoint and a Touchpad that's a common thing to do. 16.04 included this option and in 18.04 it is now missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 19 18:48:28 2018 InstallationDate: Installed on 2016-10-27 (568 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-05-19 (0 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1772192 Title: Missing setting to disable touchpad Status in gnome-control-center package in Ubuntu: New Bug description: There is no longer an option to disable the touchpad. On Thinkpads with a Trackpoint and a Touchpad that's a common thing to do. 16.04 included this option and in 18.04 it is now missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 19 18:48:28 2018 InstallationDate: Installed on 2016-10-27 (568 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-05-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1772192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752813] Re: Pointer speed is too slow even in the fastest setting
This is still an issue with 18.04. It's a little better because it now defaults to higher speeds in the driver. But even maxing out is too slow. I'm using: $ cat /etc/udev/rules.d/10-trackpoint.rules ACTION=="add|change", SUBSYSTEM=="input", ATTR{name}=="TPPS/2 IBM TrackPoint", ATTR{device/sensitivity}="250", ATTR{device/speed}="250", And even then it's too slow. This together with this new bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input- libinput/+bug/1772189 Makes the trackpoint experience in 18.04 on this laptop really bad still. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1752813 Title: Pointer speed is too slow even in the fastest setting Status in gnome-control-center package in Ubuntu: New Bug description: I use the trackpoint on my Lenovo T460s almost exclusively. Even in the fastest setting on a 2560x1440 screen it is much too slow. I've had to add the following udev rule to get it to be usable: ACTION=="add", SUBSYSTEM=="input", ATTR{name}=="TPPS/2 IBM TrackPoint", ATTR{device/sensitivity}="190", ATTR{device/speed}="220", ATTR{device/inertia}="6", ATTR{device/press_to_select}="0" And even with this and the speed in the control center set to maximum it is still a bit slow. Trying to push the sensitivity/speed settings higher will break the trackpoint and even with these settings it seems that sometimes on resume from sleep the trackpoint fails. After cycling suspend/resume again it comes back. There should be a way to set much higher speed settings for the mouse. Current settings make trackpoints very hard to use which even carries risk of hand/arm injuries. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-control-center 1:3.18.2-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 2 08:47:44 2018 InstallationDate: Installed on 2016-10-27 (490 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1752813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
To get the same effect in Ubuntu 18.04 as 16.04 I used the tweak tool to set a text scaling of 1.3. Additionally I had to set a scaling in Firefox's about:config in the layout.css.devPixelsPerPx property to the same 1.3 value. It's annoying that this has been removed from the normal UI as the underlying feature is still there and works fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling Status in Mutter: In Progress Status in Ubuntu GNOME: Triaged Status in gnome-shell package in Ubuntu: In Progress Bug description: https://trello.com/c/r12LY9iA (for 17.04 was https://trello.com/c/TvwNvXOo) --- I'm using fully updated Ubuntu GNOME 17.04. In Ubuntu Gnome, you only allow for integer scaling of things for high DPI monitors. While in theory this sounds good, on a 27 inch 4k monitor like mine, restricting it to integers is a problem. 1x is annoyingly small, and 2x is WAY too big. You need a 1.5x, and presumably to just allow most noninteger values to future proof the distribution given 8k monitors and all sorts of new and weird things coming out, like windows 10 has. Photos of the two annoying sizes are available here (it won't let me attach two files): http://i.imgur.com/vWrvZxq.jpg http://i.imgur.com/11p19k7.jpg I apologize for my photography skills in advance., you'll have to look at the ruler for scale to see the problem. Please contact me if you need any more information etc. Workaround == You can enable experimental fractional scaling in Ubuntu 17.10 or 18.04 LTS by running the following command in a terminal and then restarting your computer. Note that this is an experimental feature and is not fully supported by either Ubuntu or GNOME. gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After restarting your computer, you should find additional scale options in Settings > Devices > Displays. If you change your mind and want to get back to supported status, run: gsettings reset org.gnome.mutter experimental-features To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573728] Re: Files opened with gedit on command line no longer open within the existing gedit session
Here's the upstream bug report with an included patch: https://bugzilla.gnome.org/show_bug.cgi?id=730414 Maybe that patch could be added to the Ubuntu package? ** Bug watch added: GNOME Bug Tracker #730414 https://bugzilla.gnome.org/show_bug.cgi?id=730414 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1573728 Title: Files opened with gedit on command line no longer open within the existing gedit session Status in gedit package in Ubuntu: Confirmed Bug description: Prior to my update today to Ubuntu 16.04, I could open a file using gedit on the command line and it would open in the gedit window i already have open. After updating to 16.04 when I open a file with say `gedit /tmp/myleakycode.c` it opens in a new window. Oddly, as I was writing this bug report it's now working I expect it to, where opening files on the CLI adds to my existing session. I'll follow up if I find some pattern as to what triggers this. I am running Ubuntu Gnome 16.04 with the 4.4.0-21-generic kernel, gedit 3.18.3, terminator 0.98 to open the files. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 22 12:54:04 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1573728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772192] Re: Missing setting to disable touchpad
No switch for me. Screenshot attached. ** Attachment added: "Screenshot of my settings screen" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1772192/+attachment/5141793/+files/MouseAndTouchpad.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1772192 Title: Missing setting to disable touchpad Status in gnome-control-center package in Ubuntu: Incomplete Bug description: There is no longer an option to disable the touchpad. On Thinkpads with a Trackpoint and a Touchpad that's a common thing to do. 16.04 included this option and in 18.04 it is now missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 19 18:48:28 2018 InstallationDate: Installed on 2016-10-27 (568 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-05-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1772192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772192] Re: Missing setting to disable touchpad
Found the issue. I had installed a shell extension for touchpad disabling in 16.04 when I couldn't find a setting. Without that extension I get a bunch of touchpad options indeed. Sorry for the false alarm, and thanks for looking into it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1772192 Title: Missing setting to disable touchpad Status in gnome-control-center package in Ubuntu: Invalid Bug description: There is no longer an option to disable the touchpad. On Thinkpads with a Trackpoint and a Touchpad that's a common thing to do. 16.04 included this option and in 18.04 it is now missing. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 19 18:48:28 2018 InstallationDate: Installed on 2016-10-27 (568 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-05-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1772192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 220263]
I seem to have e10s enabled: Multiprocess Windows1/1 Enabled by default and have set Adwaita:light: widget.content.gtk-theme-override;Adwaita:light I still get white text on white background on the Find textbox within webpages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/220263 Title: Bad Firefox integration with dark themes Status in Mozilla Firefox: Fix Released Status in XULRunner: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme. Now I see all the input boxes and buttons filled with grey colour. This happened even with Firefox 2, but I solved that problem with a quick guide under the comment "firefox fix" by Proton at the bottom of this page: http://www.gnome- look.org/content/show.php/Grey+Neu?content=60824 In Firefox 3 I can't correct this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/220263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 220263]
Here's a simple way to replicate this bug for me. In both cases I have the Light theme selected: $ GTK_THEME="Adwaita:dark" firefox (firefox runs and the Find box has white text on white background) $ GTK_THEME="Adwaita:light" firefox (firefox runs and the Find box has the correct black text on white background) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/220263 Title: Bad Firefox integration with dark themes Status in Mozilla Firefox: Fix Released Status in XULRunner: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme. Now I see all the input boxes and buttons filled with grey colour. This happened even with Firefox 2, but I solved that problem with a quick guide under the comment "firefox fix" by Proton at the bottom of this page: http://www.gnome- look.org/content/show.php/Grey+Neu?content=60824 In Firefox 3 I can't correct this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/220263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780790]
I see the tooltip and context menu issue repeatedly. I'm now on a fresh install of Ubuntu 19.04 on Wayland and running Firefox 66.0.4. So it doesn't seem to be anything too specific to my install. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1780790 Title: Menus, tooltips and dropdowns are often misplaced on screen Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: New Bug description: I've noticed a few problems with misplaced elements in firefox UI that I am not sure are all the same bug: - In what appears to be random chance tooltips and menus are often misplaced on screen. It's common but not fully reproducible. What I see is right-clicking an element on a page or hovering over a link and having the menu/tooltip show up somewhere different on the page. Doing it again immediately after often results in it appearing in the right place the second time. - When using an external screen placed on top of the internal one with firefox maximized on the internal screen the URL bar's dropdown would consistently appear on the external screen, completely outside the firefox window, instead of the normal location Let me know what extra information is needed do diagnose this. I'm running gnome-shell and have used both Xorg and Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 61.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr2259 F pulseaudio BuildID: 20180703115938 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Jul 9 15:00:50 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-05-31 (39 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.203.246 metric 600 169.254.0.0/16 dev tun0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-a9ef45a0-cbbc-451a-a76b-c36ed1180623 PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=61.0/20180703115938 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1780790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809880] Re: Fullscreen vlc sometimes freezes until you Alt-Tab away and back from the window
This is most likely a vlc bug and should be reassigned to it. I am experiencing it in VLC under sway so unless the same bug exists across sway and mutter it's probably a vlc thing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1809880 Title: Fullscreen vlc sometimes freezes until you Alt-Tab away and back from the window Status in mutter package in Ubuntu: New Bug description: There seems to be a bug, which I assume is in mutter, when viewing multiple vlc videos fullscreen. The steps to reproduce are simple: 1. Open a bunch of videos in vlc in sequence with something like "vlc *" in a directory full of video files 2. Press N to move to the next video before it finishes (if you have short videos I don't think this is even needed, just let the videos finish) 3. Notice that sometimes the video freezes right after starting but if you open the activities or Alt-Tab away and back the video has been playing and will resume I've only noticed this bug in VLC but assume it's most likely a mutter or gnome-shell issue so I filed it in mutter. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 27 09:41:40 2018 InstallationDate: Installed on 2018-05-31 (209 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773955] [NEW] GDM very slow after resume from suspend
Public bug reported: When resuming from suspend GDM is very unresponsive. It takes several seconds to show the login screen after starting to type the password and it's common to need to press enter several times before it will recognize and unlock. This is a big regression on this machine compared to 16.04 where the login interface was much more usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:17:56 2018 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1773955 Title: GDM very slow after resume from suspend Status in gdm3 package in Ubuntu: New Bug description: When resuming from suspend GDM is very unresponsive. It takes several seconds to show the login screen after starting to type the password and it's common to need to press enter several times before it will recognize and unlock. This is a big regression on this machine compared to 16.04 where the login interface was much more usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:17:56 2018 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1773955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773959] [NEW] High CPU usage by gnome-shell even when idle
Public bug reported: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome- shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1773959 Title: High CPU usage by gnome-shell even when idle Status in gnome-shell package in Ubuntu: New Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal
The resolution is 2560x1440. I was testing with the terminal window maximized but the outcome is the same when the terminal is just a small window in the middle. The CPU usage is roughly half when the computer is charging, probably because the CPU is throttled up. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal Status in gnome-shell package in Ubuntu: Incomplete Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
I also confirm this on 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: In Progress Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Released Status in gnome-shell package in Debian: Confirmed Status in gnome-shell package in Fedora: In Progress Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774177] [NEW] Screen size is wrong on resume from suspend
Public bug reported: I run my screen on 100% scaling even though the ubuntu default for my 2560x1440 screen is 200%. After resume from suspend it's common for GDM to display at 200% and only after switch back to 100%. Sometimes this extends to after unlock with the mouse cursor being double size but only when hovering over the gnome shell top bar. I tried taking a screenshot but running the screenshot app fixed it and the cursor was normal sized again. I've now submitted or subscribed to several gnome-shell and gdm3 bugs. The 18.04 transition from unity to gnome-shell was clearly a step back in terms of polish of the desktop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 13:21:49 2018 InstallationDate: Installed on 2016-10-27 (579 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1774177 Title: Screen size is wrong on resume from suspend Status in gdm3 package in Ubuntu: New Bug description: I run my screen on 100% scaling even though the ubuntu default for my 2560x1440 screen is 200%. After resume from suspend it's common for GDM to display at 200% and only after switch back to 100%. Sometimes this extends to after unlock with the mouse cursor being double size but only when hovering over the gnome shell top bar. I tried taking a screenshot but running the screenshot app fixed it and the cursor was normal sized again. I've now submitted or subscribed to several gnome-shell and gdm3 bugs. The 18.04 transition from unity to gnome-shell was clearly a step back in terms of polish of the desktop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 13:21:49 2018 InstallationDate: Installed on 2016-10-27 (579 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal
For reference, logging in with Unity on the same hardware compiz uses about 1% or less CPU. So gnome-shell seems to be using 10x the CPU on this hardware at least. This was an upgraded install from 16.04 and I'll be trying a clean reinstall instead. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal Status in gnome-shell package in Ubuntu: New Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774177] Re: Personal scaling settings not used on the unlock screen
But what's strange is that the issue only happens momentarily and when returning from suspend. If I lock the screen it's correct and after a few moments after suspend it's correct again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774177 Title: Personal scaling settings not used on the unlock screen Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: I run my screen on 100% scaling even though the ubuntu default for my 2560x1440 screen is 200%. After resume from suspend it's common for GDM to display at 200% and only after switch back to 100%. Sometimes this extends to after unlock with the mouse cursor being double size but only when hovering over the gnome shell top bar. I tried taking a screenshot but running the screenshot app fixed it and the cursor was normal sized again. I've now submitted or subscribed to several gnome-shell and gdm3 bugs. The 18.04 transition from unity to gnome-shell was clearly a step back in terms of polish of the desktop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 13:21:49 2018 InstallationDate: Installed on 2016-10-27 (579 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal
Just tested this on Wayland and the situation seems slightly better. The same test (just the terminal, no extensions) is about 2-3% of CPU usage (compares with less than 1% for compiz) and when I turn on extensions (particularly system monitor) it goes to 5-7%. Not great but better. Great work on that list of issues. I don't mean just speed I've also found a bunch of other polish issues like the scaling. I'm just surprised gnome-shell is still this rough after so many years of development. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal Status in gnome-shell package in Ubuntu: Incomplete Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773959] Re: High CPU usage by gnome-shell when only running gnome-terminal
Did a clean install and here are the numbers with a Xorg session: - all default: less than 1% (comparable or even better to compiz) - turning on seconds on the top bar clock: around 3% - turning on extensions (particularly system monitor): 6-9% So it seems gnome-shell is perfectly capable of using low CPU but it's very easy to make it use a lot more CPU by adding things that only do one update a second (both the clock and system monitor are like that). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1773959 Title: High CPU usage by gnome-shell when only running gnome-terminal Status in gnome-shell package in Ubuntu: Incomplete Bug description: Even when doing nothing but displaying a terminal screen with top running gnome-shell uses 10% of a CPU. That seems excessive. I disabled all extensions to try and make the test fair. Enabling the system monitor extension increases the load to 13-14%. It seems that the gnome-shell screen painting is highly CPU consuming even if screen updates are infrequent (1 a second for all these cases). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:38:05 2018 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1773959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773955] Re: GDM very slow after resume from suspend
This is fixed for me after a clean reinstall of 18.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1773955 Title: GDM very slow after resume from suspend Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: When resuming from suspend GDM is very unresponsive. It takes several seconds to show the login screen after starting to type the password and it's common to need to press enter several times before it will recognize and unlock. This is a big regression on this machine compared to 16.04 where the login interface was much more usable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 29 11:17:56 2018 InstallationDate: Installed on 2016-10-27 (578 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (9 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1773955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774496] [NEW] Display defaults back to 200% on external screen connection
Public bug reported: I have a 2560x1440 screen that by default gets set to 200% which is way too large. I just set it to 100% and tweak the font scaling a bit instead. This is equivalent to the 1.38 scaling that used to be available in settings in 16.04. When connecting an external 1920x1080 screen the settings revert back to 200% on the internal screen. This makes no sense. The internal screen hasn't changed its properties so there's no real reason to change to 200% just because there's a second screen attached. Particularly since the setting is per-screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:02:32 2018 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1774496 Title: Display defaults back to 200% on external screen connection Status in gnome-control-center package in Ubuntu: New Bug description: I have a 2560x1440 screen that by default gets set to 200% which is way too large. I just set it to 100% and tweak the font scaling a bit instead. This is equivalent to the 1.38 scaling that used to be available in settings in 16.04. When connecting an external 1920x1080 screen the settings revert back to 200% on the internal screen. This makes no sense. The internal screen hasn't changed its properties so there's no real reason to change to 200% just because there's a second screen attached. Particularly since the setting is per-screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:02:32 2018 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1774496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774498] [NEW] Windows flash by external screen on virtual desktop change
Public bug reported: gnome-shell has the very interesting default of only doing virtual desktops on the internal screen. This works fine but has a strange visual glitch when changing virtual desktops where the contents of the internal screen flash through the external one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:06:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774498 Title: Windows flash by external screen on virtual desktop change Status in gnome-shell package in Ubuntu: New Bug description: gnome-shell has the very interesting default of only doing virtual desktops on the internal screen. This works fine but has a strange visual glitch when changing virtual desktops where the contents of the internal screen flash through the external one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:06:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774505] [NEW] OSD for volume/brightness should only appear on main display
Public bug reported: When watching a movie on an external display it's often useful to adjust the volume. Currently gnome-shell will display the OSD on both displays creating an overlay over the video. Unity would only display on the screen of the app used at the moment. Ideally it would just always show up on the main display so that you can keep focus on the video app for other keybindings to still work. I tried searching for an extension to do this but couldn't find one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 22:00:28 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774505 Title: OSD for volume/brightness should only appear on main display Status in gnome-shell package in Ubuntu: New Bug description: When watching a movie on an external display it's often useful to adjust the volume. Currently gnome-shell will display the OSD on both displays creating an overlay over the video. Unity would only display on the screen of the app used at the moment. Ideally it would just always show up on the main display so that you can keep focus on the video app for other keybindings to still work. I tried searching for an extension to do this but couldn't find one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 22:00:28 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774498] Re: Windows flash by external screen on virtual desktop change
This is really easy to reproduce. Just arrange your screens so your external screen is above the internal one instead of to the left or right. Now when you switch virtual desktops the contents are moved through the external screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774498 Title: Windows flash by external screen on virtual desktop change Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell has the very interesting default of only doing virtual desktops on the internal screen. This works fine but has a strange visual glitch when changing virtual desktops where the contents of the internal screen flash through the external one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:06:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774177] Re: Personal scaling settings not used on the unlock screen
This is not the same bug. I can't reproduce it anymore since gdm is no longer slow on resume. But is it really Ubuntu process to have the user submit bug reports upstream? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774177 Title: Personal scaling settings not used on the unlock screen Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I run my screen on 100% scaling even though the ubuntu default for my 2560x1440 screen is 200%. After resume from suspend it's common for GDM to display at 200% and only after switch back to 100%. Sometimes this extends to after unlock with the mouse cursor being double size but only when hovering over the gnome shell top bar. I tried taking a screenshot but running the screenshot app fixed it and the cursor was normal sized again. I've now submitted or subscribed to several gnome-shell and gdm3 bugs. The 18.04 transition from unity to gnome-shell was clearly a step back in terms of polish of the desktop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 13:21:49 2018 InstallationDate: Installed on 2016-10-27 (579 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774505] Re: OSD for volume/brightness should only appear on main display
Submitted here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/327 I mentioned it here because this is a regression for me compared to Unity on 16.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774505 Title: OSD for volume/brightness should only appear on main display Status in gnome-shell package in Ubuntu: Incomplete Bug description: When watching a movie on an external display it's often useful to adjust the volume. Currently gnome-shell will display the OSD on both displays creating an overlay over the video. Unity would only display on the screen of the app used at the moment. Ideally it would just always show up on the main display so that you can keep focus on the video app for other keybindings to still work. I tried searching for an extension to do this but couldn't find one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 22:00:28 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774177] Re: Personal scaling settings not used on the unlock screen
Just had the same thing happen even with gdm not being slow. Flashes for less than a second and now my pointer is at 200% when over the top bar. Trying to take a screenshot resets it again so I can't show it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774177 Title: Personal scaling settings not used on the unlock screen Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I run my screen on 100% scaling even though the ubuntu default for my 2560x1440 screen is 200%. After resume from suspend it's common for GDM to display at 200% and only after switch back to 100%. Sometimes this extends to after unlock with the mouse cursor being double size but only when hovering over the gnome shell top bar. I tried taking a screenshot but running the screenshot app fixed it and the cursor was normal sized again. I've now submitted or subscribed to several gnome-shell and gdm3 bugs. The 18.04 transition from unity to gnome-shell was clearly a step back in terms of polish of the desktop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 13:21:49 2018 InstallationDate: Installed on 2016-10-27 (579 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774177] Re: Personal scaling settings not used on the unlock screen
Upstream issue submitted: https://gitlab.gnome.org/GNOME/gnome-shell/issues/331 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774177 Title: Personal scaling settings not used on the unlock screen Status in gdm3 package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: I run my screen on 100% scaling even though the ubuntu default for my 2560x1440 screen is 200%. After resume from suspend it's common for GDM to display at 200% and only after switch back to 100%. Sometimes this extends to after unlock with the mouse cursor being double size but only when hovering over the gnome shell top bar. I tried taking a screenshot but running the screenshot app fixed it and the cursor was normal sized again. I've now submitted or subscribed to several gnome-shell and gdm3 bugs. The 18.04 transition from unity to gnome-shell was clearly a step back in terms of polish of the desktop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 13:21:49 2018 InstallationDate: Installed on 2016-10-27 (579 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775635] [NEW] Full-screen applications sometimes appear on several virtual desktops
Public bug reported: I've had both VLC and VirtualBox, when running fullscreen, show up in more than one virtual desktop. I'm using a fixed number of virtual desktops (4) and I've seen in happen between 3 and 4 and between 1 and 3. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 7 15:30:27 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1775635 Title: Full-screen applications sometimes appear on several virtual desktops Status in gnome-shell package in Ubuntu: New Bug description: I've had both VLC and VirtualBox, when running fullscreen, show up in more than one virtual desktop. I'm using a fixed number of virtual desktops (4) and I've seen in happen between 3 and 4 and between 1 and 3. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 7 15:30:27 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1775635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775634] [NEW] Occasional notifications about an application having prevented screen lock
Public bug reported: I get occasional notifications that an application has prevented lock. I believe it mostly happens when returning from suspend. As far as I can tell these are false positives as the locking seems to be happening correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 7 15:29:44 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1775634 Title: Occasional notifications about an application having prevented screen lock Status in gnome-shell package in Ubuntu: New Bug description: I get occasional notifications that an application has prevented lock. I believe it mostly happens when returning from suspend. As far as I can tell these are false positives as the locking seems to be happening correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 7 15:29:44 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1775634/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775637] [NEW] Screen tearing both in scrolling and videos
Public bug reported: Using firefox on the 18.04 default session (gnome-shell on Xorg) I get screen tearing when scrolling and also in videos. It's evident in this video for example: https://www.youtube.com/watch?v=9hIRq5HTh5s Where the lines between white and black areas seem to jump around and that's not visible in a screenshot. When scrolling it's common to see horizontal discontinuities in the text. Here's the details of my graphics card: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] Flags: bus master, fast devsel, latency 0, IRQ 126 Memory at f000 (64-bit, non-prefetchable) [size=16M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at e000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 I'm using a Lenovo T460s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 60.0.1+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr1619 F...m pulseaudio /dev/snd/controlC0: pedrocr1619 F pulseaudio BuildID: 20180517114003 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Jun 7 15:35:20 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-05-31 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.202.17 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-eee55497-e2e4-4c82-a862-236a81180223 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.0.1/20180517114003 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-eee55497-e2e4-4c82-a862-236a81180223 bp-db2b7d55-dbe6-47a3-b50d-e9b691171230 bp-280d460e-d837-442d-8543-17f3c1171202 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1775637 Title: Screen tearing both in scrolling and videos Status in firefox package in Ubuntu: New Bug description: Using firefox on the 18.04 default session (gnome-shell on Xorg) I get screen tearing when scrolling and also in videos. It's evident in this video for example: https://www.youtube.com/watch?v=9hIRq5HTh5s Where the lines between white and black areas seem to jump around and that's not visible in a screenshot. When scrolling it's common to see horizontal discontinuities in the text. Here's the details of my graphics card: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] Flags: bus master, fast devsel, latency 0, IRQ 126 Memory at f000 (64-bit, non-prefetchable) [size=16M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at e000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 I'm using a Lenovo T460s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 60.0.1+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 AddonCompatCheckDisabled
[Desktop-packages] [Bug 1775635] Re: Full-screen applications sometimes appear on several virtual desktops
I've only run the Xorg session. If that helps I'll run the Wayland session for a while to give feedback on all the bugs I've encountered. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1775635 Title: Full-screen applications sometimes appear on several virtual desktops Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I've had both VLC and VirtualBox, when running fullscreen, show up in more than one virtual desktop. I'm using a fixed number of virtual desktops (4) and I've seen in happen between 3 and 4 and between 1 and 3. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 7 15:30:27 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1775635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772189] Re: Pointer is erratic without disabling the libinput Acceleration Profile
Testing the wayland session the pointer behavior is quite different. It requires a much smaller speed setting to be usable and seems more erratic than the X one but maybe that just needs getting used to. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1772189 Title: Pointer is erratic without disabling the libinput Acceleration Profile Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I have a Lenovo T460s and have upgraded to Ubuntu 18.04. To be able to use the trackpoint I need to disable the libinput acceleration with the following: $ xinput --set-prop 'TPPS/2 IBM TrackPoint' 'libinput Accel Profile Enabled' 0, 1 Without doing this I get an extremely erratic pointer. Setting the acceleration profile to flat in the tweak tool doesn't fix it either. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-libinput 0.27.1-1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 19 18:26:20 2018 DistUpgraded: 2018-05-19 15:50:55,800 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu InstallationDate: Installed on 2016-10-27 (568 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 003: ID 5986:0706 Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FAS5TS00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=2a6b0b7e-668b-4c7f-82a9-de13f7ec5d57 ro quiet splash elevator=cfq vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to bionic on 2018-05-19 (0 days ago) dmi.bios.date: 05/25/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET57W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET57W(1.25):bd05/25/2017:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat May 19 14:54:55 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1772189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1777367] [NEW] Output device doesn't always switch back from HDMI
Public bug reported: When I disconnect to an HDMI output sometimes the configuration is left in an inconsistent state. It still shows as being connected to HDMI in volume up/down but there is no longer an HDMI option in the sound settings. After clicking the "Speakers - Built-in Audio" line in the Output tab of the settings (the only line available) everything is now correct. The same issue was also present in 16.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr 32004 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 22:54:14 2018 InstallationDate: Installed on 2018-05-31 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1777367 Title: Output device doesn't always switch back from HDMI Status in pulseaudio package in Ubuntu: New Bug description: When I disconnect to an HDMI output sometimes the configuration is left in an inconsistent state. It still shows as being connected to HDMI in volume up/down but there is no longer an HDMI option in the sound settings. After clicking the "Speakers - Built-in Audio" line in the Output tab of the settings (the only line available) everything is now correct. The same issue was also present in 16.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr 32004 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 22:54:14 2018 InstallationDate: Installed on 2018-05-31 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1777367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752813] [NEW] Pointer speed is too slow even in the fastest setting
Public bug reported: I use the trackpoint on my Lenovo T460s almost exclusively. Even in the fastest setting on a 2560x1440 screen it is much too slow. I've had to add the following udev rule to get it to be usable: ACTION=="add", SUBSYSTEM=="input", ATTR{name}=="TPPS/2 IBM TrackPoint", ATTR{device/sensitivity}="190", ATTR{device/speed}="220", ATTR{device/inertia}="6", ATTR{device/press_to_select}="0" And even with this and the speed in the control center set to maximum it is still a bit slow. Trying to push the sensitivity/speed settings higher will break the trackpoint and even with these settings it seems that sometimes on resume from sleep the trackpoint fails. After cycling suspend/resume again it comes back. There should be a way to set much higher speed settings for the mouse. Current settings make trackpoints very hard to use which even carries risk of hand/arm injuries. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-control-center 1:3.18.2-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 2 08:47:44 2018 InstallationDate: Installed on 2016-10-27 (490 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1752813 Title: Pointer speed is too slow even in the fastest setting Status in gnome-control-center package in Ubuntu: New Bug description: I use the trackpoint on my Lenovo T460s almost exclusively. Even in the fastest setting on a 2560x1440 screen it is much too slow. I've had to add the following udev rule to get it to be usable: ACTION=="add", SUBSYSTEM=="input", ATTR{name}=="TPPS/2 IBM TrackPoint", ATTR{device/sensitivity}="190", ATTR{device/speed}="220", ATTR{device/inertia}="6", ATTR{device/press_to_select}="0" And even with this and the speed in the control center set to maximum it is still a bit slow. Trying to push the sensitivity/speed settings higher will break the trackpoint and even with these settings it seems that sometimes on resume from sleep the trackpoint fails. After cycling suspend/resume again it comes back. There should be a way to set much higher speed settings for the mouse. Current settings make trackpoints very hard to use which even carries risk of hand/arm injuries. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-control-center 1:3.18.2-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 2 08:47:44 2018 InstallationDate: Installed on 2016-10-27 (490 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1752813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815135] [NEW] On resume unlocked desktop with completely broken shell
Public bug reported: Recently I've had gnome-shell be completely broken on resume from suspend. The screen contents show the apps with broken positions and missing decorations and the top bar is shown twice, once in 200% once in 100%. The screen lock is not in place so screen contents are revealed without a password (there's a long-standing bug on this). Switching to a terminal and killing gnome-shell doesn't make it respawn and the system is completely broken. I haven't been able to take a screenshot because the session is unresponsive. I wonder if it has something to do with virt-manager running with a fullscreen VM, as I've reported another bug where gnome-shell is broken when apps are fullscreen. At this point I'm planning on trying Kubuntu to see if I get a reasonable desktop. The change to gnome-shell in 18.04 has made the default Ubuntu desktop well below the standard for an LTS. Please let me know if there are logs I can provide or if there is a way to take a screenshot of a broken Xorg session from the console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 20:50:22 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (252 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1815135 Title: On resume unlocked desktop with completely broken shell Status in gnome-shell package in Ubuntu: New Bug description: Recently I've had gnome-shell be completely broken on resume from suspend. The screen contents show the apps with broken positions and missing decorations and the top bar is shown twice, once in 200% once in 100%. The screen lock is not in place so screen contents are revealed without a password (there's a long-standing bug on this). Switching to a terminal and killing gnome-shell doesn't make it respawn and the system is completely broken. I haven't been able to take a screenshot because the session is unresponsive. I wonder if it has something to do with virt-manager running with a fullscreen VM, as I've reported another bug where gnome-shell is broken when apps are fullscreen. At this point I'm planning on trying Kubuntu to see if I get a reasonable desktop. The change to gnome-shell in 18.04 has made the default Ubuntu desktop well below the standard for an LTS. Please let me know if there are logs I can provide or if there is a way to take a screenshot of a broken Xorg session from the console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 7 20:50:22 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (252 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1815135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810126] Re: Extremely visible screen tearing with VLC and Firefox/Chromium
This seems to at least help: https://extensions.gnome.org/extension/1445/fix-fullscreen-tearing/ Maybe something like that should be shipped by default -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1810126 Title: Extremely visible screen tearing with VLC and Firefox/Chromium Status in mutter package in Ubuntu: New Bug description: When watching videos in VLC on an external screen there is extremely visible screen tearing. But it's likely that the external screen only makes the problem worse as this website shows a lot of vsync issues in both Firefox and Chromium even with just the single screen: https://www.vsynctester.com/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 30 23:16:26 2018 InstallationDate: Installed on 2018-05-31 (213 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1810126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775637] Re: Screen tearing both in scrolling and videos
This is probably the same bug as the one I submitted against mutter: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1810126 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1775637 Title: Screen tearing both in scrolling and videos Status in firefox package in Ubuntu: Confirmed Bug description: Using firefox on the 18.04 default session (gnome-shell on Xorg) I get screen tearing when scrolling and also in videos. It's evident in this video for example: https://www.youtube.com/watch?v=9hIRq5HTh5s Where the lines between white and black areas seem to jump around and that's not visible in a screenshot. When scrolling it's common to see horizontal discontinuities in the text. Here's the details of my graphics card: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] Flags: bus master, fast devsel, latency 0, IRQ 126 Memory at f000 (64-bit, non-prefetchable) [size=16M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at e000 [size=64] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 I'm using a Lenovo T460s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 60.0.1+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr1619 F...m pulseaudio /dev/snd/controlC0: pedrocr1619 F pulseaudio BuildID: 20180517114003 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Jun 7 15:35:20 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-05-31 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.202.17 metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-eee55497-e2e4-4c82-a862-236a81180223 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.0.1/20180517114003 (In use) RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-eee55497-e2e4-4c82-a862-236a81180223 bp-db2b7d55-dbe6-47a3-b50d-e9b691171230 bp-280d460e-d837-442d-8543-17f3c1171202 Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1775637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 220263]
I hit this bug today by choosing the dark Adwaita theme in Gnome 3.28 and Firefox 65.0. It's amazing that this is an 18 year old bug. I found it surprising the system theme did anything to webpages and had two consecutive surprises: - First setting the system theme to Adwaita-dark changed the Firefox theme. That makes sense. What was surprising was that the Firefox theme then changed the content of the web pages. My mental model of a browser is that within the page view it's a different world and there's no reason for the web to look different to match the browser chrome or the system theme. - Because I didn't actually like the dark version of Firefox I switched it to the Light theme manually (webpages are usually light colored and so dark chrome in browsers looks weird). And yet even after doing this pages still had dark buttons and input areas. That was even stranger. Now Firefox had a light theme and yet the webpages were still picking up broken colors from the system theme inconsistent with the Firefox chrome theme. I fixed this after some web searches by setting "widget.content.gtk- theme-override:Adwaita". That at least sets a light theme for UI controls and is back to looking reasonable. I found that in bug #1283086 which seems to be a 3 year old duplicate of this 18 year old bug. The proposal for removal of all native theming in #1411425 makes perfect sense. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/220263 Title: Bad Firefox integration with dark themes Status in Mozilla Firefox: Fix Released Status in XULRunner: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I'm using Mozilla Firefox 3 Beta 5 on Ubuntu 8.04 with a dark theme. Now I see all the input boxes and buttons filled with grey colour. This happened even with Firefox 2, but I solved that problem with a quick guide under the comment "firefox fix" by Proton at the bottom of this page: http://www.gnome- look.org/content/show.php/Grey+Neu?content=60824 In Firefox 3 I can't correct this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/220263/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752813] Re: Pointer speed is too slow even in the fastest setting
Currently the settings are just barely usable at max speed. Is there any upstream I can coordinate with to try and get this solved? This is a really annoying issue. Using these same laptops in Windows has a much faster pointer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1752813 Title: Pointer speed is too slow even in the fastest setting Status in gnome-control-center package in Ubuntu: New Bug description: I use the trackpoint on my Lenovo T460s almost exclusively. Even in the fastest setting on a 2560x1440 screen it is much too slow. I've had to add the following udev rule to get it to be usable: ACTION=="add", SUBSYSTEM=="input", ATTR{name}=="TPPS/2 IBM TrackPoint", ATTR{device/sensitivity}="190", ATTR{device/speed}="220", ATTR{device/inertia}="6", ATTR{device/press_to_select}="0" And even with this and the speed in the control center set to maximum it is still a bit slow. Trying to push the sensitivity/speed settings higher will break the trackpoint and even with these settings it seems that sometimes on resume from sleep the trackpoint fails. After cycling suspend/resume again it comes back. There should be a way to set much higher speed settings for the mouse. Current settings make trackpoints very hard to use which even carries risk of hand/arm injuries. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-control-center 1:3.18.2-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 2 08:47:44 2018 InstallationDate: Installed on 2016-10-27 (490 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1752813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752813] Re: Pointer speed is too slow even in the fastest setting
Another strange thing that happens is that sometimes after suspend/resume the pointer speed is changed. Right now, using that 250/250 udev rule I was before having just enough speed at maximum setting. Today after a suspend/resume cycle I now had to set the trackpoint speed to around 40% to get a reasonable level. So it seems somewhere in kernerl/libinput/mutter there is also a bug that makes the speed inconsistent over suspend/resume. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1752813 Title: Pointer speed is too slow even in the fastest setting Status in gnome-control-center package in Ubuntu: New Bug description: I use the trackpoint on my Lenovo T460s almost exclusively. Even in the fastest setting on a 2560x1440 screen it is much too slow. I've had to add the following udev rule to get it to be usable: ACTION=="add", SUBSYSTEM=="input", ATTR{name}=="TPPS/2 IBM TrackPoint", ATTR{device/sensitivity}="190", ATTR{device/speed}="220", ATTR{device/inertia}="6", ATTR{device/press_to_select}="0" And even with this and the speed in the control center set to maximum it is still a bit slow. Trying to push the sensitivity/speed settings higher will break the trackpoint and even with these settings it seems that sometimes on resume from sleep the trackpoint fails. After cycling suspend/resume again it comes back. There should be a way to set much higher speed settings for the mouse. Current settings make trackpoints very hard to use which even carries risk of hand/arm injuries. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-control-center 1:3.18.2-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 2 08:47:44 2018 InstallationDate: Installed on 2016-10-27 (490 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1752813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752813] Re: Pointer speed is too slow even in the fastest setting
*** This bug is a duplicate of bug 924648 *** https://bugs.launchpad.net/bugs/924648 I'm not sure if this is a duplicate of it's actually a bug in the underlying driver and not GNOME. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1752813 Title: Pointer speed is too slow even in the fastest setting Status in gnome-control-center package in Ubuntu: New Bug description: I use the trackpoint on my Lenovo T460s almost exclusively. Even in the fastest setting on a 2560x1440 screen it is much too slow. I've had to add the following udev rule to get it to be usable: ACTION=="add", SUBSYSTEM=="input", ATTR{name}=="TPPS/2 IBM TrackPoint", ATTR{device/sensitivity}="190", ATTR{device/speed}="220", ATTR{device/inertia}="6", ATTR{device/press_to_select}="0" And even with this and the speed in the control center set to maximum it is still a bit slow. Trying to push the sensitivity/speed settings higher will break the trackpoint and even with these settings it seems that sometimes on resume from sleep the trackpoint fails. After cycling suspend/resume again it comes back. There should be a way to set much higher speed settings for the mouse. Current settings make trackpoints very hard to use which even carries risk of hand/arm injuries. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-control-center 1:3.18.2-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 2 08:47:44 2018 InstallationDate: Installed on 2016-10-27 (490 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1752813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780790] Re: Menus, tooltips and dropdowns are often misplaced on screen
This is an extremely annoying bug which creates quite a lot of lack of polish of the desktop. Should I be submitting it upstream or something? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1780790 Title: Menus, tooltips and dropdowns are often misplaced on screen Status in firefox package in Ubuntu: New Bug description: I've noticed a few problems with misplaced elements in firefox UI that I am not sure are all the same bug: - In what appears to be random chance tooltips and menus are often misplaced on screen. It's common but not fully reproducible. What I see is right-clicking an element on a page or hovering over a link and having the menu/tooltip show up somewhere different on the page. Doing it again immediately after often results in it appearing in the right place the second time. - When using an external screen placed on top of the internal one with firefox maximized on the internal screen the URL bar's dropdown would consistently appear on the external screen, completely outside the firefox window, instead of the normal location Let me know what extra information is needed do diagnose this. I'm running gnome-shell and have used both Xorg and Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 61.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr2259 F pulseaudio BuildID: 20180703115938 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Jul 9 15:00:50 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-05-31 (39 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.203.246 metric 600 169.254.0.0/16 dev tun0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-a9ef45a0-cbbc-451a-a76b-c36ed1180623 PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=61.0/20180703115938 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774177] Re: Personal scaling settings not used on the unlock screen
This happens to me 100% of the time now and is extremely annoying. Issues like this have made the 18.04 GNOME transition a clear step back in desktop polish. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774177 Title: Personal scaling settings not used on the unlock screen Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/331 --- I run my screen on 100% scaling even though the ubuntu default for my 2560x1440 screen is 200%. After resume from suspend it's common for GDM to display at 200% and only after switch back to 100%. Sometimes this extends to after unlock with the mouse cursor being double size but only when hovering over the gnome shell top bar. I tried taking a screenshot but running the screenshot app fixed it and the cursor was normal sized again. I've now submitted or subscribed to several gnome-shell and gdm3 bugs. The 18.04 transition from unity to gnome-shell was clearly a step back in terms of polish of the desktop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 13:21:49 2018 InstallationDate: Installed on 2016-10-27 (579 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774177] Re: Personal scaling settings not used on the unlock screen
This bug doesn't exist on Wayland. It does seem like GNOME developers don't care about Xorg anymore and these kinds of bugs won't get fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774177 Title: Personal scaling settings not used on the unlock screen Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/331 --- I run my screen on 100% scaling even though the ubuntu default for my 2560x1440 screen is 200%. After resume from suspend it's common for GDM to display at 200% and only after switch back to 100%. Sometimes this extends to after unlock with the mouse cursor being double size but only when hovering over the gnome shell top bar. I tried taking a screenshot but running the screenshot app fixed it and the cursor was normal sized again. I've now submitted or subscribed to several gnome-shell and gdm3 bugs. The 18.04 transition from unity to gnome-shell was clearly a step back in terms of polish of the desktop. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 13:21:49 2018 InstallationDate: Installed on 2016-10-27 (579 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-19 (10 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-05-19T16:06:11.723169 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780790] Re: Menus, tooltips and dropdowns are often misplaced on screen
I haven't been able to replicate it in a Unity session but I can't replicate this at will in gnome-shell either so it's hard to confirm it's a gnome-shell issue. I wouldn't be surprised though as it's been extremely buggy so far. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1780790 Title: Menus, tooltips and dropdowns are often misplaced on screen Status in firefox package in Ubuntu: New Bug description: I've noticed a few problems with misplaced elements in firefox UI that I am not sure are all the same bug: - In what appears to be random chance tooltips and menus are often misplaced on screen. It's common but not fully reproducible. What I see is right-clicking an element on a page or hovering over a link and having the menu/tooltip show up somewhere different on the page. Doing it again immediately after often results in it appearing in the right place the second time. - When using an external screen placed on top of the internal one with firefox maximized on the internal screen the URL bar's dropdown would consistently appear on the external screen, completely outside the firefox window, instead of the normal location Let me know what extra information is needed do diagnose this. I'm running gnome-shell and have used both Xorg and Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 61.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr2259 F pulseaudio BuildID: 20180703115938 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Jul 9 15:00:50 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-05-31 (39 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.203.246 metric 600 169.254.0.0/16 dev tun0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-a9ef45a0-cbbc-451a-a76b-c36ed1180623 PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=61.0/20180703115938 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780790] Re: Menus, tooltips and dropdowns are often misplaced on screen
Bug submitted here: https://bugzilla.mozilla.org/show_bug.cgi?id=1499336 I searched the related bugs and while there are a bunch of positioning bugs none seemed to be this one. The firefox subreddit only turned up one other person with a vaguely similar issue: https://www.reddit.com/r/firefox/comments/91kf3n/tooltips_and_context_menus_out_of_place/ ** Bug watch added: Mozilla Bugzilla #1499336 https://bugzilla.mozilla.org/show_bug.cgi?id=1499336 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1780790 Title: Menus, tooltips and dropdowns are often misplaced on screen Status in firefox package in Ubuntu: New Bug description: I've noticed a few problems with misplaced elements in firefox UI that I am not sure are all the same bug: - In what appears to be random chance tooltips and menus are often misplaced on screen. It's common but not fully reproducible. What I see is right-clicking an element on a page or hovering over a link and having the menu/tooltip show up somewhere different on the page. Doing it again immediately after often results in it appearing in the right place the second time. - When using an external screen placed on top of the internal one with firefox maximized on the internal screen the URL bar's dropdown would consistently appear on the external screen, completely outside the firefox window, instead of the normal location Let me know what extra information is needed do diagnose this. I'm running gnome-shell and have used both Xorg and Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 61.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr2259 F pulseaudio BuildID: 20180703115938 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Jul 9 15:00:50 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-05-31 (39 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.203.246 metric 600 169.254.0.0/16 dev tun0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-a9ef45a0-cbbc-451a-a76b-c36ed1180623 PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=61.0/20180703115938 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782458] [NEW] Missing letters scattered across the interface
Public bug reported: Today my gnome-shell instance did something extremely strange. Suddenly around 2/3 of the letters, randomly scattered, were missing from the interface. I've attached a screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 19 01:23:21 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (48 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Garbled screen with missing letters in the interface" https://bugs.launchpad.net/bugs/1782458/+attachment/5165047/+files/GarbledFonts.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1782458 Title: Missing letters scattered across the interface Status in gnome-shell package in Ubuntu: New Bug description: Today my gnome-shell instance did something extremely strange. Suddenly around 2/3 of the letters, randomly scattered, were missing from the interface. I've attached a screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 19 01:23:21 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (48 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1782458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782458] Re: Missing letters scattered across the interface
$ lspci -k 00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08) Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] Kernel driver in use: i915 Kernel modules: i915 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller Kernel driver in use: xhci_hcd 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) Subsystem: Lenovo Sunrise Point-LP Thermal subsystem Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) Subsystem: Lenovo Sunrise Point-LP SATA Controller [AHCI mode] Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1) Kernel driver in use: pcieport Kernel modules: shpchp 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) Subsystem: Lenovo Sunrise Point-LP LPC Controller 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) Subsystem: Lenovo Sunrise Point-LP PMC 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) Subsystem: Lenovo Sunrise Point-LP HD Audio Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) Subsystem: Lenovo Sunrise Point-LP SMBus Kernel modules: i2c_i801 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-V (rev 21) Subsystem: Lenovo Ethernet Connection I219-V Kernel driver in use: e1000e Kernel modules: e1000e 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) Subsystem: Intel Corporation Wireless 8260 Kernel driver in use: iwlwifi Kernel modules: iwlwifi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1782458 Title: Missing letters scattered across the interface Status in gnome-shell package in Ubuntu: Incomplete Bug description: Today my gnome-shell instance did something extremely strange. Suddenly around 2/3 of the letters, randomly scattered, were missing from the interface. I've attached a screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 19 01:23:21 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (48 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1782458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780790] Re: Menus, tooltips and dropdowns are often misplaced on screen
** Attachment added: "Example screenshot of the second issue where the URL bar is consistently misplaced in certain screen/window configurations" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/+attachment/5167938/+files/FirefoxWrongPlacement.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1780790 Title: Menus, tooltips and dropdowns are often misplaced on screen Status in firefox package in Ubuntu: New Bug description: I've noticed a few problems with misplaced elements in firefox UI that I am not sure are all the same bug: - In what appears to be random chance tooltips and menus are often misplaced on screen. It's common but not fully reproducible. What I see is right-clicking an element on a page or hovering over a link and having the menu/tooltip show up somewhere different on the page. Doing it again immediately after often results in it appearing in the right place the second time. - When using an external screen placed on top of the internal one with firefox maximized on the internal screen the URL bar's dropdown would consistently appear on the external screen, completely outside the firefox window, instead of the normal location Let me know what extra information is needed do diagnose this. I'm running gnome-shell and have used both Xorg and Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 61.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr2259 F pulseaudio BuildID: 20180703115938 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Jul 9 15:00:50 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-05-31 (39 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.203.246 metric 600 169.254.0.0/16 dev tun0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-a9ef45a0-cbbc-451a-a76b-c36ed1180623 PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=61.0/20180703115938 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1780790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
I hadn't seen this for a while and it happened again today. The dumpkeys/loadkeys workaround fixed it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774498] Re: Windows flash by external screen on virtual desktop change
I've disabled all extensions and recorded a video. Here's the output of lspci: $ lspci -k 00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 08) Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 520 (rev 07) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] Kernel driver in use: i915 Kernel modules: i915 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) Subsystem: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller Kernel driver in use: xhci_hcd 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) Subsystem: Lenovo Sunrise Point-LP Thermal subsystem Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) Subsystem: Lenovo Sunrise Point-LP CSME HECI Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) Subsystem: Lenovo Sunrise Point-LP SATA Controller [AHCI mode] Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1) Kernel driver in use: pcieport Kernel modules: shpchp 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) Subsystem: Lenovo Sunrise Point-LP LPC Controller 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) Subsystem: Lenovo Sunrise Point-LP PMC 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) Subsystem: Lenovo Sunrise Point-LP HD Audio Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) Subsystem: Lenovo Sunrise Point-LP SMBus Kernel modules: i2c_i801 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection I219-V (rev 21) Subsystem: Lenovo Ethernet Connection I219-V Kernel driver in use: e1000e Kernel modules: e1000e 02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) Subsystem: Lenovo RTS522A PCI Express Card Reader Kernel driver in use: rtsx_pci Kernel modules: rtsx_pci 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) Subsystem: Intel Corporation Wireless 8260 Kernel driver in use: iwlwifi Kernel modules: iwlwifi ** Attachment added: "Video of windows zooming by the external screen" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774498/+attachment/5170264/+files/vokoscreen-2018-08-01_08-44-41.mkv -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774498 Title: Windows flash by external screen on virtual desktop change Status in gnome-shell package in Ubuntu: Expired Bug description: gnome-shell has the very interesting default of only doing virtual desktops on the internal screen. This works fine but has a strange visual glitch when changing virtual desktops where the contents of the internal screen flash through the external one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:06:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774498] Re: Windows flash by external screen on workspace change
Of course "Workspaces span displays" fixes it as everything moves at once. Putting the external screen on the left or right also fixes it. But that just shows how the animation is broken. When the screen is on top and doesn't span displays there's no reason for the contents of the internal screen that are switching virtual desktop to fly through the external screen. That's just a bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774498 Title: Windows flash by external screen on workspace change Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell has the very interesting default of only doing virtual desktops on the internal screen. This works fine but has a strange visual glitch when changing virtual desktops where the contents of the internal screen flash through the external one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:06:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774498] Re: Windows flash by external screen on workspace change
Here's the upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/455 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774498 Title: Windows flash by external screen on workspace change Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell has the very interesting default of only doing virtual desktops on the internal screen. This works fine but has a strange visual glitch when changing virtual desktops where the contents of the internal screen flash through the external one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:06:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774498] Re: Windows flash by external screen on workspace change
>As part of that animation, windows from the old workspace fly out and windows from the new workspace fly in. This makes perfect sense but there's no reason for that flying to happen over the external screen as that one isn't changing at all. None of those windows will ever stop in that space so it's just a strange movement of windows across screen real estate they never belong to. I've already disabled animations to not have to deal with this. But the number of tweaks and extensions I've already had to do to get a semi- acceptable gnome-shell experience is amazing... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774498 Title: Windows flash by external screen on workspace change Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell has the very interesting default of only doing virtual desktops on the internal screen. This works fine but has a strange visual glitch when changing virtual desktops where the contents of the internal screen flash through the external one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:06:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1774498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1786063] [NEW] gedit should switch tabs with Ctrl-PgUp and Ctrl-PgDown to be consistent with other apps
Public bug reported: Gedit uses Ctrl-Alt-PgUp/PgDown for tab switching when others just use Ctrl-PgUp/PgDown. That's what gedit should use to be consistent with for example gnome-terminal and firefox. It also makes sense that Ctrl-Alt is reserved for more global actions like workspace switching ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 8 16:35:32 2018 InstallationDate: Installed on 2018-05-31 (69 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1786063 Title: gedit should switch tabs with Ctrl-PgUp and Ctrl-PgDown to be consistent with other apps Status in gedit package in Ubuntu: New Bug description: Gedit uses Ctrl-Alt-PgUp/PgDown for tab switching when others just use Ctrl-PgUp/PgDown. That's what gedit should use to be consistent with for example gnome-terminal and firefox. It also makes sense that Ctrl- Alt is reserved for more global actions like workspace switching ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gedit 3.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 8 16:35:32 2018 InstallationDate: Installed on 2018-05-31 (69 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1786063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573728] Re: Files opened with gedit on command line no longer open within the existing gedit session
Since upstream doesn't seem to want to commit the fix could the ubuntu package add this as a patch? I've rebuilt the package with the patch from the upstream bug (attached) and it seems to work fine as verified by other users in the upstream bug. I couldn't get dpkg-source to actually apply it automatically with the following error: dpkg-source: warning: unexpected end of diff 'gedit-3.28.1/debian/patches/09_position_fix.patch' So I patched it manually. But I'm sure that's just a simple issue someone with actual knowledge of dpkg packaging will fix easily. ** Patch added: "Patch from the upstream bug" https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1573728/+attachment/5173064/+files/09_position_fix.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1573728 Title: Files opened with gedit on command line no longer open within the existing gedit session Status in gedit package in Ubuntu: Confirmed Bug description: Prior to my update today to Ubuntu 16.04, I could open a file using gedit on the command line and it would open in the gedit window i already have open. After updating to 16.04 when I open a file with say `gedit /tmp/myleakycode.c` it opens in a new window. Oddly, as I was writing this bug report it's now working I expect it to, where opening files on the CLI adds to my existing session. I'll follow up if I find some pattern as to what triggers this. I am running Ubuntu Gnome 16.04 with the 4.4.0-21-generic kernel, gedit 3.18.3, terminator 0.98 to open the files. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 22 12:54:04 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1573728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775635] Re: Full-screen applications sometimes appear on several virtual desktops
I only see this on Xorg. The wayland session seems to work properly. In Xorg with 4 fixed virtual desktops the behaviour is the following with a fullscreen virtualbox instance: - I start it on desktop 4 and put it fullscreen - On the virtual desktop list it's on desktop 4 only - When switching desktops the virtual machine shows up on all desktops (1 through 4) - Only desktop 4 actually accepts input into the virtual machine - If I open a window and place it on desktop 1, it will now work to switch to that desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1775635 Title: Full-screen applications sometimes appear on several virtual desktops Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I've had both VLC and VirtualBox, when running fullscreen, show up in more than one virtual desktop. I'm using a fixed number of virtual desktops (4) and I've seen in happen between 3 and 4 and between 1 and 3. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 7 15:30:27 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1775635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778983] [NEW] Resume from suspend on Wayland breaks window positioning
Public bug reported: While on the Xorg session things seem to be mostly correct on Wayland after resume from suspend several things are broken: 1) The session resumes on the 4th virtual desktop independently on where it was before 2) The fullscreen virtualbox session I keep in the fourth desktop now has broken dimensions not covering the whole screen and/or being offset from the screen (a gap on the top showing the background and a covered part at the bottom of the screen) 3) In what may be the same bug the terminal and gedit windows I keep tiled to the right and left of virtual desktop 2 show up with wrong sizes. To fix 2) and 3) I have to do the same thing, take the windows out of tiling/fullscreen and go back, so somewhere the actual state of the windows was lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 20:14:45 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1778983 Title: Resume from suspend on Wayland breaks window positioning Status in gnome-shell package in Ubuntu: New Bug description: While on the Xorg session things seem to be mostly correct on Wayland after resume from suspend several things are broken: 1) The session resumes on the 4th virtual desktop independently on where it was before 2) The fullscreen virtualbox session I keep in the fourth desktop now has broken dimensions not covering the whole screen and/or being offset from the screen (a gap on the top showing the background and a covered part at the bottom of the screen) 3) In what may be the same bug the terminal and gedit windows I keep tiled to the right and left of virtual desktop 2 show up with wrong sizes. To fix 2) and 3) I have to do the same thing, take the windows out of tiling/fullscreen and go back, so somewhere the actual state of the windows was lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 20:14:45 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1778983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1775634] Re: Occasional notifications about an application having prevented screen lock
This bug only seems to happen in the Xorg session and not the Wayland one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1775634 Title: Occasional notifications about an application having prevented screen lock Status in gnome-shell package in Ubuntu: New Bug description: I get occasional notifications that an application has prevented lock. I believe it mostly happens when returning from suspend. As far as I can tell these are false positives as the locking seems to be happening correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 7 15:29:44 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1775634/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778983] Re: Resume from suspend on Wayland breaks window positioning
Submitted here: https://gitlab.gnome.org/GNOME/gnome-shell/issues/380 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1778983 Title: Resume from suspend on Wayland breaks window positioning Status in gnome-shell package in Ubuntu: Incomplete Bug description: While on the Xorg session things seem to be mostly correct on Wayland after resume from suspend several things are broken: 1) The session resumes on the 4th virtual desktop independently on where it was before 2) The fullscreen virtualbox session I keep in the fourth desktop now has broken dimensions not covering the whole screen and/or being offset from the screen (a gap on the top showing the background and a covered part at the bottom of the screen) 3) In what may be the same bug the terminal and gedit windows I keep tiled to the right and left of virtual desktop 2 show up with wrong sizes. To fix 2) and 3) I have to do the same thing, take the windows out of tiling/fullscreen and go back, so somewhere the actual state of the windows was lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 20:14:45 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1778983/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779096] [NEW] Mouse speed settings not used on the login screen
Public bug reported: The login screen doesn't use the mouse hardware settings. In particular it doesn't seem to use the mouse speed settings. This gives an inconsistent feeling between the login screen and the desktop if you're not using the default speed in the desktop. In my case I need to make the mouse speed much slower to be usable and that means that when I'm in the login screen the mouse is very jumpy. The same thing happens for the screen size settings (defaulting to 200% instead of the 100% I've set) but that's less inconvenient although still shows lack of polish. I assume this is because these settings are per-user but for the vast majority of desktops that's a single person anyway so it's a bad default. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 28 11:28:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1779096 Title: Mouse speed settings not used on the login screen Status in gnome-shell package in Ubuntu: New Bug description: The login screen doesn't use the mouse hardware settings. In particular it doesn't seem to use the mouse speed settings. This gives an inconsistent feeling between the login screen and the desktop if you're not using the default speed in the desktop. In my case I need to make the mouse speed much slower to be usable and that means that when I'm in the login screen the mouse is very jumpy. The same thing happens for the screen size settings (defaulting to 200% instead of the 100% I've set) but that's less inconvenient although still shows lack of polish. I assume this is because these settings are per-user but for the vast majority of desktops that's a single person anyway so it's a bad default. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 28 11:28:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1779096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779096] Re: Mouse speed settings not used on the login screen
I don't agree this is an invalid bug. It may be hard to fix but it's still a bug. Editing xml files to get a reasonable user experience is not a polished desktop. There are already settings (like wifi) that apply system-wide so there's no reason for mouse and screen settings to not be the same. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1779096 Title: Mouse speed settings not used on the login screen Status in gnome-shell package in Ubuntu: Invalid Bug description: The login screen doesn't use the mouse hardware settings. In particular it doesn't seem to use the mouse speed settings. This gives an inconsistent feeling between the login screen and the desktop if you're not using the default speed in the desktop. In my case I need to make the mouse speed much slower to be usable and that means that when I'm in the login screen the mouse is very jumpy. The same thing happens for the screen size settings (defaulting to 200% instead of the 100% I've set) but that's less inconvenient although still shows lack of polish. I assume this is because these settings are per-user but for the vast majority of desktops that's a single person anyway so it's a bad default. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 28 11:28:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1779096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779096] Re: Mouse speed settings not used on the login screen
Issue submitted here: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/124 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1779096 Title: Mouse speed settings not used on the login screen Status in gnome-shell package in Ubuntu: Won't Fix Bug description: The login screen doesn't use the mouse hardware settings. In particular it doesn't seem to use the mouse speed settings. This gives an inconsistent feeling between the login screen and the desktop if you're not using the default speed in the desktop. In my case I need to make the mouse speed much slower to be usable and that means that when I'm in the login screen the mouse is very jumpy. The same thing happens for the screen size settings (defaulting to 200% instead of the 100% I've set) but that's less inconvenient although still shows lack of polish. I assume this is because these settings are per-user but for the vast majority of desktops that's a single person anyway so it's a bad default. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 28 11:28:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1779096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779096] Re: Mouse speed settings not used on the login screen
How is this different from Wifi and keyboard settings that I'm already setting system wide? And how does this compromise the security of the system? The gdm user doesn't need to be able to change my settings. All it needs is to be able to read some settings to use them instead of the defaults if I'm the only user. I'll open a bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1779096 Title: Mouse speed settings not used on the login screen Status in gnome-shell package in Ubuntu: Won't Fix Bug description: The login screen doesn't use the mouse hardware settings. In particular it doesn't seem to use the mouse speed settings. This gives an inconsistent feeling between the login screen and the desktop if you're not using the default speed in the desktop. In my case I need to make the mouse speed much slower to be usable and that means that when I'm in the login screen the mouse is very jumpy. The same thing happens for the screen size settings (defaulting to 200% instead of the 100% I've set) but that's less inconvenient although still shows lack of polish. I assume this is because these settings are per-user but for the vast majority of desktops that's a single person anyway so it's a bad default. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jun 28 11:28:31 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1779096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1777367] Re: Output device doesn't always switch back from HDMI
*** This bug is a duplicate of bug 1711101 *** https://bugs.launchpad.net/bugs/1711101 I don't think this is a duplicate. My laptop does switch from HDMI most of the time, just not always. And today I just noticed something very strange. I booted the computer and the audio got set to HDMI even though I had nothing attached to it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1777367 Title: Output device doesn't always switch back from HDMI Status in pulseaudio package in Ubuntu: New Bug description: When I disconnect to an HDMI output sometimes the configuration is left in an inconsistent state. It still shows as being connected to HDMI in volume up/down but there is no longer an HDMI option in the sound settings. After clicking the "Speakers - Built-in Audio" line in the Output tab of the settings (the only line available) everything is now correct. The same issue was also present in 16.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr 32004 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 22:54:14 2018 InstallationDate: Installed on 2018-05-31 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1777367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1777367] Re: Output device doesn't always switch back from HDMI
*** This bug is a duplicate of bug 1711101 *** https://bugs.launchpad.net/bugs/1711101 There are two reasons I wonder if it's a duplicate: - bug 1711101 mentions that "We now have autoswitching on connect in 17.10, but not on disconnect". This is not the behavior I'm seeing. Autoswitching on disconnect works fine most of the time, it's just not consistent - I've gotten HDMI selected on boot without any HDMI attached at all so the issue doesn't even seem to be about state changes necessarily. Something is selecting a wrong output from the start sometimes. But I can report these findings to the other bug as well if that helps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1777367 Title: Output device doesn't always switch back from HDMI Status in pulseaudio package in Ubuntu: New Bug description: When I disconnect to an HDMI output sometimes the configuration is left in an inconsistent state. It still shows as being connected to HDMI in volume up/down but there is no longer an HDMI option in the sound settings. After clicking the "Speakers - Built-in Audio" line in the Output tab of the settings (the only line available) everything is now correct. The same issue was also present in 16.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr 32004 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 22:54:14 2018 InstallationDate: Installed on 2018-05-31 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1777367/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780790] [NEW] Menus, tooltips and dropdowns are often misplaced on screen
Public bug reported: I've noticed a few problems with misplaced elements in firefox UI that I am not sure are all the same bug: - In what appears to be random chance tooltips and menus are often misplaced on screen. It's common but not fully reproducible. What I see is right-clicking an element on a page or hovering over a link and having the menu/tooltip show up somewhere different on the page. Doing it again immediately after often results in it appearing in the right place the second time. - When using an external screen placed on top of the internal one with firefox maximized on the internal screen the URL bar's dropdown would consistently appear on the external screen, completely outside the firefox window, instead of the normal location Let me know what extra information is needed do diagnose this. I'm running gnome-shell and have used both Xorg and Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 61.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr2259 F pulseaudio BuildID: 20180703115938 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Jul 9 15:00:50 2018 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-05-31 (39 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.120.200.1 dev wlp4s0 proto dhcp metric 600 10.23.69.0/24 dev tun0 proto kernel scope link src 10.23.69.103 10.120.200.0/22 dev wlp4s0 proto kernel scope link src 10.120.203.246 metric 600 169.254.0.0/16 dev tun0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-a9ef45a0-cbbc-451a-a76b-c36ed1180623 PrefErrors: Unexpected character ',' whilst parsing int @ /usr/lib/firefox/defaults/pref/vendor-gre.js:8 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=61.0/20180703115938 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1780790 Title: Menus, tooltips and dropdowns are often misplaced on screen Status in firefox package in Ubuntu: New Bug description: I've noticed a few problems with misplaced elements in firefox UI that I am not sure are all the same bug: - In what appears to be random chance tooltips and menus are often misplaced on screen. It's common but not fully reproducible. What I see is right-clicking an element on a page or hovering over a link and having the menu/tooltip show up somewhere different on the page. Doing it again immediately after often results in it appearing in the right place the second time. - When using an external screen placed on top of the internal one with firefox maximized on the internal screen the URL bar's dropdown would consistently appear on the external screen, completely outside the firefox window, instead of the normal location Let me know what extra information is needed do diagnose this. I'm running gnome-shell and have used both Xorg and Wayland sessions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 61.0+build3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pedrocr2259 F pulseaudio BuildID: 20180703115938 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Jul 9 15:00:50 2018 Extensions: extensions.sqlite corrupt or miss
[Desktop-packages] [Bug 1809880] [NEW] Fullscreen vlc sometimes freezes until you Alt-Tab away and back from the window
Public bug reported: There seems to be a bug, which I assume is in mutter, when viewing multiple vlc videos fullscreen. The steps to reproduce are simple: 1. Open a bunch of videos in vlc in sequence with something like "vlc *" in a directory full of video files 2. Press N to move to the next video before it finishes (if you have short videos I don't think this is even needed, just let the videos finish) 3. Notice that sometimes the video freezes right after starting but if you open the activities or Alt-Tab away and back the video has been playing and will resume I've only noticed this bug in VLC but assume it's most likely a mutter or gnome-shell issue so I filed it in mutter. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 27 09:41:40 2018 InstallationDate: Installed on 2018-05-31 (209 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1809880 Title: Fullscreen vlc sometimes freezes until you Alt-Tab away and back from the window Status in mutter package in Ubuntu: New Bug description: There seems to be a bug, which I assume is in mutter, when viewing multiple vlc videos fullscreen. The steps to reproduce are simple: 1. Open a bunch of videos in vlc in sequence with something like "vlc *" in a directory full of video files 2. Press N to move to the next video before it finishes (if you have short videos I don't think this is even needed, just let the videos finish) 3. Notice that sometimes the video freezes right after starting but if you open the activities or Alt-Tab away and back the video has been playing and will resume I've only noticed this bug in VLC but assume it's most likely a mutter or gnome-shell issue so I filed it in mutter. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Dec 27 09:41:40 2018 InstallationDate: Installed on 2018-05-31 (209 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809880/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810126] [NEW] Extremely visible screen tearing with VLC and Firefox/Chromium
Public bug reported: When watching videos in VLC on an external screen there is extremely visible screen tearing. But it's likely that the external screen only makes the problem worse as this website shows a lot of vsync issues in both Firefox and Chromium even with just the single screen: https://www.vsynctester.com/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 30 23:16:26 2018 InstallationDate: Installed on 2018-05-31 (213 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1810126 Title: Extremely visible screen tearing with VLC and Firefox/Chromium Status in mutter package in Ubuntu: New Bug description: When watching videos in VLC on an external screen there is extremely visible screen tearing. But it's likely that the external screen only makes the problem worse as this website shows a lot of vsync issues in both Firefox and Chromium even with just the single screen: https://www.vsynctester.com/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.3-2~ubuntu18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 30 23:16:26 2018 InstallationDate: Installed on 2018-05-31 (213 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1810126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811902] [NEW] Echo cancelation should be enabled by default
Public bug reported: Echo cancellation is a basic feature for anything where you are using a video or audio conference. According to instructions like these: https://bugs.launchpad.net/elementaryos/+bug/1682253 https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb There is now enough support in pulseaudio to do this well, but it's just not enabled by default. Users shouldn't need to fish around for strange things to add to config files. More complete defaults should be included. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr2684 F...m pulseaudio /dev/snd/controlC0: pedrocr2684 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 23:45:10 2019 InstallationDate: Installed on 2018-05-31 (229 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1811902 Title: Echo cancelation should be enabled by default Status in pulseaudio package in Ubuntu: New Bug description: Echo cancellation is a basic feature for anything where you are using a video or audio conference. According to instructions like these: https://bugs.launchpad.net/elementaryos/+bug/1682253 https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb There is now enough support in pulseaudio to do this well, but it's just not enabled by default. Users shouldn't need to fish around for strange things to add to config files. More complete defaults should be included. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr2684 F...m pulseaudio /dev/snd/controlC0: pedrocr2684 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 23:45:10 2019 InstallationDate: Installed on 2018-05-31 (229 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811902] Re: Echo cancelation should be enabled by default
I agree with your point so won't be opening a bug to change the defaults. But it should be easy to enable somewhere in the GUI sound settings at least for specific applications. Video conferencing like appear.in is only really usable with headphones because of this. Adjusting text config files is not a good user experience. And I suspect most people only care about the microphone because of these kinds of uses. According to this: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/196 It's possible for apps to request echo cancelation with 'filter.want =echo-cancel' so maybe this is actually a bug in firefox? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1811902 Title: Echo cancelation should be enabled by default Status in pulseaudio package in Ubuntu: Incomplete Bug description: Echo cancellation is a basic feature for anything where you are using a video or audio conference. According to instructions like these: https://bugs.launchpad.net/elementaryos/+bug/1682253 https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb There is now enough support in pulseaudio to do this well, but it's just not enabled by default. Users shouldn't need to fish around for strange things to add to config files. More complete defaults should be included. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr2684 F...m pulseaudio /dev/snd/controlC0: pedrocr2684 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 23:45:10 2019 InstallationDate: Installed on 2018-05-31 (229 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811902] Re: Echo cancelation should be enabled by default
I don't agree that it's just a Firefox issue. There should be a simple way to enable this in the normal sound UI, at least as default for everything and ideally per-app. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1811902 Title: Echo cancelation should be enabled by default Status in pulseaudio package in Ubuntu: Opinion Bug description: Echo cancellation is a basic feature for anything where you are using a video or audio conference. According to instructions like these: https://bugs.launchpad.net/elementaryos/+bug/1682253 https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb There is now enough support in pulseaudio to do this well, but it's just not enabled by default. Users shouldn't need to fish around for strange things to add to config files. More complete defaults should be included. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr2684 F...m pulseaudio /dev/snd/controlC0: pedrocr2684 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 23:45:10 2019 InstallationDate: Installed on 2018-05-31 (229 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811902] Re: Echo cancelation should be enabled by default
Thanks for that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1811902 Title: Echo cancelation should be enabled by default Status in pulseaudio package in Ubuntu: Opinion Bug description: Echo cancellation is a basic feature for anything where you are using a video or audio conference. According to instructions like these: https://bugs.launchpad.net/elementaryos/+bug/1682253 https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Enable_Echo/Noise-Cancellation https://medium.com/@tim_73574/ubuntu-microphone-noise-cancellation-and-volume-auto-adjusted-issue-2c79678542bb There is now enough support in pulseaudio to do this well, but it's just not enabled by default. Users shouldn't need to fish around for strange things to add to config files. More complete defaults should be included. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: pedrocr2684 F...m pulseaudio /dev/snd/controlC0: pedrocr2684 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 15 23:45:10 2019 InstallationDate: Installed on 2018-05-31 (229 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET66W (1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1811902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573728] Re: Files opened with gedit on command line no longer open within the existing gedit session
I've ran the patch for a few months now with no issues. A new update has now reverted that so I have to go back and reapply it. Could the patch just be added to the ubuntu package and be done with it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1573728 Title: Files opened with gedit on command line no longer open within the existing gedit session Status in gedit package in Ubuntu: Confirmed Bug description: Prior to my update today to Ubuntu 16.04, I could open a file using gedit on the command line and it would open in the gedit window i already have open. After updating to 16.04 when I open a file with say `gedit /tmp/myleakycode.c` it opens in a new window. Oddly, as I was writing this bug report it's now working I expect it to, where opening files on the CLI adds to my existing session. I'll follow up if I find some pattern as to what triggers this. I am running Ubuntu Gnome 16.04 with the 4.4.0-21-generic kernel, gedit 3.18.3, terminator 0.98 to open the files. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 22 12:54:04 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1573728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1573728] Re: Files opened with gedit on command line no longer open within the existing gedit session
That will only come out with newer gnome versions, so this would only be fixed in 20.04 if you're using LTS releases. I'm running the original patch with no issues, so maybe it would be nice to just add that to the current package? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1573728 Title: Files opened with gedit on command line no longer open within the existing gedit session Status in gedit: Unknown Status in gedit package in Ubuntu: Triaged Bug description: Prior to my update today to Ubuntu 16.04, I could open a file using gedit on the command line and it would open in the gedit window i already have open. After updating to 16.04 when I open a file with say `gedit /tmp/myleakycode.c` it opens in a new window. Oddly, as I was writing this bug report it's now working I expect it to, where opening files on the CLI adds to my existing session. I'll follow up if I find some pattern as to what triggers this. I am running Ubuntu Gnome 16.04 with the 4.4.0-21-generic kernel, gedit 3.18.3, terminator 0.98 to open the files. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 22 12:54:04 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1573728/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 782512] Re: VPN connection is not enabled without supposedly optional username
Unfortunately I can't test this anymore as I've since left Stanford. Pedro On Sat, Jun 30, 2012 at 5:22 PM, Thomas Hood <782...@bugs.launchpad.net> wrote: > Is this bug still present in Ubuntu 12.04? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/782512 > > Title: > VPN connection is not enabled without supposedly optional username > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/782512/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/782512 Title: VPN connection is not enabled without supposedly optional username Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I just setup a Cisco VPN using Stanford's pcf file. I would link to it but it seems to only be available to registered users. network-manager is able to import the file just fine and produce what seems to be a well filled out VPN configuration. I'm using it through the indicator applet in the traditional gnome panel. I was baffled for a while that the new VPN connection didn't show up in the indicator applet dropdown. Once I filled in the username (under the Optional setting) it appeared. I also noticed some other strange occurrences: - Renaming the VPN interface did not show up in the dropdown until I selected the VPN connection at which point it showed the new name when asking for a password and the indicator was updated. - Removing the name didn't remove the VPN interface from the indicator and using it was still possible, and it did not ask for a username. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Fri May 13 20:53:59 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback IpRoute: 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.104 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 192.168.1.1 dev wlan0 proto static NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to natty on 2011-05-07 (6 days ago) WpaSupplicantLog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/782512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 800249] Re: network manager doesn't see Huawei e1550 USB GSM modem
My up-to-date natty install now detects the USB dongle, asks for a PIN and successfully connects to the network. As far as I can tell the bug has been fixed. The network-manager version itself seems to be the same so something else must have fixed this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/800249 Title: network manager doesn't see Huawei e1550 USB GSM modem Status in “network-manager” package in Ubuntu: New Bug description: Binary package hint: network-manager I'm trying to use a huawei e1550 modem in Ubuntu natty. Unlike previous versions of Ubuntu the mode switching between mass storage and serial is done automatically in udev and 4 tty devices are created (/dev/ttyUSB0..3). The problem is that network manager has absolutely no reaction to the plugging in of the card. The interface does not change and nothing shows up in the log. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: network-manager 0.8.4~git.20110319t175609.d14809b-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic x86_64 Architecture: amd64 Date: Tue Jun 21 14:25:10 2011 EcryptfsInUse: Yes IfupdownConfig: auto lo iface lo inet loopback IpRoute: 10.23.67.0/24 dev wlan0 proto kernel scope link src 10.23.67.250 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 10.23.67.254 dev wlan0 proto static Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to natty on 2011-05-07 (45 days ago) WpaSupplicantLog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/800249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1370407] Re: pulseaudio should be compiled by default with noice cancelling and echo reduction
*** This bug is a duplicate of bug 1261666 *** https://bugs.launchpad.net/bugs/1261666 This bug is not really a duplicate of #1261666 because all that one fixed was the compiling with webrtc part. Pulseaudio in 16.04 is still not configured by default to enable echo cancellation and just doing the changes to /etc/pulse/default.pa doesn't seem to work as the module fails to load complaining about configuration settings. It would be very nice if this was just a regular part of the distribution and enabled by default out of the box. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1370407 Title: pulseaudio should be compiled by default with noice cancelling and echo reduction Status in pulseaudio package in Ubuntu: Confirmed Bug description: In other OSs either the system itself or the sound drivers provide settings to enable noise reduction and echo cancellation. However in pulseaudio it has to be manually compiled in. It's a feature that should be a standard, and don't come with such a pain to enable, as I believe it would of very useful to provide by default. To implement this a dependency to Webrtc library should be added, as well as a couple of configuration lines: In debian/rules file, go to ~line 57 and add "--enable-webrtc-aec" to DEB_CONFIGURE_EXTRA_FLAGS (say after the --disable-hal-compat option) In debian/pulseaudio.install file and add: usr/lib/pulse-*/modules /libwebrtc-util.so Enable webrtc plugin in /etc/pulse/default.pa: sudo gedit /etc/pulse/default.pa ### Load echo cancellation module load-module module-echo-cancel source_name=echosource aec_method=webrtc set-default-source echosource To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1370407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631643] [NEW] 1920x1080 HDMI output is corrupted in 16.04
Public bug reported: Ever since upgrading to 16.04 from 14.04 on my Lenovo x230 the HDMI output to a Benq W1070 is corrupted if run at 1920x1080 (native resolution). At 1280x720 the display looks fine. Looking at similar reports for other graphics cards it seems similar to cases when the frequency is too low. I've tested that the projector still works fine with the same cable and another computer. I've attached a photo of the kind of corruption that shows up on screen. It's mostly green/magenta pixels sprinkled across the screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 8 19:38:39 2016 DistUpgraded: 2016-08-07 01:11:54,340 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2014-05-03 (889 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 23252QG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic root=UUID=9018e190-86bb-4fbf-a348-d47ea769640f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-08-07 (62 days ago) dmi.bios.date: 05/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET31WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 23252QG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET31WW(1.11):bd05/24/2012:svnLENOVO:pn23252QG:pvrThinkPadX230:rvnLENOVO:rn23252QG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23252QG dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Oct 5 10:26:16 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption ubuntu xenial ** Attachment added: "Photo of on screen corruption" https://bugs.launchpad.net/bugs/1631643/+attachment/4757498/+files/IMG_20161008_193924.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631643 Title: 1920x1080 HDMI output is corrupted in 16.04 Status in xorg package in Ubuntu: New Bug description: Ever since upgrading to 16.04 from 14.04 on my Lenovo x230 the HDMI output to a Benq W1070 is corrupted if run at 1920x1080 (native resolution). At 1280x720 the display looks fine. Looking at similar reports for other graphics cards it seems similar to cases when the frequency is too low. I've tested that the projector still works fine with the same cable and another computer. I've attached a photo of the kind of corruption that shows up on screen. It's mostly green/magenta pixels sprinkled across the screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDrive
[Desktop-packages] [Bug 1637754] [NEW] No image out of display port in Lenovo T460s
Public bug reported: I've tried to connect my Lenovo T460s to a HDMI projector using a mini display port to HDMI cable. Although this works in windows on the same hardware, on linux nothing is displayed and the projector says "No signal". Ubuntu recognizes the projector and sets everything up in the Displays settings though. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/mapper/sda5_crypt: clean, 246292/61235200 files, 19529009/244923392 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 29 19:00:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:2233] InstallationDate: Installed on 2016-10-27 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 003: ID 5986:0706 Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FAS5TS00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=UUID=2a6b0b7e-668b-4c7f-82a9-de13f7ec5d57 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET45W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS5TS00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET45W(1.13):bd06/02/2016:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FAS5TS00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Oct 28 03:36:51 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 38562 vendor MEI xserver.version: 2:1.18.3-1ubuntu2.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1637754 Title: No image out of display port in Lenovo T460s Status in xorg package in Ubuntu: New Bug description: I've tried to connect my Lenovo T460s to a HDMI projector using a mini display port to HDMI cable. Although this works in windows on the same hardware, on linux nothing is displayed and the projector says "No signal". Ubuntu recognizes the projector and sets everything up in the Displays settings though. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/mapper/sda5_crypt: clean, 246292/61235200 files, 19529009/244923392 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 29 19:00:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox
[Desktop-packages] [Bug 1637754] Re: No image out of display port in Lenovo T460s
The dmesg includes a section that seems related. Seems like something in i915 crashed: [70806.923660] [ cut here ] [70806.923752] WARNING: CPU: 1 PID: 2941 at /build/linux-dcxD3m/linux-4.4.0/ubuntu/i915/intel_pm.c:3586 skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]() [70806.923758] WARN_ON(!wm_changed) [70806.923763] Modules linked in: [70806.923769] ses enclosure uas usb_storage btrfs xor raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ctr ccm bnep arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common iwlmvm videodev media mac80211 input_leds joydev snd_hda_codec_hdmi serio_raw snd_hda_codec_realtek snd_soc_skl btusb snd_hda_codec_generic snd_soc_skl_ipc btrtl btbcm snd_hda_ext_core btintel snd_soc_sst_ipc snd_soc_sst_dsp bluetooth snd_soc_core iwlwifi snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_core rtsx_pci_ms cfg80211 memstick snd_hda_intel thinkpad_acpi snd_hda_codec snd_hda_core snd_hwdep nvram snd_pcm snd_seq_midi snd_seq_midi_event [70806.923903] snd_rawmidi mei_me mei shpchp snd_seq snd_seq_device snd_timer snd soundcore mac_hid coretemp parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_alg dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915_bpo psmouse e1000e intel_ips i2c_algo_bit ptp drm_kms_helper pps_core rtsx_pci syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm libahci wmi video fjes [70806.923992] CPU: 1 PID: 2941 Comm: Xorg Tainted: G OE 4.4.0-31-generic #50-Ubuntu [70806.923998] Hardware name: LENOVO 20FAS5TS00/20FAS5TS00, BIOS N1CET45W (1.13 ) 06/02/2016 [70806.924003] 0286 174a8c60 880216e379a8 813f1143 [70806.924014] 880216e379f0 c0292c98 880216e379e0 81081102 [70806.924022] 880214032000 880213ec9d9c 880214037000 880218fe5378 [70806.924031] Call Trace: [70806.924052] [] dump_stack+0x63/0x90 [70806.924065] [] warn_slowpath_common+0x82/0xc0 [70806.924074] [] warn_slowpath_fmt+0x5c/0x80 [70806.924132] [] skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo] [70806.924188] [] skl_update_wm+0x186/0x5f0 [i915_bpo] [70806.924243] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] [70806.924328] [] intel_atomic_commit+0x485/0xdc0 [i915_bpo] [70806.924341] [] ? wake_atomic_t_function+0x60/0x60 [70806.924405] [] ? drm_atomic_check_only+0x18e/0x590 [drm] [70806.924458] [] drm_atomic_commit+0x37/0x60 [drm] [70806.924496] [] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper] [70806.924551] [] ? drm_modeset_lock_all_ctx+0x9a/0xb0 [drm] [70806.924601] [] drm_mode_set_config_internal+0x62/0x100 [drm] [70806.924651] [] drm_mode_setcrtc+0x3d2/0x4f0 [drm] [70806.924662] [] ? recalc_sigpending+0x1b/0x50 [70806.924697] [] drm_ioctl+0x152/0x540 [drm] [70806.924707] [] ? __set_current_blocked+0x36/0x60 [70806.924749] [] ? drm_mode_setplane+0x1b0/0x1b0 [drm] [70806.924761] [] do_vfs_ioctl+0x29f/0x490 [70806.924772] [] ? fpu__restore_sig+0x4d/0x60 [70806.924780] [] SyS_ioctl+0x79/0x90 [70806.924790] [] entry_SYSCALL_64_fastpath+0x16/0x71 [70806.924865] ---[ end trace 916cb4f596cad652 ]--- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1637754 Title: No image out of display port in Lenovo T460s Status in xorg package in Ubuntu: New Bug description: I've tried to connect my Lenovo T460s to a HDMI projector using a mini display port to HDMI cable. Although this works in windows on the same hardware, on linux nothing is displayed and the projector says "No signal". Ubuntu recognizes the projector and sets everything up in the Displays settings though. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/mapper/sda5_crypt: clean, 246292/61235200 files, 19529009/244923392 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 29 19:00:40 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsys