[Desktop-packages] [Bug 1911921] Re: gnome-shell crashed with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL)
Ah! You need to configure the auto-move-windows extension specifically for Chrome. Then it occurs. ** Summary changed: - gnome-shell crashed with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL) + When using auto-move-windows extension, gnome-shell crashed with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => In Progress ** Changed in: gnome-shell-extensions (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1911921 Title: When using auto-move-windows extension, gnome-shell crashed with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extensions package in Ubuntu: Confirmed Bug description: As in bug 1864052, putting a Chrome video into PiP mode crashes gnome- shell, although this time, in a different location. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-12.13-generic 5.10.6 Uname: Linux 5.10.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jan 15 16:04:30 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-03-14 (1037 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 meta_window_stick () at /lib/x86_64-linux-gnu/libmutter-7.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1911921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911921] Re: gnome-shell crashed with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL)
I can't seem to get the crash to occur. Tried Chrome and Chromium with PiP in both Xorg and Wayland and it works. Also tried with the auto-move-windows extension which the upstream bug suggests is the trigger, but again no crash. Also tried both hirsute and upstream GNOME. Any more hints? Can you point to a free URL that triggers the problem? ** Also affects: gnome-shell-extensions (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-shell-extensions (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/1911921 Title: When using auto-move-windows extension, gnome-shell crashed with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL) Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extensions package in Ubuntu: Confirmed Bug description: As in bug 1864052, putting a Chrome video into PiP mode crashes gnome- shell, although this time, in a different location. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-12.13-generic 5.10.6 Uname: Linux 5.10.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jan 15 16:04:30 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-03-14 (1037 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 meta_window_stick () at /lib/x86_64-linux-gnu/libmutter-7.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1911921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913045] Re: [i915] System freezes with kernel 5.8, but not 5.4
** Summary changed: - System freezes when in lockscreen + [i915] System freezes with kernel 5.8, but not 5.4 ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New ** Tags added: regression-update -- 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/1913045 Title: [i915] System freezes with kernel 5.8, but not 5.4 Status in linux package in Ubuntu: Confirmed Bug description: My system freezes when I'm in lockscreen. This happens every few ours after I leave the computer running some low to mediocre computation tasks, no memory problems. It does not happen when I run heavy tasks. I can only hard reboot, nothing else is working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 11:26:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2020-06-02 (236 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20HD0001MZ ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=df6eb87b-cd89-4867-9c7c-de8b08bbdbcf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2020 dmi.bios.release: 1.63 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET88W (1.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HD0001MZ dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET88W(1.63):bd04/22/2020:br1.63:efr1.35:svnLENOVO:pn20HD0001MZ:pvrThinkPadT470:rvnLENOVO:rn20HD0001MZ:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HD0001MZ dmi.product.sku: LENOVO_MT_20HD_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1913045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913480] Re: Sound>Output>Configuration always resets
** Package changed: ubuntu => gnome-control-center (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913480 Title: Sound>Output>Configuration always resets Status in gnome-control-center package in Ubuntu: New Bug description: In "Settings>Sound>Output" If set my "Output Device" to "HDMI / DisplayPort 5" and set "Configuration" to "Digital Surround 5.1" If I close the receiver and open it again... The configuration will reset to "Digital stereo" The expected behavior would be to keep the "Digital Surround 5.1"; not resetting it every time. Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913480] [NEW] Sound>Output>Configuration always resets
You have been subscribed to a public bug: In "Settings>Sound>Output" If set my "Output Device" to "HDMI / DisplayPort 5" and set "Configuration" to "Digital Surround 5.1" If I close the receiver and open it again... The configuration will reset to "Digital stereo" The expected behavior would be to keep the "Digital Surround 5.1"; not resetting it every time. Ubuntu 20.04 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Sound>Output>Configuration always resets https://bugs.launchpad.net/bugs/1913480 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center 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 1913045] Re: System freezes when in lockscreen
Good morning. Yes, this does not happen with 5.4.92. I reproduced the exact same situation that always made my system freeze with the 5.8 kernel. It has been running the whole night now and it did not freeze with 5.4.92. -- 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/1913045 Title: System freezes when in lockscreen Status in gnome-shell package in Ubuntu: Incomplete Bug description: My system freezes when I'm in lockscreen. This happens every few ours after I leave the computer running some low to mediocre computation tasks, no memory problems. It does not happen when I run heavy tasks. I can only hard reboot, nothing else is working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 11:26:10 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:2245] InstallationDate: Installed on 2020-06-02 (236 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20HD0001MZ ProcEnviron: LANGUAGE=de_CH:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_CH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=df6eb87b-cd89-4867-9c7c-de8b08bbdbcf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2020 dmi.bios.release: 1.63 dmi.bios.vendor: LENOVO dmi.bios.version: N1QET88W (1.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HD0001MZ dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.35 dmi.modalias: dmi:bvnLENOVO:bvrN1QET88W(1.63):bd04/22/2020:br1.63:efr1.35:svnLENOVO:pn20HD0001MZ:pvrThinkPadT470:rvnLENOVO:rn20HD0001MZ:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470 dmi.product.name: 20HD0001MZ dmi.product.sku: LENOVO_MT_20HD_BU_Think_FM_ThinkPad T470 dmi.product.version: ThinkPad T470 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913045/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910235] Re: The mouse stops working after trying to take an area screenshot in some apps on Xorg
** Tags added: fixed-in-3.38.4 -- 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/1910235 Title: The mouse stops working after trying to take an area screenshot in some apps on Xorg Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Steps to reproduce this bug: 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen 5. Try to switch between applications using the panel and check the operation of the mouse in other applications besides browser (in my case Slack) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-26 (71 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1910235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1062888] Re: gedit wrote critical errors on output
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1062888 Title: gedit wrote critical errors on output Status in gedit package in Ubuntu: Expired Bug description: The following was written on the output when gedit was started from the command line. Even though no visible malfunction was observed, maybe one of developers has a couple minutes to fix it. (gedit:4303): LibZeitgeist-CRITICAL **: Failed to create proxy for Zeitgeist daemon: Error calling StartServiceByName for org.gnome.zeitgeist.Engine: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/zeitgeist-daemon exited with status 1 (gedit:4303): LibZeitgeist-CRITICAL **: Unable to connect to Zeitgeist daemon: Error calling StartServiceByName for org.gnome.zeitgeist.Engine: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/zeitgeist-daemon exited with status 1 (gedit:4303): GLib-GIO-CRITICAL **: g_dbus_proxy_get_connection: assertion `G_IS_DBUS_PROXY (proxy)' failed (gedit:4303): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (gedit:4303): GLib-GIO-CRITICAL **: g_dbus_connection_signal_subscribe: assertion `G_IS_DBUS_CONNECTION (connection)' failed ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Sat Oct 6 17:10:45 2012 InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1062888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1325063] Re: Gedit preferences windows is empty
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1325063 Title: Gedit preferences windows is empty Status in gedit package in Ubuntu: Expired Bug description: When I click the preferences item in menu I get a empty window that is just titled preferences. There is nothing in it and if I drag it to a bigger size an empty plane appears. When starting gedit as root I see the following error in terminal: (gedit:13564): Gtk-CRITICAL **: Error building template class 'GeditPreferencesDialog' for an instance of type 'GeditPreferencesDialog': Invalid object type `PeasGtkPluginManager' (gedit:13564): GLib-GIO-CRITICAL **: g_settings_bind_with_mapping: assertion 'G_IS_OBJECT (object)' failed (gedit:13564): GLib-GIO-CRITICAL **: g_settings_bind_with_mapping: assertion 'G_IS_OBJECT (object)' failed (gedit:13564): GLib-GIO-CRITICAL **: g_settings_bind_with_mapping: assertion 'G_IS_OBJECT (object)' failed ... UBUNTU 14.04, xsfc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1325063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913218] Re: Obscure shortcut selector behaviour
Actually it's much less than one in 400. Most complaints are just "you didn't fix my bug and this is the first notification I've received in N years". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913218 Title: Obscure shortcut selector behaviour Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: I'm trying to set a shortcut for keyboard layout switching, but it's impossible to use some keyboard buttons. Also, pressing some combinations leads to unexpected results. For example: - Shift+Ctrl - impossible to set - Shift+Alt - impossible to set - Ctrl+Alt - impossible to set - Shift+Ctrl+Alt - impossible to set - Shift+Alt+Space - this combination is being detected as "Shift+Space" - Cmd (Win) + any two or three keys is impossible to set (works with 4 keys though). Since Shift+Ctrl and Shift+Alt are very popular shortcuts (due to being default in Windows for ages), not being able to use them in Ubuntu is a pain. Reproduction steps: - Open gnome-control-center - Go to "Keyboard shortcuts" - Try to change any shortcut to one from my list System info: Ubuntu 20.10 gnome-control-center: Installed: 1:3.38.1-1ubuntu1 Candidate: 1:3.38.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1913218/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913218] Re: Obscure shortcut selector behaviour
Any bug reported through the ideal means of 'ubuntu-bug' or from errors.ubuntu.com will get the tags automatically. So the tags themselves are not new. As for people who don't like the process, that's OK. I find about one in 400 bugs receive a complaint from affected persons. And one in 400 is pretty low so I consider the procedure a success. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913218 Title: Obscure shortcut selector behaviour Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: I'm trying to set a shortcut for keyboard layout switching, but it's impossible to use some keyboard buttons. Also, pressing some combinations leads to unexpected results. For example: - Shift+Ctrl - impossible to set - Shift+Alt - impossible to set - Ctrl+Alt - impossible to set - Shift+Ctrl+Alt - impossible to set - Shift+Alt+Space - this combination is being detected as "Shift+Space" - Cmd (Win) + any two or three keys is impossible to set (works with 4 keys though). Since Shift+Ctrl and Shift+Alt are very popular shortcuts (due to being default in Windows for ages), not being able to use them in Ubuntu is a pain. Reproduction steps: - Open gnome-control-center - Go to "Keyboard shortcuts" - Try to change any shortcut to one from my list System info: Ubuntu 20.10 gnome-control-center: Installed: 1:3.38.1-1ubuntu1 Candidate: 1:3.38.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1913218/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910235] Re: The mouse stops working after trying to take a screenshot while Chrome menus are open in Xorg sessions
Let's assume this is https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/2869 which was just fixed upstream. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2869 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2869 ** Also affects: gnome-shell-extensions Importance: Undecided Status: New ** Project changed: gnome-shell-extensions => gnome-shell ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2869 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2869 ** Changed in: gnome-shell Importance: Undecided => Unknown ** Changed in: gnome-shell Status: New => Unknown ** Changed in: gnome-shell Remote watch: None => gitlab.gnome.org/GNOME/gnome-shell/-/issues #2869 ** Tags added: fixed-upstream ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-40 ** Summary changed: - The mouse stops working after trying to take a screenshot while Chrome menus are open in Xorg sessions + The mouse stops working after trying to take an area screenshot in some apps on Xorg -- 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/1910235 Title: The mouse stops working after trying to take an area screenshot in some apps on Xorg Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Steps to reproduce this bug: 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen 5. Try to switch between applications using the panel and check the operation of the mouse in other applications besides browser (in my case Slack) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-26 (71 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1910235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913218] Re: Obscure shortcut selector behaviour
On 2021-01-28 04:29, Daniel van Vugt wrote: > When a release reaches end of life we can then quickly identify which > bugs are no longer affecting any supported release, and close them. That's what I suspected. ;) While I understand, I don't really like it. For bugs of some significance I would prefer them to stay until resolved. For truly upstream and less important bugs, why not just point the bug reporter to upstream and close it with "won't fix", with the explanation that we don't have the resources to fix it in Ubuntu only. > If you are confident that other releases are affected then just add > more tags like 'focal'. Done. ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913218 Title: Obscure shortcut selector behaviour Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: I'm trying to set a shortcut for keyboard layout switching, but it's impossible to use some keyboard buttons. Also, pressing some combinations leads to unexpected results. For example: - Shift+Ctrl - impossible to set - Shift+Alt - impossible to set - Ctrl+Alt - impossible to set - Shift+Ctrl+Alt - impossible to set - Shift+Alt+Space - this combination is being detected as "Shift+Space" - Cmd (Win) + any two or three keys is impossible to set (works with 4 keys though). Since Shift+Ctrl and Shift+Alt are very popular shortcuts (due to being default in Windows for ages), not being able to use them in Ubuntu is a pain. Reproduction steps: - Open gnome-control-center - Go to "Keyboard shortcuts" - Try to change any shortcut to one from my list System info: Ubuntu 20.10 gnome-control-center: Installed: 1:3.38.1-1ubuntu1 Candidate: 1:3.38.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1913218/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913218] Re: Obscure shortcut selector behaviour
It's a handy tool for dealing with masses of bugs, on average. When a release reaches end of life we can then quickly identify which bugs are no longer affecting any supported release, and close them. This prevents the backlogs from growing indefinitely and has been quite successful... https://docs.google.com/spreadsheets/d/e/2PACX- 1vRDHPxGBHqM6XkT_S8ggtYfD0xchKSUD_z9PopNVE3G1rU05fVSnxDGcDsEstl7gu7N- tzCU6mLUp2V/pubchart?oid=254968654=interactive If you are confident that other releases are affected then just add more tags like 'focal'. And then the bug is protected and will stay open for years to come. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913218 Title: Obscure shortcut selector behaviour Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: I'm trying to set a shortcut for keyboard layout switching, but it's impossible to use some keyboard buttons. Also, pressing some combinations leads to unexpected results. For example: - Shift+Ctrl - impossible to set - Shift+Alt - impossible to set - Ctrl+Alt - impossible to set - Shift+Ctrl+Alt - impossible to set - Shift+Alt+Space - this combination is being detected as "Shift+Space" - Cmd (Win) + any two or three keys is impossible to set (works with 4 keys though). Since Shift+Ctrl and Shift+Alt are very popular shortcuts (due to being default in Windows for ages), not being able to use them in Ubuntu is a pain. Reproduction steps: - Open gnome-control-center - Go to "Keyboard shortcuts" - Try to change any shortcut to one from my list System info: Ubuntu 20.10 gnome-control-center: Installed: 1:3.38.1-1ubuntu1 Candidate: 1:3.38.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1913218/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913218] Re: Obscure shortcut selector behaviour
On 2021-01-27 08:24, Daniel van Vugt wrote: > ** Tags added: groovy Let me ask out of curiosity: Why did you add that tag? The issue at hand has been there for many cycles. While I see that the OP happens to use groovy, I don't see how the tag adds any relevant info from a bug triaging POV. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913218 Title: Obscure shortcut selector behaviour Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: I'm trying to set a shortcut for keyboard layout switching, but it's impossible to use some keyboard buttons. Also, pressing some combinations leads to unexpected results. For example: - Shift+Ctrl - impossible to set - Shift+Alt - impossible to set - Ctrl+Alt - impossible to set - Shift+Ctrl+Alt - impossible to set - Shift+Alt+Space - this combination is being detected as "Shift+Space" - Cmd (Win) + any two or three keys is impossible to set (works with 4 keys though). Since Shift+Ctrl and Shift+Alt are very popular shortcuts (due to being default in Windows for ages), not being able to use them in Ubuntu is a pain. Reproduction steps: - Open gnome-control-center - Go to "Keyboard shortcuts" - Try to change any shortcut to one from my list System info: Ubuntu 20.10 gnome-control-center: Installed: 1:3.38.1-1ubuntu1 Candidate: 1:3.38.1-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1913218/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913453] Re: Xorg freeze
Next time the problem starts please open a Terminal window and run: journalctl -b0 > curboot.txt Or if you had to reboot then instead run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. Also, while the problem is happening, does 'top' show any process using high CPU? ** 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/1913453 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1913453/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913485] Re: PulseEffects + YTMD
Please explain in more detail what kind of problem you are experiencing. ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => pulseeffects (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/1913485 Title: PulseEffects + YTMD Status in pulseeffects package in Ubuntu: Incomplete Bug description: when opening both apps its always a big complication with a lot a latency and distortion ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CompositorRunning: None Date: Wed Jan 27 13:56:37 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0682] InstallationDate: Installed on 2018-01-28 (1095 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Acer TravelMate P653-M ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=068acae8-2f26-4217-b2a3-e5afc4dd438d ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.03. dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P653-M dmi.board.vendor: Acer dmi.board.version: V2.03. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.03. dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.03.:bd10/16/2012:svnAcer:pnTravelMateP653-M:pvrV2.03.:rvnAcer:rnTravelMateP653-M:rvrV2.03.:cvnAcer:ct9:cvrV2.03.: dmi.product.family: TravelMate P653-M dmi.product.name: TravelMate P653-M dmi.product.sku: TravelMate P653-M_0682_2.03 dmi.product.version: V2.03. dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseeffects/+bug/1913485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913217] Re: [nvidia] Screen going black and not responding to input
Also unfortunately, you already have the latest Nvidia driver that supports your GPU :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1913217 Title: [nvidia] Screen going black and not responding to input Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expecting: (usually after opening a new application): window to open Happened instead: Screen going black. System not responding to inputs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 21:49:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed nvidia-340, 340.108, 5.8.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] InstallationDate: Installed on 2021-01-24 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=22238608-1c5f-40aa-a8f4-1fded14f6b84 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/nvidia-graphics-drivers-340/+bug/1913217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913217] Re: [nvidia] Screen going black and not responding to input
Thanks. Unfortunately it looks like the nvidia kernel module that's crashing, which of course will affect your graphics. ** Summary changed: - Screen going black and not responding to input + [nvidia] Screen going black and not responding to input ** Package changed: gnome-shell (Ubuntu) => nvidia-graphics-drivers-340 (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/1913217 Title: [nvidia] Screen going black and not responding to input Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expecting: (usually after opening a new application): window to open Happened instead: Screen going black. System not responding to inputs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 21:49:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed nvidia-340, 340.108, 5.8.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] InstallationDate: Installed on 2021-01-24 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=22238608-1c5f-40aa-a8f4-1fded14f6b84 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/nvidia-graphics-drivers-340/+bug/1913217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1913411] Re: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu.
Thanks for the bug report. it appears version 1.14.2 is not supported on Ubuntu 20.04. If you need that version then you might need to upgrade to Ubuntu 20.10. ** Tags added: focal ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid ** Also affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Changed in: modemmanager (Ubuntu) Status: New => 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/1913411 Title: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. Status in gnome-shell package in Ubuntu: Invalid Status in modemmanager package in Ubuntu: Invalid Bug description: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. I just can see mobile broadband in network in system settings menu. OS: ubuntu20.04 Module: SDX55 ModemManager:1.14.2 iusse: 1.No mobile broadband in system status bar drop-down menu. 2.Every time I connect to the mobile broadband network in system settings menu, I need to add new connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913439] Re: "Alert Sound" change has no effect at all
** Tags added: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913439 Title: "Alert Sound" change has no effect at all Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1) Change "Alert Sound" to , say, Drip. 2) open terminal and press "Backspace" to test Expected: Hear Drip Actual: hear default Related to https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320 but in my case doesn't change to anything else at all even via "Default" intermediate. It is always "Default". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880405] Re: Unresponsive GUI, sometimes high CPU, and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDia
A potential fix has been proposed upstream: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1676 ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Importance: Undecided => High -- 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/1880405 Title: Unresponsive GUI, sometimes high CPU, and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: In Progress Bug description: O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873365] Re: gedit icon is too pale
It's not released to Ubuntu yet, so that's Fix Committed. ** Changed in: yaru-theme (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1873365 Title: gedit icon is too pale Status in yaru-theme package in Ubuntu: Fix Committed Bug description: The grey lines representing text on the paper sheet and the tip of the pencil in the icon are too pale. They are almost invisible so that the gedit icon is seen as a white rectangle crossed by a blue bar. Before focal, the icons of gedit and Evince used to have similar design, that is they both were pale. Now in focal, the Evince icon is redesigned and it is more clear with more contrast. The suggestion is to apply similar modifications to the gedit icon to make it more clear. For example, it can use the same dark gray color of the text lines as Evince icon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-icon 20.04.5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 01:10:13 2020 Dependencies: InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1873365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880405] Re: Unresponsive GUI, sometimes high CPU, and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDia
** Summary changed: - High CPU and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 + Unresponsive GUI, sometimes high CPU, and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 -- 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/1880405 Title: Unresponsive GUI, sometimes high CPU, and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: In Progress Bug description: O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
Thanks. The fix is not in Ubuntu yet, so not "released". ** Changed in: yaru-theme (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Fix Committed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868330] Re: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work
Hello, did you fix this issue? -- 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/1868330 Title: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work Status in alsa-driver package in Ubuntu: Confirmed Bug description: On Focal Fossa the microphone is recognised but doesn't work. Chromium shows the microphone as present but off, and if it is renabled it goes off again after a couple of seconds. Chromium logs this error: [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th chromium_chromium.desktop[9531]: [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation is nullptr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1687 F pulseaudio /dev/snd/pcmC0D0p: user 1687 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 23:03:01 2020 InstallationDate: Installed on 2020-03-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913499] [NEW] Bluetooth input doesn't work w/ Bose QC35 ii
Public bug reported: When connecting the Bose QC35 ii, the bluetooth audio works just fine initially, but the microphone does not. When I go to the sound settings and change the mic input to use the QC35 ii bluetooth input, the audio changes from stereo to mono and sounds terrible and cannot understand anything. Also the mic picks up some input, but the result output sounds about the same, completely un-understandable, a stuttering digitized version of the input. > lsb_release -rd Description:Ubuntu 20.10 Release:20.10 Linux dan-xps-9700 5.10.5-051005-generic #202101061537 SMP Wed Jan 6 15:43:53 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux 3. I expected the microphone input and headset output to both work simultaneously via bluetooth. 4. Only the headset output worked well, when enabling microphone both sounded terrible (unusable). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 Uname: Linux 5.10.5-051005-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 17:53:00 2021 InstallationDate: Installed on 2021-01-06 (21 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep bluetooth MachineType: Dell Inc. XPS 17 9700 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.5-051005-generic root=UUID=d87c0f2c-adf4-493f-95dc-e2df02f584b3 ro quiet splash vt.handoff=7 SourcePackage: bluez 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: 03CPGC 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.:rn03CPGC:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: UART BD Address: 28:C2:1F:87:52:EC ACL MTU: 1024:8 SCO MTU: 240:4 UP RUNNING PSCAN RX bytes:1599 acl:0 sco:0 events:91 errors:0 TX bytes:198368 acl:0 sco:0 commands:849 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2021-01-27T17:24:11.108718 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Summary changed: - Bluetooth input doesn't work w/ Bose QC36 ii + Bluetooth input doesn't work w/ Bose QC35 ii -- 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/1913499 Title: Bluetooth input doesn't work w/ Bose QC35 ii Status in bluez package in Ubuntu: New Bug description: When connecting the Bose QC35 ii, the bluetooth audio works just fine initially, but the microphone does not. When I go to the sound settings and change the mic input to use the QC35 ii bluetooth input, the audio changes from stereo to mono and sounds terrible and cannot understand anything. Also the mic picks up some input, but the result output sounds about the same, completely un-understandable, a stuttering digitized version of the input. > lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 Linux dan-xps-9700 5.10.5-051005-generic #202101061537 SMP Wed Jan 6 15:43:53 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux 3. I expected the microphone input and headset output to both work simultaneously via bluetooth. 4. Only the headset output worked well, when enabling microphone both sounded terrible (unusable). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 Uname: Linux 5.10.5-051005-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 17:53:00 2021 InstallationDate: Installed on 2021-01-06 (21 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep bluetooth MachineType: Dell Inc. XPS 17 9700 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.5-051005-generic root=UUID=d87c0f2c-adf4-493f-95dc-e2df02f584b3 ro quiet splash vt.handoff=7 SourcePackage: bluez 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: 03CPGC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1826290] Re: geoclue mozilla location api key rate limited
@osomon any news on the key request for Ubuntu ? I'm hitting usage
limits randomly with the generic "geoclue" key which makes redshift not
work sometimes. It's the same error as @heap
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Triaged
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913485] Re: PulseEffects + YTMD
** 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/1913485 Title: PulseEffects + YTMD Status in xorg package in Ubuntu: New Bug description: when opening both apps its always a big complication with a lot a latency and distortion ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CompositorRunning: None Date: Wed Jan 27 13:56:37 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0682] InstallationDate: Installed on 2018-01-28 (1095 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Acer TravelMate P653-M ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=068acae8-2f26-4217-b2a3-e5afc4dd438d ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.03. dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P653-M dmi.board.vendor: Acer dmi.board.version: V2.03. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.03. dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.03.:bd10/16/2012:svnAcer:pnTravelMateP653-M:pvrV2.03.:rvnAcer:rnTravelMateP653-M:rvrV2.03.:cvnAcer:ct9:cvrV2.03.: dmi.product.family: TravelMate P653-M dmi.product.name: TravelMate P653-M dmi.product.sku: TravelMate P653-M_0682_2.03 dmi.product.version: V2.03. dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1913485/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913485] [NEW] PulseEffects + YTMD
You have been subscribed to a public bug: when opening both apps its always a big complication with a lot a latency and distortion ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CompositorRunning: None Date: Wed Jan 27 13:56:37 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics Controller [1025:0682] InstallationDate: Installed on 2018-01-28 (1095 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Acer TravelMate P653-M ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=068acae8-2f26-4217-b2a3-e5afc4dd438d ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.03. dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P653-M dmi.board.vendor: Acer dmi.board.version: V2.03. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.03. dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.03.:bd10/16/2012:svnAcer:pnTravelMateP653-M:pvrV2.03.:rvnAcer:rnTravelMateP653-M:rvrV2.03.:cvnAcer:ct9:cvrV2.03.: dmi.product.family: TravelMate P653-M dmi.product.name: TravelMate P653-M dmi.product.sku: TravelMate P653-M_0682_2.03 dmi.product.version: V2.03. dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- PulseEffects + YTMD https://bugs.launchpad.net/bugs/1913485 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 1846718] Re: Pressing and holding the Super key should display numbers [1-9] on the dock icons before pressing any number key
Super+Q is NOT enough and, worse, it increases the memory burden for people who need to use the keyboard because using the mouse aggravates their RSI. Please have some consideration for non-mouse users. -- 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/1846718 Title: Pressing and holding the Super key should display numbers [1-9] on the dock icons before pressing any number key Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Triaged Bug description: Currently, this feature is incomplete, pressing and holding the Super key should display numbers [1-9] on the dock icons before actually pressing any number key. Steps to reproduce the bug: 1. Press and hold the Super key 2. Notice that no numbers appear on the dock icons 3. Press 0 (zero) key while still holding the Super key 4. Numbers appear on the dock icons for 2 seconds then disappear 5. Press any number key [1-9] that corresponds to an icon 6. Numbers appear on the dock icons for 2 seconds then disappear and the app launches What should happen: Numbers should appear on the dock icons while holding the Super key before pressing any number key in order to choose which number key to press to launch the corresponding app. I believe that's how this feature is supposed to work. And that's how it is working in Unity7 in Ubuntu 16.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Oct 4 13:21:32 2019 InstallationDate: Installed on 2018-11-29 (308 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1846718/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913336] Re: snap : connected usb storage don't show up in left pane
Maybe a better illustration, see attachment gtk-FE-deb-snap.png ** Attachment added: "gtk-FE-deb-snap.png" https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1913336/+attachment/5457484/+files/gtk-FE-deb-snap.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1913336 Title: snap : connected usb storage don't show up in left pane Status in xdg-desktop-portal package in Ubuntu: New Bug description: Hi, coming from https://forum.snapcraft.io/t/gtk-file-explorer-does-not- show-removable-media-in-left-pane/22344 while using snap app's, gtk-file-explorer does not show usb connected storage at first sight in left pane, as it does in same regular .deb app's - I tried in chromium, libreoffice and gimp. Where it's supposed to appear : https://snapforum.s3.dualstack.us-east-1.amazonaws.com/original/2X/a/ae3104599555b6bb3ffbe642d88b6f2522d8e291.png Actually, in snap, to access an usb storage you have to browse the full path other places → computer → /media → $USER → usb label or uuid ( see attachment ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1913336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724872] Re: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1724872 Title: nvidia-graphics-drivers-340 340.102-0ubuntu0.16.04.2 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 source package in Xenial: Fix Released Bug description: [Impact] Currently the DKMS package fails to install in supported custom kernels that are based on 4.11 or 4.13. That includes the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud kernels as well. [Test Case] Install the DKMS package with the 4.13 hwe-edge kernel from -proposed. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.10 - linux-hwe-edge 4.11 - linux-hwe-edge 4.13 (from xenial-proposed) [Original description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/nvidia-graphics-drivers-340/20171018_120806_eb45b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/n/nvidia-graphics-drivers-340/20171018_121546_eb45b@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1724872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913388] Re: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
if the ABI changes without changing the soname, we should rename the library packages: Package: clucene-core Format: 3.0 (quilt) Binary: libclucene-dev, libclucene-core1v5, libclucene-contribs1v5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in Ubuntu on IBM z Systems: Triaged Status in clucene-core package in Ubuntu: Confirmed Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913217] Re: Screen going black and not responding to input
Hi Daniel, Thanks for the response, attaching the file. The installation is pretty new and has no additional GNOME extensions. Also submitted a new crash report today: https://errors.ubuntu.com/oops/ed647ea2-60cb-11eb-8e09-fa163e6cac46 By the way: found out today I can still access the system externally through ssh after a freeze. Let me know if there is anything else I can do to help pinpoint the issue. Cheers, Hanno ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913217/+attachment/5457469/+files/prevboot.txt -- 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/1913217 Title: Screen going black and not responding to input Status in gnome-shell package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expecting: (usually after opening a new application): window to open Happened instead: Screen going black. System not responding to inputs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 21:49:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed nvidia-340, 340.108, 5.8.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] InstallationDate: Installed on 2021-01-24 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=22238608-1c5f-40aa-a8f4-1fded14f6b84 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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
[Desktop-packages] [Bug 1907433] Re: [SRU] New stable release 2.64.6
> retry the test That has been done. Now the only red is netplan.io. -- 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/1907433 Title: [SRU] New stable release 2.64.6 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Focal: Fix Committed Bug description: [ Description ] Take this new upstrem stable release. It was easiest for me to merge the latest release in this series from Debian, and then import the subsequent point releases on top of that. Visually in the diff there is one change resulting from this: splitting a two-patch upstream cherry pick into two individual patch files. This is cleaner anyway IMO, but is also no change if you look at the resulting patched source. Overview of changes in GLib 2.64.6 == * This is expected to be the last release in the 2.64 series; the new stable series is 2.66, and maintenance efforts will shift to that * Bugs fixed: - #2194 gtk3/glib crash on gimp - #2209 gthreadedresolver: faulty logic in parse_res_txt - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64 - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64 - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to glib-2-64 - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64 - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not succeeding” to glib-2-64 - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too far in the past” to glib-2-64 * Translation updates: - Croatian - Portuguese Overview of changes in GLib 2.64.5 == * Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander Larsson) (#2182) * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868) * Bugs fixed: - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual Studio” to glib-2-64 - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64 - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked URI list” to glib-2-64 - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64 - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” to glib-2-64 - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64 Overview of changes in GLib 2.64.4 == * Bugs fixed: - #2140 calling malloc in fork child is undefined-behaviour - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to return” to glib-2-64 - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64 - !1547 Backport !1544 “Resolve "calling malloc in fork child is undefined-behaviour"” to glib-2-64 * Translation updates: - Kazakh - Slovenian [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1907433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913388] Re: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
** Tags added: fr-1088 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in Ubuntu on IBM z Systems: Triaged Status in clucene-core package in Ubuntu: Confirmed Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913453] [NEW] Xorg freeze
Public bug reported: System Description:Ubuntu 20.04.1 LTS Release:20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2018-12-25 (763 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 2324AS7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago) dmi.bios.date: 04/11/2018 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETB2WW (2.72 ) dmi.board.asset.tag: Not Available dmi.board.name: 2324AS7 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 2324AS7 dmi.product.sku: LENOVO_MT_2324 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Nov 24 16:32:27 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2.4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze third-party-packages ubuntu wayland-session ** Description changed: System Description: Ubuntu 20.04.1 LTS Release: 20.04 Description: Plugging in USB hub with peripherals while system is running causes gradual lag of a visual response, until freezing. usually takes < 1 min. Only work around is to sleep system between plugging in hub. - I thought I fixed it by change DE but the issue has persisted. + I thought I fixed it by change DM but the issue has persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 14:27:12 2021 DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed - acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed - acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed + acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed + acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed + acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed
[Desktop-packages] [Bug 1817785] Re: installation of texlive-latex-base-doc does not make the documentation available to 'texdoc'
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: texlive-base (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1817785 Title: installation of texlive-latex-base-doc does not make the documentation available to 'texdoc' Status in texlive-base package in Ubuntu: Confirmed Bug description: I had texlive installed previously, on a freshly installed 18.04 system. Now I installed texlive-latex-base-doc. after installation, texdoc did not find the requested documentation, e.g. $texdoc amsldoc Sorry, no documentation found for amsldoc. Only after executing 'dpkg-reconfigure texlive-base' the documentation was found. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: texlive-latex-base-doc (not installed) ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Feb 26 20:56:05 2019 InstallationDate: Installed on 2014-08-28 (1643 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) SourcePackage: texlive-base UpgradeStatus: Upgraded to bionic on 2018-08-14 (196 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1817785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1912706] Re: Ubuntu 21.04 QEMU virgl Couldn't find current GLX or EGL context
... I guess "qemu(5.2+dfsg-3ubuntu1)+virgl on GTK/X11" is the bad case then? ** Also affects: libepoxy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libepoxy in Ubuntu. https://bugs.launchpad.net/bugs/1912706 Title: Ubuntu 21.04 QEMU virgl Couldn't find current GLX or EGL context Status in libepoxy package in Ubuntu: New Status in qemu package in Ubuntu: Incomplete Bug description: command "qenu-system-x86_64 ...-accel kvm -device virtio-gpu,virgl=on -display gtk,gl=on ... " failed with "qemu-system-x86_64: ../src/dispatch_common.c:863: epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL context.\n"' failed." [1] 105637 abort after qemu-system-x86_64 Version: 1:5.2+dfsg-3ubuntu1 target linux virtual machine Ubuntu 21.04 (development branch) x86_64 CPU: AMD Ryzen 5 4600H with Radeon Graphics (12) @ 3.000GHz GPU: AMD ATI 05:00.0 Renoir qemu virgl works flawlessly on Ubuntu 20.04 and 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1912706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913439] Re: "Alert Sound" change has no effect at all
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 1913439 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-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913439 Title: "Alert Sound" change has no effect at all Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1) Change "Alert Sound" to , say, Drip. 2) open terminal and press "Backspace" to test Expected: Hear Drip Actual: hear default Related to https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320 but in my case doesn't change to anything else at all even via "Default" intermediate. It is always "Default". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913439] Re: "Alert Sound" change has no effect at all
ice@ice-ubuntu:~$ uname -a Linux ice-ubuntu 5.8.0-41-generic #46-Ubuntu SMP Mon Jan 18 16:48:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux OS Name: Ubuntu 20.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913439 Title: "Alert Sound" change has no effect at all Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1) Change "Alert Sound" to , say, Drip. 2) open terminal and press "Backspace" to test Expected: Hear Drip Actual: hear default Related to https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320 but in my case doesn't change to anything else at all even via "Default" intermediate. It is always "Default". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913439] [NEW] "Alert Sound" change has no effect at all
Public bug reported: Steps to reproduce: 1) Change "Alert Sound" to , say, Drip. 2) open terminal and press "Backspace" to test Expected: Hear Drip Actual: hear default Related to https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320 but in my case doesn't change to anything else at all even via "Default" intermediate. It is always "Default". ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913439 Title: "Alert Sound" change has no effect at all Status in gnome-control-center package in Ubuntu: New Bug description: Steps to reproduce: 1) Change "Alert Sound" to , say, Drip. 2) open terminal and press "Backspace" to test Expected: Hear Drip Actual: hear default Related to https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871320 but in my case doesn't change to anything else at all even via "Default" intermediate. It is always "Default". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1912952] Re: simple-scan SANE_STATUS_NO_MEM
Reduced paper size tu a5 and resolution to 75 dpi. same problem:
corrado@corrado-x6-hh-0122:~$ simple-scan --debug
[+0,00s] DEBUG: simple-scan.vala:2012: Starting simple-scan 3.38.1, PID=15394
[+0,00s] DEBUG: unsetenv() is not thread-safe and should not be used after
threads are created
[+0,01s] DEBUG: _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
[+0,03s] DEBUG: app-window.vala:1990: Loading state from
/home/corrado/.cache/simple-scan/state
[+0,03s] DEBUG: app-window.vala:1969: Restoring window to 600x400 pixels
[+0,07s] DEBUG: scanner.vala:1548: sane_init () -> SANE_STATUS_GOOD
[+0,07s] DEBUG: scanner.vala:1554: SANE version 1.0.31
[+0,07s] DEBUG: scanner.vala:1615: Requesting redetection of scan devices
[+0,07s] DEBUG: scanner.vala:828: Processing request
[+0,44s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+7,69s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+7,69s] DEBUG: scanner.vala:353: Device: name="escl:http://127.0.0.1:6;
vendor="HP" model="DeskJet 2600 series [665032] (USB)" type="flatbed scanner"
[+7,69s] DEBUG: scanner.vala:353: Device:
name="hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS"
vendor="Hewlett-Packard" model="DeskJet_2600_series" type="all-in-one"
[+8,01s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+9,47s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+14,39s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+39,51s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+52,09s] DEBUG: simple-scan.vala:1817: Requesting scan at 75 dpi from device
'escl:http://127.0.0.1:6'
[+52,09s] DEBUG: scanner.vala:1683: Scanner.scan
("escl:http://127.0.0.1:6;, dpi=75, scan_mode=ScanMode.COLOR, depth=8,
type=single, paper_width=1480, paper_height=2100, brightness=0, contrast=0,
delay=3000ms)
[+52,09s] DEBUG: scanner.vala:828: Processing request
[+52,09s] DEBUG: scanner.vala:889: sane_open ("escl:http://127.0.0.1:6;) ->
SANE_STATUS_NO_MEM
[+52,09s] WARNING: scanner.vala:893: Unable to open device: Out of memory
[+52,40s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+52,96s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+62,38s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+65,04s] DEBUG: autosave-manager.vala:201: Deleting autosave records
[+65,04s] DEBUG: scanner.vala:1711: Stopping scan thread
[+65,04s] DEBUG: scanner.vala:828: Processing request
[+65,05s] DEBUG: scanner.vala:1722: sane_exit ()
corrado@corrado-x6-hh-0122:~$
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1912952
Title:
simple-scan SANE_STATUS_NO_MEM
Status in simple-scan package in Ubuntu:
Incomplete
Bug description:
Ubuntu 21.04: Start simple-scan, click on 'scan' I have a message 'Failed to
scan - Unable to connect scanner'
debug log says 'SANE_STATUS_NO_MEM'
Same scanner works fine on Ubuntu 20.10
corrado@corrado-x6-hh-0122:~$ simple-scan --debug
[+0,00s] DEBUG: simple-scan.vala:2012: Starting simple-scan 3.38.1, PID=3523
[+0,00s] DEBUG: unsetenv() is not thread-safe and should not be used after
threads are created
[+0,01s] DEBUG: _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
[+0,03s] DEBUG: app-window.vala:1990: Loading state from
/home/corrado/.cache/simple-scan/state
[+0,03s] DEBUG: app-window.vala:1969: Restoring window to 600x400 pixels
[+0,07s] DEBUG: scanner.vala:1548: sane_init () -> SANE_STATUS_GOOD
[+0,07s] DEBUG: scanner.vala:1554: SANE version 1.0.31
[+0,07s] DEBUG: scanner.vala:1615: Requesting redetection of scan devices
[+0,07s] DEBUG: scanner.vala:828: Processing request
[+0,44s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+7,68s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+7,68s] DEBUG: scanner.vala:353: Device: name="escl:http://127.0.0.1:6;
vendor="HP" model="DeskJet 2600 series [665032] (USB)" type="flatbed scanner"
[+7,68s] DEBUG: scanner.vala:353: Device:
name="hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS"
vendor="Hewlett-Packard" model="DeskJet_2600_series" type="all-in-one"
[+8,00s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+14,99s] DEBUG: simple-scan.vala:1817: Requesting scan at 75 dpi from device
'escl:http://127.0.0.1:6'
[+14,99s] DEBUG: scanner.vala:1683: Scanner.scan
("escl:http://127.0.0.1:6;, dpi=75, scan_mode=ScanMode.COLOR, depth=8,
type=single, paper_width=0, paper_height=0, brightness=0, contrast=0,
[Desktop-packages] [Bug 1913388] Re: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
Typically a source package (.dsc) publishes all binary packages (.deb) for all architectures into the same component. That is the default behavior of launchpad. We try to avoid split-publishing of .deb into main/universe where possible, or split-publishing across different architectures. Especially since some otherwise graphical/desktop stack packages at times end up in the reverse build-dependencies cycles to build otherwise CLI-only software. The obvious example being cmake. s390x is explicitly an Ubuntu Server architecture only. Thus whilst many desktop packages are built automatically on s390x they are provided on the best effort basis out of convenience. It would require manual interventions and changes to exclude them on s390x. Similar caveats apply on other architectures too. At the moment we only fully support Ubuntu Desktop on amd64; Pi 4+ arm64. ** Changed in: clucene-core (Ubuntu) Status: Incomplete => Confirmed ** Changed in: clucene-core (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in Ubuntu on IBM z Systems: Triaged Status in clucene-core package in Ubuntu: Confirmed Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913388] Comment bridged from LTC Bugzilla
--- Comment From marius.hillenbr...@ibm.com 2021-01-27 05:05 EDT--- The clucene packages are built and shipped on s390x as part of the "main" repository (just verified in an Ubuntu 20.04 -- http://ports.ubuntu.com/pool/main/c/clucene-core/). I do not know how what role the grouping into Ubuntu Desktop plays. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in Ubuntu on IBM z Systems: Triaged Status in clucene-core package in Ubuntu: Incomplete Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913414] [NEW] no system tray on this system
Public bug reported: HPLIP no system tray on this system ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 11:22:49 2021 InstallationDate: Installed on 2019-12-22 (401 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to focal on 2020-10-02 (116 days ago) ** Affects: gnome-shell-extension-appindicator (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 gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1913414 Title: no system tray on this system Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: HPLIP no system tray on this system ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 27 11:22:49 2021 InstallationDate: Installed on 2019-12-22 (401 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to focal on 2020-10-02 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1913414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1668309] Re: Scaling on xps13 means only a part of the screen is visible at any time.
Hi, while we wait for a fix, does anyone know how to reliably toggle between 3840x2160+gnome-scaling and 1920x1080-gnome-scaling? I've tried SSHing in a using xrandr before starting the session, but turning ON/OFF the GNOME scaling doesn't seem to work (xrandr controls DPI which is different, and i didn't find a simple gsettings to toggle that worksed). My current work around is manually changing this before I leave the computer just in case I need to VNC in, then setting it back which is not ideal... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1668309 Title: Scaling on xps13 means only a part of the screen is visible at any time. Status in vino: Unknown Status in vino package in Ubuntu: Triaged Bug description: STEPS: 1. On a 4K system 2. Do a default install of the current iso for Zesty 3. Make sure scalling is set to 2 4. Once in the user session activate desktop-sharing 5. Connect from another machine EXPECTED: I expect to see the whole screen or for the screen to scroll to allow access to the whole screen ACTUAL: Top left hand quarter is the only thing visible and no changes to remina make it better. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2016-11-09 (109 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161109) Package: vino 3.8.1-0ubuntu12 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Tags: zesty Uname: Linux 4.10.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/1668309/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815550] Re: gnome-shell high memory and CPU usage when desktop files are constantly created or deleted
Just retested the pathological case of this leak, which involves creating and deleting desktop files as fast as you can (thousands of times) via a script. In that case even the latest gnome-shell-extension- desktop-icons still leaks badly. So the fix I had hopes for is not enough: https://gitlab.gnome.org/World/ShellExtensions/desktop- icons/-/commit/16447ab5bebcd4efb792e25335438f43b503c3e6 Of course this bug was already closed because a bigger leak was successfully fixed. If anyone finds the pathological case in the wild then we should handle it in a new bug. ** Tags added: gnome-shell-leak -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1815550 Title: gnome-shell high memory and CPU usage when desktop files are constantly created or deleted Status in gnome-shell-extension-desktop-icons: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Disco: Won't Fix Bug description: [Impact] gnome-shell memory usage grows rapidly each time files are created or deleted in the Desktop directory. [Test Case] 0. Create a number of files/icons on the Desktop. The more existing icons you have, the faster the test will be. 1. Start monitoring gnome-shell's memory usage. 2. Repeatedly create and delete a new file on the Desktop every second. 3. Check that gnome-shell's memory usage doesn't quickly grow by hundreds of megabytes. It should only grow a little. [Regression Potential] Low. The current upstream stable release 19.01.4 is just a bug fix release on the same series as what's already in disco and eoan. The same fix has also been released early to eoan already. [Original Bug Report] This *may* be an nvidia-specific problem, but the RSS of gnome-shell on my system grows without limit (over a couple of hours it's increased past 10G). At the same time, gnome-shell appears to become progressively less responsive. Restarting gnome-shell (via restart) drops shell RSS down to ~400MB and improves system responsiveness a bit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.30.2-2ubuntu2 ProcVersionSignature: Ubuntu 4.20.0+bcachefs.git20190130.d1f70147-1.0-generic 4.20.0 Uname: Linux 4.20.0+bcachefs.git20190130.d1f70147-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 12 13:35:59 2019 DisplayManager: gdm3 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-extension-desktop-icons/+bug/1815550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906741] Re: Firefox sometimes causes garbled audio
For me many videos have garbled audio, today it's https://octopus.com/, some others, e.g. a cloud guru, tedx weren't working before, but are now. Perhaps it's not related to the video format. Ubuntu 20.04 and FF 84.0.2 -- 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/1906741 Title: Firefox sometimes causes garbled audio Status in firefox package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Opening certain applications/websites at the same time as Firefox causes the audio to become garbled. The audio sounds distorted with an echo. Certain actions are guaranteed to cause this, but it can also happening when only running instances of Firefox. I've been able to consistently cause this by launching Zoom from a link within Firefox. This does not occur when using Chrome. The only way to fix the issue is to shut down all audio-related programs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rdevans 55475 F pulseaudio /dev/snd/controlC0: rdevans 55475 F pulseaudio /dev/snd/controlC3: rdevans 55475 F pulseaudio /dev/snd/controlC1: rdevans 55475 F pulseaudio BuildID: 20201112153044 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:55:36 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-10-20 (1140 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 10.0.0.1 dev enp7s0 proto dhcp metric 100 10.0.0.0/24 dev enp7s0 proto kernel scope link src 10.0.0.7 metric 100 169.254.0.0/16 dev enp7s0 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:354 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=83.0/20201112153044 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2020-11-12 (21 days ago) dmi.bios.date: 02/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.40 dmi.board.name: H67M 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.40:bd02/18/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M: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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1906741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913411] Re: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu.
** Attachment added: "1.JPG" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913411/+attachment/5457333/+files/1.JPG -- 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/1913411 Title: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. Status in gnome-shell package in Ubuntu: New Bug description: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. I just can see mobile broadband in network in system settings menu. OS: ubuntu20.04 Module: SDX55 ModemManager:1.14.2 iusse: 1.No mobile broadband in system status bar drop-down menu. 2.Every time I connect to the mobile broadband network in system settings menu, I need to add new connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913411] [NEW] While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu.
Public bug reported: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. I just can see mobile broadband in network in system settings menu. OS: ubuntu20.04 Module: SDX55 ModemManager:1.14.2 iusse: 1.No mobile broadband in system status bar drop-down menu. 2.Every time I connect to the mobile broadband network in system settings menu, I need to add new connection. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1913411 Title: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. Status in gnome-shell package in Ubuntu: New Bug description: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. I just can see mobile broadband in network in system settings menu. OS: ubuntu20.04 Module: SDX55 ModemManager:1.14.2 iusse: 1.No mobile broadband in system status bar drop-down menu. 2.Every time I connect to the mobile broadband network in system settings menu, I need to add new connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
Fixed with https://github.com/ubuntu/yaru/pull/2546 ** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Fix Released Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873365] Re: gedit icon is too pale
Fixed with https://github.com/ubuntu/yaru/pull/2479 ** Changed in: yaru-theme (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1873365 Title: gedit icon is too pale Status in yaru-theme package in Ubuntu: Fix Released Bug description: The grey lines representing text on the paper sheet and the tip of the pencil in the icon are too pale. They are almost invisible so that the gedit icon is seen as a white rectangle crossed by a blue bar. Before focal, the icons of gedit and Evince used to have similar design, that is they both were pale. Now in focal, the Evince icon is redesigned and it is more clear with more contrast. The suggestion is to apply similar modifications to the gedit icon to make it more clear. For example, it can use the same dark gray color of the text lines as Evince icon. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-icon 20.04.5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 01:10:13 2020 Dependencies: InstallationDate: Installed on 2019-04-25 (357 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1873365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1889991] Re: Highlight for the task switcher is too subtle
** Changed in: yaru-theme (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1889991 Title: Highlight for the task switcher is too subtle Status in yaru-theme package in Ubuntu: Opinion Bug description: The task switcher has a highlight to enable the user to see which task has focus. In Ubuntu 20.04 (but not earlier versions, I think) this highlight is so subtle that one can easily miss it. I'm all for subtlety, but this is *too* subtle. I find myself repeatedly choosing the wrong task. My vision is not perfect but decent. Users with poor vision may find this problem particularly difficult. 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.4 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Aug 1 12:50:46 2020 DistUpgraded: 2020-04-20 13:45:34,098 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.10, 5.4.0-40-generic, x86_64: installed virtualbox, 6.1.10, 5.4.0-42-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad X1 Carbon 5th Gen [17aa:224f] InstallationDate: Installed on 2017-12-08 (966 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20HRCTO1WW ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a890597b-ae6f-4f55-a929-cdd87de29f97 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (102 days ago) dmi.bios.date: 06/03/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET63W (1.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET63W(1.48):bd06/03/2020:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.sku: LENOVO_MT_20HR_BU_Think_FM_ThinkPad X1 Carbon 5th dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO 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 20.0.8-0ubuntu1~20.04.1 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/yaru-theme/+bug/1889991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1912952] Re: simple-scan SANE_STATUS_NO_MEM
Try to decrease resolution or paper size, and check if it helps
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to simple-scan in Ubuntu.
https://bugs.launchpad.net/bugs/1912952
Title:
simple-scan SANE_STATUS_NO_MEM
Status in simple-scan package in Ubuntu:
Incomplete
Bug description:
Ubuntu 21.04: Start simple-scan, click on 'scan' I have a message 'Failed to
scan - Unable to connect scanner'
debug log says 'SANE_STATUS_NO_MEM'
Same scanner works fine on Ubuntu 20.10
corrado@corrado-x6-hh-0122:~$ simple-scan --debug
[+0,00s] DEBUG: simple-scan.vala:2012: Starting simple-scan 3.38.1, PID=3523
[+0,00s] DEBUG: unsetenv() is not thread-safe and should not be used after
threads are created
[+0,01s] DEBUG: _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
[+0,03s] DEBUG: app-window.vala:1990: Loading state from
/home/corrado/.cache/simple-scan/state
[+0,03s] DEBUG: app-window.vala:1969: Restoring window to 600x400 pixels
[+0,07s] DEBUG: scanner.vala:1548: sane_init () -> SANE_STATUS_GOOD
[+0,07s] DEBUG: scanner.vala:1554: SANE version 1.0.31
[+0,07s] DEBUG: scanner.vala:1615: Requesting redetection of scan devices
[+0,07s] DEBUG: scanner.vala:828: Processing request
[+0,44s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+7,68s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+7,68s] DEBUG: scanner.vala:353: Device: name="escl:http://127.0.0.1:6;
vendor="HP" model="DeskJet 2600 series [665032] (USB)" type="flatbed scanner"
[+7,68s] DEBUG: scanner.vala:353: Device:
name="hpaio:/usb/DeskJet_2600_series?serial=CN0569B27006PS"
vendor="Hewlett-Packard" model="DeskJet_2600_series" type="all-in-one"
[+8,00s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+14,99s] DEBUG: simple-scan.vala:1817: Requesting scan at 75 dpi from device
'escl:http://127.0.0.1:6'
[+14,99s] DEBUG: scanner.vala:1683: Scanner.scan
("escl:http://127.0.0.1:6;, dpi=75, scan_mode=ScanMode.COLOR, depth=8,
type=single, paper_width=0, paper_height=0, brightness=0, contrast=0,
delay=3000ms)
[+14,99s] DEBUG: scanner.vala:828: Processing request
[+14,99s] DEBUG: scanner.vala:889: sane_open ("escl:http://127.0.0.1:6;)
-> SANE_STATUS_NO_MEM
[+14,99s] WARNING: scanner.vala:893: Unable to open device: Out of memory
[+15,30s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+15,86s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+473,36s] DEBUG: app-window.vala:2065: Saving state to
/home/corrado/.cache/simple-scan/state
[+474,87s] DEBUG: autosave-manager.vala:201: Deleting autosave records
[+474,87s] DEBUG: scanner.vala:1711: Stopping scan thread
[+474,87s] DEBUG: scanner.vala:828: Processing request
[+474,88s] DEBUG: scanner.vala:1722: sane_exit ()
corrado@corrado-x6-hh-0122:~$
corrado@corrado-x6-hh-0122:~$ inxi -SCMIx
System:Host: corrado-x6-hh-0122 Kernel: 5.8.0-36-generic x86_64 bits: 64
compiler: gcc v: 10.2.1 Desktop: GNOME 3.38.2
Distro: Ubuntu 21.04 (Hirsute Hippo)
Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10
date: 05/11/2017
CPU: Info: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP
arch: Kaby Lake rev: 9 L2 cache: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
bogomips: 31199
Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2:
800 3: 800 4: 800
Info: Processes: 219 Uptime: 31m Memory: 7.48 GiB used: 1.73 GiB (23.1%)
Init: systemd runlevel: 5 Compilers: gcc: N/A
Packages: 1827 Shell: Bash v: 5.1.0 inxi: 3.2.02
corrado@corrado-x6-hh-0122:~$
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: simple-scan 3.38.1-1
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu55
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 24 19:05:51 2021
InstallationDate: Installed on 2021-01-22 (2 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210122)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic
root=UUID=20c90aa4-17f1-4012-931a-04287724baba ro quiet splash vt.handoff=7
SimpleScanLog:
SourcePackage: simple-scan
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: H110M-G/M.2
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
[Desktop-packages] [Bug 1913400] Re: While I updating ModemManager to 1.14.2, there is no mobile broadband dop down menu in system state bar.
No mobile broadband in system status bar drop-down menu. ** Attachment added: "1.JPG" https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1913400/+attachment/5457328/+files/1.JPG -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1913400 Title: While I updating ModemManager to 1.14.2, there is no mobile broadband dop down menu in system state bar. Status in modemmanager package in Ubuntu: New Bug description: While I updating ModemManager to 1.14.2, there is no mobile broadband dop down menu in system state bar. I just can see mobile broadband in network in system settings menu my step: git clone -b 1.24.2 https://gitlab.freedesktop.org/mobile-broadband/libmbim NOCONFIGURE=1 ./autogen.sh ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu make sudo make install git clone -b 1.26.4 https://gitlab.freedesktop.org/mobile-broadband/libqmi NOCONFIGURE=1 ./autogen.sh ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --enable-mbim-qmux --enable-collection=basic make sudo make install git clone -b 1.14.2 https://gitlab.freedesktop.org/mobile-broadband/ModemManager NOCONFIGURE=1 ./autogen.sh ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --enable-gtk-doc --with-polkit=strict --with-suspend-resume=systemd --with-systemdsystemunitdir=/lib/systemd/systemmake make sudo make install OS: ubuntu20.04 Module: SDX55 ModemManager:1.14.2 iusse: 1.No mobile broadband in system status bar drop-down menu. 2.Every time I connect to the mobile broadband network in system settings menu, I need to add new connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1913400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913400] [NEW] While I updating ModemManager to 1.14.2, there is no mobile broadband dop down menu in system state bar.
Public bug reported: While I updating ModemManager to 1.14.2, there is no mobile broadband dop down menu in system state bar. I just can see mobile broadband in network in system settings menu my step: git clone -b 1.24.2 https://gitlab.freedesktop.org/mobile-broadband/libmbim NOCONFIGURE=1 ./autogen.sh ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu make sudo make install git clone -b 1.26.4 https://gitlab.freedesktop.org/mobile-broadband/libqmi NOCONFIGURE=1 ./autogen.sh ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --enable-mbim-qmux --enable-collection=basic make sudo make install git clone -b 1.14.2 https://gitlab.freedesktop.org/mobile-broadband/ModemManager NOCONFIGURE=1 ./autogen.sh ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --enable-gtk-doc --with-polkit=strict --with-suspend-resume=systemd --with-systemdsystemunitdir=/lib/systemd/systemmake make sudo make install OS: ubuntu20.04 Module: SDX55 ModemManager:1.14.2 iusse: 1.No mobile broadband in system status bar drop-down menu. 2.Every time I connect to the mobile broadband network in system settings menu, I need to add new connection. ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1913400 Title: While I updating ModemManager to 1.14.2, there is no mobile broadband dop down menu in system state bar. Status in modemmanager package in Ubuntu: New Bug description: While I updating ModemManager to 1.14.2, there is no mobile broadband dop down menu in system state bar. I just can see mobile broadband in network in system settings menu my step: git clone -b 1.24.2 https://gitlab.freedesktop.org/mobile-broadband/libmbim NOCONFIGURE=1 ./autogen.sh ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu make sudo make install git clone -b 1.26.4 https://gitlab.freedesktop.org/mobile-broadband/libqmi NOCONFIGURE=1 ./autogen.sh ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --enable-mbim-qmux --enable-collection=basic make sudo make install git clone -b 1.14.2 https://gitlab.freedesktop.org/mobile-broadband/ModemManager NOCONFIGURE=1 ./autogen.sh ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --enable-gtk-doc --with-polkit=strict --with-suspend-resume=systemd --with-systemdsystemunitdir=/lib/systemd/systemmake make sudo make install OS: ubuntu20.04 Module: SDX55 ModemManager:1.14.2 iusse: 1.No mobile broadband in system status bar drop-down menu. 2.Every time I connect to the mobile broadband network in system settings menu, I need to add new connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1913400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913368] Re: Xorg freeze
Thanks for the bug report. Your kernel errors: [32883.824222] pcieport :00:1c.0: AER: Corrected error received: :00:1c.0 [32883.824246] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [32883.824254] pcieport :00:1c.0: AER: device [8086:a111] error status/mask=1000/2000 [32883.824259] pcieport :00:1c.0: AER:[12] Timeout [32975.541566] pcieport :00:1c.0: AER: Corrected error received: :00:1c.0 [32975.541583] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [32975.541592] pcieport :00:1c.0: AER: device [8086:a111] error status/mask=1000/2000 [32975.541598] pcieport :00:1c.0: AER:[12] Timeout [32994.793110] pcieport :00:1c.0: AER: Corrected error received: :00:1c.0 [32994.793125] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID) [32994.793133] pcieport :00:1c.0: AER: device [8086:a111] error status/mask=1000/2000 [32994.793139] pcieport :00:1c.0: AER:[12] Timeout remind me of bug 1912898. Please try an older kernel series like: https://kernel.ubuntu.com /~kernel-ppa/mainline/v5.4.92/ ** 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/1913368 Title: System freeze Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell laptop with a Magic Trackpad 2. A couple of days ago my system crashed overnight and hung on reboot. Once I unplugged the trackpad, it came right up. If I attach the trackpad to the running system it does not recognize it. I've been using this hardware configuration for months and haven't made any changes to my libinput configuration for at least a couple of months. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 23:23:45 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07a9] InstallationDate: Installed on 2020-09-13 (135 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Precision 3520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=ff5fae3d-e88f-436d-8a84-d0a544463eb9 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2020 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0C7J6P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd01/07/2020:br1.17:svnDellInc.:pnPrecision3520:pvr:rvnDellInc.:rn0C7J6P:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 3520 dmi.product.sku: 07A9 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1913368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913388] Re: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
Please notice that clucene (clucene-core) belongs to Ubuntu Desktop (ubuntu-desktop). ** Package changed: linux (Ubuntu) => clucene-core (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core in Ubuntu. https://bugs.launchpad.net/bugs/1913388 Title: clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 Status in Ubuntu on IBM z Systems: Triaged Status in clucene-core package in Ubuntu: Incomplete Bug description: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene- core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913388] [NEW] clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33
You have been subscribed to a public bug: On s390x, the type float_t has historically been defined as double for no good reason, yet with unexpected and unnecessary impact on performance in some scenarios. The upcoming glibc release 2.33 will be a first step towards cleaning that up, which will change float_t to become float on s390x when compiling C++ code, such as in clucene-core. That would break the ABI of clucene-core on s390x for existing binaries. Today, clucene-core uses float_t for some parameters in its API; that type is defined as double on s390x today. Together with gcc's default behavior, that contradicts the C standard. To get to a more sane combination, the upcoming glibc release 2.33 will change float_t to become float on s390x (with some exceptions when compiling C code, which do not apply for clucene-core). To my knowledge, glibc 2.33 is a candidate for inclusion in Ubuntu 21.04. To avoid breaking the API of clucene-core in the process, I have prepared a trivial patch that fixes clucene-core's API to always use double instead of float_t on s390x. That patch effectively persists the current de-facto API on s390x, without changes for other architectures. Note that using float_t in an API is generally "not a great idea", because that type can have different definitions even with the same compiler and glibc version on the same system (e.g., on 32-bit x86, when switching between SSE and x87 FP ops). Patch submitted in https://sourceforge.net/p/clucene/bugs/233/ and https://sourceforge.net/p/clucene/mailman/message/37153930/ yet upstream clucene is effectively unmaintained. If Ubuntu 21.04 adopts glibc 2.33, please consider pulling in this patch in clucene-core. Related request for ImageMagick: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1913268 ** Affects: ubuntu-z-systems Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: Triaged ** Affects: clucene-core (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: architecture-s3903164 bugnameltc-191033 severity-medium targetmilestone-inin2104 -- clucene-core: please pull in patch to stabilize API on s390x during upgrade to glibc 2.33 https://bugs.launchpad.net/bugs/1913388 You received this bug notification because you are a member of Desktop Packages, which is subscribed to clucene-core 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 1896627] Re: Windows flicker when being resized with the mouse (Xorg sessions)
It's not clear to me which change in 1.20.10 that upstream think solved this. The release notes are here: https://lists.x.org/archives/xorg- announce/2020-December/003067.html Maybe this fix? https://gitlab.freedesktop.org/xorg/xserver/-/commit/c3e4c1a0fd5d4d6015e9e6317b758018317e56d1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1896627 Title: Windows flicker when being resized with the mouse (Xorg sessions) Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Bug description: When resizing a window with the mouse by dragging the edge or corner, the window begins to flicker. It only flickers when actively being resized, and when I stop dragging, it looks normal. This behavior is does not occur on same pc in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Sep 22 10:21:51 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231] InstallationDate: Installed on 2020-09-22 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200921) MachineType: LENOVO 20FJS0AJ00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET26W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FJS0AJ00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T560 dmi.product.name: 20FJS0AJ00 dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560 dmi.product.version: ThinkPad T560 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1896627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913366] Re: Login screen freezes when xserver-xorg-video-openchrome is in use
Please try editing /etc/gdm3/custom.conf and change: #WaylandEnable=false to WaylandEnable=false Then reboot. ** Summary changed: - Persiste problema con ubuntu 18.04 no reconoce monitor ni resolución óptima + Login screen freezes when xserver-xorg-video-openchrome is in use ** Package changed: xorg (Ubuntu) => xserver-xorg-video-openchrome (Ubuntu) ** Changed in: xserver-xorg-video-openchrome (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/1913366 Title: Login screen freezes when xserver-xorg-video-openchrome is in use Status in xserver-xorg-video-openchrome package in Ubuntu: Incomplete Bug description: Tuve que reinstalar ubuntu 18.04 ya que no pude ingresar más al sistema operativo, ya que se quedaba congelado en el inicio, no me permitía ingresar la contraseña. Al hacerlo seguía presentando el mismo problema de baja resolución, volví a tratar de solucionarlo con sudo apt install xserver-xorg-video-openchrome y nuevamente se congeló el sistema. Me vi forzado a realizar una segunda reinstalación de Ubuntu y no he vuelto a intentar porque obviamente se corre el riesgo de que se quede colgada otra vez. Así que estoy tratando de trabajar con la baja resolución 640x480 especificada en el informe. La instale un escritorio cinamon y me informa al inicio que està trabajando sin aceleración de software lo cual puede afectar el rendimiento del equipo. Esta es la situación. Gracias por el interés demostrado en mi caso. Saludos. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic i686 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: i386 CompositorRunning: None Date: Tue Jan 26 23:47:50 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] [1106:3371] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Biostar Microtech Int'l Corp CN896/VN896/P4M900 [Chrome 9 HC] [1565:1207] InstallationDate: Installed on 2021-01-26 (0 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release i386 (20190805) MachineType: BIOSTAR Group P4M900-M7 FE ProcEnviron: LANGUAGE=es_VE:es TERM=xterm-256color PATH=(custom, no user) LANG=es_VE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=c6c9ee95-4dbf-4f30-b579-32cfe165d16e ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: P4M900-M7 FE dmi.board.vendor: BIOSTAR Group dmi.board.version: Ver:1.0 dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: P4M900-M7 FE dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/25/2008:svnBIOSTARGroup:pnP4M900-M7FE:pvrVer1.0:rvnBIOSTARGroup:rnP4M900-M7FE:rvrVer1.0:cvnBIOSTARGroup:ct3:cvrP4M900-M7FE: dmi.product.name: P4M900-M7 FE dmi.product.version: Ver:1.0 dmi.sys.vendor: BIOSTAR Group version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1913366/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913368] Re: Xorg freeze
** 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/1913368 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I have a Dell laptop with a Magic Trackpad 2. A couple of days ago my system crashed overnight and hung on reboot. Once I unplugged the trackpad, it came right up. If I attach the trackpad to the running system it does not recognize it. I've been using this hardware configuration for months and haven't made any changes to my libinput configuration for at least a couple of months. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 23:23:45 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07a9] InstallationDate: Installed on 2020-09-13 (135 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Precision 3520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=ff5fae3d-e88f-436d-8a84-d0a544463eb9 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2020 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0C7J6P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd01/07/2020:br1.17:svnDellInc.:pnPrecision3520:pvr:rvnDellInc.:rn0C7J6P:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 3520 dmi.product.sku: 07A9 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1913368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913356] Re: Windows flicker when resizing
*** This bug is a duplicate of bug 1896627 *** https://bugs.launchpad.net/bugs/1896627 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 1896627, 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: - Windows flicker when resizing after update to 20.10 + Windows flicker when resizing ** This bug has been marked a duplicate of bug 1896627 Windows flicker when being resized with the mouse (Xorg sessions) -- 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/1913356 Title: Windows flicker when resizing Status in mutter package in Ubuntu: Confirmed Bug description: Yesterday I updated to Ubuntu 20.10 (from 20.04 LTS) and immediately noticed an issue with windows flickering when I resize them. Here is a video demonstrating the issue: https://youtu.be/nNOoJWdDEes This did not happen in 20.04. Windows this has been noticed on include: - Software & Updates (as shown in video) - Tilix - KeePassXC Here is some information about my system: - OS: Ubuntu 20.10 x86_64 - Host: XPS 13 9370 - Kernel: 5.8.0-40-generic - Shell: bash 5.0.17 - Resolution: 1920x1080 - DE: GNOME 3.38.2 - WM: Mutter - WM Theme: Adwaita - Theme: Yaru-dark [GTK2/3] - Icons: Yaru [GTK2/3] - CPU: Intel i7-8550U (8) @ 4.000GHz - GPU: Intel UHD Graphics 620 - Memory: 6139MiB / 15725MiB Please let me know if there's any further details or diagnostics that would be useful. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Wed Jan 27 00:23:33 2021 DistUpgraded: 2021-01-25 15:06:27,142 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-02-01 (1090 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 7: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 7: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=04d2ce0b-b5d2-4184-93fc-428c29d5e2fd ro SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2021-01-25 (1 days ago) dmi.bios.date: 05/25/2018 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0F6P3V 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:bd05/25/2018:br1.4:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
[Desktop-packages] [Bug 1913356] Re: Windows flicker when resizing after update to 20.10
*** This bug is a duplicate of bug 1896627 *** https://bugs.launchpad.net/bugs/1896627 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/1913356 Title: Windows flicker when resizing Status in mutter package in Ubuntu: Confirmed Bug description: Yesterday I updated to Ubuntu 20.10 (from 20.04 LTS) and immediately noticed an issue with windows flickering when I resize them. Here is a video demonstrating the issue: https://youtu.be/nNOoJWdDEes This did not happen in 20.04. Windows this has been noticed on include: - Software & Updates (as shown in video) - Tilix - KeePassXC Here is some information about my system: - OS: Ubuntu 20.10 x86_64 - Host: XPS 13 9370 - Kernel: 5.8.0-40-generic - Shell: bash 5.0.17 - Resolution: 1920x1080 - DE: GNOME 3.38.2 - WM: Mutter - WM Theme: Adwaita - Theme: Yaru-dark [GTK2/3] - Icons: Yaru [GTK2/3] - CPU: Intel i7-8550U (8) @ 4.000GHz - GPU: Intel UHD Graphics 620 - Memory: 6139MiB / 15725MiB Please let me know if there's any further details or diagnostics that would be useful. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Wed Jan 27 00:23:33 2021 DistUpgraded: 2021-01-25 15:06:27,142 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-02-01 (1090 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 7: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 7: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=04d2ce0b-b5d2-4184-93fc-428c29d5e2fd ro SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2021-01-25 (1 days ago) dmi.bios.date: 05/25/2018 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0F6P3V 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:bd05/25/2018:br1.4:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Dec 16 15:22:33 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5252 vendor SHP xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1896627] Re: Windows flicker when being resized with the mouse (Xorg sessions in groovy)
Still happening in focal, groovy and hirsute. :( Although none of them have Xorg 1.20.10 yet, so fingers crossed. ** Summary changed: - Windows flicker when being resized with the mouse (Xorg sessions in groovy) + Windows flicker when being resized with the mouse (Xorg sessions) ** Tags added: focal 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/1896627 Title: Windows flicker when being resized with the mouse (Xorg sessions) Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Triaged Bug description: When resizing a window with the mouse by dragging the edge or corner, the window begins to flicker. It only flickers when actively being resized, and when I stop dragging, it looks normal. This behavior is does not occur on same pc in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: Budgie:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Tue Sep 22 10:21:51 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231] InstallationDate: Installed on 2020-09-22 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200921) MachineType: LENOVO 20FJS0AJ00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET26W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FJS0AJ00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T560 dmi.product.name: 20FJS0AJ00 dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560 dmi.product.version: ThinkPad T560 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1896627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913356] Re: Windows flicker when resizing after update to 20.10
*** This bug is a duplicate of bug 1896627 *** https://bugs.launchpad.net/bugs/1896627 ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1913356 Title: Windows flicker when resizing Status in mutter package in Ubuntu: Confirmed Bug description: Yesterday I updated to Ubuntu 20.10 (from 20.04 LTS) and immediately noticed an issue with windows flickering when I resize them. Here is a video demonstrating the issue: https://youtu.be/nNOoJWdDEes This did not happen in 20.04. Windows this has been noticed on include: - Software & Updates (as shown in video) - Tilix - KeePassXC Here is some information about my system: - OS: Ubuntu 20.10 x86_64 - Host: XPS 13 9370 - Kernel: 5.8.0-40-generic - Shell: bash 5.0.17 - Resolution: 1920x1080 - DE: GNOME 3.38.2 - WM: Mutter - WM Theme: Adwaita - Theme: Yaru-dark [GTK2/3] - Icons: Yaru [GTK2/3] - CPU: Intel i7-8550U (8) @ 4.000GHz - GPU: Intel UHD Graphics 620 - Memory: 6139MiB / 15725MiB Please let me know if there's any further details or diagnostics that would be useful. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Wed Jan 27 00:23:33 2021 DistUpgraded: 2021-01-25 15:06:27,142 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2018-02-01 (1090 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 7: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 7: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=04d2ce0b-b5d2-4184-93fc-428c29d5e2fd ro SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2021-01-25 (1 days ago) dmi.bios.date: 05/25/2018 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0F6P3V 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:bd05/25/2018:br1.4:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sun Dec 16 15:22:33 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5252 vendor SHP xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1913368] [NEW] Xorg freeze
You have been subscribed to a public bug: I have a Dell laptop with a Magic Trackpad 2. A couple of days ago my system crashed overnight and hung on reboot. Once I unplugged the trackpad, it came right up. If I attach the trackpad to the running system it does not recognize it. I've been using this hardware configuration for months and haven't made any changes to my libinput configuration for at least a couple of months. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 26 23:23:45 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07a9] InstallationDate: Installed on 2020-09-13 (135 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Precision 3520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=ff5fae3d-e88f-436d-8a84-d0a544463eb9 ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2020 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.1 dmi.board.name: 0C7J6P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.1:bd01/07/2020:br1.17:svnDellInc.:pnPrecision3520:pvr:rvnDellInc.:rn0C7J6P:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 3520 dmi.product.sku: 07A9 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.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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 freeze ubuntu -- Xorg freeze https://bugs.launchpad.net/bugs/1913368 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
