[Desktop-packages] [Bug 1924184] Re: drive not showing
Sounds like this is about graphics drivers. This system has an Intel GPU so there are no additional graphics drivers. There is no bug here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Invalid -- 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/1924184 Title: drive not showing Status in Ubuntu: Incomplete Bug description: i coudnt find graphic drive ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 03:35:34 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0844] Subsystem: Dell Jet PRO [Radeon R5 M230 / R7 M260DX / Radeon 520 Mobile] [1028:0844] InstallationDate: Installed on 2021-04-13 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Vostro 3578 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-49-generic root=UUID=7cf915de-bb29-49e2-a9cc-0079efc75ed1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 01Y7V4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd01/09/2020:br1.10:svnDellInc.:pnVostro3578:pvr:rvnDellInc.:rn01Y7V4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3578 dmi.product.sku: 0844 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/+bug/1924184/+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 1925705] Re: 100% cpu
Which process is using 100% CPU? I also wonder if this is related to bug 1924624... ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1925705 Title: 100% cpu Status in Ubuntu: Incomplete Bug description: my spek i5 gen3 ram 8Gb ssd 512 fresh install and my cpu always 100% when open and run apps, like firefox, chrome ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Apr 23 07:15:41 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround 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 2021-04-20 (2 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 2349CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=6e403edb-143d-4aa1-8a31-b84abf6175a9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2019 dmi.bios.release: 2.82 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETC2WW (2.82 ) dmi.board.asset.tag: Not Available dmi.board.name: 2349CTO 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.14 dmi.modalias: dmi:bvnLENOVO:bvrG1ETC2WW(2.82):bd08/07/2019:br2.82:efr1.14:svnLENOVO:pn2349CTO:pvrThinkPadT430:rvnLENOVO:rn2349CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2349CTO dmi.product.sku: LENOVO_MT_2349 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/+bug/1925705/+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 1927019] Re: Xorg freeze
Thanks for the bug report. Next time the problem happens please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Although I notice the attached logs already show your SSD is experiencing hardware errors. You might need to replace the SSD: [ 1633.238345] pcieport 1:e0:06.0: AER: Corrected error received: 1:e1:00.0 [ 1633.238381] nvme 1:e1:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 1633.238384] nvme 1:e1:00.0: device [15b7:5006] error status/mask=0001/e000 [ 1633.238387] nvme 1:e1:00.0:[ 0] RxErr (First) ** Summary changed: - Xorg freeze + System freeze ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1927019 Title: System freeze Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from top to bottom and ubuntu doesn't react to any keyboard shortcut. It's appears, maybe after 2 hours of work. I didn't see this bug with my previous ubuntu 20.10. My computer is a new DELL XPS 13 - intel core i7. I disabled the 4K screen and I am using a resolution 1920x1080. I enabled the night mode. 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 non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 4 00:10:39 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Xe Graphics [1028:0a5c] InstallationDate: Installed on 2021-04-30 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9305 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=37473b6f-8714-4a48-91c1-f6964b09347d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0PPYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd01/13/2021:br1.0:svnDellInc.:pnXPS139305:pvr:rvnDellInc.:rn0PPYW4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9305 dmi.product.sku: 0A5C 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.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/ubuntu/+source/linux/+bug/1927019/+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 1926976] Re: during mouse drag operations I'm getting undesired/unprompted dropping and potentially picking up of something else
It sounds like you are getting spurious mouse button (or even keyboard) events from one of your input devices, which will randomly break drag operations. This does happen to people occasionally and in every case (so far) it turns out to be a broken input device. Please try unplugging all input devices from the machine and then adding them back in one-by-one. Please also try a different mouse if you can, and hit all the keys on your keyboard in case one of them is sticking or causing unwanted events. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1926976 Title: during mouse drag operations I'm getting undesired/unprompted dropping and potentially picking up of something else Status in Ubuntu: Incomplete Bug description: I am not really sure this is an Xorg problem. Since my last system update (upon the system prompting), I think less than a week ago, I have noticed this troubling intermittent behavior. I go to drag (mouse-initiated) a window across some screen distances (between external monitors and my laptop's builtin monitor) the window will get dropped without me releasing the mouse button before arriving at my desired drop point. More than half the times this happens, something will immediately be picked up in a drag operation. Sometimes it is another window that begins being moved. Other times it is a window resize operation that is picked up. A third option is the selection of text. I have noticed that most of the time it is triggered when I am moving rapidly (though no more rapidly than I have done successfully in the past). Sometimes it happens when I pause during the drag operation. It even happens infrequently when I am dragging slowly. Often I can just go back and pick up the window and complete the operation. However, sometimes the problem just keeps happening until I give up and go away for 5 minutes or so. I have a stock configuration of 20.04. I keep it updated and haven't changed anything significant about X, Gnome, etc. I have done a few tweaks, but nothing I can think of that would relate to this problem. My laptop, a Dell XPS 13, uses a USB 3.1 hub and through that drives two monitors via HDMI. My mouse is bluetooth - Logitech MX Vertical. I don't believe I have installed any proprietary drivers. My 3 displays are arranged into an inverted "L" shape, as the laptop display is "below" and identically sized to the 27" monitor "above" it. The other 27" monitor is to the left of the first one. Some, potentially useful, debugging info: $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ bluetoothctl --version bluetoothctl: 5.53 $ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 9C:B6:D0:99:27:2C ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING RX bytes:21743080 acl:954252 sco:0 events:141080 errors:0 TX bytes:6895 acl:169 sco:0 commands:208 errors:0 Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT Name: 'kbuchs' Class: 0x0c010c Service Classes: Rendering, Capturing Device Class: Computer, Laptop HCI Version: 4.2 (0x8) Revision: 0x0 LMP Version: 4.2 (0x8) Subversion: 0x25a Manufacturer: Qualcomm (29) $ bluetoothctl Agent registered [CHG] Controller 9C:B6:D0:99:27:2C Pairable: yes [MX Vertical]# show Controller 9C:B6:D0:99:27:2C (public) Name: kbuchs Alias: kbuchs Class: 0x000c010c Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0535 Discovering: no Advertising Features:
[Desktop-packages] [Bug 1926799] Re: Multiple issues with zoom in accessibility
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1926799 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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: Multiple issues with zoom in accessibility Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete 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 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 1926799] Re: Multiple issues with zoom in accessibility
Please be careful to make each bug report about a single issue in future. The first issue you mention sounds like bug 1925683. Which issue would you like this bug to be about? ** Tags added: zoom ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4228 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4228 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4228 Importance: Unknown Status: Unknown -- 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: Multiple issues with zoom in accessibility Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete 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 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 1926811] Re: After upgrading to 20.04 applications no longer launch from overview
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1926811 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: focal ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1926811 Title: After upgrading to 20.04 applications no longer launch from overview Status in gnome-shell package in Ubuntu: Incomplete Bug description: System info: $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy gnome gnome: Installed: (none) Candidate: 1:3.30+2 Version table: 1:3.30+2 500 500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal/universe amd64 Packages $ apt-cache policy gnome-shell gnome-shell: Installed: 3.36.7-0ubuntu0.20.04.1 Candidate: 3.36.7-0ubuntu0.20.04.1 Version table: *** 3.36.7-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.4-1ubuntu1~20.04.2 500 500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal-security/main amd64 Packages 3.36.1-5ubuntu1 500 500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal/main amd64 Packages $ apt-cache policy ubuntu-desktop ubuntu-desktop: Installed: 1.450.2 Candidate: 1.450.2 Version table: *** 1.450.2 500 500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.450 500 500 http://archive.ubuntu.csg.uzh.ch/ubuntu focal/main amd64 Packages I upgraded my system from 19.10/Eoan to 20.04 and when I go to the overview (Activities menu/hotspot), search an application and click on it it no longer launches. If I right click on it and select "Add to favorites" and then go to the dock and click on it it launches fine. I have not been able to find how to debug this issue but it is very annoying. Someone said it may have to do with the way .desktop files are handled now. Can someone please help? Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926811/+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 1926364] Re: interactive resizes window jumps out of screen
** Changed in: mutter (Ubuntu) Status: New => Fix Released ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1700 https://gitlab.gnome.org/GNOME/mutter/-/issues/1700 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1700 Importance: Unknown Status: Unknown ** Tags added: fixed-in-3.36.8 fixed-upstream ** Also affects: mutter (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Bionic) Status: New => Fix Committed ** No longer affects: mutter (Ubuntu Bionic) ** Also affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Focal) Status: New => Fix Committed -- 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/1926364 Title: interactive resizes window jumps out of screen Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Bug description: Interactively resizing a Wayland window while it resizes itself results in the window jumping out of the screen. This happens on GNOME Shell and pure mutter on the 3.36 branch but has been resolved on newer versions (3.37.1 onwards). See https://gitlab.gnome.org/GNOME/mutter/-/issues/1700 for the mutter upstream bug report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libmutter-6-0 3.36.9-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-51.57~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 27 21:58:40 2021 SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1926364/+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 1926783] Re: [MSI MS-7B98] Sound is faster, high-pitched and distorted
Since you say the current kernel for Ubuntu 20.04 does not have the problem then it is considered Fix Released. If there is a newer kernel that does still have the bug then you should report it upstream, not here. ** Summary changed: - [USB-Audio - Saffire 6 USB, playback] Sound is faster, high-pitched and distorted + [MSI MS-7B98] Sound is faster, high-pitched and distorted ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1926783 Title: [MSI MS-7B98] Sound is faster, high-pitched and distorted Status in linux package in Ubuntu: Fix Released Bug description: It works normally when playing youtube videos, only audio files on PC are a problem. Also, kernel 5.8.0-50-generic does not have this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.11.0-7614.15~1618626693~20.04~ecb25cd-generic 5.11.13 Uname: Linux 5.11.0-7614-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michal 1518 F pulseaudio /dev/snd/controlC2: michal 1518 F pulseaudio /dev/snd/controlC1: michal 1518 F pulseaudio /dev/snd/pcmC1D0p: michal 1518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Fri Apr 30 17:05:38 2021 InstallationDate: Installed on 2021-01-31 (89 days ago) InstallationMedia: SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful Symptom_Card: TU104 HD Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [USB-Audio - Saffire 6 USB, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.80 dmi.board.asset.tag: Default string dmi.board.name: Z390-A PRO (MS-7B98) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd12/25/2019:br5.13:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B98:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnZ390-APRO(MS-7B98):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B98 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926783/+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 1926062] Re: [RTL8821A][ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1926095, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - [RTL8821A][ideapad_bluetooth] I am unable to open/close/connect/scan bluetooth + [hirsute] Can't turn bluetooth on again after turning it off ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1926062 Title: [hirsute] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) 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: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+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 1926121] Re: After suspending, no video signal appears after waking up
** Tags added: regression-release ** Tags added: amdgpu ** Summary changed: - After suspending, no video signal appears after waking up + [amdgpu] After suspending, no video signal appears after waking up ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) -- 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/1926121 Title: [amdgpu] After suspending, no video signal appears after waking up Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: No video signal appears after waking up my computer from suspending it and leaving it in this state for a while. This issue has appeared after upgrading from Ubuntu 20.10 (where suspending and waking up worked flawlessly) to 21.04. The computer in question is a HP Desktop - M01-F0230ng with a Ryzen 5 3400G processor. A similar issue exists with a Lenovo Desktop and a Ryzen 7 4600G. 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] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 07:12:31 2021 DistUpgraded: 2021-04-22 20:20:35,886 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-io-error-quark: Konnte Unterprozess "./xorg_fix_proprietary.py" nicht ausführen: Failed to execve: Datei oder Verzeichnis nicht gefunden (1)) DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:8643] InstallationDate: Installed on 2020-03-28 (393 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200328) MachineType: HP HP Desktop M01-F0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=8fc8c49e-2944-4e22-9137-fd8870710ea3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-04-22 (3 days ago) dmi.bios.date: 11/26/2019 dmi.bios.release: 15.17 dmi.bios.vendor: AMI dmi.bios.version: F.11 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.38 dmi.modalias: dmi:bvnAMI:bvrF.11:bd11/26/2019:br15.17:efr52.38:svnHP:pnHPDesktopM01-F0xxx:pvr:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Desktop PC dmi.product.name: HP Desktop M01-F0xxx dmi.product.sku: 8KX18EA#ABD dmi.sys.vendor: HP 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 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/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1926121/+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 1926244] Re: System Blinking and Menu Closing Autometically
** Tags added: 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/1926244 Title: System Blinking and Menu Closing Autometically Status in xorg-server package in Ubuntu: Incomplete Bug description: This is youtube video of the bug -> https://youtu.be/Kna72p3smqI. Happing on ubuntu 21.04 amd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1926244/+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 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
One possible explanation for this bug: https://gitlab.gnome.org/GNOME/gjs/-/merge_requests/613 -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete 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.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d 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/. Similar errors: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd https://errors.ubuntu.com/problem/e3f9ab8232005403e935c6038edd99f13e609e01 https://errors.ubuntu.com/problem/9d421ecaba25357f5c3ef73f438313e40ac24e77 https://errors.ubuntu.com/problem/42cfd76250a81cca07f8c548ec27e245315b5e01 --- Anyone experiencing this crash reliably, please help us to find its root cause by editing your /etc/environment and adding a line: MUTTER_SYNC=1 and then reboot. Then next time a crash happens please tell us (here) the bug ID or error URL of the new crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+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 1926071] Re: crash in xwl_pointer_warp_emulator_maybe_lock
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1169 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1169 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/-/issues/1169 Importance: Unknown Status: Unknown -- 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/1926071 Title: crash in xwl_pointer_warp_emulator_maybe_lock Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: New Bug description: I got a nonreproducible crash of Xwayland with the following backtrace: ``` #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7f88c73c4859 in __GI_abort () at abort.c:79 #2 0x55dfca054e40 in OsAbort () at ../../../../os/utils.c:1351 #3 0x55dfca05a279 in AbortServer () at ../../../../os/log.c:879 #4 0x55dfca05b0da in FatalError (f=f@entry=0x55dfca080d90 "Caught signal %d (%s). Server aborting\n") at ../../../../os/log.c:1017 #5 0x55dfca052189 in OsSigHandler (unused=, sip=0x7ffc013b4070, signo=11) at ../../../../os/osinit.c:156 #6 OsSigHandler (signo=11, sip=0x7ffc013b4070, unused=) at ../../../../os/osinit.c:110 #7 #8 0x55dfc9ef041e in xwl_pointer_warp_emulator_maybe_lock (warp_emulator=warp_emulator@entry=0x55dfccbf5ce0, xwl_window=, sprite=, x=x@entry=683, y=y@entry=384) at ../../../../../hw/xwayland/xwayland-input.c:2694 #9 0x55dfc9ef3fa1 in xwl_pointer_warp_emulator_warp (y=384, x=683, sprite=, xwl_window=, warp_emulator=0x55dfccbf5ce0) at ../../../../../hw/xwayland/xwayland-input.c:2823 #10 xwl_seat_emulate_pointer_warp (xwl_seat=, xwl_window=, sprite=, x=683, y=384) at ../../../../../hw/xwayland/xwayland-input.c:2823 #11 0x55dfca028da2 in ProcWarpPointer (client=0x55dfcc3e2fc0) at ../../../../dix/events.c:3624 #12 0x55dfca01b564 in Dispatch () at ../../../../dix/dispatch.c:478 #13 0x55dfca01f614 in dix_main (argc=16, argv=0x7ffc013b4788, envp=) at ../../../../dix/main.c:276 #14 0x7f88c73c60b3 in __libc_start_main (main=0x55dfc9eed580 , argc=16, argv=0x7ffc013b4788, init=, fini=, rtld_fini=, stack_end=0x7ffc013b4778) at ../csu/libc-start.c:308 #15 0x55dfc9eed5be in _start () ``` The issue has been reported upstream as: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1169 I am also attaching my apport crash file "_usr_bin_Xwayland.1000.crash" as I cannot see if this has been reported already by apport. I don't see it in the list of my own crash reports as described in https://popey.com/blog/2021/03/finding-ubuntu- crash-reports/. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xwayland 2:1.20.9-2ubuntu1.2~20.04.2 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 13:27:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5034] MachineType: LENOVO 20BUS15H00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=d1694733-96aa-4a12-9c6f-2ed18308ab56 ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2019 dmi.bios.release: 1.37 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BUS15H00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:br1.37:efr1.4:svnLENOVO:pn20BUS15H00:pvrThinkPadT450:rvnLENOVO:rn20BUS15H00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BUS15H00 dmi.product.sku: LENOVO_MT_20BU_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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-v
[Desktop-packages] [Bug 1890891] Re: Dock icons don't appear or appear delayed
VMGuy23, Please open your own bug. ** Summary changed: - Dock icons don't appear or appear delayed + Dock icons don't appear or appear delayed if you have none pinned -- 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/1890891 Title: Dock icons don't appear or appear delayed if you have none pinned Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: when no one program is pinned and no one open dock stop working normally. When I open program it appear only 10 sec later as well for closing. restarting with alt + f2 is solving problem until all programs again unpinned and closed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 16:08:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=bfd431bb-2152-4fc0-98a1-a1e23b252397 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H V2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd12/02/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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-extension-ubuntu-dock/+bug/1890891/+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 1890891] Re: Dock icons don't appear or appear delayed if you have none pinned
... or look at bug 1874578 instead. -- 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/1890891 Title: Dock icons don't appear or appear delayed if you have none pinned Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: when no one program is pinned and no one open dock stop working normally. When I open program it appear only 10 sec later as well for closing. restarting with alt + f2 is solving problem until all programs again unpinned and closed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 16:08:55 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2020-08-07 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. A320M-S2H V2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=bfd431bb-2152-4fc0-98a1-a1e23b252397 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H V2-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd12/02/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H V2 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.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-extension-ubuntu-dock/+bug/1890891/+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: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
I think it's more of a security feature than a bug, so no I don't think it's appropriate to open a bug against the protocol itself. And Ubuntu was not involved in the design of Wayland, so complaining about it here won't achieve much. As a workaround you can: * Use Xorg sessions instead; or * Find a gnome-shell extension that will remember window positions for you; or * Just place windows manually. ** Changed in: gnome-terminal (Ubuntu) Status: Incomplete => Invalid ** Changed in: mutter (Ubuntu) Status: Incomplete => Invalid -- 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: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid 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 1926032] Re: [i915] Screen "disconnects" when updating screen buffer
There certainly are invisible differences between Linux and Windows kernels internally how they implement HDMI signalling. So it is possible Linux is more fragile than Windows in this respect. As such, avoiding the receiver or changing cables might be a workaround. A proper fix in that case would go in the kernel so reassigning there... ** No longer affects: xorg-server (Ubuntu) -- 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/1926032 Title: [i915] Screen "disconnects" when updating screen buffer Status in linux package in Ubuntu: Incomplete Bug description: I have a problem in which the screen will behave as if I pulled the HDMI or turned the computer off (no source) for a few seconds until the screen comes back on again. This happens a lot when I open a new window, moves the mouse after it has been still for a while or I open a new window or move the current window. I can watch a whole movie without this problem but as soon as I pause or touch the controls of VLC or move the mouse the problem reocurr. It seems to be after a certain idle period most of the time, but not always. Sometimes it happens many times in a row. The setup is my home built media PC with intel integrated graphics (i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer AV receiver. I have tried probably every possible resolution and screen update frequency and the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 21:57:54 2021 DistUpgraded: 2020-12-01 07:11:08,428 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation UHD Graphics 630 (Desktop 9 Series) [1849:3e98] InstallationDate: Installed on 2020-12-01 (144 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-12-01 (144 days ago) dmi.bios.date: 05/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.10 dmi.board.name: H310CM-ITX/ac 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.:bvrP4.10:bd05/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH310CM-ITX/ac: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.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/linux/+bug/1926032/+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 1926032] Re: [i915] Screen "disconnects" when updating screen buffer
Most certainly not a problem with hdmi connection. I have had windows installed on the same machine without issues. The behavior is such that it is very clear that as soon as you move the mouse after a period of idle, the problem occurs. Also if the computer receives a notification after a period of idle it occurs. There is a definite link to activity which renders new information on the screen buffer. It can play a movie without a problem on vlc but when I pause, it disconnects the screen (presumably because the "pause" bars appear on the screen). If I right click to add subtitles or change something else in the video it also appears at the exact same time I click. This problem is very repeatable. I can do a phone quality video if that would be of interest. If it was a problem with hdmi it would be more random in behavior and it would be a problem on windows as well. -- 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/1926032 Title: [i915] Screen "disconnects" when updating screen buffer Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a problem in which the screen will behave as if I pulled the HDMI or turned the computer off (no source) for a few seconds until the screen comes back on again. This happens a lot when I open a new window, moves the mouse after it has been still for a while or I open a new window or move the current window. I can watch a whole movie without this problem but as soon as I pause or touch the controls of VLC or move the mouse the problem reocurr. It seems to be after a certain idle period most of the time, but not always. Sometimes it happens many times in a row. The setup is my home built media PC with intel integrated graphics (i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer AV receiver. I have tried probably every possible resolution and screen update frequency and the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 21:57:54 2021 DistUpgraded: 2020-12-01 07:11:08,428 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation UHD Graphics 630 (Desktop 9 Series) [1849:3e98] InstallationDate: Installed on 2020-12-01 (144 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-12-01 (144 days ago) dmi.bios.date: 05/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.10 dmi.board.name: H310CM-ITX/ac 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.:bvrP4.10:bd05/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH310CM-ITX/ac: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.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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:/
[Desktop-packages] [Bug 1925732] Re: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
I do not find how to add "Wayland" to the "affects" list, help please. Thanks. "wayland-protocols (wayland-protocols) (Choose another project) wayland- protocols doesn't use Launchpad to track its bugs. If you know this bug has been reported in another bug tracker, you can link to it; Launchpad will keep track of its status for you." -- 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: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete 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: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
"... this is expected because windows only have control over their size, and NEVER THEIR POSITION, in Wayland" This is really a tragedy. One significant benefit for me of the linux world over the micro and soft world, that I can POSITION the windows of a project from my shell script starting that project or during the project. This is a design bug of Wayland, what needs to be fixed, regardless of the outcome of the test with "Xorg" (I will do after the funeral today). If there was no other protocol, if the Wayland was the only protocol, even in that case this is a very serious design bug. Hence I suggest to add "Wayland" to the "affects" list. Do I have to leave the Wayland world, and switch back to Xorg? But it was told, that Wayland is more advanced, that is the new direction. Is the new direction in 2021 that I can not control the location of a new windows from script? Then why it STILL is allowed, that we can control the location of a new window using a mouse? Is it possibble --- as a further enhancement --- to disable also the window positioning by the mouse? I do not find how to add "Wayland" to the "affects" list, help please. Thanks. -- 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: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete 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 1927026] Re: Monitor Display problem
*** This bug is a duplicate of bug 1924624 *** https://bugs.launchpad.net/bugs/1924624 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1924624, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1924624 After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge) graphics a lot of glitches render screen unusable -- 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/1927026 Title: Monitor Display problem Status in xorg package in Ubuntu: New Bug description: Dual boot OS Windows 7x64 & Ubuntu 20.04 64-bit.While booting everything is OD. But as soon as password is entered, brightness of the screen is so blurred that it is practically impossible to work. Further the problem is common for all programs run on the system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 4 06:49:21 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.8.0-49-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.8.0-50-generic, x86_64: installed GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Foxconn International, Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [105b:0d93] InstallationDate: Installed on 2021-01-24 (99 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: DIGILITE DL-H61MXP. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=d6ed0705-777b-4a1a-9121-6963b7c2d394 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C36DLS09 dmi.board.name: DL-H61MXP dmi.board.vendor: DIGILITE 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.:bvrC36DLS09:bd01/16/2014:br4.6:svnDIGILITE:pnDL-H61MXP.:pvrTobefilledbyO.E.M.:rvnDIGILITE:rnDL-H61MXP:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: DL-H61MXP. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: DIGILITE version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/xorg/+bug/1927026/+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 1927026] Re: Monitor Display problem
*** This bug is a duplicate of bug 1924624 *** https://bugs.launchpad.net/bugs/1924624 ** Package changed: ubuntu => xorg (Ubuntu) -- 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/1927026 Title: Monitor Display problem Status in xorg package in Ubuntu: New Bug description: Dual boot OS Windows 7x64 & Ubuntu 20.04 64-bit.While booting everything is OD. But as soon as password is entered, brightness of the screen is so blurred that it is practically impossible to work. Further the problem is common for all programs run on the system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 4 06:49:21 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.8.0-49-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.8.0-50-generic, x86_64: installed GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Foxconn International, Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [105b:0d93] InstallationDate: Installed on 2021-01-24 (99 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: DIGILITE DL-H61MXP. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=d6ed0705-777b-4a1a-9121-6963b7c2d394 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C36DLS09 dmi.board.name: DL-H61MXP dmi.board.vendor: DIGILITE 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.:bvrC36DLS09:bd01/16/2014:br4.6:svnDIGILITE:pnDL-H61MXP.:pvrTobefilledbyO.E.M.:rvnDIGILITE:rnDL-H61MXP:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: DL-H61MXP. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: DIGILITE version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/xorg/+bug/1927026/+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 1927026] [NEW] Monitor Display problem
You have been subscribed to a public bug: Dual boot OS Windows 7x64 & Ubuntu 20.04 64-bit.While booting everything is OD. But as soon as password is entered, brightness of the screen is so blurred that it is practically impossible to work. Further the problem is common for all programs run on the system. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 4 06:49:21 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.8.0-49-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.8.0-50-generic, x86_64: installed GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Foxconn International, Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [105b:0d93] InstallationDate: Installed on 2021-01-24 (99 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: DIGILITE DL-H61MXP. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=d6ed0705-777b-4a1a-9121-6963b7c2d394 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C36DLS09 dmi.board.name: DL-H61MXP dmi.board.vendor: DIGILITE 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.:bvrC36DLS09:bd01/16/2014:br4.6:svnDIGILITE:pnDL-H61MXP.:pvrTobefilledbyO.E.M.:rvnDIGILITE:rnDL-H61MXP:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: DL-H61MXP. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: DIGILITE version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- Monitor Display problem https://bugs.launchpad.net/bugs/1927026 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- 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 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min
** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min Status in gdm3 package in Ubuntu: Won't Fix Bug description: UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system left idle for ~22min it becomes unresponsive. The system will not take any inputs like from UART, ping ..etc. The system will completely freeze and we need to hard reset the system. It could be possible the system goes to hibernate state and could not able to come out of the state. Dmesg log when system halts/no response on Saber boards (TX2) Ubuntu 19.10 ubuntu ttyAMA0 ubuntu login: ubuntu Password: Last login: Wed Jan 29 20:08:22 PST 2020 on ttyAMA0 Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-26-generic aarch64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan [ +0.732512] audit: type=1400 audit(1580358920.412:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=3087 comm="apparmor_parser" [ +0.64] audit: type=1400 audit(1580358920.412:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=3091 comm="apparmor_parser" [ +0.000168] audit: type=1400 audit(1580358920.412:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3086 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=3086 comm="apparmor_parser" [ +0.000546] audit: type=1400 audit(1580358920.412:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=3085 comm="apparmor_parser" [ +0.06] audit: type=1400 audit(1580358920.412:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=3085 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=3085 comm="apparmor_parser" [ +0.000854] audit: type=1400 audit(1580358920.412:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=3089 comm="apparmor_parser" [ +0.002667] audit: type=1400 audit(1580358920.416:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=3093 comm="apparmor_parser" [ +0.04] audit: type=1400 audit(1580358920.416:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=3093 comm="apparmor_parser" [ +1.382579] igb :92:00.1 enp146s0f1: igb: enp146s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ +0.000299] IPv6: ADDRCONF(NETDEV_CHANGE): enp146s0f1: link becomes ready [ +3.131173] mpt3sas_cm0: port enable: SUCCESS [Jan29 20:36] random: crng init done [ +0.04] random: 7 urandom warning(s) missed due to ratelimiting *[Jan29 20:37] rfkill: input handler disabled* *[Jan29 20:57] PM: suspend entry (deep)* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559/+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 1926070] Re: Please backport Desktop Icons NG to 20.04
On 2021-05-04 03:41, Daniel van Vugt wrote: > That's not a definite comment. More recently than that we found a > few bugs in the extension that I had to try and fix quickly, late in > the cycle. It's my opinion that this extension does not yet qualify > as stable so should not be considered for 20.04.x. Thanks for clarifying. Indeed that speaks for only backporting it without enforcing the change for all 20.04 users. Please disregard my noise above. :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1926070 Title: Please backport Desktop Icons NG to 20.04 Status in Focal Backports: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Bug description: After testing Hirsute for a bit, I am convinced that Desktop Icons NG fixes a large and frustrating usability issue on the LTS desktop. It’s a wonderful restoration of functionality that I still trip over myself expecting from “muscle memory” in 20.04, but being reminded that I can’t do simple things like drag and drop. I have read some others suggestions to just install the extension oneself, and upon investigation, I found that it wasn’t a very clear process. Even Igor at dedoimedo.com had issues with going this route -> https://www.dedoimedo.com/computers/gnome-ding.html 4 . For these reasons, I am hoping that someone out there (hopefully more than one) agrees that replacing the current desktop icons package in 20.04 would only help those on an LTS desktop. As excited as I am for the interim releases (especially concerning Wayland and Pipewire), I don’t want to move away from a well-supported release to have a desktop that we could have (and I feel should have) in 20.04. I know that some work would be involved, but I for one would be very grateful, for what it’s worth. Thanks to all for your time. To manage notifications about this bug go to: https://bugs.launchpad.net/focal-backports/+bug/1926070/+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 1926050] Re: Web benchmark freezing and crashing the system
Next time the problem happens, after rebooting please run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Please also follow these instructions to check for application crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: linux (Ubuntu) => linux-hwe-5.8 (Ubuntu) ** Changed in: linux-hwe-5.8 (Ubuntu) Status: Confirmed => Incomplete ** Summary changed: - Web benchmark freezing and crashing the system + [radeon] Web benchmark freezing and crashing the system ** No longer affects: mesa (Ubuntu) ** No longer affects: wayland (Ubuntu) ** No longer affects: xorg-server (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1926050 Title: [radeon] Web benchmark freezing and crashing the system Status in linux-hwe-5.8 package in Ubuntu: Incomplete Bug description: Expected behavior: perform the "Basemark Web 3.0" benchmark (Firefox 87 and 88), at most a loss of performance. Real behavior: the benchmark completely crashes the system in one of the initial stages (4). The screen presents graphical distortion (it never happens), intense crashes and sometimes it is solved with the automatic suspension of the computer (which remains on at times). But it doesn't usually come back from the crash. The problem happens with the onboard ATI RADEON 3000 (RS780 driver) and it happens in both xorg and wayland. Ubuntu and kernel duly updated to the present date. Crash moment: WebGL 1.0.2 Test (test 4/20); "Loading scene_uv2.DAE" Benchmark website: https://web.basemark.com/ Motherboard: GA78LMT Ubuntu 20.04.2 LTS Kernel 5.8.0-50-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: poe1860 F pulseaudio /dev/snd/pcmC2D0p: poe1860 F...m pulseaudio /dev/snd/controlC0: poe1860 F pulseaudio /dev/snd/controlC1: poe1860 F pulseaudio BootLog: Error: [Errno 13] Permissão recusada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2021-03-25 15:17:02,784 DEBUG /openCache(), new cache size 67025 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2021-03-04 (51 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 Package: xorg-server (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal wayland-session wayland-session ubuntu Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-03-25 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/linux-hwe-5.8/+bug/1926050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-pa
[Desktop-packages] [Bug 1926274] Re: gnome-terminal --geometry option not working properly on Wayland Ubuntu 21.04
*** This bug is a duplicate of bug 1925732 *** https://bugs.launchpad.net/bugs/1925732 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1925732, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1925732 new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal ** Tags added: 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/1926274 Title: gnome-terminal --geometry option not working properly on Wayland Ubuntu 21.04 Status in gnome-shell package in Ubuntu: New Bug description: I want to open a Terminal window and Snap it to the Right half. In Ubuntu 20.10, I was using the following command in Startup Applications - ``` $ gnome-terminal --geometry=91x47+996+8 ``` I found the right geometry numbers from this answer - https://askubuntu.com/a/1169268/934644 Unfortunately, after upgrading to Ubuntu 21.04 it doesn't seem to be working. COLS 91 and ROWS 47 scaling correctly but X 996 and Y 8 not translating at all. My screen resolution is 1920 x 1080. This is definitely linked to the Wayland as default graphics. After selecting "Ubuntu on Xorg", the terminal window translates correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926274/+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 1926032] Re: Screen "disconnects" when updating screen buffer
This sounds like an HDMI connection/signalling problem. Please check to see if a direct connection (no receiver), and even a new cable, exhibits the same problem. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - Screen "disconnects" when updating screen buffer + [i915] Screen "disconnects" when updating screen buffer ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => 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/1926032 Title: [i915] Screen "disconnects" when updating screen buffer Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a problem in which the screen will behave as if I pulled the HDMI or turned the computer off (no source) for a few seconds until the screen comes back on again. This happens a lot when I open a new window, moves the mouse after it has been still for a while or I open a new window or move the current window. I can watch a whole movie without this problem but as soon as I pause or touch the controls of VLC or move the mouse the problem reocurr. It seems to be after a certain idle period most of the time, but not always. Sometimes it happens many times in a row. The setup is my home built media PC with intel integrated graphics (i5-9400) connected to a philips 55" TV (55POS901F) through a Pioneer AV receiver. I have tried probably every possible resolution and screen update frequency and the problem is still there. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 24 21:57:54 2021 DistUpgraded: 2020-12-01 07:11:08,428 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation UHD Graphics 630 (Desktop 9 Series) [1849:3e98] InstallationDate: Installed on 2020-12-01 (144 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-12-01 (144 days ago) dmi.bios.date: 05/14/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.10 dmi.board.name: H310CM-ITX/ac 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.:bvrP4.10:bd05/14/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH310CM-ITX/ac: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.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/linux/+bug/1926032/+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 1926009] Re: [amdgpu] Incomplete display of text
Also you have unsupported graphics packages installed, one of which was the package you rolled back. In future please ensure you are not using any PPAs before reporting bugs to Ubuntu. ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1926009 Title: [amdgpu] Incomplete display of text Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-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: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/xserver-xorg-video-amdgpu/+bug/1926009/+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 1926009] Re: Incomplete display of text
It appears 'amdgpu' is the wrong driver for this system. 'radeon' is the correct driver. Maybe you had a config file that was forcefully loading the wrong one? ** Summary changed: - Incomplete display of text + [amdgpu] Incomplete display of text ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) -- 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/1926009 Title: [amdgpu] Incomplete display of text Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: Ubuntu release: 20.04.1 * What is expected to happen. All gui text elements to display complete words. * What actually happens. Since a recent update, gui text displays incompletely. I'm posting this with some difficulty from the affected system, but have noted similar issues being experienced by others and I share links below: https://askubuntu.com/questions/1328937/ubuntu-20-04-only-shows-half-text https://askubuntu.com/questions/1329312/xubuntu-20-04-incomplete-words https://askubuntu.com/questions/1329059/on-the-desktop-xfce-displays-text-incorrectly https://askubuntu.com/questions/1332354/ubuntu-20-04-is-showing-a-bad-text The issues above seem to suggest the the issue may lie with the AMD graphics driver, although in my case I think I am using the 'radeon' open source driver. The issue occurs regardless of me use the current or previous kernel version installed. Please let me know if there is any more information that I can provide, and I will do my best to get it to you. Many thanks, Mark. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Sat Apr 24 12:07:35 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] [1002:990e] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Richland [Radeon HD 8570D] [1043:8526] MachineType: NOVATECH LTD MBB-66004G ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-72-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: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A55-M LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6102:bd05/03/2013:svnNOVATECHLTD:pnMBB-66004G:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnF2A55-MLK:rvrRevX.0x:cvnNOVATECHLTD:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: MBB-66004G dmi.product.sku: SKU dmi.product.version: 1.0 dmi.sys.vendor: NOVATECH LTD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-1ubuntu1~f~mesarc2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.1.0~rc2+git2104212235.09d505a3ab7~f~mesarc2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/xserver-xorg-video-amdgpu/+bug/1926009/+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 1926023] Re: display broken on logout
** Tags added: nvidia ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Package changed: xorg-server (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) ** Summary changed: - display broken on logout + [nvidia] display broken on logout ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: Incomplete => New -- 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/1926023 Title: [nvidia] display broken on logout Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: I can login and use the system, but when I logout, the monitor complains that it can't display the video mode. Pressing various keys and clicking randomly doesn't help, I have to press the hard reset button to login again. 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 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..07.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:07: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.73.01 Thu Apr 1 21:40:36 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: Sat Apr 24 18:13:51 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TU106 [GeForce RTX 2060 SUPER] [1462:c752] InstallationDate: Installed on 2021-04-24 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=901be83b-8764-4544-acd9-b13439d1ab8f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: B450M Pro4-F 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.:bvrP1.60:bd08/01/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4-F: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.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: 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/ubuntu/+source/nvidia-graphics-drivers-460/+bug/1926023/+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 1925824] Re: [Avita NS14A2] Screen doesn't display on warm boot and turning on after Suspend (i915 0000:00:02.0: [drm] *ERROR* failed to enable link training)
** Summary changed: - Display Error (hardware bug: Screen doesnt display on warm boot and turning on after Suspend) + [Avita NS14A2] Screen doesn't display on warm boot and turning on after Suspend (i915 :00:02.0: [drm] *ERROR* failed to enable link training) ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: regression-update -- 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/1925824 Title: [Avita NS14A2] Screen doesn't display on warm boot and turning on after Suspend (i915 :00:02.0: [drm] *ERROR* failed to enable link training) Status in linux package in Ubuntu: New Bug description: I have Avita NS14A2 laptop where i dual boot windows 10 and Ubuntu 20.04. In past few days might be after installing updates I am facing issue where my screen dont display at all when i first boot it and after multiple force shut down and then boot in it work, even on doing Suspend and then opening it, screen didnt not display for about 5-6 minutes, and then shows login screen. On checking logs software i got these line on those time stamp when display doesnt shows this is the line: (Hardware) i915 :00:02.0: [drm] *ERROR* failed to enable link training this line continues for about 30-40 times on average during time when screen doesnt display anything on turing on. So I think there is some issue with it. As I primarily use Ubuntu 20.04 so didnt check it with windows 10 but on doing cold boot it didnt even shows the boot menu where i can choose between Ubuntu 20.04 and Windows 10. But once screen starts displaying i dont see that error in logs software anymore and screen doesnt freezes or hangs. It only happen when i either open after suspend or do cold boot. Please consider this issue on urgent basis, as it takes a lot of time and efforts to make screen display something. :( And please let me know whether I should do fresh installation of ubuntu 20.04 again. Sorry for any grammatical mistakes. :) Thank you, Bipul Harsh bipulharsh...@gmail.com ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 20:36:38 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation UHD Graphics 620 [8086:5917] InstallationDate: Installed on 2020-11-22 (151 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: AVITA NS14A2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=011d61ba-ef72-40ed-9957-25830622d9c7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2019 dmi.bios.release: 0.22 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BSR5IPHK-14UF80-AVI-V22 dmi.board.asset.tag: Default string dmi.board.name: 6614UFWC80 dmi.board.vendor: AVITA dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: AVITA dmi.chassis.version: Default string dmi.ec.firmware.release: 0.22 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBSR5IPHK-14UF80-AVI-V22:bd04/19/2019:br0.22:efr0.22:svnAVITA:pnNS14A2:pvrDefaultstring:rvnAVITA:rn6614UFWC80:rvrDefaultstring:cvnAVITA:ct10:cvrDefaultstring: dmi.product.family: CN6614 dmi.product.name: NS14A2 dmi.product.sku: CN6614F56U1IN-MB dmi.product.version: Default string dmi.sys.vendor: AVITA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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/linux/+bug/1925824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1925739] Re: Strange sound when speaker is muted
If the problem was /sys/module/snd_hda_intel/parameters/power_save then this should be assigned to the kernel. ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Summary changed: - Strange sound when speaker is muted + [Dell Vostro 3668] Strange sound when speaker is muted -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1925739 Title: [Dell Vostro 3668] Strange sound when speaker is muted Status in linux package in Ubuntu: Incomplete Bug description: when everything is off even sound is muted I am getting sound like connecting 3.5mm jack. It's not sure why this sound is coming to my headphone. It's coming unevenly few seconds later. It's not case with ubuntu 20.10 usb stick. It begin when I upgrade pkgs. ubuntu 20.10 all updated. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bapi 1453 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-04-22 (2 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.2-1ubuntu2.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Tags: groovy Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/30/2020 dmi.bios.release: 1.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.1 dmi.board.name: 0VFD52 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.1:bd09/30/2020:br1.14:svnDellInc.:pnVostro3668:pvr:rvnDellInc.:rn0VFD52:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3668 dmi.product.sku: 0760 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925739/+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 1925766] Re: extensions disabled after upgrade
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- 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/1925766 Title: extensions disabled after upgrade Status in gnome-shell package in Ubuntu: New Bug description: I updated yesterday (I think), and after a reboot today all extensions were disabled. I went to the gnome-shell extensions website, ticked to enable my extension and it toggled on. The extensions did not seem to work. I reloaded the page and they are off again. I clicked enabled, still nothing. Reload page and all are off. I check logs in journalctl and could see nothing relevant. Eventually a bit of searching suggests enabling via gnome-shell- tweaks, so I open that up and they're all unticked, and disabled (can't be ticked). I realised there's a global "enable extensions" tickbox which has been unticked. Enabling this fixes everything. I have had to do this in the past, several months back as I had forgotten until now. Something is disabling this on upgrade and it is not obvious from the extensions web-page that they have been disabled. Ideally they should not be disabled at all, but if they are at least there should be some more obvious feedback after upgrade and on the extensions website ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 10:24:59 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-07-22 (640 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-15 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1925766/+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
** Tags added: a11y zoom
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4112
Importance: Unknown
Status: Unknown
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
--
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:
New
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 1926070] Re: Please backport Desktop Icons NG to 20.04
It appears the main problem here is an upstream one: The extension does not support GNOME 3.36 used in Ubuntu 20.04. The upstream code only declares support for 3.38 and 40, while the GNOME page for the extension offers downloads for 3.30, 3.32, 3.34, 3.38, 40. Please report a bug to the developer requesting support for GNOME 3.36: https://gitlab.com/rastersoft/desktop-icons-ng/-/issues and then tell us the new issue ID. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1926070 Title: Please backport Desktop Icons NG to 20.04 Status in Focal Backports: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Bug description: After testing Hirsute for a bit, I am convinced that Desktop Icons NG fixes a large and frustrating usability issue on the LTS desktop. It’s a wonderful restoration of functionality that I still trip over myself expecting from “muscle memory” in 20.04, but being reminded that I can’t do simple things like drag and drop. I have read some others suggestions to just install the extension oneself, and upon investigation, I found that it wasn’t a very clear process. Even Igor at dedoimedo.com had issues with going this route -> https://www.dedoimedo.com/computers/gnome-ding.html 4 . For these reasons, I am hoping that someone out there (hopefully more than one) agrees that replacing the current desktop icons package in 20.04 would only help those on an LTS desktop. As excited as I am for the interim releases (especially concerning Wayland and Pipewire), I don’t want to move away from a well-supported release to have a desktop that we could have (and I feel should have) in 20.04. I know that some work would be involved, but I for one would be very grateful, for what it’s worth. Thanks to all for your time. To manage notifications about this bug go to: https://bugs.launchpad.net/focal-backports/+bug/1926070/+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 1873052] Re: X11 fractional scaling causes two cursors after login (usually with amdgpu)
** Summary changed: - Showing two cursors after login (usually with amdgpu) + X11 fractional scaling causes two cursors after login (usually with amdgpu) -- 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/1873052 Title: X11 fractional scaling causes two cursors after login (usually with amdgpu) Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+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: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal
Please try logging into 'Ubuntu on Xorg' and tell us if that fixes the problem. If the problem only happens in the default Ubuntu (which is Wayland) session then this is expected because windows only have control over their size, and never their position, in Wayland. ** Tags added: hirsute ** No longer affects: ubuntu ** Changed in: gnome-terminal (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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: new in 21.04: gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete 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 1926335] Re: Dead mouse cursor left after login
*** This bug is a duplicate of bug 1873052 *** https://bugs.launchpad.net/bugs/1873052 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1873052, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1873052 Showing two cursors after login (usually with amdgpu) -- 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/1926335 Title: Dead mouse cursor left after login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, A small mouse cursor is left on the desktop after login screen to a fractionally scaled desktop. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu2 Uname: Linux 5.12.0-051200rc8-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: X-Cinnamon Date: Tue Apr 27 20:06:41 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-20 (7 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210418) 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/1926335/+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
There are also errors suggesting a broken extension:
mai 03 12:22:54 myDell gnome-shell[2245]: Couldn't find child [0x55d671ebe830
Gjs_ui_windowPreview_WindowPreview:first-child last-child ("(2) reddit: the
front page of the internet - Google Chrome")] in window slots
mai 03 12:22:54 myDell gnome-shell[2245]: Couldn't find child [0x55d674a3d740
Gjs_ui_windowPreview_WindowPreview ("(2) reddit: the front page of the internet
- Google Chrome")] in window slots
mai 03 12:22:56 myDell gnome-shell[2245]: Couldn't find child [0x55d674a3d740
Gjs_ui_windowPreview_WindowPreview:first-child last-child ("(2) reddit: the
front page of the internet - Google Chrome")] in window slots
Please do:
cd ~/.local/share/gnome-shell
rm -rf extensions
to be sure any local extensions are gone. And then reboot.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3969
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3969
--
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/1926620
Title:
Gnome-Shell freezes when touchscreen is used
Status in gnome-shell package in Ubuntu:
Incomplete
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/ubuntu/+source/gnome-shell/+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 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
^^^ Bug 1925320 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+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
The issue in comment #7 is also related to bug 1922353 and https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3969 -- 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/1926620 Title: Gnome-Shell freezes when touchscreen is used Status in gnome-shell package in Ubuntu: Incomplete 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/ubuntu/+source/gnome-shell/+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 1926620] Re: Gnome-Shell freezes when touchscreen is used
Thanks. It appears the issue is: mai 03 12:22:52 myDell gnome-shell[2245]: value "nan" of type 'gfloat' is invalid or out of range for property 'x' of type 'gfloat' mai 03 12:22:52 myDell gnome-shell[2245]: value "nan" of type 'gfloat' is invalid or out of range for property 'y' of type 'gfloat' mai 03 12:22:52 myDell gnome-shell[2245]: JS ERROR: Exception in callback for signal: shown: Error: Wrong type number; float expected. But it's out of range: -Infinity _init/GObject.Object.prototype.set@resource:///org/gnome/gjs/modules/core/overrides/GObject.js:553:16 _easeActor@resource:///org/gnome/shell/ui/environment.js:155:15 init/Clutter.Actor.prototype.ease@resource:///org/gnome/shell/ui/environment.js:294:19 _syncWorkspacesActualGeometry@resource:///org/gnome/shell/ui/workspacesView.js:728:21 _init/this._overviewShownId<@resource:///org/gnome/shell/ui/workspacesView.js:396:18 _emit@resource:///org/gnome/gjs/modules/core/_signals.js:114:47 _showDone@resource:///org/gnome/shell/ui/overview.js:604:14 onComplete@resource:///org/gnome/shell/ui/overview.js:589:36 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:85:13 _easeActor/<@resource:///org/gnome/shell/ui/environment.js:168:64 -- 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/1926620 Title: Gnome-Shell freezes when touchscreen is used Status in gnome-shell package in Ubuntu: Incomplete 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/ubuntu/+source/gnome-shell/+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 1720438] Re: brightness control broken nvidia
Judging by the age of this bug and the number of people subscribed, this page seems to have become a forum and not a current relevant bug report. The release 17.10 this bug was about is no longer supported anyway. Anyone experiencing problems please open a new bug of your own by running: ubuntu-bug xorg ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid ** Changed in: mutter (Ubuntu) Status: Incomplete => Invalid ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: Confirmed => Invalid -- 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/1720438 Title: brightness control broken nvidia Status in gnome-power: Confirmed Status in gnome-power-manager package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1720438/+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 1926070] Re: Please backport Desktop Icons NG to 20.04
That's not a definite comment. More recently than that we found a few bugs in the extension that I had to try and fix quickly, late in the cycle. It's my opinion that this extension does not yet qualify as stable so should not be considered for 20.04.x. It's not really even finished in hirsute so let's try to get it right in impish first... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1926070 Title: Please backport Desktop Icons NG to 20.04 Status in Focal Backports: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Bug description: After testing Hirsute for a bit, I am convinced that Desktop Icons NG fixes a large and frustrating usability issue on the LTS desktop. It’s a wonderful restoration of functionality that I still trip over myself expecting from “muscle memory” in 20.04, but being reminded that I can’t do simple things like drag and drop. I have read some others suggestions to just install the extension oneself, and upon investigation, I found that it wasn’t a very clear process. Even Igor at dedoimedo.com had issues with going this route -> https://www.dedoimedo.com/computers/gnome-ding.html 4 . For these reasons, I am hoping that someone out there (hopefully more than one) agrees that replacing the current desktop icons package in 20.04 would only help those on an LTS desktop. As excited as I am for the interim releases (especially concerning Wayland and Pipewire), I don’t want to move away from a well-supported release to have a desktop that we could have (and I feel should have) in 20.04. I know that some work would be involved, but I for one would be very grateful, for what it’s worth. Thanks to all for your time. To manage notifications about this bug go to: https://bugs.launchpad.net/focal-backports/+bug/1926070/+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 1926932] Re: Error message too short to understand what is wrong
Indeed the source code suggests that error is from gnome-shell itself. Next time the problem happens, please run: journalctl -b0 > journal.txt and then attach the resulting text file here. ** Tags added: groovy ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1926932 Title: Error message too short to understand what is wrong Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is on Ubuntu 20.10 (Groovy Gorilla). I placed a text file on my desktop, and on clicking it, I was shown the error "Execution of /home/myUsername/Desktop/.goutputstream-WU... Command not found". Even on clicking the error message that popped up, it didn't expand to show more details. So basically, the bug I'm reporting is about error messages being too short/obscure to be useful for users to figure out what the problem actually is. Image attached. The black spot in the middle was added by me to obscure the username. (on a a side note, I was clicking a plain text document which had the checkbox for "allow executing file as a program" ticked). Clicking any other textfile didn't show this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926932/+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 1924613] Re: gnome-shell assert failure: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
*** This bug is a duplicate of bug 1886059 *** https://bugs.launchpad.net/bugs/1886059 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1886059, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1886059 gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] -- 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/1924613 Title: gnome-shell assert failure: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-shell: Installed: 3.36.7-0ubuntu0.20.04.1 Candidate: 3.36.7-0ubuntu0.20.04.1 Version table: *** 3.36.7-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.4-1ubuntu1~20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 3.36.1-5ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages mutter 3.36.7 Description of issue: The GUI seems to freeze/reload/refresh instantly. It happens when I e.g. click on the docker panel and/or just move the mouse cursor around, click on apps and do something GUI related, open folders. The GUI reload/refresh crash lasts for about 2 seconds, it suddenly/instantly repositions my mouse cursor to the lower right corner of the screen and my laptop's fan works harder at those 2 seconds. The issue started after I updated and, at a later time, rebooted the machine. Below are the gnome-related upgrades that I did (`cat /var/log/dpkg.log | grep gnome`): 2021-04-15 17:50:29 status triggers-pending gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 17:50:30 upgrade libreoffice-gnome:amd64 1:6.4.6-0ubuntu0.20.04.1 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:30 status half-configured libreoffice-gnome:amd64 1:6.4.6-0ubuntu0.20.04.1 2021-04-15 17:50:30 status unpacked libreoffice-gnome:amd64 1:6.4.6-0ubuntu0.20.04.1 2021-04-15 17:50:30 status half-installed libreoffice-gnome:amd64 1:6.4.6-0ubuntu0.20.04.1 2021-04-15 17:50:30 status unpacked libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:56 configure libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:56 status unpacked libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:56 status half-configured libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:56 status installed libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:57 trigproc gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 17:50:57 status half-configured gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 17:50:57 status installed gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 18:00:30 status triggers-pending gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 18:00:30 trigproc gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 18:00:30 status half-configured gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 18:00:30 status installed gnome-menus:amd64 3.36.0-1ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AssertionMessage: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 22:04:15 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1608008084 InstallationDate: Installed on 2021-01-17 (88 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/freekostageo RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7feadaaeb588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7feada528858 "!xcb_xlib_threads_sequence_lost", file=0x7feada5286c3 "../../src/xcb_io.c", line=260, function=) at assert.c:92 __GI___assert_fail (assertion=0x7fea
[Desktop-packages] [Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
Thanks Kostas. Next please follow the instructions in comment #11. -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete 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.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d 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/. Similar errors: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd https://errors.ubuntu.com/problem/e3f9ab8232005403e935c6038edd99f13e609e01 https://errors.ubuntu.com/problem/9d421ecaba25357f5c3ef73f438313e40ac24e77 https://errors.ubuntu.com/problem/42cfd76250a81cca07f8c548ec27e245315b5e01 --- Anyone experiencing this crash reliably, please help us to find its root cause by editing your /etc/environment and adding a line: MUTTER_SYNC=1 and then reboot. Then next time a crash happens please tell us (here) the bug ID or error URL of the new crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+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 1927013] Re: gnome gets stuck in the overview mode
*** This bug is a duplicate of bug 1922353 *** https://bugs.launchpad.net/bugs/1922353 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1922353, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1922353 Overview sometimes fails to appear or disappear fully when Ubuntu Dock is loaded -- 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/1927013 Title: gnome gets stuck in the overview mode Status in gnome-shell package in Ubuntu: New Bug description: It appears rather randomly and so is hard to reproduce reliably, but every once in a while the gnome gets stuck in the activities overview mode. Windows may be closed and the drop down menu in the right corner may still be accessed, but it is not possible to exit the overview mode without logging out of the shell. The frequency of the bug increases greatly if the "Activities hot corner" extension is enabled (which probably just makes entering this mode more frequent after random mouse moves). It appears both in Wayland and Xorg (though more often in Xorg). I might be mistaken, but it's possible that the bug also happens more often when there's some contextual menu open at the same when the switch to the overview mode is made. This bug started appearing for me only after upgrade to 21.04, so I am reporting it as a new bug even though similar things happened to various users earlier... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927013/+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 1902768] Re: [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10
Alright, maybe it was bug 1897965 but Fix Released regardless. ** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902768 Title: [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10 Status in pulseaudio package in Ubuntu: Fix Released Bug description: In 20/04 sound worked via headphones worked fine. After upgrade no sound is heard and the audio output device list only has HDMI and S/PDIF as possible choices. Windows 10 on the same machine works without problems. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Nov 3 20:39:59 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-09-19 (44 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity Symptom: installer UpgradeStatus: Upgraded to groovy on 2020-11-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-12-10 (137 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: pulseaudio 1:13.99.2-1ubuntu2.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Tags: groovy Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1004 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1004:bd08/13/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902768/+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 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04
** Summary changed: - XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04 + XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04 Status in xserver-xorg-input-libinput package in Ubuntu: New Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+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 1927019] [NEW] Xorg freeze
Public bug reported: Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from top to bottom and ubuntu doesn't react to any keyboard shortcut. It's appears, maybe after 2 hours of work. I didn't see this bug with my previous ubuntu 20.10. My computer is a new DELL XPS 13 - intel core i7. I disabled the 4K screen and I am using a resolution 1920x1080. I enabled the night mode. 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 non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 4 00:10:39 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Xe Graphics [1028:0a5c] InstallationDate: Installed on 2021-04-30 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9305 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=37473b6f-8714-4a48-91c1-f6964b09347d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2021 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.name: 0PPYW4 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd01/13/2021:br1.0:svnDellInc.:pnXPS139305:pvr:rvnDellInc.:rn0PPYW4:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9305 dmi.product.sku: 0A5C 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.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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze hirsute ubuntu ** Description changed: - Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from top to bottom and ubuntu doesn't react to any keyboard. It's appears, maybe after 2 hours of work. - I didn't see this bug with my previous ubuntu 20.10. + Ubuntu 21.04 Freeze sometime ( using wayland ) . A black screen appear from top to bottom and ubuntu doesn't react to any keyboard shortcut. It's appears, maybe after 2 hours of work. + I didn't see this bug with my previous ubuntu 20.10. My computer is a new DELL XPS 13 - intel core i7. I disabled the 4K screen and I am using a resolution 1920x1080. I enabled the night mode. 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 non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 4 00:10:39 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: - Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) -Subsystem: Dell Iris Xe Graphics [1028:0a5c] + Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) + Subsystem: Dell Iris Xe Graphics [1028:0a5c] InstallationDate: Installed on 2021-04-30 (3 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. XPS 13 9305 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/usr/bin/zsh + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SH
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
@Timo, any ETA for when this would land into Focal? thanks. -- 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/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: Fix Released Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+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 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
Hi Daniel, I made my bug report public (https://bugs.launchpad.net/ubuntu/+source /gnome-shell/+bug/1924613). You can also read through the two update comments I've posted there. Thanks, Kostas -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete 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.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d 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/. Similar errors: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd https://errors.ubuntu.com/problem/e3f9ab8232005403e935c6038edd99f13e609e01 https://errors.ubuntu.com/problem/9d421ecaba25357f5c3ef73f438313e40ac24e77 https://errors.ubuntu.com/problem/42cfd76250a81cca07f8c548ec27e245315b5e01 --- Anyone experiencing this crash reliably, please help us to find its root cause by editing your /etc/environment and adding a line: MUTTER_SYNC=1 and then reboot. Then next time a crash happens please tell us (here) the bug ID or error URL of the new crash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+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 1924613] Re: gnome-shell assert failure: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
** Information type changed from Private Security to Public Security ** Information type changed from Public Security to Public -- 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/1924613 Title: gnome-shell assert failure: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu 20.04.2 LTS Release: 20.04 gnome-shell: Installed: 3.36.7-0ubuntu0.20.04.1 Candidate: 3.36.7-0ubuntu0.20.04.1 Version table: *** 3.36.7-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.4-1ubuntu1~20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 3.36.1-5ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages mutter 3.36.7 Description of issue: The GUI seems to freeze/reload/refresh instantly. It happens when I e.g. click on the docker panel and/or just move the mouse cursor around, click on apps and do something GUI related, open folders. The GUI reload/refresh crash lasts for about 2 seconds, it suddenly/instantly repositions my mouse cursor to the lower right corner of the screen and my laptop's fan works harder at those 2 seconds. The issue started after I updated and, at a later time, rebooted the machine. Below are the gnome-related upgrades that I did (`cat /var/log/dpkg.log | grep gnome`): 2021-04-15 17:50:29 status triggers-pending gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 17:50:30 upgrade libreoffice-gnome:amd64 1:6.4.6-0ubuntu0.20.04.1 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:30 status half-configured libreoffice-gnome:amd64 1:6.4.6-0ubuntu0.20.04.1 2021-04-15 17:50:30 status unpacked libreoffice-gnome:amd64 1:6.4.6-0ubuntu0.20.04.1 2021-04-15 17:50:30 status half-installed libreoffice-gnome:amd64 1:6.4.6-0ubuntu0.20.04.1 2021-04-15 17:50:30 status unpacked libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:56 configure libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:56 status unpacked libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:56 status half-configured libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:56 status installed libreoffice-gnome:amd64 1:6.4.7-0ubuntu0.20.04.1 2021-04-15 17:50:57 trigproc gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 17:50:57 status half-configured gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 17:50:57 status installed gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 18:00:30 status triggers-pending gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 18:00:30 trigproc gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 18:00:30 status half-configured gnome-menus:amd64 3.36.0-1ubuntu1 2021-04-15 18:00:30 status installed gnome-menus:amd64 3.36.0-1ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AssertionMessage: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. CasperMD5CheckResult: skip CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 15 22:04:15 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1608008084 InstallationDate: Installed on 2021-01-17 (88 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/freekostageo RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7feadaaeb588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7feada528858 "!xcb_xlib_threads_sequence_lost", file=0x7feada5286c3 "../../src/xcb_io.c", line=260, function=) at assert.c:92 __GI___assert_fail (assertion=0x7feada528858 "!xcb_xlib_threads_sequence_lost", file=0x7feada5286c3 "../../src/xcb_io.c", line=260, function=0x7feada528b10 "poll_for_event") at assert.c:101 ?? () from /lib/x86_64-linux-gnu/libX11.so.6 Title: gnome-shell assert failure: gnome-shell: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: [modified] mtime.conffile..etc.xdg.autostart.
[Desktop-packages] [Bug 1926860] Re: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04
** Also affects: xserver-xorg-input-libinput (Arch Linux) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04 Status in xserver-xorg-input-libinput package in Ubuntu: New Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+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 1926860] Re: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04
Can I fix the title? Sorry have a few typos in there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04 Status in xserver-xorg-input-libinput package in Ubuntu: New Status in xserver-xorg-input-libinput package in Arch Linux: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+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 1926860] Re: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04
** Attachment added: "21.04-screen2.png" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+attachment/5494499/+files/21.04-screen2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04 Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+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 1926860] Re: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04
** Attachment added: "21.04-screen.png" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+attachment/5494498/+files/21.04-screen.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04 Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+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 1926860] Re: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04
** Attachment added: "21.04.libinput-list-devices-and-lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+attachment/5494497/+files/21.04.libinput-list-devices-and-lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04 Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+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 1926860] Re: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04
** Attachment added: "18.04-libinput-list-devices-and-lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+attachment/5494496/+files/18.04-libinput-list-devices-and-lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04 Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+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 1926860] Re: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04
Ok the following comments are a bunch of screenshots form my Ubutu 18.04 Setup as well as from my 21.04 setup. I made those with the XP Pen Star 03 attached into each setup. Also attached are output from lineinput list-devices and lsusb for 18.04 and 21.04. 21.04 does recognize that the device is plugged in, but no stylus pen and tablet are recognized. 18.04 everything work perfectly fine. Plug and play. I can use it perfectly fine in software like Krita as well. -> That is how it should work on any version after 18.04 as well. However the newer versions I tested all have the same issue like 21.04. I tested 19.04, 20.04 and currently am running 21.04. I also tested 18.04 on that setup and it worked perfectly fine. I'm not sure why it worked out of the box in 18.04 but not in any newer version. I'm unble to find a working fix btw. It should of course work just like in 18.04. ** Attachment added: "18.04-screen.png" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+attachment/5494494/+files/18.04-screen.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04 Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+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 1926860] Re: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04
** Attachment added: "18.04-screen2.png" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+attachment/5494495/+files/18.04-screen2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04 Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+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 1927013] [NEW] gnome gets stuck in the overview mode
Public bug reported: It appears rather randomly and so is hard to reproduce reliably, but every once in a while the gnome gets stuck in the activities overview mode. Windows may be closed and the drop down menu in the right corner may still be accessed, but it is not possible to exit the overview mode without logging out of the shell. The frequency of the bug increases greatly if the "Activities hot corner" extension is enabled (which probably just makes entering this mode more frequent after random mouse moves). It appears both in Wayland and Xorg (though more often in Xorg). I might be mistaken, but it's possible that the bug also happens more often when there's some contextual menu open at the same when the switch to the overview mode is made. This bug started appearing for me only after upgrade to 21.04, so I am reporting it as a new bug even though similar things happened to various users earlier... ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gnome get stuck in the overview mode + gnome gets stuck in the overview mode -- 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/1927013 Title: gnome gets stuck in the overview mode Status in gnome-shell package in Ubuntu: New Bug description: It appears rather randomly and so is hard to reproduce reliably, but every once in a while the gnome gets stuck in the activities overview mode. Windows may be closed and the drop down menu in the right corner may still be accessed, but it is not possible to exit the overview mode without logging out of the shell. The frequency of the bug increases greatly if the "Activities hot corner" extension is enabled (which probably just makes entering this mode more frequent after random mouse moves). It appears both in Wayland and Xorg (though more often in Xorg). I might be mistaken, but it's possible that the bug also happens more often when there's some contextual menu open at the same when the switch to the overview mode is made. This bug started appearing for me only after upgrade to 21.04, so I am reporting it as a new bug even though similar things happened to various users earlier... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927013/+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 1754140] Re: Gnome gets stuck in overview mode
I have started getting this very bug after upgrade to hippo (21.04). Happens much more often when the "Activities" hot corner extension is enabled. But also happens without it... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1754140 Title: Gnome gets stuck in overview mode Status in ubuntu-meta package in Ubuntu: New Bug description: I'm running Ubuntu 17.10, and I have repeatedly had a problem with the desktop environment getting stuck in overview mode. When stuck, I can close and select windows, and access the menus at on the top bar, but I cannot exit overview mode. The only solution I've found is to log out and log back in. I'm not exactly sure what combination of circumstances causes it to happen, but it seems to happen more often if invoked via the corner hover point. It also happens in both Wayland and Xorg. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.404.1 Uname: Linux 4.14.15-041415-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Mar 7 11:02:02 2018 InstallationDate: Installed on 2017-05-04 (307 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to artful on 2017-10-29 (129 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1754140/+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 1926860] Re: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04
I think this fits better into xserver-xorg-input-libinput let me know if you know where exactly this is bug is located and coming from. ** Package changed: ubuntu-release-upgrader (Ubuntu) => xserver-xorg- input-libinput (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1926860 Title: XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04 Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1926860/+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 1915677] Re: [ snap ] libreoffice-style-* packages are missing ?
Well but I added the non-svg theme'd icons: https://git.launchpad.net/~hellsworth/+git/libreoffice- snap/commit/?id=8251050c164e4c876ef24864087e641ad9aceaf4 Since it does work, I'll go ahead and push for merging. -- 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/1915677 Title: [ snap ] libreoffice-style-* packages are missing ? Status in libreoffice package in Ubuntu: In Progress Bug description: Hi, trying LibreOffice 7 as a snap on UbuntuBudgie 20.04. I generally use dark gtk theme style system wide - and some are available as snap ( Adapta ). I often use Papirus icons set - and those are also ( partly ) available as snap ( through Adpata gtk theme ). I can't see if the same choice exists while using LO as a snap : I can find some icons theme ( elementary, colibre, breeze, and so on ) but they all look designed for global light gtk themes. In other words icons in my LO are black on black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1915677/+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 1926860] [NEW] XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04
You have been subscribed to a public bug: The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no longer working in any other Version of Ubuntu released afterwards. I tested 20.04 and am currently running 21.04. it is recognized but in the system settings it says not tablet and not stylus found. The terminal gives me the info that the UC-Logic TABLET 1060N is plugged in. In the system settings it shows "Wacom Tablet" but says not tablet and stylus pen are recognized. It works perfectly fine on my 18.04 install. I found a few reports on the internet with the exact same issue. They installed some evdev driver and somehow managed to resolve. I was not able to do so yet. If the tablet used to work out of the box with Ubuntu 18.04 I wonder why it is no longer working. There is also a XP Pen Star 03 V2 by now. The tablet look identical but the hardware or firmware must be different. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.11 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 2 03:16:00 2021 InstallationDate: Installed on 2021-04-15 (16 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade hirsute wayland-session -- XP Pen Star 03 Grafiktable not running on Ubuntu later than 18.04 https://bugs.launchpad.net/bugs/1926860 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. -- 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 1925392] Re: firefox remote on wayland/dbus does not work
** Branch linked: lp:~mozillateam/firefox/firefox-beta.groovy
** Branch linked: lp:~mozillateam/firefox/firefox-beta.focal
** Branch linked: lp:~mozillateam/firefox/firefox-beta.bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1925392
Title:
firefox remote on wayland/dbus does not work
Status in firefox package in Ubuntu:
Fix Committed
Bug description:
[agnew(~)] lsb_release -rc
Release:21.04
Codename: hirsute
[agnew(~)] dpkg-query -W firefox
firefox 87.0+build3-0ubuntu4
[agnew(~)]
Attempting to open links with `firefox $URL` times out and gives me
the old familiar profile-locked error dialog.
As far as I can tell, all of the ducks are lined up correctly (thanks
to the fix for LP:1921931)
[agnew(~)] tr \\0 \\n < /proc/$(pgrep -x firefox)/environ | egrep -i
'dbus|wayland'
XDG_SESSION_TYPE=wayland
MOZ_ENABLE_WAYLAND=1
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
MOZ_DBUS_REMOTE=1
WAYLAND_DISPLAY=wayland-0
XAUTHORITY=/run/user/1000/.mutter-Xwaylandauth.QKTZ10
[agnew(~)] sh -x $(which firefox) https://ubuntu.com/
+ set -e
+ MOZ_LIBDIR=/usr/lib/firefox
+ which /usr/bin/firefox
+ MOZ_APP_LAUNCHER=/usr/bin/firefox
+ MOZ_APP_NAME=firefox
+ export MOZ_APP_LAUNCHER
+ [ wayland = wayland ]
+ export MOZ_ENABLE_WAYLAND=1
+ export MOZ_DBUS_REMOTE=1
+ [ ! -x /usr/lib/firefox/firefox ]
+ moz_debug=0
+ moz_debugger_args=
+ moz_debugger=gdb
+ [ 1 -gt 0 ]
+ break
+ [ 0 -eq 1 ]
+ exec /usr/lib/firefox/firefox https://ubuntu.com/
[GFX1-]: No GPUs detected via PCI
[GFX1-]: glxtest: process failed (received signal 11)
(firefox:60063): Gtk-WARNING **: 10:09:52.171: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.174: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.179: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.179: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.197: Loading IM context type
'xim' failed
(firefox:60063): Gtk-WARNING **: 10:09:52.199: Loading IM context type
'xim' failed
###!!! [Parent][RunMessage] Error: Channel closing: too late to
send/recv, messages will be lost
[agnew(~)]
However, on dbus-monitor, I see:
method call time=1619043038.755430 sender=:1.392 ->
destination=org.mozilla.firefox.ZGVmYXVsdA__ serial=2
path=/org/mozilla/firefox/Remote; interface=org.mozilla.firefox; member=OpenURL
array of bytes [
02 00 00 00 17 00 00 00 30 00 00 00 2f 68 6f 6d 65 2f 70 61 75 6c 00 2f
75 73 72 2f 6c 69 62 2f 66 69 72 65 66 6f 78 2f 66 69 72 65 66 6f 78 00
68 74 74 70 73 3a 2f 2f 75 62 75 6e 74 75 2e 63 6f 6d 2f 00
]
error time=1619043038.755479 sender=org.freedesktop.DBus ->
destination=:1.392 error_name=org.freedesktop.DBus.Error.ServiceUnknown
reply_serial=2
string "The name org.mozilla.firefox.ZGVmYXVsdA__ was not provided by any
.service files"
And, indeed, firefox is not listening on that name (which is correct
for my profile, "default") or indeed any other such name:
[agnew(~)] busctl --user | grep -i firefox
:1.162 54607
firefox paul :1.162user@1000.service - -
:1.163 54607
firefox paul :1.163user@1000.service - -
[agnew(~)] _
---
ProblemType: Bug
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: paul 3311 F pulseaudio
/dev/snd/controlC1: paul 3311 F pulseaudio
BuildID: 20210318103112
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: GNOME
DefaultProfileIncompatibleExtensions: Default -
{972ce4c6-7e08-4474-a285-3208198ce6fd}
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:352
DefaultProfilePrefSources:
/usr/lib/firefox/defaults/pref/all-ubuntu-gnome.js
prefs.js
DistroRelease: Ubuntu 21.04
ForcedLayersAccel: False
InstallationDate: Installed on 2011-11-06 (3454 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: firefox 87.0+build3-0ubuntu4
PackageArchitecture: amd64
ProcCmdline: BOOT_IMAGE=/vmlinuz-5.11.0-16-generic
root=UUID=617752e9-3054-4928-881c-0e0651a839b0 ro splash quiet vt.handoff=7
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
Pr
[Desktop-packages] [Bug 1861408] Re: firefox apparmor messages
** Branch linked: lp:~mozillateam/firefox/firefox-beta.groovy
** Branch linked: lp:~mozillateam/firefox/firefox-beta.focal
** Branch linked: lp:~mozillateam/firefox/firefox-beta.bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
Fix Released
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
peer_label="unconfined"
Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
[10131.880788] audit: type=1400 audit(1580237490.777:123):
apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
name="/home/dinar/.cache/mesa_shader_cache/index" pid=19720
comm="firefox" requested_mask="wrc" denied_mask=
[Desktop-packages] [Bug 1926976] Re: during mouse drag operations I'm getting undesired/unprompted dropping and potentially picking up of something else
One more bit of description, though it is rare, this problem does happen when I am dragging a text selection. In my most recent example of that, the text selection jumped to a window move. I also didn't mention the detail that the location of the unrequested drop will be offset from the location of the unrequested pick up a new drag. -- 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/1926976 Title: during mouse drag operations I'm getting undesired/unprompted dropping and potentially picking up of something else Status in xorg package in Ubuntu: New Bug description: I am not really sure this is an Xorg problem. Since my last system update (upon the system prompting), I think less than a week ago, I have noticed this troubling intermittent behavior. I go to drag (mouse-initiated) a window across some screen distances (between external monitors and my laptop's builtin monitor) the window will get dropped without me releasing the mouse button before arriving at my desired drop point. More than half the times this happens, something will immediately be picked up in a drag operation. Sometimes it is another window that begins being moved. Other times it is a window resize operation that is picked up. A third option is the selection of text. I have noticed that most of the time it is triggered when I am moving rapidly (though no more rapidly than I have done successfully in the past). Sometimes it happens when I pause during the drag operation. It even happens infrequently when I am dragging slowly. Often I can just go back and pick up the window and complete the operation. However, sometimes the problem just keeps happening until I give up and go away for 5 minutes or so. I have a stock configuration of 20.04. I keep it updated and haven't changed anything significant about X, Gnome, etc. I have done a few tweaks, but nothing I can think of that would relate to this problem. My laptop, a Dell XPS 13, uses a USB 3.1 hub and through that drives two monitors via HDMI. My mouse is bluetooth - Logitech MX Vertical. I don't believe I have installed any proprietary drivers. My 3 displays are arranged into an inverted "L" shape, as the laptop display is "below" and identically sized to the 27" monitor "above" it. The other 27" monitor is to the left of the first one. Some, potentially useful, debugging info: $ lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ bluetoothctl --version bluetoothctl: 5.53 $ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 9C:B6:D0:99:27:2C ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING RX bytes:21743080 acl:954252 sco:0 events:141080 errors:0 TX bytes:6895 acl:169 sco:0 commands:208 errors:0 Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT Name: 'kbuchs' Class: 0x0c010c Service Classes: Rendering, Capturing Device Class: Computer, Laptop HCI Version: 4.2 (0x8) Revision: 0x0 LMP Version: 4.2 (0x8) Subversion: 0x25a Manufacturer: Qualcomm (29) $ bluetoothctl Agent registered [CHG] Controller 9C:B6:D0:99:27:2C Pairable: yes [MX Vertical]# show Controller 9C:B6:D0:99:27:2C (public) Name: kbuchs Alias: kbuchs Class: 0x000c010c Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0535 Discovering: no Advertising Features: ActiveInstances: 0x00 SupportedInstances: 0x05 SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name [MX Vertical]# devices Device D4:51:67:AF:3D:FF MX Vertical [MX Vertical]# info D4:
[Desktop-packages] [Bug 1925730] Re: Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation
This also happens in Ubuntu 21.04 installed from scratch and with Kernel 5.11.0-16-generic, so this issue is not fixed by updating the kernel to 5.11. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1925730 Title: Dell XPS 17 (Ubuntu 21.04) - No sound AT ALL upon fresh installation Status in alsa-driver package in Ubuntu: New Bug description: New laptop - Dell XPS 17, bought in 2020. Upon installation of Ubuntu 21.04 sound does not work at all. System settings only show one audio output - "Dummy output". Audio input does not have even that, just an empty drop-down list. Issue can be fixed if we load a custom sound driver as described here: https://blog.fts.scot/2020/07/04/dell-xps-2020-how-to-get-audio- working-on-linux/ That poses a security risk however and according to the author of the article is not necessary since mainline Kernel release 5.11 now has required device headers included. ... lspci output: user@MYPC:~$ lspci -v | grep -i -A 10 audio 00:1f.3 Multimedia audio controller: Intel Corporation Comet Lake PCH cAVS Subsystem: Dell Comet Lake PCH cAVS Flags: bus master, fast devsel, latency 64, IRQ 229, IOMMU group 16 Memory at 609b218000 (64-bit, non-prefetchable) [size=16K] Memory at 609b10 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci -- 01:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1) Subsystem: Dell TU106 High Definition Audio Controller Flags: bus master, fast devsel, latency 0, IRQ 17, IOMMU group 1 Memory at 7300 (32-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel Looked around for soundwire drivers, found this: user@MYPC:~$ lsmod | grep soundwire soundwire_intel40960 2 snd_sof_intel_hda_common,snd_intel_dspcfg soundwire_generic_allocation16384 1 soundwire_intel soundwire_cadence 32768 1 soundwire_intel soundwire_bus 77824 7 regmap_sdw,soundwire_intel,snd_soc_rt715,soundwire_generic_allocation,soundwire_cadence,snd_soc_rt711,snd_soc_rt1308_sdw snd_soc_core 294912 8 soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_rt715,snd_soc_hdac_hda,snd_soc_rt711,snd_soc_dmic,snd_soc_rt1308_sdw snd_pcm 118784 14 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_sof_intel_ipc,snd_soc_rt715,snd_compress,snd_soc_core,snd_soc_rt711,snd_soc_rt1308_sdw,snd_hda_core,snd_pcm_dmaengine Maybe using the soundwire_intel driver would fix the problem? Need to keep digging. Will post an update if I have any progress. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iamarkadyt 1593 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 00:18:15 2021 InstallationDate: Installed on 2021-04-23 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: TU106 High Definition Audio Controller - HDA NVidia Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iamarkadyt 1593 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA NVidia, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2020 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0YK6XT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd09/03/2020:br1.4:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0YK6XT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925730/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : h
[Desktop-packages] [Bug 1926989] [NEW] lpoptions command won't create a new printer instance
Public bug reported: Running the following command : sudo lpoptions -p Letters/test -o InputSlot=Tray5 returns without error sudo lpoptions -p Letters/test -l Shows that the the above command had no effect InputSlot=Auto After running the commands, there is no file /etc/cups/lpoptions Even if an lpoptions file is created manually, it has no effect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-Gray..\' already exists W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-RGB..\' already exists W [03/May/2021:11:20:51 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-Gray..\' already exists W [03/May/2021:11:20:51 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-DeviceN..\' already exists Date: Mon May 3 11:39:40 2021 InstallationDate: Installed on 2021-04-27 (5 days ago) InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lpstat: device for Letters: dnssd://HP%20LaserJet%20600%20M602%20%5B66D356%5D._ipp._tcp.local/?uuid=a9f85a02-21b1-11e3-9d3a-1556bd6228ad MachineType: LENOVO 10ST00A6US Papersize: letter PpdFiles: Letters: HP LaserJet 600 M602, driverless, cups-filters 1.27.4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=abf53fc0-1910-4d2d-b58d-2e356575d519 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/17/2020 dmi.bios.release: 1.80 dmi.bios.vendor: LENOVO dmi.bios.version: M1UKT50A dmi.board.name: 312A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN 3305279232807 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrM1UKT50A:bd02/17/2020:br1.80:efr1.24:svnLENOVO:pn10ST00A6US:pvrThinkCentreM720s:rvnLENOVO:rn312A:rvrSDK0J40697WIN3305279232807:cvnLENOVO:ct3:cvrNone: dmi.product.family: ThinkCentre M720s dmi.product.name: 10ST00A6US dmi.product.sku: LENOVO_MT_10ST_BU_Think_FM_ThinkCentre M720s dmi.product.version: ThinkCentre M720s dmi.sys.vendor: LENOVO modified.conffile..etc.cups.snmp.conf: [deleted] ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Summary changed: - lptoptions command won't create a new instance + lpoptions command won't create a new instance ** Summary changed: - lpoptions command won't create a new instance + lpoptions command won't create a new printer instance ** Description changed: Running the following command : - lpoptions -p Letters/test -o InputSlot=Tray5 + sudo lpoptions -p Letters/test -o InputSlot=Tray5 returns without error sudo lpoptions -p Letters/test -l Shows that the the above command had no effect InputSlot=Auto After running the commands, there is no file /etc/cups/lpoptions - Even if an lptoptions file is created manually, it has no effect. + Even if an lpoptions file is created manually, it has no effect. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: - W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-Gray..\' already exists - W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-RGB..\' already exists - W [03/May/2021:11:20:51 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-Gray..\' already exists - W [03/May/2021:11:20:51 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-DeviceN..\' already exists + W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-Gray..\' already exists + W [27/Apr/2021:13:43:24 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PDF-RGB..\' already exists + W [03/May/2021:11:20:51 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-Gray..\' already exists + W [03/May/2021:11:20:51 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Letters-DeviceN..\' already exists Date: Mon
[Desktop-packages] [Bug 1926980] Re: 21.10 Impish / View Applications / Ubuntu Software / no entry possible
** Changed in: gnome-software (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1926980 Title: 21.10 Impish / View Applications / Ubuntu Software / no entry possible Status in gnome-software package in Ubuntu: Fix Released Bug description: Hello In the application: Ubuntu software, Show applications, characters cannot be entered in the search! My package hibiscus-ppa is online for 21.10 Impish for testing. Best regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1926980/+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 1841826] Re: Going to sleep instead of logging in while lid closed & external display
Agree that this is a serious issue. Like EAB, each of our setups remains constant: same laptop, dock, display, etc. This issue continues to recur probably 11 out of 12 startups when docked lid down. Notably, I have almost never seen it when the laptop is running standalone (out of the dock). Note that I do NOT try to hot dock or undock; these are all full shutdown/cold starts or manual suspend/later resume. And I rarely attempt the suspend/resume. That is only if I've been using the machine stand alone and suspended it, expecting to resume again standalone but instead wind up at my desk in the office. On the rare occasions when it's docked and doesn't suspend at the login prompt, it will then often throw an error like unable to lock due to application when it would (abnormally) suspend; and then when it reaches the desktop the wifi won't work or the dock's usb mouse won't work or something. Also, on the next restart after that, after suspending and my pressing the dock power again, I will often get a timing error instead of video on the external display. I have to then open the laptop lid in the dock and sometimes can take control to shut down. Other times I have to force power down at that point. Once that happens, I have to take the laptop out of the dock, start it stand alone, shut it fully down, dock it, and try again PLEASE fix this. Again: this was NOT an issue until the September 2020 Ubuntu updates to 20.04.1 which I believe also included a kernel update to address a security vulnerability? In any case, this started shortly after that. And yes: this should not be happening in an LTS version. -- 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/1841826 Title: Going to sleep instead of logging in while lid closed & external display Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have the above described problem, which seems to be very similar to bug #1716160 - laptop is in docking station and 2 monitors are connected (HDMI, DVI) - If the lid is closed and I boot the laptop I can input my credentials in the login screen and after hitting ENTER the laptop goes to sleep - If I then press the power button of the docking station the laptop wakes up and goes straight to the ubuntu environment w/o any user identification The device is a Lenovo T420 with classic docking station. Ubuntu 18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior independent of the graphics used. I do not know what to do now since the latest state of bug #1716160 is "fix released" and so I guess it should be part of the ubuntu version I use? Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 20:10:15 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'show-battery-percentage' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-08-13 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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-settings-daemon/+bug/1841826/+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 1720438] Re: brightness control broken nvidia
I've found this forum thread: https://forums.developer.nvidia.com/t/solus-nvidia-gtx-1070-brightness- control-not-working/54472 If I understand correctly, the OP resolved his issue by setting the kernel boot parameter nvidia.NVreg_EnableBacklightHandler=1 This did not solve the issue for me, however. -- 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/1720438 Title: brightness control broken nvidia Status in gnome-power: Confirmed Status in gnome-power-manager package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 beta 2 Nvidia 310M, 340.x official driver installed with Additional Drivers program The brightness control built into the laptop (Dell Vostro 3300) isn't changing the brightness. Normally I can use Fn + Up/Down arrow keys to change the brightness. The brightness control works fine in Ubuntu 16.04 with the same driver series. I don't know if this is a GNOME 3.26 bug but it's likely as I'm having the exact same problem with Fedora 26 on this laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1720438/+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 1849478] Re: [snap] (experimental) pipewire support not available
> Isn't better to use bindings now instead of those env variables? > As they tend to be a bit fragile... I assume you mean layouts? As long as upstream doesn't remove the ability to customize config/plugins directories, this should be functionally equivalent to using layouts. I don't have a strong opinion on the topic though, if you have good arguments in favour of layouts, I'm open to using them (the chromium snap already has one layout definition). -- 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/1849478 Title: [snap] (experimental) pipewire support not available Status in chromium-browser package in Ubuntu: In Progress Bug description: I'm using the chromium snap (currently 77.0.3865.120, rev 899), it's not possible to enable experimental support for pipewire, as the toggle doesn't show up in chrome://flags. It would be nice to have chromium compiled with pipewire support, to enable screensharing in Hangouts and similar apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1926956] Re: nautilus crashes when clicking on a mounted phone
Hi,thank you for your reply. Unfortunately there were no crashes in /var/crash that were related nor there was a "whoopsie". I will try to reproduce the crash, so far my initial attempts have failed. Best,Mateusz On Mon, 2021-05-03 at 13:32 +, Sebastien Bacher wrote: > Thank you for taking the time to report this bug and helping to > makeUbuntu better. It sounds like some part of the system has > crashed. Tohelp us find the cause of the crash please follow these > steps: > 1. Look in /var/crash for crash files and if found run:ubuntu-bug > YOURFILE.crashThen tell us the ID of the newly-created bug. > 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID > whereID is the content of file /var/lib/whoopsie/whoopsie-id on the > machine.Do you find any links to recent problems on that page? If so then > pleasesend the links to us. > 3. If step 2 also failed then apply the workaround from bug > 994921,reboot, reproduce the crash, and retry step 1. > Please take care to avoid attaching .crash files to bugs as we > areunable to process them as file attachments. It would also be a > securityrisk for yourself. > ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low > ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1926956 Title: nautilus crashes when clicking on a mounted phone Status in nautilus package in Ubuntu: Invalid Bug description: Mounted share (phone) went to sleep (lock screen activated), but the share was still mounted. I logged in to the phone at almost the same time when I clicked the mount in nautilus, which caused it to crash. May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: ** May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: ERROR:../src/nautilus-bookmark.c:372:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file)) May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: Bail out! ERROR:../src/nautilus-bookmark.c:372:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file)) Best, Mateusz ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 3 15:01:51 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'347' b'org.gnome.nautilus.window-state' b'initial-size' b'(1204, 765)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1926956/+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 1926980] Re: 21.10 Impish / View Applications / Ubuntu Software / no entry possible
Hello The software center is the basic installation. gnome software package missing? This must be included in the basic installation, the Ubuntu software program is there! This is not good? I want to test this again. Best regards -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1926980 Title: 21.10 Impish / View Applications / Ubuntu Software / no entry possible Status in gnome-software package in Ubuntu: New Bug description: Hello In the application: Ubuntu software, Show applications, characters cannot be entered in the search! My package hibiscus-ppa is online for 21.10 Impish for testing. Best regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1926980/+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 1926980] Re: 21.10 Impish / View Applications / Ubuntu Software / no entry possible
Hello Ok i can this make 2 new start i can entry in the search! Best Regards -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1926980 Title: 21.10 Impish / View Applications / Ubuntu Software / no entry possible Status in gnome-software package in Ubuntu: New Bug description: Hello In the application: Ubuntu software, Show applications, characters cannot be entered in the search! My package hibiscus-ppa is online for 21.10 Impish for testing. Best regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1926980/+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 1926070] Re: Please backport Desktop Icons NG to 20.04
When asking those questions, I assumed that changing it for everyone in 20.04 is an option under consideration. At least that's how I interpreted Sebastien's comment here: https://discourse.ubuntu.com/t/desktop-icons-integration- problems/14577/22 OTOH, if we'd only backport the package without changing any reverse dependencies, I realize that "main" does not apply. Doing so would help a few, but most users wouldn't notice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1926070 Title: Please backport Desktop Icons NG to 20.04 Status in Focal Backports: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Triaged Bug description: After testing Hirsute for a bit, I am convinced that Desktop Icons NG fixes a large and frustrating usability issue on the LTS desktop. It’s a wonderful restoration of functionality that I still trip over myself expecting from “muscle memory” in 20.04, but being reminded that I can’t do simple things like drag and drop. I have read some others suggestions to just install the extension oneself, and upon investigation, I found that it wasn’t a very clear process. Even Igor at dedoimedo.com had issues with going this route -> https://www.dedoimedo.com/computers/gnome-ding.html 4 . For these reasons, I am hoping that someone out there (hopefully more than one) agrees that replacing the current desktop icons package in 20.04 would only help those on an LTS desktop. As excited as I am for the interim releases (especially concerning Wayland and Pipewire), I don’t want to move away from a well-supported release to have a desktop that we could have (and I feel should have) in 20.04. I know that some work would be involved, but I for one would be very grateful, for what it’s worth. Thanks to all for your time. To manage notifications about this bug go to: https://bugs.launchpad.net/focal-backports/+bug/1926070/+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 1926980] Re: 21.10 Impish / View Applications / Ubuntu Software / no entry possible
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1926980 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu => gnome-software (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1926980 Title: 21.10 Impish / View Applications / Ubuntu Software / no entry possible Status in gnome-software package in Ubuntu: New Bug description: Hello In the application: Ubuntu software, Show applications, characters cannot be entered in the search! My package hibiscus-ppa is online for 21.10 Impish for testing. Best regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1926980/+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 1926980] [NEW] 21.10 Impish / View Applications / Ubuntu Software / no entry possible
You have been subscribed to a public bug: Hello In the application: Ubuntu software, Show applications, characters cannot be entered in the search! My package hibiscus-ppa is online for 21.10 Impish for testing. Best regards ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- 21.10 Impish / View Applications / Ubuntu Software / no entry possible https://bugs.launchpad.net/bugs/1926980 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. -- 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 1923040] Re: en-gb thesaurus is missing
@Mattia: Please see this short readme file: https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice- dictionaries/-/blob/master/dictionaries/en/README_en_GB_thes.txt My interpretation of that is that a symlink would not be a workaround, but it would be a setup in accordance with upstream's intention. That's also in line with Richard's info provided in comment #3. If I understand it correctly, they have put words and spelling variants for both American and British English in the same thesaurus. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice-dictionaries in Ubuntu. https://bugs.launchpad.net/bugs/1923040 Title: en-gb thesaurus is missing Status in libreoffice-dictionaries package in Ubuntu: Won't Fix Status in libreoffice-dictionaries package in Debian: Fix Released Bug description: Problem: The EN-GB thesaurus is missing for LibreOffice. To observe: 1. Fresh install of 21.04, set Location to United Kingdom. 2. Start LibreOffice Writer, choose the Tools menu. 3. The "Thesaurus" item is greyed out. Root cause: there is no mythes-en-gb package available (but there is mythes-en-us). Workaround: Give British English speakers the American English thesaurus i.e. symlink the US thesaurus by the GB one. cd /usr/share/mythes; ln -s th_en_US_v2.dat th_en_GB_v2.dat; ln -s th_en_US_v2.idx th_en_GB_v2.idx; Note: this report and tested workaround is on a fresh install of 21.04, although this problem has been extant for years. There appears to be no GB version of the thesaurus. However, as UK-english and USA- english language is so similar, it would be OK to provide the thesaurus from the US package in the meantime as a symlink. For others who find this bug report while searching the same issue, note that en-us is "english united-states" en-gb is "english great-britain", -ukis "ukraine". (Don't look for "english united-kingdom", en-uk, which doesn't exist). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1923040/+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 1926976] [NEW] during mouse drag operations I'm getting undesired/unprompted dropping and potentially picking up of something else
Public bug reported: I am not really sure this is an Xorg problem. Since my last system update (upon the system prompting), I think less than a week ago, I have noticed this troubling intermittent behavior. I go to drag (mouse- initiated) a window across some screen distances (between external monitors and my laptop's builtin monitor) the window will get dropped without me releasing the mouse button before arriving at my desired drop point. More than half the times this happens, something will immediately be picked up in a drag operation. Sometimes it is another window that begins being moved. Other times it is a window resize operation that is picked up. A third option is the selection of text. I have noticed that most of the time it is triggered when I am moving rapidly (though no more rapidly than I have done successfully in the past). Sometimes it happens when I pause during the drag operation. It even happens infrequently when I am dragging slowly. Often I can just go back and pick up the window and complete the operation. However, sometimes the problem just keeps happening until I give up and go away for 5 minutes or so. I have a stock configuration of 20.04. I keep it updated and haven't changed anything significant about X, Gnome, etc. I have done a few tweaks, but nothing I can think of that would relate to this problem. My laptop, a Dell XPS 13, uses a USB 3.1 hub and through that drives two monitors via HDMI. My mouse is bluetooth - Logitech MX Vertical. I don't believe I have installed any proprietary drivers. My 3 displays are arranged into an inverted "L" shape, as the laptop display is "below" and identically sized to the 27" monitor "above" it. The other 27" monitor is to the left of the first one. Some, potentially useful, debugging info: $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status $ bluetoothctl --version bluetoothctl: 5.53 $ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 9C:B6:D0:99:27:2C ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING RX bytes:21743080 acl:954252 sco:0 events:141080 errors:0 TX bytes:6895 acl:169 sco:0 commands:208 errors:0 Features: 0xff 0xfe 0x8f 0xfe 0xd8 0x3f 0x5b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF Link mode: SLAVE ACCEPT Name: 'kbuchs' Class: 0x0c010c Service Classes: Rendering, Capturing Device Class: Computer, Laptop HCI Version: 4.2 (0x8) Revision: 0x0 LMP Version: 4.2 (0x8) Subversion: 0x25a Manufacturer: Qualcomm (29) $ bluetoothctl Agent registered [CHG] Controller 9C:B6:D0:99:27:2C Pairable: yes [MX Vertical]# show Controller 9C:B6:D0:99:27:2C (public) Name: kbuchs Alias: kbuchs Class: 0x000c010c Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0535 Discovering: no Advertising Features: ActiveInstances: 0x00 SupportedInstances: 0x05 SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name [MX Vertical]# devices Device D4:51:67:AF:3D:FF MX Vertical [MX Vertical]# info D4:51:67:AF:3D:FF Device D4:51:67:AF:3D:FF (random) Name: MX Vertical Alias: MX Vertical Appearance: 0x03c2 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device(1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046
[Desktop-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
Update for groovy? Not likely at this point, focal will get it via 1925320 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+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 1841826] Re: Going to sleep instead of logging in while lid closed & external display
My work setup doesn't change. Same laptop (Thinkpad P14s), Ultradock, peripherals, screens etc ... and yet the behavior is very erratic. Just locking the screen will set the laptop into this useless zombie state. Most of the time the laptop has then got to be removed from the dock, woken out of sleep, lid closed again, and re-docked, before it's useful again on the dock. I cannot believe how badly broken this is! And in an LTS no less ... -- 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/1841826 Title: Going to sleep instead of logging in while lid closed & external display Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have the above described problem, which seems to be very similar to bug #1716160 - laptop is in docking station and 2 monitors are connected (HDMI, DVI) - If the lid is closed and I boot the laptop I can input my credentials in the login screen and after hitting ENTER the laptop goes to sleep - If I then press the power button of the docking station the laptop wakes up and goes straight to the ubuntu environment w/o any user identification The device is a Lenovo T420 with classic docking station. Ubuntu 18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior independent of the graphics used. I do not know what to do now since the latest state of bug #1716160 is "fix released" and so I guess it should be part of the ubuntu version I use? Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 20:10:15 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'show-battery-percentage' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-08-13 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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-settings-daemon/+bug/1841826/+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 1926932] Re: Error message too short to understand what is wrong
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1926932 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1926932 Title: Error message too short to understand what is wrong Status in gnome-shell package in Ubuntu: New Bug description: This is on Ubuntu 20.10 (Groovy Gorilla). I placed a text file on my desktop, and on clicking it, I was shown the error "Execution of /home/myUsername/Desktop/.goutputstream-WU... Command not found". Even on clicking the error message that popped up, it didn't expand to show more details. So basically, the bug I'm reporting is about error messages being too short/obscure to be useful for users to figure out what the problem actually is. Image attached. The black spot in the middle was added by me to obscure the username. (on a a side note, I was clicking a plain text document which had the checkbox for "allow executing file as a program" ticked). Clicking any other textfile didn't show this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1926932/+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 1902768] Re: [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10
I actually updated to Hirsute and the issue seems to be gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902768 Title: [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10 Status in pulseaudio package in Ubuntu: New Bug description: In 20/04 sound worked via headphones worked fine. After upgrade no sound is heard and the audio output device list only has HDMI and S/PDIF as possible choices. Windows 10 on the same machine works without problems. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Nov 3 20:39:59 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-09-19 (44 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity Symptom: installer UpgradeStatus: Upgraded to groovy on 2020-11-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-12-10 (137 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: pulseaudio 1:13.99.2-1ubuntu2.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Tags: groovy Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1004 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1004:bd08/13/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902768/+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 1926932] [NEW] Error message too short to understand what is wrong
You have been subscribed to a public bug: This is on Ubuntu 20.10 (Groovy Gorilla). I placed a text file on my desktop, and on clicking it, I was shown the error "Execution of /home/myUsername/Desktop/.goutputstream-WU... Command not found". Even on clicking the error message that popped up, it didn't expand to show more details. So basically, the bug I'm reporting is about error messages being too short/obscure to be useful for users to figure out what the problem actually is. Image attached. The black spot in the middle was added by me to obscure the username. (on a a side note, I was clicking a plain text document which had the checkbox for "allow executing file as a program" ticked). Clicking any other textfile didn't show this error. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Error message too short to understand what is wrong https://bugs.launchpad.net/bugs/1926932 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- 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 1902768] Re: [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10
@Jussi could you check if you have pipewire installed and if you do try to uninstall it to see if that makes a difference? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1902768 Title: [ASUS ROG STRIX B550-F] headphone not correctly detected on 20.10 Status in pulseaudio package in Ubuntu: New Bug description: In 20/04 sound worked via headphones worked fine. After upgrade no sound is heard and the audio output device list only has HDMI and S/PDIF as possible choices. Windows 10 on the same machine works without problems. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Nov 3 20:39:59 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-09-19 (44 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity Symptom: installer UpgradeStatus: Upgraded to groovy on 2020-11-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-12-10 (137 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Package: pulseaudio 1:13.99.2-1ubuntu2.3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Tags: groovy Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/13/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1004 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1004:bd08/13/2020:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1902768/+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 1926956] Re: nautilus crashes when clicking on a mounted phone
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1926956 Title: nautilus crashes when clicking on a mounted phone Status in nautilus package in Ubuntu: Invalid Bug description: Mounted share (phone) went to sleep (lock screen activated), but the share was still mounted. I logged in to the phone at almost the same time when I clicked the mount in nautilus, which caused it to crash. May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: ** May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: ERROR:../src/nautilus-bookmark.c:372:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file)) May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: Bail out! ERROR:../src/nautilus-bookmark.c:372:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file)) Best, Mateusz ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 3 15:01:51 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'347' b'org.gnome.nautilus.window-state' b'initial-size' b'(1204, 765)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1926956/+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 1923267] Re: Gjs promises on Gio.File operations don't work anymore after upgrading libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
The package is waiting in the SRU queue
https://launchpad.net/ubuntu/hirsute/+queue?queue_state=1&queue_text=gjs
you may ask in #ubuntu-release to speed it up :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1923267
Title:
Gjs promises on Gio.File operations don't work anymore after upgrading
libglib2.0-0 2.67.5-2 to 2.68.0-1 (and indicator-multiload app broke)
Status in gjs package in Ubuntu:
Fix Released
Status in gnome-shell-extension-appindicator package in Ubuntu:
Won't Fix
Status in gjs source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
As per glib commit
https://gitlab.gnome.org/GNOME/glib/-/commit/d52728f99
Gio.File.new_for_path("") returns a GDummyFile implementation, while
Gio._promisify relies on it being a LocalFile, so we don't promisify
the right methods.
[ Test case ]
gjs -c "imports.gi.Gio._promisify(imports.gi.Gio._LocalFilePrototype,
'delete_async', 'delete_finish');
print(imports.gi.Gio.File.new_for_path('/').delete_async(0, null));" &&
echo GJS works
Should write on terminal:
[object Promise]
GJS works
In the bugged version would instead just:
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: JS ERROR: TypeError: method
Gio.File.delete_async: At least 3 arguments required, but only 2 passed
@:2:48
(gjs:226393): Gjs-CRITICAL **: 16:45:51.396: Script
threw an exception
[ Regression potential ]
Gjs apps are slower in starting up, or not act properly when / is not
a local location.
---
Problem tested in two different environments:
- Ubuntu 21.04 Beta amd64
- Ubuntu 21.04 Beta arm64 (Raspberry Pi 4B 8GB)
After upgrading these packages:
libglib2.0-02.67.5-2 to 2.68.0-1
libglib2.0-bin 2.67.5-2 to 2.68.0-1
libglib2.0-data 2.67.5-2 to 2.68.0-1
The app indicator-multiload (0.4-0ubuntu5) doesn't work showing only
three dots (...) instead of the graphic expected. It's throwing error
messages to the system journal every second or so (depends of the
refresh interval selected in the app settings):
abr 10 01:08:06 fpgrpi ubuntu-appindicat...@ubuntu.com[1487]:
multiload, Impossible to read image from path '/run/user/1026
/multiload-icons-Wc8kck/icons/indicator-multiload-graphs-0.png':
TypeError: method Gio.File.read_async: At least 3 arguments required,
but only 2 passed
Don't know if this is a documented change of that method and the bug
should be open for the indicator-multiload app. Please, if that's the
case just let me know to do it.
Thanks and best reagrds
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1923267/+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 1926956] [NEW] nautilus crashes when clicking on a mounted phone
Public bug reported: Mounted share (phone) went to sleep (lock screen activated), but the share was still mounted. I logged in to the phone at almost the same time when I clicked the mount in nautilus, which caused it to crash. May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: ** May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: ERROR:../src/nautilus-bookmark.c:372:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file)) May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: Bail out! ERROR:../src/nautilus-bookmark.c:372:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file)) Best, Mateusz ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 3 15:01:51 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'347' b'org.gnome.nautilus.window-state' b'initial-size' b'(1204, 765)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2020.03.04 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1926956 Title: nautilus crashes when clicking on a mounted phone Status in nautilus package in Ubuntu: New Bug description: Mounted share (phone) went to sleep (lock screen activated), but the share was still mounted. I logged in to the phone at almost the same time when I clicked the mount in nautilus, which caused it to crash. May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: ** May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: ERROR:../src/nautilus-bookmark.c:372:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file)) May 3 14:58:41 testosteron org.gnome.Nautilus[21582]: Bail out! ERROR:../src/nautilus-bookmark.c:372:nautilus_bookmark_connect_file: assertion failed: (!nautilus_file_is_gone (bookmark->file)) Best, Mateusz ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 3 15:01:51 2021 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'347' b'org.gnome.nautilus.window-state' b'initial-size' b'(1204, 765)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1926956/+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 1838890] Re: Suspected memory leak in xenial backport of fix for CVE-2019-13012
This bug was fixed in the package glib2.0 - 2.32.4-0ubuntu1.4 --- glib2.0 (2.32.4-0ubuntu1.4) precise-security; urgency=medium * SECURITY REGRESSION: regression in last security update (LP: #1838890) - debian/patches/CVE-2019-13012-regression.patch: fix a memory leak introduced by the last security update while not properly handled the g_file_get_patch function in gio/gkeyfilesettingsbackend.c. -- leo.barb...@canonical.com (Leonidas S. Barbosa) Mon, 05 Aug 2019 12:54:19 -0300 ** Changed in: glib2.0 (Ubuntu Precise) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1838890 Title: Suspected memory leak in xenial backport of fix for CVE-2019-13012 Status in glib2.0 package in Ubuntu: In Progress Status in glib2.0 source package in Precise: Fix Released Status in glib2.0 source package in Trusty: In Progress Status in glib2.0 source package in Xenial: Fix Released Bug description: (This is only from source code inspection, not tested in real use - I don't actually use Ubuntu.) The upstream fix for CVE-2019-13012 included this change: - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + g_mkdir_with_parents (g_file_peek_path (kfsb->dir), 0700); However, g_file_peek_path() was only introduced in GLib 2.56. The backport in the xenial package has this instead: - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + g_mkdir_with_parents (g_file_get_path (kfsb->dir), 0700); This is not equivalent. The difference between g_file_peek_path() and the older g_file_get_path() is that g_file_get_path() makes a copy, which must be freed with g_free() after use. As a result, there is now a memory leak. A non-leaky backport would look something like this, which is what I've done in a proposed backport for Debian 9 'stretch': + char *dir; ... - g_file_make_directory_with_parents (kfsb->dir, NULL, NULL); + dir = g_file_get_path (kfsb->dir); + g_mkdir_with_parents (dir, 0700); + g_free (dir); To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1838890/+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 1821415] Autopkgtest regression report (apport/2.20.11-0ubuntu50.6)
All autopkgtests for the newly accepted apport (2.20.11-0ubuntu50.6) for groovy have finished running. The following regressions have been reported in tests triggered by the package: ubuntu-release-upgrader/1:20.10.15 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/groovy/update_excuses.html#apport [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Fix Released Status in policykit-1 package in Ubuntu: Won't Fix Status in apport source package in Focal: Fix Committed Status in policykit-1 source package in Focal: Won't Fix Status in apport source package in Groovy: Fix Committed Status in policykit-1 source package in Groovy: Won't Fix Bug description: [Impact] The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. [Test Case] 1) ssh into an Ubuntu Desktop install of Ubuntu 20.04 LTS or Ubuntu 20.10 2) sudo touch /var/log/plymouth-debug.log 3) ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. With the version of apport from -proposed you will not see the "AUTHENTICATION FAILED" error and the plymouth-debug.log file will be collected. [Where Problems Could Occur] It's possible that the spawned pkttyagent process does not get cleaned up properly and could be left running. When testing the SRU we should confirm it is not still running. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1925530] Re: Backport Metro Exodus Mesa fix into Hirsute
This will be fixed when mesa 21.0.x is backported (see #1925434). Closing this ticket. ** Changed in: mesa (Ubuntu) Status: New => Invalid ** Changed in: hundredpapercuts Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1925530 Title: Backport Metro Exodus Mesa fix into Hirsute Status in One Hundred Papercuts: Invalid Status in mesa package in Ubuntu: Invalid Bug description: Please, consider backporting an important fix for "memory leak on descriptor pool reset with layout_size=0" into Ubuntu 21.04 Mesa. Without this fix, Metro Exodus and possibly other games cause system to hang or crash after playing for some time. Here is a MR with the fix: https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/10317 It is already staged to be backported into current stable Mesa releases and so it should be fine to apply it as a downstream patch for Mesa 21.0.1 in Ubuntu Hirsute. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1925530/+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 1926951] [NEW] SRU the current 40.1 stable update
Public bug reported: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/blob/gnome-40/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the system activity is correctly reflected on the different views, also than doing changes to priorities is working * Regression potential There is a fix for the headerbar buttons moving, check that the windows layout is still correct and that the buttons and menus are working as expected ** Affects: gnome-system-monitor (Ubuntu) Importance: Low Status: Fix Committed ** Changed in: gnome-system-monitor (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1926951 Title: SRU the current 40.1 stable update Status in gnome-system-monitor package in Ubuntu: Fix Committed Bug description: * Impact That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/blob/gnome-40/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Check that the system activity is correctly reflected on the different views, also than doing changes to priorities is working * Regression potential There is a fix for the headerbar buttons moving, check that the windows layout is still correct and that the buttons and menus are working as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1926951/+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 1926316] Re: lxappearance crashes on launch
** Tags added: rls-hh-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1926316 Title: lxappearance crashes on launch Status in glib2.0 package in Ubuntu: Fix Committed Bug description: Backtrace of the segmentation fault Program received signal SIGSEGV, Segmentation fault. 0x7790c79d in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 (gdb) bt #0 0x7790c79d in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7790ccc1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7790cf41 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7790d079 in g_key_file_load_from_file () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x55407072 in load_icon_themes_from_dir () #5 0x554073dd in icon_theme_init () #6 0x55404c92 in main () Strace shows that the programs borks while trying to load the icon theme "/usr/share/icons/gnome/index.theme". ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lxappearance 0.6.3-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown Config_System_openbox: Error: [Errno 2] No such file or directory: '/etc/xdg/lxsession/openbox/desktop.conf' CurrentDesktop: lxde Date: Tue Apr 27 21:47:03 2021 Icons_Default: No icons theme configured by default InstallationDate: Installed on 2021-01-12 (105 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: lxappearance UpgradeStatus: Upgraded to hirsute on 2021-04-22 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1926316/+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
