[Desktop-packages] [Bug 1928317] Re: window focus is lost after blank screen
** Tags removed: hirsute ** Changed in: gnome-shell (Ubuntu) Status: Won't Fix => Confirmed ** Changed in: mutter (Ubuntu) Status: Won't Fix => Confirmed -- 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/1928317 Title: window focus is lost after blank screen Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: New in 21.04 hirsute default installation, the problem was not there in 20.10 . Environment: the default Wayland (source of other trubles as well, the most disturbing out of them is https://bugs.launchpad.net/ubuntu/+bug/1925732) and the Gnome shell Problem steps: (1) there are few windows on my screen and the focus is in one of them, I edit there something, (2) after 5 minutes of user inactivity the screen blanks, (3) I wish to resume the editing in the same window, hence I hit either a ctrl or shift key, or slightly move the mouse, (4) the view comes back, but none of the windows have the input focus! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928317/+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 1888098] Re: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen
tags: added: impish ** Tags added: impish -- 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/1888098 Title: Ubuntu 20.04 gnome-shell places windows on second screen when started from primary screen Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 LTS gnome-shell: Geïnstalleerd: 3.36.3-1ubuntu1~20.04.2 What I expected to happen: When clicking a button on the primary screen to open a new window in any application, that window should always open on the same monitor. What happened instead: Gnome-shell in Ubuntu 20.04 insists on placing new windows on the secondary monitor. Why this is a problem: My setup are Point of Sale terminals and the primary (a touchscreen) and secondary monitors are back to back. When the cashier presses the payment type button, the payment type pop-up is opening on the secondary screen which is displayed to the customer and not accessible to the cashier who needs to complete the transaction. The cashier can't move the pop-up on their own as there is no keyboard access (all buttons needed are in the application it self), and the touchscreen touches on itself (most of the time). In the past I was able to fix this with devilspie. As this problem has been around since Ubuntu 10.04. Was fine in Unity and 16.04/18.04 gnome-shell. But now devilspie is ignored by gnome-shell in 20.04 and gnome-shell keeps opening all the windows on the secondary screen. I've tried various gnome extensions and gnome-tweaks but none of them will open all windows (except the customer display) on the primary monitor only. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.3-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 19 01:21:39 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-14 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.3-0ubuntu0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1888098/+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 1936238] Re: Lock screen does not properly give focus after unlocking on Wayland
*** This bug is a duplicate of bug 1928317 *** https://bugs.launchpad.net/bugs/1928317 ** Tags removed: impish -- 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/1936238 Title: Lock screen does not properly give focus after unlocking on Wayland Status in mutter package in Ubuntu: New Bug description: When using GDM on Wayland, after unlocking, the previously focused window (such as Firefox) is not focused. Alt+tab (or click) must be used to gain focus. On X, everything works as excepted (if you were using Firefox at the time of locking, Firefox will be focused after unlocking too). (Ubuntu 21.04, ThinkPad P14s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1936238/+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 1916890] Re: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column
*** This bug is a duplicate of bug 1288655 *** https://bugs.launchpad.net/bugs/1288655 Duplicate status is still correct. ** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1916890 Title: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column Status in gnome-shell package in Ubuntu: New Status in gnome-terminal package in Ubuntu: New Bug description: each maximisation + un-maximisation cycle of a gnome-termial windows will shrink the terminal by 1 row and by 1 column two such a sycles (maximize, unmaximize, maximize, unmaximize) shrinks from 80x42 to 78x40: prohlep@pc56:~$ resize COLUMNS=80; LINES=42; export COLUMNS LINES; prohlep@pc56:~$ resize COLUMNS=79; LINES=41; export COLUMNS LINES; prohlep@pc56:~$ resize COLUMNS=78; LINES=40; export COLUMNS LINES; prohlep@pc56:~$ My 20.10 is almost release default state, no extension, only a few kbd shortcuts, that's all. I use gnome shell with gnome-terminals. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916890/+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 1925732] Re: gnome-terminal ignores the --geometry location requests
This bug is still there, I am interested in discussing it, but nobody assigned this bug to anybody. -- 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/1925732 Title: gnome-terminal ignores the --geometry location requests Status in gnome-terminal package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in gnome-terminal package in Fedora: Invalid Bug description: The more gnome-specific and detailed bug description: the gnome-terminal either ignores or misinterprets the --geometry=+0+0 , --geometry=+0-0 , --geometry=-0+0 and --geometry=-0-0 requests, while mate-terminal executes the correct positioning in the same environment (display manager and window manager). In case of Wayland, the gnome-terminal ignores the requests listed above, while mate-terminal is correctly positioned, in contrary to the urban legend, that under Wayland such a positioning is imposibble. In case of Xorg, the gnome-terminal positions itself into the corners of the rectangle containing the physical screens, even if that corner is not inside any of the physical screens. I.e.: in case of Xorg the gnome-terminal is ready to position itself into a not visible corner of the virtual space contaning the physical screens instead of do the same as the mate-terminal can do: to position itself into a corner of the visible physical screen. === The bug of gnome-terminal is that it is not able to position intself into visible corners, while the mate-terminal can do it, ... and in general the usual graphical programs can do it since the 80's. *** The original bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+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 1925732] Re: gnome-terminal ignores the --geometry location requests
tags:added: impish ** Tags added: impish -- 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/1925732 Title: gnome-terminal ignores the --geometry location requests Status in gnome-terminal package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in gnome-terminal package in Fedora: Invalid Bug description: The more gnome-specific and detailed bug description: the gnome-terminal either ignores or misinterprets the --geometry=+0+0 , --geometry=+0-0 , --geometry=-0+0 and --geometry=-0-0 requests, while mate-terminal executes the correct positioning in the same environment (display manager and window manager). In case of Wayland, the gnome-terminal ignores the requests listed above, while mate-terminal is correctly positioned, in contrary to the urban legend, that under Wayland such a positioning is imposibble. In case of Xorg, the gnome-terminal positions itself into the corners of the rectangle containing the physical screens, even if that corner is not inside any of the physical screens. I.e.: in case of Xorg the gnome-terminal is ready to position itself into a not visible corner of the virtual space contaning the physical screens instead of do the same as the mate-terminal can do: to position itself into a corner of the visible physical screen. === The bug of gnome-terminal is that it is not able to position intself into visible corners, while the mate-terminal can do it, ... and in general the usual graphical programs can do it since the 80's. *** The original bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+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 1958508] Re: System will use sleep-inactive-ac-timeout after unplug AC adapter
Trying to use newer version of kernel, the status of upower is correct. This bug is not related to gsd. Set it to 'invalid' ** Changed in: oem-priority Status: New => Invalid ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1958508 Title: System will use sleep-inactive-ac-timeout after unplug AC adapter Status in OEM Priority Project: Invalid Status in gnome-settings-daemon package in Ubuntu: Invalid Bug description: [Summary] System will use sleep-inactive-ac-timeout after unplug AC adapter [Reproduce Steps] 1. Plug AC and boot into OS 2. Open Setting > Power section 3. Adjust Blank Screen to 1 minute 4. Adjust Automatic Suspend to be On Batter Power and Delay 15 minutes 6. Wait 15 minutes [Expected result] System can enter suspend [Actual result] System won't enter suspend, the screen becomes black only. It takes `sleep-inactive-ac-timeout` to automatically suspend. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958508/+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 1936238] Re: Lock screen does not properly give focus after unlocking on Wayland
*** This bug is a duplicate of bug 1928317 *** https://bugs.launchpad.net/bugs/1928317 ** Tags added: impish -- 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/1936238 Title: Lock screen does not properly give focus after unlocking on Wayland Status in mutter package in Ubuntu: New Bug description: When using GDM on Wayland, after unlocking, the previously focused window (such as Firefox) is not focused. Alt+tab (or click) must be used to gain focus. On X, everything works as excepted (if you were using Firefox at the time of locking, Firefox will be focused after unlocking too). (Ubuntu 21.04, ThinkPad P14s) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1936238/+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 1928317] Re: window focus is lost after blank screen
This bug is still there, I am interested in discussing it, but nobody assigned this bug to anybody. -- 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/1928317 Title: window focus is lost after blank screen Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: New in 21.04 hirsute default installation, the problem was not there in 20.10 . Environment: the default Wayland (source of other trubles as well, the most disturbing out of them is https://bugs.launchpad.net/ubuntu/+bug/1925732) and the Gnome shell Problem steps: (1) there are few windows on my screen and the focus is in one of them, I edit there something, (2) after 5 minutes of user inactivity the screen blanks, (3) I wish to resume the editing in the same window, hence I hit either a ctrl or shift key, or slightly move the mouse, (4) the view comes back, but none of the windows have the input focus! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928317/+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 1928317] Re: window focus is lost after blank screen
tags:added: impish ** Tags added: impish -- 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/1928317 Title: window focus is lost after blank screen Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: New in 21.04 hirsute default installation, the problem was not there in 20.10 . Environment: the default Wayland (source of other trubles as well, the most disturbing out of them is https://bugs.launchpad.net/ubuntu/+bug/1925732) and the Gnome shell Problem steps: (1) there are few windows on my screen and the focus is in one of them, I edit there something, (2) after 5 minutes of user inactivity the screen blanks, (3) I wish to resume the editing in the same window, hence I hit either a ctrl or shift key, or slightly move the mouse, (4) the view comes back, but none of the windows have the input focus! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928317/+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 1918370] Re: 21.04 natural scrolling broken
The LTS releases are even numbered: 20.04 and 22.04 https://wiki.ubuntu.com/Releases -- 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/1918370 Title: 21.04 natural scrolling broken Status in Mutter: Unknown Status in mutter package in Ubuntu: Won't Fix Bug description: Since 20.10 upgrade to 21.04, natural scrolling on touchpad does not follow the "push page up" that natural scrolling did... Super low priority, but here's my uname -a: Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3 15:50:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1918370/+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 1850651]
try this scheduling API https://onsched.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: [SRU] Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Fix Released Status in thunderbird source package in Bionic: Fix Released Status in thunderbird source package in Disco: Won't Fix Status in thunderbird source package in Eoan: Fix Released Status in thunderbird source package in Focal: Fix Released Bug description: [Impact] A recent server-side change with google e-mail accounts (gmail) means that thunderbird consistently fails to authenticate, prompting for the user's e-mail address and password over and over, without ever succeeding. This has been fixed upstream and is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1592407. [Test Case] In a clean environment, launch thunderbird and add an existing gmail account. Thunderbird should auto-detect all the relevant parameters, and then an external webview should pop up to prompt for your e-mail address (it's not auto-filled, that's a separate issue that's also known upstream) and your password. After filling this in and authorizing thunderbird to access your e-mails, your account should be set up and thunderbird should start fetching e-mails from your inbox. Instead it fails to authenticate and displays the authentication pop up again. [Regression Potential] Low, as this is an official upstream point release that addresses only this regression (see https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/). The fix is minimal and self-contained (https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343), if the bug is indeed confirmed to be fixed then it should be safe. [Original Bug Description] When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 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 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.sku: LENOVO_MT_2347
Re: [Desktop-packages] [Bug 1918370] Re: 21.04 natural scrolling broken
Just out of interest isn't 21.04 an LTS release, and for that matter the latest LTS until April? On Fri, 21 Jan 2022 at 05:36, Daniel van Vugt <1918...@bugs.launchpad.net> wrote: > Thank you for reporting this bug to Ubuntu. > Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. > > See this document for currently supported Ubuntu releases: > https://wiki.ubuntu.com/Releases > > We appreciate that this bug may be old and you might not be interested > in discussing it any more. But if you are then please upgrade to the > latest Ubuntu version and re-test. If you then find the bug is still > present in the newer Ubuntu version, please add a comment here telling > us which new version it is in. > > ** Changed in: mutter (Ubuntu) >Status: Incomplete => Won't Fix > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1918370 > > Title: > 21.04 natural scrolling broken > > Status in Mutter: > Unknown > Status in mutter package in Ubuntu: > Won't Fix > > Bug description: > Since 20.10 upgrade to 21.04, natural scrolling on touchpad does not > follow the "push page up" that natural scrolling did... > > Super low priority, but here's my uname -a: > > Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3 > 15:50:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux > > To manage notifications about this bug go to: > https://bugs.launchpad.net/mutter/+bug/1918370/+subscriptions > > -- 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/1918370 Title: 21.04 natural scrolling broken Status in Mutter: Unknown Status in mutter package in Ubuntu: Won't Fix Bug description: Since 20.10 upgrade to 21.04, natural scrolling on touchpad does not follow the "push page up" that natural scrolling did... Super low priority, but here's my uname -a: Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3 15:50:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1918370/+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 1937015] Re: Xorg crashed with SIGSEGV in drmmode_set_mode() from drmmode_set_mode_major() from AMDGPUUnblank() from AMDGPUSaveScreen_KMS() from dixSaveScreens()
** Tags removed: hirsute ** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1937015 Title: Xorg crashed with SIGSEGV in drmmode_set_mode() from drmmode_set_mode_major() from AMDGPUUnblank() from AMDGPUSaveScreen_KMS() from dixSaveScreens() Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.11-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/aed212d57bbb3324ec4d5c5380adbeb10e7ad74d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1937015/+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 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
** Tags removed: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in gnome-control-center: Unknown Status in X.Org X server: New Status in gnome-control-center package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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 1745799] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_ou
** Tags removed: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745799 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_registry@2: error 0: invalid global wl_output (20)\n"] Status in xorg-server package in Ubuntu: Confirmed Bug description: Crashes when plugging in Dell WD15 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.5-0ubuntu2 Uname: Linux 4.15.0-rc8+ x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CompositorRunning: None CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 27 22:12:41 2018 DistUpgraded: 2018-01-26 09:36:11,455 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:591e] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:077a] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:5690 Realtek Semiconductor Corp. Bus 001 Device 003: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9365 ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc8+ root=UUID=fe08dba8-d746-4a04-82c9-cac962e9321c ro quiet splash wmi.debug_dump_wdg=1 vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to bionic on 2018-01-26 (1 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo dmi.bios.date: 12/05/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.21 dmi.board.name: 0DVT6M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.21:bd12/05/2017:svnDellInc.:pnXPS139365:pvr:rvnDellInc.:rn0DVT6M:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9365 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1 version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1745799/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
** Tags removed: hirsute -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1939186] Re: Wayland causes arrow key scroll lock behavior when using Japanese or US-intl keyboard layouts
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- 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/1939186 Title: Wayland causes arrow key scroll lock behavior when using Japanese or US-intl keyboard layouts Status in Mutter: Unknown Status in mutter package in Ubuntu: Won't Fix Bug description: After upgrading to Ubuntu 21.04 with Wayland as default, the arrow keys on my Japanese 108-key USB keyboard scroll in LibreOffice Calc as though scroll lock is toggled on (even though the scroll lock light is not on) instead of moving the cell in focus. (This happens with the US-intl keyboard layout too.) The arrow keys work as expected in other programs though, including LibreOffice Writer. If I switch to the default US keyboard layout, the arrow keys on the same keyboard work properly: moving the cell in focus. I tried removing grp_led:scroll from XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll" in /etc/default/keyboard, but that did not fix it. I also tried uninstalling LibreOffice and removing the config files as explained here, but that didn't fix it either. This was not a problem in Ubuntu 20.10 and the Japanese USB keyboard arrow keys work correctly in LibreCalc on Windows, so the issue appears to be specific to Ubuntu 21.04, not LibreOffice, nor this keyboard. As a workaround, if I start the session with Xorg instead, the arrow keys work as expected with any keyboard layout. Therefore, this bug appears to be related to Wayland. I was encouraged to file this bug report for gnome-shell in the comments on this AskUbuntu post: https://askubuntu.com/questions/1356052/why-do-japanese-keyboard- arrow-keys-scroll-in-libreoffice-calc-but-move-cell- wit/1356059?noredirect=1#comment2321519_1356059 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 7 12:18:23 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (548 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2021-07-06T20:58:08.463515 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1939186/+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 1913963] Re: [Cherry Trail] [modeset] Cursor flickering on dual screen setup
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1913963 Title: [Cherry Trail] [modeset] Cursor flickering on dual screen setup Status in linux package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Bug description: When running on dual screen config, the cursor is heavily flickering. Makes it a very unpleasant experience, if not renders it unusable. If switched to only single screen, cursor is completely stable. When issuing xrandr --output HDMI-2 --scale 0.99x0.99 again cursor is stable. Switching to 200% scaling in the desktop settings, doesn't help. I tried to catch the effect in a movie. However, because of frame rate, it is not possible to show the effect. If if its helpful, let me know and I'll try harder. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu56 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun Jan 31 19:55:12 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2021-01-30 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115) MachineType: BESSTAR (HK) LIMITED Z83-F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 08/13/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A dmi.board.asset.tag: Default string dmi.board.name: T3 MRD dmi.board.vendor: BESSTAR Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z83-F dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: BESSTAR (HK) LIMITED version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913963/+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 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)
** Tags removed: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1683383 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: From duplicate bug 1720364 report. Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher in mate-control-center 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. --- Original description below: This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04 Zesty Zapus. This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. Apparently, the bug has reappeared after the patch that used to fix the problem (208_switch_on_release.diff) has been removed from X.Org 1.19 packages. There is an updated patch in the upstream ticket https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xserver-xorg-core 2:1.19.3-1ubuntu1 Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 17 17:46:35 2017 InstallationDate: Installed on 2015-05-01 (716 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: xorg-server UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1683383/+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 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions
** Tags removed: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1823516 Title: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions Status in xorg-server package in Ubuntu: Fix Committed Status in xwayland package in Ubuntu: Fix Released Bug description: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1823516/+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 1925344] Re: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: nvidia-prime (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1925344 Title: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth Status in gdm3 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-460 package in Ubuntu: Won't Fix Status in nvidia-prime package in Ubuntu: Won't Fix Status in xorg-server package in Ubuntu: Won't Fix Bug description: After installation, the first boot works as expected - the system boots into a graphical shell login screen. However all subsequent reboots end up with a black screen with a blinking cursor in the top- left corner of the screen. To get to the login screen, one has to switch to a different tty (like tty2 with ctrl+alt+f2) and then to tty1. Running `prime-select query` shows `nvidia`. Interesting enough, when I change the nvidia-prime settings at least once, like to on-demand via `prime-select on-demand` - then everything starts working as expected. Even when I switch back to `nvidia`. Not sure which package I should fill this under. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.67 Thu Mar 11 00:11:45 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 21 15:20:15 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:09e1] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1] InstallationDate: Installed on 2021-04-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. G3 3500 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06ND9G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3500 dmi.product.sku: 09E1 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1746656] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log()
** Tags removed: hirsute ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1746656 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() Status in xorg-server package in Ubuntu: Confirmed Status in xwayland package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.19.5-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/919f7b6d37f2b2e23bf18d4cc9fad6a6116edf82 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1746656/+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 1811023] Re: Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
** Tags removed: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1811023 Title: Xorg aborts with ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. Status in X.Org X server: New Status in xorg-server package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.3-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/e1038a75ca80364c2c74351221e2ad5ec5d00916 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1811023/+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 1926620] Re: Gnome-Shell freezes when touchscreen is used in Wayland sessions
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- 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/1926620 Title: Gnome-Shell freezes when touchscreen is used in Wayland sessions Status in Mutter: Unknown Status in mutter package in Ubuntu: Won't Fix Bug description: Gnome-Shell freezes when touchscreen is used on Dell Inspiron 2-in-1 running 21.04, the dock and the upper bar stop responding, while the windows keep running. The problem was notice after upgrade (do- release-upgrade -c) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Apr 29 15:58:43 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-03-01 (58 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-22 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1926620/+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 1928932] Re: external monitor disabled upon editing file with vim
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- 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/1928932 Title: external monitor disabled upon editing file with vim Status in Mutter: Unknown Status in mutter package in Ubuntu: Won't Fix Bug description: This is the strangest bug I've encountered in my 20+ years of linux use. See a video of the bug at: https://drive.google.com/file/d/1StYD5kbL5pLRBOc6V-TXuE5DgymTdM0R/view?usp=sharing Using an external monitor I am editing a Snakefile with vim and syntax highlighting. Under certain condition the monitor will go to sleep. 0. download the Snakefile, vimrc, and the colorscheme that are the attached archive 1. move the colorscheme to ~/.vim/colors/ 1. `vim -u vimrc Snakefile` 2. delete one of the quotes, and see the external monitor go into sleep mode. Pertinent points: - If I disable the custom colorscheme or disable syntax highlighting there is no problem. - If I move the gnome-terminal onto the builtin display, then the external monitor reactivates. I wouldn't normally report this bug because it seems so specific to my setup. What is alarming is that a vim session in a gnome-terminal, under certain conditions, can cause the monitor to go to sleep! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libwayland-client0 1.18.0-2~exp1.1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Wed May 19 12:14:23 2021 DistUpgraded: 2021-04-27 09:44:28,765 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.11.0-16-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.11.0-17-generic, x86_64: installed facetimehd, 0.1, 5.11.0-16-generic, x86_64: installed facetimehd, 0.1, 5.11.0-17-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a26] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Haswell-ULT Integrated Graphics Controller [106b:011b] InstallationDate: Installed on 2021-01-19 (119 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Apple Inc. MacBookAir6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=418e02d0-7fe0-4fe3-a1c4-ac2167ada4fe ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: Upgraded to hirsute on 2021-04-27 (22 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 02/22/2021 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 431.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvr431.0.0.0.0:bd02/22/2021:br0.1:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.family: MacBook Air dmi.product.name: MacBookAir6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
[Desktop-packages] [Bug 1924859] Re: VMware not grabbing Alt+Tab input in Wayland sessions
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: mutter (Ubuntu) Status: Triaged => Won't Fix -- 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/1924859 Title: VMware not grabbing Alt+Tab input in Wayland sessions Status in Mutter: Unknown Status in mutter package in Ubuntu: Won't Fix Bug description: I am currently running VMware workstation pro 16.1. When pressing alt+tab to toggle the windows in the guest OS, the input is instead applied to the host OS and not the guest. When switching from Wayland to Xorg the problem is resolved. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Sat Apr 17 15:48:45 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASRock Incorporation 2nd Generation Core Processor Family Integrated Graphics Controller [1849:0112] NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GM206 [GeForce GTX 960] [1462:3202] InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=739968f7-1aa4-47f1-8d68-55af0ffb428d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 07/11/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: Z77 OC Formula dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd07/11/2013:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77OCFormula:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924859/+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 1938596] Re: Always on top windows obscure context menus and tooltips
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- 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/1938596 Title: Always on top windows obscure context menus and tooltips Status in mutter package in Ubuntu: Won't Fix Bug description: "Always on top" windows are meant to be on top of other non-transient windows (its peers), but they're also on top of other windows' transient GUI components like context menus and tooltips. It is not constructive to obscure menus and tooltips with always on top windows any more than it is helpful to obscure the actual mouse cursor with AOT windows. They are short lived. Users can't decide where to place them. They will disappear by themselves when the user is done with them. A hidden tooltip or context menu helps no one. ubuntu 21.04 gnome wayland --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2020-10-30 (274 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: wl Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: wayland-session hirsute Uname: Linux 5.11.0-25-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-04-23 (99 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1938596/+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 1933890] Re: No wacom tablet or stylus discovered, Fujitsu T935
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-control-center (Ubuntu) Status: New => Won't Fix ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- 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/1933890 Title: No wacom tablet or stylus discovered, Fujitsu T935 Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: I installed Ubuntu 21.04 on my Fujitsu T935, which has a Wacom stylus and screen. The command line seems to find it, and it works fine, but I cannot calibrate it without the gnome-control-center. $ xsetwacom --list devices Wacom MultiTouch Sensor Finger touch id: 10 type: TOUCH Wacom MultiTouch Sensor Pen stylusid: 11 type: STYLUS Wacom MultiTouch Sensor Pen eraserid: 15 type: ERASER Any ideas what to do? Thanks, Rob ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 17:45:08 2021 InstallationDate: Installed on 2021-05-25 (34 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1933890/+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 1929650] Re: Screen doesn't turn off when using Wayland on some devices
** Tags removed: hirsute -- 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/1929650 Title: Screen doesn't turn off when using Wayland on some devices Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: When the screen of my laptop (Thinkpad E480) is supposed to turn off (because of inactivity or when actively locking screen), the screen dims, turns off for a second and then turns back on while remaining dimmed. I can see the backlight of the screen and the cursor. This bug is only present when using a wayland-session regardless of my settings. It also happens with a fresh user account. Additionally, I tested with the 5.8 and 5.12 kernels with the same result. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 26 08:13:27 2021 InstallationDate: Installed on 2021-05-24 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1929650/+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 1918370] Re: 21.04 natural scrolling broken
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: mutter (Ubuntu) Status: Incomplete => Won't Fix -- 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/1918370 Title: 21.04 natural scrolling broken Status in Mutter: Unknown Status in mutter package in Ubuntu: Won't Fix Bug description: Since 20.10 upgrade to 21.04, natural scrolling on touchpad does not follow the "push page up" that natural scrolling did... Super low priority, but here's my uname -a: Linux robsta-zenbook 5.11.2-051102-generic #202103030902 SMP Wed Mar 3 15:50:19 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1918370/+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 1922047] Re: Touchpad scrolling is too fast
** Tags removed: hirsute ** Tags added: jammy ** Tags added: impish ** Tags added: focal -- 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/1922047 Title: Touchpad scrolling is too fast Status in Mozilla Firefox: New Status in GTK+: Unknown Status in Mutter: Unknown Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: This is an issue which has troubled me for a while. Anecdotally, scrolling feels way too fast in GNOME on Wayland compared to on X11. I finally tested it semi-scientifically, and it seems like GNOME on Wayland scrolls almost exactly 1.5x faster than GNOME on X11. I tested this by testing how many lines are scrolled from a full two- finger touchpad swipe from the bottom of my touchpad to the top of my touchpad, and logged a few attempts in both X and Wayland. I kept track of the results in this spreadsheet: https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing I scrolled in one of my own GTK applications (https://github.com/mortie/lograt) because it lets me easily see how many lines I scrolled. Attach is a video of one full scroll on X11 and one full scroll on Wayland. This testing was performed on a Dell XPS 13 9343, but I've also used Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way too fast. I don't have other hardware to test on. This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 31 11:44:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-21 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1922047/+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 1933186] Re: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from met
** Tags removed: hirsute -- 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/1933186 Title: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement() Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter package in Fedora: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7ae33f650c2de2c5580905f0c63e5b6c35fb46c6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1933186/+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 1927276] Re: Drag-and-drop from Nautilus causes Mutter to close Wayland connections
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- 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/1927276 Title: Drag-and-drop from Nautilus causes Mutter to close Wayland connections Status in Mutter: Unknown Status in mutter package in Ubuntu: Won't Fix Bug description: When dragging a file from Nautilus to another window (either another Nautilus window or a GNOME Terminal window), and you hold down the alt key while dropping, Mutter closes the connection to the target application (which GDK handles by calling `_exit(1)` unconditionally). When the target application is a GNOME Terminal window, the entire GNOME Terminal Server exits, so all terminal windows close. This is likely to lead to data loss (I have personally experienced having many very important terminal windows with neovim just close because I dared to drag and drop a file into another terminal window instead of typing out the path). I made an issue upstream: https://gitlab.gnome.org/GNOME/mutter/-/issues/1789, but I thought it should be in Launchpad as well. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mutter 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed May 5 22:12:37 2021 InstallationDate: Installed on 2019-11-21 (530 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: Upgraded to hirsute on 2021-03-16 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1927276/+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 1938867] Re: Logitech K400R keyboard not entering text into input fields on Raspberry Pi 4 in Wayland sessions
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix -- 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/1938867 Title: Logitech K400R keyboard not entering text into input fields on Raspberry Pi 4 in Wayland sessions Status in mutter package in Ubuntu: Won't Fix Bug description: I am running Hirsuite on a Raspberry Pi 4. My main keyboard for this (TV) machine is a wireless Logitech K400r combined keyboard/trackpad. When I first installed, I do not think there were any issues with the keyboard. When I did updates, my keyboard half-stopped working. It is very odd -- the keyboard is obviously working, as I can enter in my password on the lock screen or press Ctrl+Alt t for a terminal, but then I cannot enter anything into the terminal, Firefox input fields or anything else. Even more strangely, when I attach a second USB keyboard, both that new keyboard and my K400r work perfectly.When I unplug the USB keyboard, it stops working again. I'm not sure where this problem is, but: $ apt policy xserver-xorg-input-all xserver-xorg-input-all: Installed: 1:7.7+22ubuntu1 Please let me know if I can provide anything further to help diagnose this. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg-input-all 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-1015.16-raspi 5.11.22 Uname: Linux 5.11.0-1015-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 4 08:46:44 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1280x720M@60 smsc95xx.macaddr=E4:5F:01:48:E1:03 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1938867/+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 1930567] Re: Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions
** Tags removed: hirsute -- 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/1930567 Title: Popup menus don't appear at all if opened close to inter-monitor boundaries in Wayland sessions Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: I have two (hopefully related) problems with popup-menus for applications on an external monitor. For background I have two displays, the first a builtin LCD panel, the second and HDMI connected LCD monitor. The external monitor is stacked "above" the internal LCD panel, the internal LCD panel is the "primary" display from a where the dash et al are placed. The first issue occurs with gnome-terminal. When using right-click on an element in the window such as a link, a menu is shown to allow OpenURL et al. This menu will not appear when the link it too close to the bottom of the upper display (the external one); the cursor changes to the arrow menu item selector cursor but not menu is rendered. This occurs regardless of whether the window is maximised and it related to proximity to the boundary of the display. It behaves correctly at the bottom boundary of the lower display. Two screenshots attached showing it working/not-working. The second issue occurs in firefox. When it is rendered on the upper displays its internal menus are displayed at the top of the lower display rather than on the upper display rooted at the menu item itself. This also does not occur on the lower display. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1930567/+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 1872230] Re: The left Ctrl key does not work with key combos when using pointer location in Xorg sessions
** Tags removed: hirsute -- 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/1872230 Title: The left Ctrl key does not work with key combos when using pointer location in Xorg sessions Status in mutter package in Ubuntu: Triaged Bug description: I am using 20.04 Focal. I am using a US international keyboard layout with dead keys, so that I can enter text in many different languages. After I had rebooted my system today and so loaded the newest GNOME Shell, the left Ctrl key stopped working in the terminal windows and also in emacs, while the right Ctrl still works. To get the left Ctrl working again I have to switch to a plain US English keyboard layout, without dead keys. I have also tried the different alternatives of US International keyboard layouts, each of them seems to work as intended but the left Ctrl key is not working. Only with plain US English layout I get the left Ctrl working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1872230/+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 1917939] Re: Windows maximise underneath dock after monitor sleep
** Tags removed: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1917939 Title: Windows maximise underneath dock after monitor sleep Status in Dash to dock: New Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock. If I switch to the application in question, unmaximise and re- maximise, it goes back to maximising inside the usable area of my desktop. But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 19:21:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-11 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+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 1870597] Re: libinput says "your system is too slow"
** Tags removed: hirsute -- 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/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Unknown Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5570 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+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 1882291] Re: Gnome Shell clock is truncated/corrupt on the right side
** Tags removed: hirsute -- 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/1882291 Title: Gnome Shell clock is truncated/corrupt on the right side Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: When clock changes value, it doesn't displaying time properly To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1882291/+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 1923431] Re: Chrome/Chromium is composited slower without "system title bar and borders"
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released ** Changed in: mutter (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1923431 Title: Chrome/Chromium is composited slower without "system title bar and borders" Status in Mutter: Unknown Status in chromium-browser package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Won't Fix Bug description: Chrome/Chromium is composited slower without "system title bar and borders". I had a feeling I could see a difference on my 4K monitor and weak Intel GPU. Enabling "Use system title bar and borders" eliminated stutters and gave me a smoother experience. So now I've taken some measurements from gnome-shell (CLUTTER_SHOW_FPS=1) running Chromium, not stuttering but playing a smoothly rendered video: --- Xorg Use system title bar and borders ON: *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.0ms, peak: 2.8ms *** X11 screen frame timings over 1.0s: 60.03 FPS, average: 0.9ms, peak: 2.4ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.0ms, peak: 2.2ms *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.3ms, peak: 2.9ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.5ms, peak: 2.9ms Use system title bar and borders OFF: *** X11 screen frame timings over 1.0s: 56.92 FPS, average: 3.8ms, peak: 5.7ms *** X11 screen frame timings over 1.0s: 59.94 FPS, average: 3.9ms, peak: 5.5ms *** X11 screen frame timings over 1.0s: 60.11 FPS, average: 3.7ms, peak: 4.6ms *** X11 screen frame timings over 1.0s: 59.98 FPS, average: 3.8ms, peak: 4.8ms *** X11 screen frame timings over 1.0s: 60.00 FPS, average: 3.9ms, peak: 5.4ms --- Xwayland Use system title bar and borders ON: *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 0.9ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 58.95 FPS, average: 1.2ms, peak: 2.0ms *** DP-2 frame timings over 1.0s: 60.02 FPS, average: 1.0ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.0ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 60.05 FPS, average: 1.0ms, peak: 1.7ms Use system title bar and borders OFF: *** DP-2 frame timings over 1.0s: 56.99 FPS, average: 1.4ms, peak: 2.9ms *** DP-2 frame timings over 1.0s: 58.98 FPS, average: 1.7ms, peak: 2.7ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.5ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 58.04 FPS, average: 1.5ms, peak: 2.6ms *** DP-2 frame timings over 1.0s: 59.99 FPS, average: 1.3ms, peak: 2.5ms To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1923431/+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 1896627] Re: Windows flicker when being resized with the mouse (Xorg sessions)
I haven't seen this in 9 months or so, so incomplete again. ** Tags removed: hirsute ** Changed in: mutter (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1896627 Title: Windows flicker when being resized with the mouse (Xorg sessions) Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: When resizing a window with the mouse by dragging the edge or corner, the window begins to flicker. It only flickers when actively being resized, and when I stop dragging, it looks normal. This behavior is does not occur on same pc in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Sep 22 10:21:51 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231] InstallationDate: Installed on 2020-09-22 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200921) MachineType: LENOVO 20FJS0AJ00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET26W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FJS0AJ00 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.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T560 dmi.product.name: 20FJS0AJ00 dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560 dmi.product.version: ThinkPad T560 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1896627/+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 1919400] Re: Wayland login option is missing if booted with the monitor turned off
** Tags removed: hirsute ** Tags added: jammy -- 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/1919400 Title: Wayland login option is missing if booted with the monitor turned off Status in gdm3 package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: Wayland sessions are missing/not supported, if booted with the monitor turned off. and the system log suggests why: gnome-shell[1007]: Failed to create backend: No GPUs with outputs found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1919400/+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 1872870] Re: When zoom is enabled, mouse pointer leaves square trails on desktop
** Tags removed: hirsute -- 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/1872870 Title: When zoom is enabled, mouse pointer leaves square trails on desktop Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: Problem: When you turn on Zoom from the Accessibility menu, the mouse leaves square shaped trails as it moves. Steps to Reproduce: 1. Under the Settings applet's Accessibility menu, turn on Zoom. 2. Observe the mouse cursor leaving little square patterns wherever it goes, obscuring whatever you're trying to work on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 21:50:16 2020 InstallationDate: Installed on 2020-01-09 (96 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to focal on 2020-01-24 (82 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1872870/+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 1933996] Re: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27]
** Tags removed: hirsute -- 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/1933996 Title: Alt-tab stops switching windows [JS ERROR: TypeError: window is null _createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27] Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: When a new Wayland session is created from a login, Alt-tab works as expected to change windows. After sometime Alt-tab fails to do anything (super-tab still works to change applications) and the following error is created in syslog: gnome-shell[18]: JS ERROR: TypeError: window is null#012_createWindowClone@resource:///org/gnome/shell/ui/altTab.js:29:27#012_init@resource:///org/gnome/shell/ui/altTab.js:1004:34#012_init@resource:///org/gnome/shell/ui/altTab.js:1045:24#012_init@resource:///org/gnome/shell/ui/altTab.js:568:30#012_startSwitcher@resource:///org/gnome/shell/ui/windowManager.js:2069:24 The only workaround I have found is to logout and log back in, however after some time the error repeats itself. Ubuntu 21.04 gnome-shell: Installed: 3.38.4-1ubuntu3~21.04.1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 10:53:32 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-11 (230 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-27 (62 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933996/+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 951153]
Developing some resiliency and healing whatever open wounds you may have will make it much easier to work on your marriage. https://tutuappx.com/ https://vidmate.onl/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/951153 Title: [Upstream] Can't open XML files larger than 1.1 MB Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.0-2ubuntu1 Candidate: 1:3.5.0-2ubuntu1 Version table: *** 1:3.5.0-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in Writer via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/951153/+attachment/2845961/+files/.xml && lowriter --nologo .xml is the file opens successfully. 4) What happens instead is a window pops up: LibreOffice 3.5 General input/output error. The file was verified a valid one via: http://www.w3schools.com/dom/dom_validate.asp http://www.xmlvalidation.com WORKAROUND: Use AbiWord. apt-cache policy abiword abiword: Installed: 2.9.2+svn20120213-1 Candidate: 2.9.2+svn20120213-1 Version table: *** 2.9.2+svn20120213-1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Fri Mar 9 16:18:43 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120306) ProcEnviron: LANGUAGE=es_CO:es TERM=xterm LANG=es_CO.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/951153/+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 1916255] Re: Caps Lock initially not detected in GNOME password dialogs if you logged in with it on
This doesn't seem to happen anymore in 22.04. Correct me if I am wrong. ** Tags removed: hirsute ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Released -- 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/1916255 Title: Caps Lock initially not detected in GNOME password dialogs if you logged in with it on Status in gnome-shell package in Ubuntu: Fix Released Bug description: Caps lock is not properly detected, for example if you log in with a password that is in upper case, when entering the desktop without deactivating caps lock, when trying to open an encrypted drive whose password is in upper case even though the indicator shows that Caps lock is active and detects it as if it were not. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xwayland 2:1.20.9-2ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Feb 19 09:03:42 2021 DistUpgraded: 2020-10-24 20:57:52,724 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:2ae2] InstallationDate: Installed on 2020-04-09 (316 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Hewlett-Packard CQ2951LA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=f43448ef-2a06-45ab-8bac-fe9e8907ff57 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: Upgraded to groovy on 2020-10-25 (117 days ago) dmi.bios.date: 08/31/2012 dmi.bios.release: 4.6 dmi.bios.vendor: AMI dmi.bios.version: 8.08 dmi.board.asset.tag: 3CR2390SBN dmi.board.name: 2AE2 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02 dmi.chassis.asset.tag: 3CR2390SBN dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.08:bd08/31/2012:br4.6:svnHewlett-Packard:pnCQ2951LA:pvr1.00:rvnPEGATRONCORPORATION:rn2AE2:rvr1.02:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: CQ2951LA dmi.product.sku: H3X53AA#ABM dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916255/+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 1951142] Re: App window jumps between monitors when not even being used
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1951142 Title: App window jumps between monitors when not even being used Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: When using the Wayland session, the screen will sometimes randomly flash (usually after opening an application). After the screen flashes, the open windows will often end up in different positions or in different monitors. Video of the issue is attached. Expected Behavior: For the LibreOffice window to stay on the right monitor and to not change size or position. Actual Behavior: The LibreOffice window opens to the right after I open Lollypop. This issue doesn't exclusively happen while LibreOffice or when opening Lollypop, however, opening Lollypop is one of the most predictable ways to trigger the bug. The majority of the time, the bug occurs in the middle of regular use without me triggering anything. I'm using a dual monitor set-up, with a 2560X1080 monitor at 1x scaling hooked up to a 4K Hi-DPI laptop screen at 2x scaling. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 11:22:32 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:08ac] Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac] InstallationDate: Installed on 2020-11-18 (362 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Precision 5530 2-in-1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2020 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.10 dmi.board.name: 02TH5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:br1.11:svnDellInc.:pnPrecision55302-in-1:pvr:sku08AC:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 2-in-1 dmi.product.sku: 08AC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1951142/+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 1951142] Re: App window jumps between monitors when not even being used
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1951142 Title: App window jumps between monitors when not even being used Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Bug description: When using the Wayland session, the screen will sometimes randomly flash (usually after opening an application). After the screen flashes, the open windows will often end up in different positions or in different monitors. Video of the issue is attached. Expected Behavior: For the LibreOffice window to stay on the right monitor and to not change size or position. Actual Behavior: The LibreOffice window opens to the right after I open Lollypop. This issue doesn't exclusively happen while LibreOffice or when opening Lollypop, however, opening Lollypop is one of the most predictable ways to trigger the bug. The majority of the time, the bug occurs in the middle of regular use without me triggering anything. I'm using a dual monitor set-up, with a 2560X1080 monitor at 1x scaling hooked up to a 4K Hi-DPI laptop screen at 2x scaling. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 16 11:22:32 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:08ac] Subsystem: Dell Polaris 22 MGL XL [Radeon Pro WX Vega M GL] [1028:08ac] InstallationDate: Installed on 2020-11-18 (362 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Precision 5530 2-in-1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2020 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.10 dmi.board.name: 02TH5P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.10:bd07/09/2020:br1.11:svnDellInc.:pnPrecision55302-in-1:pvr:sku08AC:rvnDellInc.:rn02TH5P:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 2-in-1 dmi.product.sku: 08AC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1951142/+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 1948612] Re: gnome-shell crashed with SIGSEGV in std::__uniq_ptr_impl::_M_ptr from std::unique_ptr::get from std::unique_ptr::operator bool from GjsMaybeOwned::get
** Tags removed: groovy hirsute ** Tags added: jammy -- 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/1948612 Title: gnome-shell crashed with SIGSEGV in std::__uniq_ptr_impl::_M_ptr from std::unique_ptr::get from std::unique_ptr::operator bool from GjsMaybeOwned::get Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8881ba9950cb2700ff108d1d2f7a557229355321 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948612/+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 1942066] Re: Fractional scaling with 2 UHD and one QHD screen renders gnome-panel too short, and mouse pointer is off as well
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix ** Changed in: gnome-shell-extension-dash-to-panel (Ubuntu) Status: New => Won't Fix -- 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/1942066 Title: Fractional scaling with 2 UHD and one QHD screen renders gnome-panel too short, and mouse pointer is off as well Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Status in gnome-shell-extension-dash-to-panel package in Ubuntu: Won't Fix Bug description: Initially posted here https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/4585#note_12590270 Affected version Ubuntu 21.04 5.11.0-31-generic GNOME Shell 3.38.4 Tested on Wayland Bug summary With 2 UHD screens(3840x2160) and one QHD screen(2560x1440), the fractional scaling of the two UHD screens to 125 percent results in the gnome shell panels to be too short in width on the right side. The panel does not reach the end of the screen on the right side on the UHD monitor. The panel on the QHD monitor is fine. Also the mouse hovers the wrong icons, the position is translated to the left of the actual position. In the screenshots, the actual mouse pointer hovers on the bottom panel settings icon, but clicks would be registered on the icon left to it. The offset increases as the mouse moves to the right. All other applications are unaffected and work fine (Nautilus, browser, etc.). It just affects the gnome-shell. The bug does not occur when: I use fractional scaling on just the two UHD screens (QHD monitor disconnected). When I use fractional scaling to 150 percent on the two UHD screens. This results in the same relative size to the QHD screen. Steps to reproduce Connected one UHD and one QHD screen. Set the UHD screen to fractional scaling of 125 percent. Look at the gnome panels. Move your mouse over the panels and see the wrong icons being highlighted. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell-extension-ubuntu-dock 69ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 30 11:33:44 2021 InstallationDate: Installed on 2021-01-05 (236 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: Upgraded to hirsute on 2021-05-12 (109 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1942066/+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 1947832] Re: gnome-shell crashed with SIGSEGV in gjs_value_from_g_argument from gjs_array_from_g_list from gjs_value_from_g_argument from Function::invoke from Function::call
** Tags removed: hirsute -- 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/1947832 Title: gnome-shell crashed with SIGSEGV in gjs_value_from_g_argument from gjs_array_from_g_list from gjs_value_from_g_argument from Function::invoke from Function::call Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/501ff55393b0cd5e224d7b92171e685686f55847 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947832/+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 1938352] Re: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch inpu
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- 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/1938352 Title: [wayland] gnome-shell elements (dock, top bar, on-screen keyboard) becomes unresponsive to touch / mouse while windows & desktop are still responsive to touch input Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Further detailed information filed in gnome-shell bug filing: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4508#note_1213365 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 28 17:56:57 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-15 (13 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1938352/+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 1946300] Re: gnome-shell crashed with SIGSEGV in meta_wayland_shell_surface_close() from meta_wayland_surface_delete() from meta_window_wayland_delete() from meta_window_delete
** Tags removed: hirsute -- 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/1946300 Title: gnome-shell crashed with SIGSEGV in meta_wayland_shell_surface_close() from meta_wayland_surface_delete() from meta_window_wayland_delete() from meta_window_delete() from ffi_call_unix64() Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4a17f73a842e3285a54a0c5b552d2c6a7dfd9be0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946300/+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 1942655] Re: Minimized windows stay ghosted on the background wallpaper
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1942655 Title: Minimized windows stay ghosted on the background wallpaper Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Hello, the problem that I am presented with is basic, but quite annoying. At any time without any type of pattern, when minimizing a window (of any program), these remain as "background", and become part of the wallpaper. You do not interact with it but it remains static on the site. I attach an example. The only temporary solution that has worked for me is to log out, but it almost certainly happens again. I appreciate the help :) (The theme has nothing to do with it, it happens to me even though it is stock) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 17:12:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-28 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1942655/+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 1947685] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_width(texture = NULL) from get_buffer_width() from get_buffer_width() from meta_wayland_surface_get_width() fr
** Tags removed: hirsute -- 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/1947685 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_width(texture = NULL) from get_buffer_width() from get_buffer_width() from meta_wayland_surface_get_width() from meta_wayland_surface_get_width() Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/7fa09adf57bf9e8d35fbe3a152ee4110a1e2e174 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1947685/+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 1947315] Re: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_pa
** Tags removed: hirsute -- 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/1947315 Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from st_theme_node_transition_get_paint_box() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/9e0eb2f488ad83e41a8977709955a661857ba95e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1947315/+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 1866999] Re: gnome-calendar does not sync with Google Calendar
Also on 21.10 sync does not work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1866999 Title: gnome-calendar does not sync with Google Calendar Status in gnome-calendar package in Ubuntu: Confirmed Bug description: Since upgrading to 20.04dev, gnome-calendar doesn't show the events in my Google Calendar. Online accounts is activated and, for example, gnome-contacts does show the contacts I have in Google. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-calendar 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 09:47:25 2020 InstallationDate: Installed on 2018-02-23 (746 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to focal on 2020-03-01 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1866999/+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 1937958] Re: gnome-shell gdb instructions cause immediate "Oh no" crash
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- 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/1937958 Title: gnome-shell gdb instructions cause immediate "Oh no" crash Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Bug description: I wanted to report a gnome-shell bug with a backtrace, so tried to use the instructions in https://wiki.gnome.org/Projects/GnomeShell/Debugging which say to do the following in an ssh login or separate VT: gnome_session=$(pgrep -u $USER gnome-session) eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DISPLAY) eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep XAUTHORITY) eval export $(sed 's/\o000/\n/g;' < /proc/$gnome_session/environ | grep DBUS_SESSION_BUS_ADDRESS) gdb ...etc... However three problems came up, two minor (wrong instructions), the other major: (1) There is more than one gnome-session process, and so the shell variable $gnome_session gets set to a list of several PIDs, which in turn causes syntax errors when using the expression "/proc/$gnome_session/environ". In Ubuntu 21.04 I have three gnome-session processes immediately after rebooting and logging in (I have auto-login enabled, so the login happens by itself, in case that matters): $ ps -F $(pgrep -u $USER gnome-session|perl -p -e 's/(\d+)/-p $1/') UID PIDPPID CSZ RSS PSR STIME TTY TIME CMD jima97439725 0 55216 16084 2 13:41 tty3 00:00:00 /usr/libexec/gnome-session-binary --systemd --session=ubuntu jima98288066 0 24031 6148 8 13:41 ?00:00:00 /usr/libexec/gnome-session-ctl --monitor jima98388066 0 129272 18176 7 13:41 ?00:00:00 /usr/libexec/gnome-session-binary --systemd-service --session=ubuntu (2) The instructions specify this gdb command: call gjs_dumpstack () However that results in an error and the call is not made: 'gjs_dumpstack' has unknown return type; cast the call to its declared return type (3) Most importantly, a crash: Immediately upon starting the new gnome-shell process (with option --replace) a white screen appears with "Oh No... something went wrong..." forcing me log out. The crash happens whether using an independent VT or an ssh login. Afterwards I typed Control-C to get control in gdb, and produced the attached backtraces but they don't seem useful (see attached typescript file). /var/syslog might be useful. I will attach the portion beginning just before starting the new gnome-shell The attached typescript file shows what I did to circumvent the buggy instructions at https://wiki.gnome.org/Projects/GnomeShell/Debugging P.S. The original crash I wanted to report was that opening any .jpg in gimp and selecting part of the image and then doing Select->Invert instantly freezes the system. The only recovery is to use a separate VT to kill the gimp process, after which gnome-shell restarts. A system error dialog appears saying gnome-session [correction: gnome- shell] got a segfault somewhere; thus the desire to get a backtrace. But this bug report is _not_ about that bug, but is about how using the debug instructions in the wiki are incorrect and when fixed seem to cause a crash on their own. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Jul 25 13:41:54 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-20 (5 days ago) InstallationMedia: Ubuntu-Server 21.04 "Hirsute Hippo" - Release amd64 (20210421) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1937958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1947132] Re: [nvidia] gnome-shell crashed with SIGSEGV in XRRGetCrtcInfo() from update_outputs() from _cogl_xlib_renderer_connect() from _cogl_winsys_renderer_connect() from co
** Tags removed: artful cosmic hirsute -- 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/1947132 Title: [nvidia] gnome-shell crashed with SIGSEGV in XRRGetCrtcInfo() from update_outputs() from _cogl_xlib_renderer_connect() from _cogl_winsys_renderer_connect() from connect_custom_winsys() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/2acefc8fc5476d2f02ae266fe5892dd8bffc1fed contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1947132/+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 1928317] Re: window focus is lost after blank screen
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mutter (Ubuntu) Status: Confirmed => Won't Fix -- 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/1928317 Title: window focus is lost after blank screen Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: New in 21.04 hirsute default installation, the problem was not there in 20.10 . Environment: the default Wayland (source of other trubles as well, the most disturbing out of them is https://bugs.launchpad.net/ubuntu/+bug/1925732) and the Gnome shell Problem steps: (1) there are few windows on my screen and the focus is in one of them, I edit there something, (2) after 5 minutes of user inactivity the screen blanks, (3) I wish to resume the editing in the same window, hence I hit either a ctrl or shift key, or slightly move the mouse, (4) the view comes back, but none of the windows have the input focus! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1928317/+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 1933799] Re: gnome-shell crashed with SIGSEGV in rescan_icon_theme() from installed_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist()
** Tags removed: hirsute -- 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/1933799 Title: gnome-shell crashed with SIGSEGV in rescan_icon_theme() from installed_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/0743486472675f657b0ac6603c8e0fda941d5c40 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1933799/+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 1916814] Re: gnome-shell crashed with SIGSEGV in meta_workspace_index() from meta_workspace_activate_with_focus() from ffi_call_unix64() from ffi_call_int() from gjs_invoke_c_f
Zero crashes after 21.04 so consider it fixed. ** Changed in: gnome-shell (Ubuntu) Status: New => Fix Released -- 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/1916814 Title: gnome-shell crashed with SIGSEGV in meta_workspace_index() from meta_workspace_activate_with_focus() from ffi_call_unix64() from ffi_call_int() from gjs_invoke_c_function() Status in gnome-shell package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.2-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/28cc92eb593f6277a02bec4fba68d499e8a79f53 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916814/+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 1920718] Re: gnome-shell crashed with SIGSEGV in js::gc::CellHeaderWithTenuredGCPointer from JSObject::groupRaw from JSObject::isSingleton from js::TypeSet::ObjectType from js:
** Tags removed: hirsute -- 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/1920718 Title: gnome-shell crashed with SIGSEGV in js::gc::CellHeaderWithTenuredGCPointer from JSObject::groupRaw from JSObject::isSingleton from js::TypeSet::ObjectType from js::TypeSet::GetValueType Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.3-3ubuntu1, the problem page at https://errors.ubuntu.com/problem/0a21e8bd45695d98b43a284c99e84988965a41ec contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1920718/+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 1933027] Re: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled
** Tags removed: hirsute -- 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/1933027 Title: Gdm3 with smartcard asks for login/smartcard pin even if there is no smartcard authentication enabled Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I use my Ubuntu PC with Yubikey almost always plugged in. It provides several security token interfaces, such as U2F, GPG smartcard, proprieritary Yubico interfaces (of which I mostly use TOTP codes), and also PIV smartcard. However, I haven't configured a PIV smartcard on it. Whenever I login into the system having Yubikey plugged in, I'm prompted for login name, and then for PIN for some smartcard while also being asked to plug in one. This is very misleading on several layers: 1. I have the device providing smartcard plugged id, 2. But it's not the smartcard GDM would think it is as it's not configured properly, 3. There are no local smartcard-authenticating users right now in the system, 3. There are no remote authentication systems configured on the system (so no ActiveDirectory-smartcard logins or such). If I unplug the token UX goes back on old good track. Given the circumstances above, I'd consider that GDM (and, on my bet, any PAM configuration it uses) shouldn't offer to login using smartcard if there is no way to actually do so. I feel something is off here, so I'm reporting a bug. It could be an upstream problem though; it also could be an upstream SSSD problem, or all combined. I believe there is a more clear user experience: 1. GDM should display users that can login into the system, as it always does (if configured). It may also provide entering other login name (also if configured). This is GDM usually does without smartcards altogether. 2. When user is chosen (from the list or manually typed in), check can this user even authenticate with smartcards (i.e. if any of available smartcards is actually recognised for this user). If so, then ask for PIN. Else, don't show anything about smartcards at all (this includes when SSSD is not configured for any AD or related and this user has no local smartcard configuration). This can switch there & back based on device events. I've seen other OS doing this. Ubuntu/Gnome session doesn't ask me for PIN for a smartcard on a lock screen, so I guess it doesn't support it at all or correctly finds out it can't be used. Even more, I couldn't find a way to actually add my smartcard as a local login method. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 14:02:02 2021 InstallationDate: Installed on 2017-03-05 (1567 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-05-13 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1933027/+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 1934457] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from sig
** Tags removed: hirsute ** Tags removed: kylin-21.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/1934457 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/eca665045730307781118f49eecca44ef0b9ea17 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1934457/+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 1857392] Re: Window manager warning: Overwriting existing binding of keysym...
** Tags removed: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1857392 Title: Window manager warning: Overwriting existing binding of keysym... Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) No error. 4) Error in Ubuntu Logs App. Sender: gnome-shell Message: 4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 GMT-0600 (CST) 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Audit Session: 2 Priority: 6 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+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 1926799] Re: Cursor is not rendered in the correct location when at maximum desktop zoom
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- 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/1926799 Title: Cursor is not rendered in the correct location when at maximum desktop zoom Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Affected version LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Gnome Version: 3.38.4 Occurs in: Xorg and Wayland Bug summary 1. zoom focus shifts - lets assume a window in the center of the screen and i am at 3x zoom and i try to point my mouse at something and try to click that. 90% of the time zoom focus shifts away from the mouse location to mostly top left corner of the screen. 2. mouse pointing away from the object - Similarly when i reach above some zoom limit sets say 4x and now lets say i am in a browser trying to click a link i point at the link cursor changes to hand and when i try to click i couldnt. So i try to zoom out and i fid that the pointer was not exactly placed on the link. To sum up when zoomed in it seems like i am pointing at a link while the cursor is actually placed away from the link 3. Compressing text - after reaching certain high zoom level as said 4x or 5x the content on the screen becomes a bit compressed on the sides texts and images and everything on screen becomes elongated Steps to reproduce 1. Turn on zoom from settings -> Accessibility 2. Zoom in above 3.x 3. Try clicking on some object inside a window 4. Choose Follow mouse cursor or on screen part droopdown choose full screen. 5. My current settings are Screen part: Full Screen, Magnifier cursor pushes content arround. However these issues persist with all the other options under magnifier position. Such as Follow mouse cursor or magnifier cursor pushes content arround or any such option provided. Screenshot_from_2021-05-03_14-37-09 What happened 1. Zoom focus shifts away from the cursor mostly towards top left of the window or the desktop. 2.While zoomed in cursor seems to be placed above a link or an object but is actually placed awway either to the left or right of the object. Original position of the cursor reveals when zoomed out. 3.Content on screen seems to be compressed from the sides as text and other objects appear elongated. I have also posted the same issue on the GNOME Community: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4228 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.04 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.38.4-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 Tags: wayland-session hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1926799/+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 1927948] Re: Windows switch monitor after resuming from sleep
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mutter (Ubuntu) Status: Confirmed => Won't Fix -- 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/1927948 Title: Windows switch monitor after resuming from sleep Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: What I expect: Window layout/positioning is identical after resume from sleep. What I observe: After resume from sleep, windows appear on a different monitor than before. I found this possibly relevant GNOME bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mutter 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 10 13:40:28 2021 InstallationDate: Installed on 2019-12-02 (524 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1927948/+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 1930371] Re: top bar displayed on top of a fullscreen window that gets moved from one monitor to another
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Won't Fix -- 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/1930371 Title: top bar displayed on top of a fullscreen window that gets moved from one monitor to another Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Bug description: I have two monitors: the laptop's internal one (primary), and an external LCD positioned above the it. I have configured mpv to be the default video player in Nautilus. I have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'. Steps to reproduce: - click on a video file in Nautilus - mpv is launches in fullscreen mode on the external monitor - drag the mpv window with the mouse to the internal monitor Expected behavior: - mpv is fullscreen on the internal monitor Actual behavior - mpv is fullscreen, but the gnome-shell top bar is displayed on top of the video Workaround: hit twice. Alternative workaround: alt-tab so a different window is on top of mpv then alt-tab back. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 1 10:02:15 2021 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (719 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-23 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1930371/+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 1923075] Re: Unmaximizing a window by dragging is buggy
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: mutter (Ubuntu) Status: Confirmed => Won't Fix -- 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/1923075 Title: Unmaximizing a window by dragging is buggy Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: The unmaximize animation does not play correctly (only "slides" but does not "scale"). Note that unmaximizing by using the maximize button or alt+f10 works correctly. Also X applications such as xterm unmaximize correctly when dragged off from the top bar. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 17:42:01 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:5024] InstallationDate: Installed on 2021-04-06 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) MachineType: LENOVO 80B6QB0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=431ba979-ee7c-490a-b2db-4996f68514e9 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2013 dmi.bios.release: 2.2 dmi.bios.vendor: LENOVO dmi.bios.version: J7ET57WW (2.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 80B6QB0 dmi.board.vendor: LENOVO dmi.board.version: 31900058 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 2.2 dmi.modalias: dmi:bvnLENOVO:bvrJ7ET57WW(2.02):bd11/07/2013:br2.2:efr2.2:svnLENOVO:pn80B6QB0:pvrB5400:rvnLENOVO:rn80B6QB0:rvr31900058STD:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: B5400 dmi.product.name: 80B6QB0 dmi.product.sku: LENOVO_MT_80B6 dmi.product.version: B5400 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1923075/+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 1936703] Re: screen keyboard doesn't work on authentication window
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix -- 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/1936703 Title: screen keyboard doesn't work on authentication window Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Bug description: Before reporting the bug, lets me mention my hate about you, abandoned 'onboard'. Bug description: pressing key on screen keyboard doesn't work on authentication window, until you press [Enter]. See screenshot ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 17 04:41:09 2021 EcryptfsInUse: Yes InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent file=/cdrom/preseed/ubuntu.seed quiet splash --- InstallationDate: Installed on 2021-06-17 (29 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1936703/+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 1934458] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_
** Tags removed: hirsute -- 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/1934458 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/29945d56fd6502de24678bddb8f825c97977fcbb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1934458/+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 1943463] Re: Lock screen notifications break sleep
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix -- 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/1943463 Title: Lock screen notifications break sleep Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Bug description: On Ubuntu 21.04: With pulseaudio lock screen notifications turned on (by default), every time an audio device is added or removed, the screen gets woken up to show the notification. When a monitor goes to sleep, it switches off the HDMI audio channel connected to pulseaudio, which causes a notification, which causes the screen to switch on again. Then the lock screen goes to sleep again after a timeout. Rinse, repeat. Fixed by switching off lock screen notifications for pulseaudio, but this was a head scratcher for a good few months. Suggested fix - don't cause notifications to wake up a monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1943463/+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 1867578] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [asse
** Tags removed: hirsute -- 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/1867578 Title: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from clutter_actor_set_mapped() [assertion failed: (!CLUTTER_ACTOR_IS_MAPPED (self))] Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.35.91-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/be5b3f189bba5293ce040f812f28644f7ba22e17 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867578/+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 1922559] Re: osk: umlauts do not work in password prompts
Thank you for reporting this bug to Ubuntu.
Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Won't Fix
--
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/1922559
Title:
osk: umlauts do not work in password prompts
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Won't Fix
Bug description:
When I try to input a german umlaut like "ü" in a gnome-shell password
prompt using the onscreen keyboard, nothing appears in the input
field. In regular applications like gedit umlauts work however, so it
seems to be specific to password prompts.
Couldn't find anything interesting the the journalctl log, only
messages related to gnome-shell at the time of trying to input the
umlaut are:
Apr 05 14:41:24 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70
Gjs_ui_windowPreview_WindowPreview:last-child ("Loading…")] in window slots
Apr 05 14:41:25 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70
Gjs_ui_windowPreview_WindowPreview:first-child ("Home")] in window slots
Apr 05 14:41:25 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70
Gjs_ui_windowPreview_WindowPreview:last-child ("Home")] in window slots
Apr 05 14:41:25 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70
Gjs_ui_windowPreview_WindowPreview:last-child ("Home")] in window slots
Apr 05 14:41:25 pc gnome-shell[2094]: Couldn't find child [0x55cb1c6ece70
Gjs_ui_windowPreview_WindowPreview:last-child ("Home")] in window slots
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu1
Uname: Linux 5.11.11+ x86_64
ApportVersion: 2.20.11-0ubuntu61
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Mon Apr 5 14:24:19 2021
DisplayManager: gdm3
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1922559/+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 1925683] Re: Cursor Tracking with Gnome Shell Magnifier on Wayland
Thank you for reporting this bug to Ubuntu.
Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.
** Changed in: gnome-shell (Ubuntu)
Status: New => Won't Fix
--
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/1925683
Title:
Cursor Tracking with Gnome Shell Magnifier on Wayland
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Won't Fix
Bug description:
Affected version
GNOME 3.36 - 3.40.
Ubuntu 20.04, 20.10, 21.04 and Fedora 34 Beta.
Wayland only.
Bug summary
When running GNOME shell with Wayland, the cursor and focus tracking
functionality of the magnifier (a11y feature) do not correctly compute the
cursor/focus location. The position is calculated from the top left of the
window but the windows position is not included. This causes the magnifier to
track the wrong location when the window is not maximiser or is on a second
monitor.
I suspect this is related to the way in which wayland is designed. But
my experience in this area is minimal. When using X11 this feature
works correctly.
The wiki page states that under wayland the cursor and focus tracking
work but this information is either out dated or was not tested
correctly.
Steps to reproduce
From the Gnome desktop, open a terminal by pressing ctrl + alt + t or by
opening the activities overlay and searching for "terminal".
Press super + left arrow key to maximize the terminal window on the left side
of the screen.
Activity the magnifier by pressing super + alt + 8.
Type text into the terminal window. The magnified view will move with the
text cursor.
Press super + right arrow key to maximize the terminal windows on the right
side of the screen.
Type text into the terminal. The magnified view will move but it will not
show the text cursor. It will move when text is entered but will focus on the
left side of the screen.
What happened
The magnified view does not follow the text/focus cursor correctly.
What did you expect to happen
The magnified view should follow the cursor and show the cursor as it does
when the widnows is maximized. The correct behaviour can also be seen in Gnome
shell running with X11.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.4-1ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 22 20:55:25 2021
DisplayManager: gdm3
GsettingsChanges:
b'org.gnome.shell' b'command-history' redacted by apport
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2021-04-22 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1925683/+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 1855711] Re: Add keyboard navigation to desktop icons
** Tags removed: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1855711 Title: Add keyboard navigation to desktop icons Status in gnome-shell-extension-desktop-icons: Unknown Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Pressing tab does not allow the user to select UI elements. If tab is pressed "Activities" should be selected. Left or right arrow to select items on Activities bar. If tab is pressed again, select top icon on Dock. Press down arrow to navigate down the dock. Press enter to start app. If tab is pressed instead of enter, Desktop icons should be selected. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1855711/+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 1919377] Re: gnome-shell 3.38+ HUD app grid is limited to only 6x4 or 4x6
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix -- 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/1919377 Title: gnome-shell 3.38+ HUD app grid is limited to only 6x4 or 4x6 Status in gnome-shell package in Ubuntu: Won't Fix Bug description: For some reason after Ubuntu 20.04 (Gnome 3.36) the app grid was limited to a maximum of 4x6. This might be acceptable on an iPhone, which is where they actually got the limit from, but it is not at all acceptable for an actual large computer screen. It looks farcical. Even the spacing prior to Ubuntu 20.10 (Gnome 3.38) was much too wide, but this is MUCH MUCH WORSE. It looks like previously it was limited to only ~ 6x12 which was still pretty bad. See the attached screenshot of what this looks like on Gnome 3.36 vs 3.38. Also notice there is more than one page of apps on 3.38 and that it only shows 4x6 at maximum. 臘 As you will notice this is a 4K screen at 100 dpi, its not a small screen, but is being treated like its a phone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1919377/+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 1922340] Re: GNOME lock screen wallpaper turns black on main display
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix -- 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/1922340 Title: GNOME lock screen wallpaper turns black on main display Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Bug description: 1) Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 2) gnome-shell: Installed: 3.38.4-1ubuntu1 Candidate: 3.38.4-1ubuntu1 Version table: *** 3.38.4-1ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status 3) This bug only appears on Gnome with Wayland. It does not affect Gnome on xorg. After the screen stays off and locked for some time the wallpaper on the main display turns black. It never happens on the secondary display. The issue is also reported, here on gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3206 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 11:50:15 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922340/+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 1908341] Re: gnome-shell crashed with SIGSEGV in get_application_proxy() from g_task_return_now() from g_task_return() from init_second_async_cb() from g_task_return_now()
** Tags removed: hirsute -- 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/1908341 Title: gnome-shell crashed with SIGSEGV in get_application_proxy() from g_task_return_now() from g_task_return() from init_second_async_cb() from g_task_return_now() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.1-1ubuntu1.1, the problem page at https://errors.ubuntu.com/problem/1614f6f99fae747f6d3291c5cdbc46a816cc5025 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908341/+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 1858414] Re: gnome-shell crashed with SIGTRAP in ObjectInstance::disassociate_js_gobject() from std::function::operator() from ObjectInstance::remove_wr
** Tags removed: hirsute -- 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/1858414 Title: gnome-shell crashed with SIGTRAP in ObjectInstance::disassociate_js_gobject() from std::function::operator() from ObjectInstance::remove_wrapped_gobjects_if() from ObjectInstance::update_heap_wrapper_weak_pointers Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/c81c4bee503e4c7ae8551cb68187b7da66472c9b --- This happened after selecting and entering the password of the GDM user. GDM gives the pass to gnome-shell, and it does not start. I reboot the notebook, and it successfully enters gnome-shell --- https://gitlab.gnome.org/GNOME/gnome-shell/issues/2084 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 Uname: Linux 5.4.8-050408-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 6 07:42:52 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-02 (399 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CL.UTF-8 LANGUAGE=es_CL:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to focal on 2018-12-02 (399 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1858414/+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 1937127] Re: Gnome-shell animations smoother when external monitor is connected
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: In Progress => Won't Fix -- 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/1937127 Title: Gnome-shell animations smoother when external monitor is connected Status in gnome-shell package in Ubuntu: Won't Fix Bug description: When no external monitor is connected Gnome Shell activities animation is sluggish. Once an external monitor is connected the animation becomes noticeably smoother. It looks like the OS is not properly responding to the extra processing demands by raising the CPU/GPU performance, and having an external monitor connected somehow triggers a higher performance level. This is on a System76 Darter Pro machine with Intel® Core™ i7-8565U and Intel UHD 620 running Ubuntu 21.04 in Wayland session. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-7620.21~1624379747~21.04~3abeff8~dev-generic 5.11.21 Uname: Linux 5.11.0-7620-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 21 12:51:55 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-07-14 (7 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 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/1937127/+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
** Tags removed: hirsute -- 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: Unknown 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 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 1787049] Re: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event()
** Tags removed: hirsute -- 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/1787049 Title: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() from update_move() from meta_window_handle_mouse_grab_op_event() from meta_display_handle_event() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/5fb0c783621f10ac741a0a841432fcc9a74ca69c --- I did not notice anything, but the system reported a crash. This is a macbookpro14,3 kernel 4.18. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 Uname: Linux 4.18.0-041800-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 14 12:38:19 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-09 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f598429b278 : mov 0x18(%rax),%esi PC (0x7f598429b278) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_unmaximize () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_window_handle_mouse_grab_op_event () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_window_unmaximize() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom chrome-remote-desktop dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1787049/+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 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()
** Tags removed: hirsute -- 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/1702151 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: In Progress Bug description: https://errors.ubuntu.com/problem/7db21198c9a21745b60cc46aabafb2b7e636bf95 --- Todays update had a kernal and my gnome shell update. Happened when I rebooted. I now have a black screen and no panel. Icons are all that shows up on desktop. ProblemType: CrashDistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 3 12:46:31 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: gnome-shell --sm-client-id 102c52716a25d9b2dd1495780366603150001329 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9bec254d5c : movzbl 0x14(%rax),%edx PC (0x7f9bec254d5c) ok source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_theme_get_custom_stylesheets () from /usr/lib/gnome-shell/libgnome-shell.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1702151/+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 1928082] Re: Display freezes and log flooded: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor o
Thank you for reporting this bug to Ubuntu. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell (Ubuntu) Status: New => Won't Fix -- 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/1928082 Title: Display freezes and log flooded: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Won't Fix Bug description: the display freezes when i try minimizing after a very long use time ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 11 13:09:28 2021 DistUpgraded: 2021-04-26 11:56:19,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Failed to execute child process “./xorg_fix_proprietary.py”: Failed to execve: No such file or directory (1)) DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed virtualbox, 6.1.18, 5.8.0-50-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches 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:21f3] InstallationDate: Installed on 2019-06-10 (701 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 23445HU ProcEnviron: LANGUAGE=en_NG:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NG SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=65bd11b5-874d-460b-8539-b2b68af2927a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-26 (15 days ago) dmi.bios.date: 03/06/2014 dmi.bios.release: 2.64 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETA4WW (2.64 ) dmi.board.asset.tag: Not Available dmi.board.name: 23445HU dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrG1ETA4WW(2.64):bd03/06/2014:br2.64:efr1.13:svnLENOVO:pn23445HU:pvrThinkPadT430:rvnLENOVO:rn23445HU:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 23445HU dmi.product.sku: LENOVO_MT_2344 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1928082/+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 1958586] Re: [Atheros AR3012] bluetooth fails shortly after startup
** Summary changed: - bluetooth fails shortly after startup + [Atheros AR3012] bluetooth fails shortly after startup ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1958586 Title: [Atheros AR3012] bluetooth fails shortly after startup Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: On a new install of Ubuntu 21.10 on a new Librem14 laptop, I have a MX Ergo bluetooth mouse which works fine for a couple minutes after fresh startup. Seems like Bluetooth flickers on/off a few times (stutters briefly (half a second or so) and then starts working again. After a few times of that, it fails entirely and the Bluetooth mouse stops working. The touchpad on the laptop controls the mouse just fine. The indicators on the mouse itself show that it is avialable to connect to Bluetooth (slow blinking light on the mouse), but never indicates a valid connection (solid light on the mouse) once connection is lost. I then try to turn Bluetooth on/off from the gnome applet at the top- right of the screen, but regardless of how many times I toggle it on/off, the Bluetooth always appears to stay in the off position. Seems like bluetooth has crashed. Is there a way to monitor bluetooth and confirm if it is still running properly and if not why? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 18:50:10 2022 InstallationDate: Installed on 2022-01-19 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05e3:0749 Genesys Logic, Inc. SD Card Reader and Writer Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M |__ Port 6: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 6, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 6, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 14 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=de2aa352-980b-4e66-b7e1-511ec72cd176 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: 4.14-Purism-1 dmi.board.name: Librem 14 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.14-Purism-1:bd06/18/2021:br4.14:efr0.0:svnPurism:pnLibrem14:pvr1.0:rvnPurism:rnLibrem14:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 14 dmi.product.name: Librem 14 dmi.product.version: 1.0 dmi.sys.vendor: Purism hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:CF:5E:D7:DC:DC ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:2164672 acl:120176 sco:0 events:117 errors:0 TX bytes:5753 acl:42 sco:0 commands:70 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1958586/+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 1958583] Re: entering gnome lockscreen causes astfb displays to hang
While waiting for a kernel fix, this workaround might avoid it: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 in /etc/environment ** No longer affects: gnome-shell (Ubuntu) ** Tags added: jammy ** Tags added: regression-release -- 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/1958583 Title: entering gnome lockscreen causes astfb displays to hang Status in linux package in Ubuntu: Confirmed Bug description: When I install ubuntu-desktop on servers with an AMI BMC, I find a remote desktop running on the BMC's virtual KVM display hangs when I transition to the lock screen. The screen either goes blank and fails to wake up on keyboard/mouse input - or the lock screen appears but freezes, leaving the clock display frozen in time. Correlated with the issue are the following messages in /var/log/syslog, which are emitted when I move the mouse cursor while the lock screen is frozen: Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument A commonality of these systems is that they use the astfb driver. I've found that this issue follows the kernel version. If I run a jammy desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just the kernel back to focal's 5.4, the issue vanishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958583/+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 1958572] Re: kernel bug causing screen corruption on AMD GPU
** Package changed: xorg (Ubuntu) => linux-hwe-5.4 (Ubuntu) ** Tags added: radeon ** Summary changed: - kernel bug causing screen corruption on AMD GPU + [radeon] kernel bug causing screen corruption on AMD GPU -- 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/1958572 Title: [radeon] kernel bug causing screen corruption on AMD GPU Status in linux-hwe-5.4 package in Ubuntu: New Bug description: Hi, I'm running Ubuntu MATE 18.04.6 LTS. The bug information was sadly collected from the working configuration of the system after dropping to an earlier kernel. This bug is a display bug where 1-pixel horizontal lines of multicolored corruption or occasionally incorrect screen contents appear across the screen, particularly during scrolling or moving the mouse. They appear intermittently, being more common near the top of the screen. My GPU is the built-in one on the AMD A10-5750M APU, the Radeon HD 8650G. (Laptop: G505s) I have found that this bug occurs on vmlinuz-5.4.0-96-generic but does not appear to occur on vmlinuz-5.4.0-91-generic when booting with that option in GRUB. I have not yet been able to capture an image of the issue as it becomes difficult to use the system when the bug occurs (though it appears to be fully functional, graphics aside). If very important I can try again later. -Matt ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-91.102~18.04.1-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE Date: Thu Jan 20 14:05:30 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-91-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-94-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-96-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Lenovo Richland [Radeon HD 8650G] [17aa:397c] InstallationDate: Installed on 2019-12-28 (754 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 20255 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=3e3ee235-a725-4a35-a01f-8c156ee072f1 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 83CN53WW(V3.00) dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo G505s dmi.board.vendor: LENOVO dmi.board.version: 3193Std dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G505s dmi.modalias: dmi:bvnLENOVO:bvr83CN53WW(V3.00):bd01/08/2014:svnLENOVO:pn20255:pvrLenovoG505s:rvnLENOVO:rnLenovoG505s:rvr3193Std:cvnLENOVO:ct10:cvrLenovoG505s: dmi.product.family: IDEAPAD dmi.product.name: 20255 dmi.product.sku: LENOVO_MT_20255 dmi.product.version: Lenovo G505s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1958572/+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 1958538] Re: Extreme Screen flickering when setting a non-native resolution
** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - Extreme Screen flickering when setting a non-native resolution + [amdgpu] Extreme screen flickering when setting a non-native resolution -- 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/1958538 Title: [amdgpu] Extreme screen flickering when setting a non-native resolution Status in linux package in Ubuntu: New Bug description: As soon I set the screen resolution to non native (4k laptop display) the screen begins to flicker and horizontal/vertical lines appear. (See attached image) Interestingly this happens only to the internal screen, external monitors work fine. Also during boot (supposedly when the display driver is loaded) severe tearing is visible for brief moment. An issue with the screen itself can be ruled out since there are no issues when running ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Thu Jan 20 15:14:11 2022 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:5094] InstallationDate: Installed on 2022-01-03 (16 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 20XLS0CJ00 ProcEnviron: LANGUAGE=de_CH:de TERM=xterm-256color PATH=(custom, no user) LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-27-generic root=UUID=9b2ef1f6-51f0-4f81-a1cd-0e7a073ff58e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2021 dmi.bios.release: 1.11 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET41W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XLS0CJ00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.11 dmi.modalias: dmi:bvnLENOVO:bvrR1MET41W(1.11):bd09/03/2021:br1.11:efr1.11:svnLENOVO:pn20XLS0CJ00:pvrThinkPadT14Gen2a:rvnLENOVO:rn20XLS0CJ00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XL_BU_Think_FM_ThinkPadT14Gen2a: dmi.product.family: ThinkPad T14 Gen 2a dmi.product.name: 20XLS0CJ00 dmi.product.sku: LENOVO_MT_20XL_BU_Think_FM_ThinkPad T14 Gen 2a dmi.product.version: ThinkPad T14 Gen 2a dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958538/+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 1958592] Re: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent()
This crash appears to be so rare that I can't tell if it was fixed after 20.04 or just too uncommon to be reported yet in newer releases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1958592 Title: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.13-1ubuntu1~20.04.2, the problem page at https://errors.ubuntu.com/problem/0d919d402b708884960b8624a96c568ee5357955 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958592/+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 1958592] Re: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent()
** Summary changed: - /usr/lib/xorg/Xorg:11:mieqEnqueue:queueEventList:QueueKeyboardEvents:xf86PostKeyEventM:xf86PostKeyboardEvent + Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1958592 Title: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.13-1ubuntu1~20.04.2, the problem page at https://errors.ubuntu.com/problem/0d919d402b708884960b8624a96c568ee5357955 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958592/+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 1958444] Re: Xorg sometimes seems to crash when Plover is running
*** This bug is a duplicate of bug 1958592 *** https://bugs.launchpad.net/bugs/1958592 Thanks. That's now being tracked in bug 1958592. Although I don't have any additional info. ** This bug has been marked a duplicate of bug 1958592 Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1958444 Title: Xorg sometimes seems to crash when Plover is running Status in xorg-server package in Ubuntu: Incomplete Bug description: If I'm typing text into an application like gedit or Firefox using Plover, I occasionally get a screen freeze, then a black screen, and then I'm thrown back to the login screen, and all applications seem to get closed. I think I first noticed this in March 2021, but at that time, removing some Plover plugins that I had installed (system switcher and VLC controls) seemed to make it stop happen, at least for a while. There's also been some time in the middle where I rarely used Plover. It seems Plover isn't seeing anything going wrong. I'm using the version of Plover that's in Ubuntu's repositories. But now it seems to happen pretty often again. Symptoms: The crashes only happen when I'm typing text using Plover. At random but pretty frequent times (I think it's more than once every 2000 words), I will press a chord, release it, nothing will happen for a moment (I think I've tried moving the mouse and finding it didn't move), then I briefly get a black screen and then I'm back at the login screen. No sign of being logged in. I can type my password on qwerty, Plover isn't running. And when I'm logged in, all applications, including Plover and the one I was typing into, are closed. System: Ubuntu 20.04.3 LTS Xorg: 1:7.7+19ubuntu14 (if I understood correctly how to get the version number) Other: I got a software update today, and haven't had any crashes today so far, but I'm not sure Xorg was among the updated packages. And once I started typing this report and realized it could theoretically have been fixed today without me noticing, I decided to finish submitting the report so that I don't have to start over typing it. I'm typing it on qwerty so that I don't get any crashes while typing it. I looked through the last part of Xorg0.log right after logging back in after a crash: [ 13245.576] (II) config/udev: Adding input device Corsair Corsair K65 Gaming Keyboard (/dev/input/event14) [ 13245.576] (**) Corsair Corsair K65 Gaming Keyboard: Applying InputClass "libinput keyboard catchall" [ 13245.576] (**) Corsair Corsair K65 Gaming Keyboard: Applying InputClass "system-keyboard" [ 13245.576] (II) Using input driver 'libinput' for 'Corsair Corsair K65 Gaming Keyboard' [ 13245.578] (II) systemd-logind: got fd for /dev/input/event14 13:78 fd 25 paused 1 [ 13245.578] (II) systemd-logind: releasing fd for 13:78 [ 13245.607] (II) config/udev: Adding input device Corsair Corsair K65 Gaming Keyboard (/dev/input/event13) [ 13245.607] (**) Corsair Corsair K65 Gaming Keyboard: Applying InputClass "libinput keyboard catchall" [ 13245.607] (**) Corsair Corsair K65 Gaming Keyboard: Applying InputClass "system-keyboard" [ 13245.607] (II) Using input driver 'libinput' for 'Corsair Corsair K65 Gaming Keyboard' [ 13245.609] (II) systemd-logind: got fd for /dev/input/event13 13:77 fd 25 paused 1 [ 13245.609] (II) systemd-logind: releasing fd for 13:77 [ 13245.646] (II) config/udev: Adding input device Corsair Corsair K65 Gaming Keyboard (/dev/input/event12) [ 13245.646] (**) Corsair Corsair K65 Gaming Keyboard: Applying InputClass "libinput keyboard catchall" [ 13245.646] (**) Corsair Corsair K65 Gaming Keyboard: Applying InputClass "system-keyboard" [ 13245.646] (II) Using input driver 'libinput' for 'Corsair Corsair K65 Gaming Keyboard' [ 13245.648] (II) systemd-logind: got fd for /dev/input/event12 13:76 fd 25 paused 1 [ 13245.648] (II) systemd-logind: releasing fd for 13:76 [ 27639.231] (II) UnloadModule: "libinput" [ 27639.231] (II) systemd-logind: releasing fd for 13:67 [ 27639.363] (II) UnloadModule: "libinput" [ 27639.363] (II) systemd-logind: releasing fd for 13:69 [ 27639.398] (II) UnloadModule: "libinput" [ 27639.398] (II) systemd-logind: releasing fd for 13:70 [ 27639.422] (II) UnloadModule: "libinput" [ 27639.422] (II) systemd-logind: releasing fd for 13:71 [ 27639.442] (II) UnloadModule: "libinput" [ 27639.442] (II) systemd-logind: releasing fd for 13:75 [ 27639.462] (II) UnloadModule: "libinput" [ 27639.462] (II) systemd-logind: releasing fd for 13:65 [ 27639.486] (II) UnloadModule: "libinput" [ 27639.486] (II) systemd-logind: releasing fd for 13:68 [ 27639.506] (II) UnloadModule:
[Desktop-packages] [Bug 1958592] Re: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1958592 Title: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.13-1ubuntu1~20.04.2, the problem page at https://errors.ubuntu.com/problem/0d919d402b708884960b8624a96c568ee5357955 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958592/+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 1958592] [NEW] Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.13-1ubuntu1~20.04.2, the problem page at https://errors.ubuntu.com/problem/0d919d402b708884960b8624a96c568ee5357955 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bionic focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1958592 Title: Xorg crashed with SIGSEGV in mieqEnqueue() from queueEventList() from QueueKeyboardEvents() from xf86PostKeyEventM() from xf86PostKeyboardEvent() Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.13-1ubuntu1~20.04.2, the problem page at https://errors.ubuntu.com/problem/0d919d402b708884960b8624a96c568ee5357955 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1958592/+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 1958435] Re: Icons on Dock get stuck in Dragging Mode
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1958435 Title: Icons on Dock get stuck in Dragging Mode Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 $ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 0.9.1ubuntu18.04.3 Candidate: 0.9.1ubuntu18.04.3 Version table: *** 0.9.1ubuntu18.04.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu bionic/main i386 Packages What I expect to happen: When I drag an icon on the Dock, I expect the dragging to finish once I release the mouse. What happened instead: The icon gets stuck in dragging mode. When my mouse clicks on the icon that was previously dragged, the icon gets stuck to the mouse cursor as if I were dragging it. Related bug reports: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1880764 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-94.106~18.04.1-generic 5.4.157 Uname: Linux 5.4.0-94-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 12:38:15 2022 InstallationDate: Installed on 2019-10-04 (837 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1958435/+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 1958583] Re: entering gnome lockscreen causes astfb displays to hang
** Attachment added: "sosreport-starbuck-2022-01-20-ziauesz.tar.xz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958583/+attachment/972/+files/sosreport-starbuck-2022-01-20-ziauesz.tar.xz -- 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/1958583 Title: entering gnome lockscreen causes astfb displays to hang Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: When I install ubuntu-desktop on servers with an AMI BMC, I find a remote desktop running on the BMC's virtual KVM display hangs when I transition to the lock screen. The screen either goes blank and fails to wake up on keyboard/mouse input - or the lock screen appears but freezes, leaving the clock display frozen in time. Correlated with the issue are the following messages in /var/log/syslog, which are emitted when I move the mouse cursor while the lock screen is frozen: Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument A commonality of these systems is that they use the astfb driver. I've found that this issue follows the kernel version. If I run a jammy desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just the kernel back to focal's 5.4, the issue vanishes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958583/+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 1958586] [NEW] bluetooth fails shortly after startup
Public bug reported: On a new install of Ubuntu 21.10 on a new Librem14 laptop, I have a MX Ergo bluetooth mouse which works fine for a couple minutes after fresh startup. Seems like Bluetooth flickers on/off a few times (stutters briefly (half a second or so) and then starts working again. After a few times of that, it fails entirely and the Bluetooth mouse stops working. The touchpad on the laptop controls the mouse just fine. The indicators on the mouse itself show that it is avialable to connect to Bluetooth (slow blinking light on the mouse), but never indicates a valid connection (solid light on the mouse) once connection is lost. I then try to turn Bluetooth on/off from the gnome applet at the top- right of the screen, but regardless of how many times I toggle it on/off, the Bluetooth always appears to stay in the off position. Seems like bluetooth has crashed. Is there a way to monitor bluetooth and confirm if it is still running properly and if not why? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 18:50:10 2022 InstallationDate: Installed on 2022-01-19 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 05e3:0749 Genesys Logic, Inc. SD Card Reader and Writer Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M |__ Port 6: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 6, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 3: Dev 6, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Purism Librem 14 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=de2aa352-980b-4e66-b7e1-511ec72cd176 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2021 dmi.bios.release: 4.14 dmi.bios.vendor: coreboot dmi.bios.version: 4.14-Purism-1 dmi.board.name: Librem 14 dmi.board.vendor: Purism dmi.board.version: 1.0 dmi.chassis.type: 9 dmi.chassis.vendor: Purism dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvncoreboot:bvr4.14-Purism-1:bd06/18/2021:br4.14:efr0.0:svnPurism:pnLibrem14:pvr1.0:rvnPurism:rnLibrem14:rvr1.0:cvnPurism:ct9:cvr:sku: dmi.product.family: Librem 14 dmi.product.name: Librem 14 dmi.product.version: 1.0 dmi.sys.vendor: Purism hciconfig: hci0: Type: Primary Bus: USB BD Address: 18:CF:5E:D7:DC:DC ACL MTU: 1022:8 SCO MTU: 183:5 DOWN RX bytes:2164672 acl:120176 sco:0 events:117 errors:0 TX bytes:5753 acl:42 sco:0 commands:70 errors:0 syslog: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1958586 Title: bluetooth fails shortly after startup Status in bluez package in Ubuntu: New Bug description: On a new install of Ubuntu 21.10 on a new Librem14 laptop, I have a MX Ergo bluetooth mouse which works fine for a couple minutes after fresh startup. Seems like Bluetooth flickers on/off a few times (stutters briefly (half a second or so) and then starts working again. After a few times of that, it fails entirely and the Bluetooth mouse stops working. The touchpad on the laptop controls the mouse just fine. The indicators on the mouse itself show that it is avialable to connect to Bluetooth (slow blinking light on the mouse), but never indicates a valid connection (solid light on the mouse) once connection is lost. I then try to turn Bluetooth on/off from the gnome applet at the top- right of the screen, but regardless of how many times I toggle it on/off, the Bluetooth always appears to stay in the off position. Seems like bluetooth has crashed. Is there a way to monitor bluetooth and confirm if it is still running properly and if not why? ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluez 5.60-0ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-27.29-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 18:50:10 2022
[Desktop-packages] [Bug 1958583] Re: entering gnome lockscreen causes display to hang
I found that this issue also impacts upstream kernels, so I bisected and found that the problem was introduced in this commit: commit d6ddbd5c97d1b9156646ac5c42b8851edd664ee2 Author: Thomas Zimmermann Date: Thu May 7 11:06:40 2020 +0200 drm/ast: Don't check new mode if CRTC is being disabled I verified that this issue can still be reproduced with current upstream (currently between v5.16 & v5.17-rc1), and that reverting the above patch[*] causes it to go away. [*] The patch doesn't cleanly revert because the underlying code has evolved a bit, but it's straightforward to back out: diff --git a/drivers/gpu/drm/ast/ast_mode.c b/drivers/gpu/drm/ast/ast_mode.c index 956c8982192b..336c545c46f5 100644 --- a/drivers/gpu/drm/ast/ast_mode.c +++ b/drivers/gpu/drm/ast/ast_mode.c @@ -1012,9 +1012,6 @@ static int ast_crtc_helper_atomic_check(struct drm_crtc *crtc, const struct drm_format_info *format; bool succ; - if (!crtc_state->enable) - return 0; /* no mode checks if CRTC is being disabled */ - ast_state = to_ast_crtc_state(crtc_state); format = ast_state->format; ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - entering gnome lockscreen causes display to hang + entering gnome lockscreen causes astfb displays to hang ** Description changed: When I install ubuntu-desktop on servers with an AMI BMC, I find a - remote desktop running over BMC's virtual KVM display hangs when I + remote desktop running on the BMC's virtual KVM display hangs when I transition to the lock screen. The screen either goes blank and fails to wake up on keyboard/mouse input - or the lock screen appears but freezes, leaving the clock display frozen in time. A commonality of these systems is that they use the astfb driver. I've found that this symptom follows the kernel. If I run a jammy desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just the kernel back to focal's 5.4, the issue vanishes. Correlated with the issue are the following messages in /var/log/syslog, which are emitted when I move the mouse cursor while the lock screen is frozen: Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument ** Description changed: When I install ubuntu-desktop on servers with an AMI BMC, I find a remote desktop running on the BMC's virtual KVM display hangs when I transition to the lock screen. The screen either goes blank and fails to wake up on keyboard/mouse input - or the lock screen appears but freezes, leaving the clock display frozen in time. - - A commonality of these systems is that they use the astfb driver. - - I've found that this symptom follows the kernel. If I run a jammy - desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just - the kernel back to focal's 5.4, the issue vanishes. Correlated with the issue are the following messages in /var/log/syslog, which are emitted when I move the mouse cursor while the lock screen is frozen: Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument + + A commonality of these systems is that they use the astfb driver. + + I've found that this issue follows the kernel version. If I run a jammy + desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just + the kernel back to focal's 5.4, the issue vanishes. -- 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/1958583
