[Desktop-packages] [Bug 1956135] Re: Powerful icons
This doesn't appear to be a useful bug report. If you have any concerns about the Yaru theme then please report them to https://github.com/ubuntu/yaru/issues ** Changed in: yaru-theme (Ubuntu) Status: New => Invalid -- 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/1956135 Title: Powerful icons Status in yaru-theme package in Ubuntu: Invalid Bug description: Hi! What if Ubuntu icons aren't powerful? :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1956135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886948] Re: Can't calibrate monitor
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #951 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/951 -- 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/1886948 Title: Can't calibrate monitor Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 Tried to calibrate my monitor with an external device (x-rite huey pro). Process seems to go fine and starts working on the calibration. At about 80% of the progress bar I receive the message (in basque, not sure where to search it in english): Kalibrazioak huts egin du Kalibratzeko behar diren tresnak ez daude instalatuta Kalibrazioaren gailua ken dezakezu Which translates to (free non-official translation) Calibration has failed. The tools needed for calibration are not installed You can remove the calibration device Launching the tool from the command line, I receive these messages: (gnome-control-center:3471): color-cc-panel-WARNING **: 13:28:57.868: calibration failed with code 4: failed to get filename for colprof (gnome-control-center:3471): color-cc-panel-WARNING **: 13:33:46.435: Failed to send Cancel: GDBus.Error:org.freedesktop.ColorHelper.Internal: cannot cancel as status is idle (gnome-control-center:3471): color-cc-panel-WARNING **: 13:33:46.436: failed to start calibrate: failed to calibrate ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 9 13:38:26 2020 InstallationDate: Installed on 2020-06-25 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=eu_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1886948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
xorg-server 1.20.13 is in focal/impish/jammy now ** Changed in: xorg-server (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: xorg-server (Ubuntu Hirsute) Status: In Progress => Won't Fix ** Summary changed: - Ubuntu 20.04 and Displaylink is extremely slow + Displaylink is extremely slow -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832407] Re: Ubuntu's gnome-shell extensions can't be uninstalled (safely)
I agree this should be fixed, but it's also not a priority. You can disable them in the Extensions app (sudo apt install gnome-shell- extension-prefs). ** Description changed: I like the Ubuntu themed GNOME desktop but I don't like dash-to-dock. - As the preinstalled extensions, especially gnome-shell-extension-ubuntu-dock are not deactivable and not removable atomic (they are hard dependcies of ubuntu-desktop), the only way to remove them is to rename the extensions folder. This will also restore the dock with every update of the gnome-shell-extension-ubuntu-dock package, as it creates this folder. + As the pre-installed extensions, especially gnome-shell-extension-ubuntu-dock are not atomically removable (they are hard dependencies of ubuntu-desktop), the only way to remove them is to rename the extensions folder. This will also restore the dock with every update of the gnome-shell-extension-ubuntu-dock package, as it creates this folder. - Therfore, we should remove the hard dependcies. + Therefore, we should remove the hard dependencies. ** Changed in: ubuntu-meta (Ubuntu) Importance: Medium => Low ** Changed in: ubuntu-meta (Ubuntu) Status: Confirmed => Triaged ** Tags added: jammy ** Tags removed: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1832407 Title: Ubuntu's gnome-shell extensions can't be uninstalled (safely) Status in ubuntu-meta package in Ubuntu: Triaged Bug description: I like the Ubuntu themed GNOME desktop but I don't like dash-to-dock. As the pre-installed extensions, especially gnome-shell-extension-ubuntu-dock are not atomically removable (they are hard dependencies of ubuntu-desktop), the only way to remove them is to rename the extensions folder. This will also restore the dock with every update of the gnome-shell-extension-ubuntu-dock package, as it creates this folder. Therefore, we should remove the hard dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1832407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917939] Re: Windows maximise underneath dock after monitor sleep
It looks like the Ubuntu fix/workaround in gnome-shell (layout-Try-to- allocate-before-getting-size-of-tracke.patch) can be dropped starting in GNOME 42. Because GNOME 42 has the upstream fix https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2103 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1917939 Title: Windows maximise underneath dock after monitor sleep Status in Dash to dock: New Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock. If I switch to the application in question, unmaximise and re- maximise, it goes back to maximising inside the usable area of my desktop. But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 19:21:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-11 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917939] Re: Windows maximise underneath dock after monitor sleep
** Tags removed: fixed-in-42 ** Tags added: fixed-in-40.6 fixed-in-42.0 ** Tags added: fixed-in-41.1 ** Tags removed: fixed-in-40.6 fixed-in-41.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1917939 Title: Windows maximise underneath dock after monitor sleep Status in Dash to dock: New Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: Under wayland on 21.04 windows keep maximising underneath the dock. So I can see icons "through" the dock, when I shouldn't. In the attached screenshot you can see Telegram showing through the dock. If I switch to the application in question, unmaximise and re- maximise, it goes back to maximising inside the usable area of my desktop. But when I suspend and resume, then login, I'm left with windows under the dock again. Never seen this under xorg. I only discovered I was in wayland when I tried to ALT+F2, R to restart. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-2ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 5 19:21:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-11 (267 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.3-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2020-12-14 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1917939/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1955586] Re: Revert "layout: Exclude hidden actors from struts"
*** This bug is a duplicate of bug 1917939 *** https://bugs.launchpad.net/bugs/1917939 Please try to ensure bug reports describe a problem, and don't describe a solution. I will try to update bug 1917939 for this. -- 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/1955586 Title: Revert "layout: Exclude hidden actors from struts" Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: New Bug description: A previous commit to mutter causes unintended problems for users. This commit is reverted upstream in gnome-shell 40.6. More information here: https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/aded2cd01b7af4d2bf355ed7cb129c6b869d84fb My original bug report is here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4886#note_1338482 I'm posting this as a Ubuntu bug in hopes that if gnome-shell 40.6 is not to be updated in 21.10 for sometime, that at least the commit can be reverted. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 22 14:12:47 2021 DisplayManager: gdm3 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-11-15 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1955586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1955586] Re: Revert "layout: Exclude hidden actors from struts"
*** This bug is a duplicate of bug 1917939 *** https://bugs.launchpad.net/bugs/1917939 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1627 https://gitlab.gnome.org/GNOME/mutter/-/issues/1627 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1627 Importance: Unknown Status: Unknown ** This bug has been marked a duplicate of bug 1917939 Windows maximise underneath dock after monitor sleep -- 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/1955586 Title: Revert "layout: Exclude hidden actors from struts" Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: New Bug description: A previous commit to mutter causes unintended problems for users. This commit is reverted upstream in gnome-shell 40.6. More information here: https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/aded2cd01b7af4d2bf355ed7cb129c6b869d84fb My original bug report is here: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4886#note_1338482 I'm posting this as a Ubuntu bug in hopes that if gnome-shell 40.6 is not to be updated in 21.10 for sometime, that at least the commit can be reverted. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 22 14:12:47 2021 DisplayManager: gdm3 ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-11-15 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1955586/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872870] Re: When zoom is enabled, mouse pointer leaves square trails on desktop
** Changed in: mutter (Ubuntu) Status: Triaged => Fix Committed ** Tags added: fixed-in-40.8 fixed-in-41.3 fixed-upstream ** Tags added: fixed-in-42.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1872870 Title: When zoom is enabled, mouse pointer leaves square trails on desktop Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: Problem: When you turn on Zoom from the Accessibility menu, the mouse leaves square shaped trails as it moves. Steps to Reproduce: 1. Under the Settings applet's Accessibility menu, turn on Zoom. 2. Observe the mouse cursor leaving little square patterns wherever it goes, obscuring whatever you're trying to work on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 21:50:16 2020 InstallationDate: Installed on 2020-01-09 (96 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to focal on 2020-01-24 (82 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1872870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934457] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from sig
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-42 fixed-upstream ** Tags removed: fixed-in-42 ** Tags added: fixed-in-42.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1934457 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_unref() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/eca665045730307781118f49eecca44ef0b9ea17 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1934457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934458] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_
** Tags added: impish ** Tags added: fixed-in-42.0 fixed-upstream ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4436 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1934458 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast() from on_window_icon_changed() from g_closure_invoke() from signal_emit_unlocked_R() from g_signal_emit_valist() from g_signal_emit() from g_object_dispatch_properties_changed() from g_object_notify_queue_thaw() from g_object_thaw_notify() from meta_window_update_icon_now() from idle_update_icon() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3~21.04.1, the problem page at https://errors.ubuntu.com/problem/29945d56fd6502de24678bddb8f825c97977fcbb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1934458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788535] Re: gnome-control-center shows 120Hz display frequencies that the display doesn't support (really only 60Hz hardware)
** Changed in: mutter (Ubuntu) Status: Confirmed => Fix Committed ** No longer affects: gnome-control-center (Ubuntu) ** Tags added: fixed-in-40.8 fixed-in-41.3 fixed-upstream -- 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/1788535 Title: gnome-control-center shows 120Hz display frequencies that the display doesn't support (really only 60Hz hardware) Status in Mutter: New Status in mutter package in Ubuntu: Fix Committed Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/275 --- gnome-control-center shows 120Hz display frequencies that the display doesn't support (it's really only 60Hz) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.29.91-1 ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12 Uname: Linux 4.17.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 Date: Thu Aug 23 11:08:09 2018 InstallationDate: Installed on 2018-08-17 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180723) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1788535/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956263] Re: Situationm
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 You mention `grub` which is a boot loader; thus it's a boot issue and the OS doesn't start? Screen blanking can occur during the boot process (video hardware switches modes) for some hardware setups. Grub config has documentation; eg. https://help.ubuntu.com/community/Grub2/Setup but it's all geared at altering the boot process; or making the grub menu more appealing. You're also not using Ubuntu kernel, with various 3rd party packages, such as what is found in a 3rd OS/source (eg. not `21.0.3-0ubuntu0.3~20.04.5` but `21.2.2-1ubuntu1pop0~1634226723~20.04~b715ae2~dev` so issues should be addressed with the 3rd party packager (possibly system76) as you're not using Ubuntu packages. ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => xorg-server (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/1956263 Title: Situationm Status in xorg-server package in Ubuntu: Incomplete Bug description: I have been using ubuntu for nearly ten years, but have only recently started taking things seriously. My particular issue is that every now and then I have a screen blinking problem. I have done a bunch of research, and it points to the grub configuration. I have downloaded and installed grub customizer. But I am not sure what all the options are and am afraid of messing anyting up. Not sure that coming here will help, or how I can pay for any help. Thanks for reading, and for any help you are able to provide. PS I am running Ubundu 20.03 on a System 76 Mini box. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.15.5-76051505-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jan 3 18:28:39 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Meerkat ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.5-76051505-generic root=UUID=bcaa96a9-3ebb-4f61-8b4d-bf8382de31aa ro Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2018 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0056.2018.1128.1717 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: meer4 dmi.ec.firmware.release: 3.20 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0056.2018.1128.1717:bd11/28/2018:br5.6:efr3.20:svnSystem76:pnMeerkat:pvrmeer4:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnSystem76:ct3:cvrmeer4:skuBOXNUC8i3BEK: dmi.product.family: Intel NUC dmi.product.name: Meerkat dmi.product.sku: BOXNUC8i3BEK dmi.product.version: meer4 d
[Desktop-packages] [Bug 1956235] Re: Pointer Location (which uses Ctrl key) conflicts with other Ctrl-based shortcuts
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1956235 Title: Pointer Location (which uses Ctrl key) conflicts with other Ctrl-based shortcuts Status in gnome-shell package in Ubuntu: New Bug description: When activating Pointer Location function, I cannot use any other Ctrl-based shortcuts. Ctrl+C, Ctrl+V, Ctrl+X, etc. just stop working because Pointer Location is fired up once Ctrl is pressed. I think that shortcuts should work as follows: shortcut bound commands should be activated after keys are released. (BTW, don't know whether it's OK to write here but I've never had such issues with Windows OS, because no shortcuts interrupt one another there and it's very important nowadays because shortcuts help saving one's valuable time). OS Name: Ubuntu 20.04.3 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956235] [NEW] Pointer Location (which uses Ctrl key) conflicts with other Ctrl-based shortcuts
You have been subscribed to a public bug: When activating Pointer Location function, I cannot use any other Ctrl- based shortcuts. Ctrl+C, Ctrl+V, Ctrl+X, etc. just stop working because Pointer Location is fired up once Ctrl is pressed. I think that shortcuts should work as follows: shortcut bound commands should be activated after keys are released. (BTW, don't know whether it's OK to write here but I've never had such issues with Windows OS, because no shortcuts interrupt one another there and it's very important nowadays because shortcuts help saving one's valuable time). OS Name: Ubuntu 20.04.3 LTS OS Type: 64-bit GNOME Version: 3.36.8 Windowing System: X11 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment conflict pointer shortcuts -- Pointer Location (which uses Ctrl key) conflicts with other Ctrl-based shortcuts https://bugs.launchpad.net/bugs/1956235 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956263] [NEW] Situationm
Public bug reported: I have been using ubuntu for nearly ten years, but have only recently started taking things seriously. My particular issue is that every now and then I have a screen blinking problem. I have done a bunch of research, and it points to the grub configuration. I have downloaded and installed grub customizer. But I am not sure what all the options are and am afraid of messing anyting up. Not sure that coming here will help, or how I can pay for any help. Thanks for reading, and for any help you are able to provide. PS I am running Ubundu 20.03 on a System 76 Mini box. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.15.5-76051505-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Jan 3 18:28:39 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Iris Plus Graphics 655 [8086:3ea5] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 655 [8086:2074] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Meerkat ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.5-76051505-generic root=UUID=bcaa96a9-3ebb-4f61-8b4d-bf8382de31aa ro Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2018 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0056.2018.1128.1717 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: System76 dmi.chassis.version: meer4 dmi.ec.firmware.release: 3.20 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0056.2018.1128.1717:bd11/28/2018:br5.6:efr3.20:svnSystem76:pnMeerkat:pvrmeer4:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnSystem76:ct3:cvrmeer4:skuBOXNUC8i3BEK: dmi.product.family: Intel NUC dmi.product.name: Meerkat dmi.product.sku: BOXNUC8i3BEK dmi.product.version: meer4 dmi.sys.vendor: System76 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.107-8ubuntu1pop0~1634226451~20.04~d7878ab~dev version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1pop0~1634226723~20.04~b715ae2~dev version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1pop0~1634226723~20.04~b715ae2~dev version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 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 Dec 17 17:36:58 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages 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/1956263 Title: Situationm Status in xorg package in Ubuntu: New Bug description: I have been using ubuntu for nearly ten years, but have only recently started taking things seriously. My particular issue is that every now and then I have a screen blinking problem. I have done a bunch of research, and it points to the grub configuration. I have downloaded and installed grub customizer. But I am not sure what all the options are and am afraid of messing anyting up. Not sure that coming here will help, or how I can pay for any help. Thanks for reading, and for any help you are able to provide. PS I am running Ubundu 20.03 on a System 76 Mini box. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.15.5-76051505-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None
[Desktop-packages] [Bug 1956257] [NEW] package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit s
Public bug reported:
Ubuntu 21.10 x64
chromium-browser:
Установлен: 1:85.0.4183.83-0ubuntu2
i view youtube and turn to pause and notebook was frozen
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
Uname: Linux 5.13.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Jan 3 21:25:35 2022
ErrorMessage: new chromium-browser package pre-installation script subprocess
returned error exit status 1
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.20.9ubuntu2.1
apt 2.3.9
Snap.Changes:
ID Status Spawn Ready Summary
5Error 2022-01-03T21:22:36+02:00 2022-01-03T21:25:35+02:00 Установить
snap-пакет "chromium"
6Done2022-01-03T21:36:28+02:00 2022-01-03T21:46:52+02:00 Установить
snap-пакет "chromium"
Snap.ChromeDriverVersion:
mkdir: cannot create directory '/run/user/0': Permission denied
ChromeDriver 96.0.4664.110
(d5ef0e8214bc14c9b5bbf69a1515e431394c62a6-refs/branch-heads/4664@{#1283})
Snap.ChromiumVersion:
mkdir: cannot create directory '/run/user/0': Permission denied
Chromium 96.0.4664.110 snap
SourcePackage: chromium-browser
Title: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package impish
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1956257
Title:
package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 1
Status in chromium-browser package in Ubuntu:
New
Bug description:
Ubuntu 21.10 x64
chromium-browser:
Установлен: 1:85.0.4183.83-0ubuntu2
i view youtube and turn to pause and notebook was frozen
ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19
Uname: Linux 5.13.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair wl
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Jan 3 21:25:35 2022
ErrorMessage: new chromium-browser package pre-installation script subprocess
returned error exit status 1
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal,
3.9.4-1build1
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.20.9ubuntu2.1
apt 2.3.9
Snap.Changes:
ID Status Spawn Ready Summary
5Error 2022-01-03T21:22:36+02:00 2022-01-03T21:25:35+02:00
Установить snap-пакет "chromium"
6Done2022-01-03T21:36:28+02:00 2022-01-03T21:46:52+02:00
Установить snap-пакет "chromium"
Snap.ChromeDriverVersion:
mkdir: cannot create directory '/run/user/0': Permission denied
ChromeDriver 96.0.4664.110
(d5ef0e8214bc14c9b5bbf69a1515e431394c62a6-refs/branch-heads/4664@{#1283})
Snap.ChromiumVersion:
mkdir: cannot create directory '/run/user/0': Permission denied
Chromium 96.0.4664.110 snap
SourcePackage: chromium-browser
Title: package chromium-browser 1:85.0.4183.83-0ubuntu2 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956257/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956256] [NEW] Apparmor profile error "run/systemd/resolve/io.systemd.Resolve"
Public bug reported: After using aa-logprof to individually resolve apparmor errors for firefox, there is at least one line that is not recognized by aa-logprof (values censored with ): audit: type=1400 audit(): apparmor="DENIED" operation="connect" info="Failed name lookup - disconnected path" error=-13 profile="firefox" name="run/systemd/resolve/io.systemd.Resolve" pid= comm= requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=102 There is no immediately recognizable functionality problem with this. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor -- 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/1956256 Title: Apparmor profile error "run/systemd/resolve/io.systemd.Resolve" Status in firefox package in Ubuntu: New Bug description: After using aa-logprof to individually resolve apparmor errors for firefox, there is at least one line that is not recognized by aa- logprof (values censored with ): audit: type=1400 audit(): apparmor="DENIED" operation="connect" info="Failed name lookup - disconnected path" error=-13 profile="firefox" name="run/systemd/resolve/io.systemd.Resolve" pid= comm= requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=102 There is no immediately recognizable functionality problem with this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1956256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956248] [NEW] I get two characters in Activities when I press one key for the first key I press...
Public bug reported: If I click the Activities in the upper right hand corner of the screen, then do NOT click in the search bar and begin to type, I get two of whatever character I hit. At first I thought it was due to my keyboard wearing out, but it happens on multiple computers, and whatever key I type, even infrequently used ones. If I click in the search bar before I type, then the characters are not duplicated. If I then backspace over the single character that was correctly displayed in the search bar and type another character, that character is doubled. Bounce keys will not eliminate this either. I started noticing doubling characters a couple of weeks (approximately) ago. I didn't start to suspect the real reason until recently. Thanks for working on this for all of us! Rob ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jan 3 11:43:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-19 (990 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-10-12 (82 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1956248 Title: I get two characters in Activities when I press one key for the first key I press... Status in gnome-shell package in Ubuntu: New Bug description: If I click the Activities in the upper right hand corner of the screen, then do NOT click in the search bar and begin to type, I get two of whatever character I hit. At first I thought it was due to my keyboard wearing out, but it happens on multiple computers, and whatever key I type, even infrequently used ones. If I click in the search bar before I type, then the characters are not duplicated. If I then backspace over the single character that was correctly displayed in the search bar and type another character, that character is doubled. Bounce keys will not eliminate this either. I started noticing doubling characters a couple of weeks (approximately) ago. I didn't start to suspect the real reason until recently. Thanks for working on this for all of us! Rob ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jan 3 11:43:59 2022 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-19 (990 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2021-10-12 (82 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956248/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956044] Re: [SRU] libreoffice 7.2.5 for impish
** Description changed: [Impact] * LibreOffice 7.2.5 is in its fifth bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.5_release - * Version 7.2.3 is currently released in impish. For a list of fixed bugs compared to 7.2.3 see the list of bugs fixed in the release candidates of 7.2.5 (that's a total of ?? bugs): + * Version 7.2.3 is currently released in impish. For a list of fixed bugs compared to 7.2.3 see the list of bugs fixed in the release candidates of 7.2.5 (that's a total of 90 bugs): https://wiki.documentfoundation.org/Releases/7.2.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.2.5/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_72/1263/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/amd64/libr/libreoffice/20211231_185725_a1fa4@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/arm64/libr/libreoffice/20211231_191240_0e3b3@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/armhf/libr/libreoffice/20211231_224047_59f05@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/ppc64el/libr/libreoffice/20211231_182048_4c641@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-impish-libreoffice-libreoffice-prereleases/impish/s390x/libr/libreoffice/20211231_175403_99078@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] - * A minor release with a total of ?? bug fixes always carries the + * A minor release with a total of 90 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. ** Changed in: libreoffice (Ubuntu Impish) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Impish) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Impish) Assignee: (unassigned) => Rico Tzschichholz (ricotz) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1956044 Title: [SRU] libreoffice 7.2.5 for impish Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Impish: In Progress Bug description: [Impact] * LibreOffice 7.2.5 is in its fifth bugfix release of the 7.2 line: https://wiki.documentfoundation.org/ReleasePlan/7.2#7.2.5_release * Version 7.2.3 is currently released in impish. For a list of fixed bugs compared to 7.2.3 see the list of bugs fixed in the release candidates of 7.2.5 (that's a total of 90 bugs): https://wiki.documentfoundation.org/Releases/7.2.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.2.5/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci
[Desktop-packages] [Bug 1952083] Re: Add support for Beige Goby
** Changed in: amd Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1952083 Title: Add support for Beige Goby Status in amd: Fix Released Status in OEM Priority Project: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Released Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845797]
Unfortunately I replicated those same failures. All five speakers work just fine in Windows (using qemu) although the played back verbs will only continue activating the same speakers. When I tested it I was able to "break" and "restore" the speakers using different verb-sets, so while it's definitely making some changes, it doesn't seem to be impacting the bottom speakers in the slightest. -- 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/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956243] [NEW] Ping give socket error initially if IPv6 is disabled
Public bug reported: With IpV6 enabled everything works well. However if you disable ipv6 by editing /etc/default/grub with the following entry GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1" then when you ping there is an initial socket error ping localhost ping: socket: Address family not supported by protocol PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms 64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.028 ms however ping -4 works ping -4 localhost PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.029 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.021 ms so it looks like ping is trying ipv6 first and not detecting that its disabled. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: iputils-ping 3:20210202-1build1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 3 17:42:07 2022 InstallationDate: Installed on 2022-01-03 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211029) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iputils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages uec-images -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1956243 Title: Ping give socket error initially if IPv6 is disabled Status in iputils package in Ubuntu: New Bug description: With IpV6 enabled everything works well. However if you disable ipv6 by editing /etc/default/grub with the following entry GRUB_CMDLINE_LINUX_DEFAULT="ipv6.disable=1" then when you ping there is an initial socket error ping localhost ping: socket: Address family not supported by protocol PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.046 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.038 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.028 ms 64 bytes from localhost (127.0.0.1): icmp_seq=4 ttl=64 time=0.028 ms however ping -4 works ping -4 localhost PING localhost (127.0.0.1) 56(84) bytes of data. 64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.032 ms 64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.029 ms 64 bytes from localhost (127.0.0.1): icmp_seq=3 ttl=64 time=0.021 ms so it looks like ping is trying ipv6 first and not detecting that its disabled. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: iputils-ping 3:20210202-1build1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jan 3 17:42:07 2022 InstallationDate: Installed on 2022-01-03 (0 days ago) InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211029) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iputils/+bug/1956243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
** Bug watch removed: github.com/DisplayLink/evdi/issues #181 https://github.com/DisplayLink/evdi/issues/181 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1955904] Re: Sync glibmm2.4 2.66.2-1 (main) from Debian unstable (main)
Hi Nicholas! This version was auto-synced to Ubuntu, but it failed to build: https://launchpad.net/ubuntu/+source/glibmm2.4/2.66.2-1 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996171 So it was removed because of that: > Deleted on 2021-12-07 by Steve Langasek > FTBFS on all archs when tests are enabled; Debian bug #996171 ** Bug watch added: Debian Bug tracker #996171 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996171 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glibmm2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1955904 Title: Sync glibmm2.4 2.66.2-1 (main) from Debian unstable (main) Status in glibmm2.4 package in Ubuntu: New Bug description: Please sync glibmm2.4 2.66.2-1 (main) from Debian unstable (main) The version 2.66.1 has an important fix of #1955044 Upstream discussion of the issue: https://mail.gnome.org/archives/gtkmm-list/2021-May/msg7.html Changelog entries since current jammy version 2.64.2-2build1: glibmm2.4 (2.66.2-1) unstable; urgency=high * New upstream release - Fix jackd segfault (Closes: #994969) -- Jeremy Bicha Sun, 10 Oct 2021 20:58:47 -0400 glibmm2.4 (2.66.1-1) unstable; urgency=medium * New upstream release * Build with meson * Build-Depend on glib-networking * debian/rules: Drop unneeded -Wl,--as-needed * Bump debhelper-compat to 13 -- Jeremy Bicha Sun, 19 Sep 2021 09:22:18 -0400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1955904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908931] Re: Kubuntu 20.04 System Settings Online Accounts - unable to add Google account
I am not using Wayland (verified by multiple ways from https://askubuntu.com/questions/904940/how-can-i-tell-if-i-am-running- wayland and https://unix.stackexchange.com/questions/202891/how-to-know- whether-wayland-or-x11-is-being-used ). I tried the reproduction again and the problem persists. I have package libwebkit2gtk-4.0-37 installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1908931 Title: Kubuntu 20.04 System Settings Online Accounts - unable to add Google account Status in systemsettings package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: New Bug description: Let's try with fresh install: Kubuntu 20.04.1 with default installer options + all packages updated, upgraded, systemsettings package version 4:5.18.4.1-0ubuntu1: - Go to System Settings -> Online Accounts - Click + Add new Account - Choose Google - Window "Web authentication with google" pops up - Enter the email, click Next - Enter the password, click Next - Enter 2FA code from the authenticator, click Next Expected result: - Google account is added, or some sort of confirmation/error Actual result: - Window title with title "Web authentication with google", buttons (menu, min, max, close), and borders are OK - Window content is empty (white canvas) - Nothing happens - Google account is not added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemsettings/+bug/1908931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1954628] Re: [USB-Audio - ALC4080] Front panel: Headphone output not working
** Summary changed: - [USB-Audio - USB Audio, playback] Headphone output mapped incorrectly + [USB-Audio - ALC4080] Front panel: Headphone output not working ** Description changed: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard - 'Starship/Matisse HD Audio Controller' controller that has a weird - mapping via USB audio (see bug: + 'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio chip) + controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. - After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. - Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. + After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. + Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: gijs 2129 F pulseaudio - /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio - /dev/snd/controlC0: gijs 2129 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: gijs 2129 F pulseaudio + /dev/snd/pcmC2D1p: gijs 2129 F...m pulseaudio + /dev/snd/controlC0: gijs 2129 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Dec 13 09:28:19 2021 InstallationDate: Installed on 2020-12-06 (371 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Audio successful Symptom_Card: USB Audio - USB Audio Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [USB-Audio - USB Audio, playback] Playback problem UpgradeStatus: Upgraded to impish on 2021-09-28 (75 days ago) dmi.bios.date: 07/09/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MAG X570S TORPEDO MAX (MS-7D54) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.00:bd07/09/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D54:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGX570STORPEDOMAX(MS-7D54):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7D54 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. -- 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/1954628 Title: [USB-Audio - ALC4080] Front panel: Headphone output not working Status in alsa-driver package in Ubuntu: New Bug description: I have a MSI MAG X570s Torpedo MAX motherboard, which has an onboard 'Starship/Matisse HD Audio Controller' (-> ALC4080 USB based audio chip) controller that has a weird mapping via USB audio (see bug: https://bugzilla.kernel.org/show_bug.cgi?id=206873 for a similar configuration). Sound via line-out works fine without any interventions. Headphone output however does not, while Ubuntu correctly detects the headphones as being plugged in when selected sound is still output via line-out, instead of via the front panel headphone jack-out. After some debugging I figured the headphones are connected to a seperate Alsa device on the same card as the line-out. Running 'pacmd load-module module-alsa-sink device=hw:2,1' gives me a working audio output that plays just via the headphone out. I guess a quirk needs to be written for the configuration. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0
[Desktop-packages] [Bug 1956227] [NEW] syestem shuts down terminal application and lose of video until restart
Public bug reported: Description:Ubuntu 20.04.3 LTS Release:20.04 Running gpu mining software t-rex with two nvidia gpu. It runs fine sometimes for 5 hours up to 3 days. Then it will stop mining and I lose video feed. I have a monitor set up to the on board video card ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 3 20:52:22 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-29 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (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 in Ubuntu. https://bugs.launchpad.net/bugs/1956227 Title: syestem shuts down terminal application and lose of video until restart Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu 20.04.3 LTS Release: 20.04 Running gpu mining software t-rex with two nvidia gpu. It runs fine sometimes for 5 hours up to 3 days. Then it will stop mining and I lose video feed. I have a monitor set up to the on board video card ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 3 20:52:22 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-12-29 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1956227/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1126858]
(In reply to NISZ LibreOffice Team from comment #23) > Created attachment 159953 [details] > Screenshot of Word and Writer side by side after following the steps > > Still happens in: > > Version: 7.0.0.0.alpha0+ (x64) > [...] > > Also: this behavior is the same as in Word. As noted by NISZ LibreOffice Team, the behaviour is very much similar i Word: Also in Word, Search & Replace while showing track-changes, does search within deleted text and replaces with non-deleted text. Just tested with MS Office 365. I can see why it can sometimes be relevant to search also in deleted text, e.g. to find where you (or a colleague) deleted something. And if you do not want this, just turn off showing track-changes. But I fail to see why anybody would want already-deleted text to be part of replacing. (Even before the problems of doing more than one search & replace, leading to several instances of the new text.) Well, failing the see the use could be just my lack of imagination. So: Can anybody come up with a case where searching within deleted text and replacing with new text would be the intended behaviour? Put another way: Can anybody see a reason why this would NOT be a bug (happening to be shared by LO and MS Office)? PS: Word notes the user that "We are through searching the document" after one pass, so the user will at least know that if s/he continues replacing, it will be in text that had already been considered. This will stop most users from repeated replacement, but does not change the question how replacing at all in deleted text could be the intended behaviour. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1126858 Title: [upstream] Search and replace, with tracked changes on, changing only format of text, causes Writer to hang Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: Create new text document with contents "Hello, World". Turn on change tracking (under Edit). Select Find and Replace (under Edit). Put "Hello" (no quotes) in both the find and the replace boxes. Click on "More". Put cursor in Replace box. Click on Format. Set it to, say Italic (leave other options empty). Accept. And now, for the fatal part: Click "Replace all". If you just replace one, you'll see why the latter fails. The replacement value gets inserted beofre the original, so then it continues on and sees the original again... ad infinitum. What should happen: If it just put its position after the original text when searching and replacing, it wouldn't have this problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Fri Feb 15 21:37:14 2013 InstallationDate: Installed on 2012-12-13 (65 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1126858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1126858]
Please don't spread incorrect information. It does not resemble the Microsoft Word behavior. I just tested on both Sharepoint and desktop MS Office 365. Please test again. You probably did not understand the bug. Libreoffice replaces the deleted text with each recursion while Microsoft Office does not replace deleted text. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1126858 Title: [upstream] Search and replace, with tracked changes on, changing only format of text, causes Writer to hang Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: Create new text document with contents "Hello, World". Turn on change tracking (under Edit). Select Find and Replace (under Edit). Put "Hello" (no quotes) in both the find and the replace boxes. Click on "More". Put cursor in Replace box. Click on Format. Set it to, say Italic (leave other options empty). Accept. And now, for the fatal part: Click "Replace all". If you just replace one, you'll see why the latter fails. The replacement value gets inserted beofre the original, so then it continues on and sees the original again... ad infinitum. What should happen: If it just put its position after the original text when searching and replacing, it wouldn't have this problem. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.5.0-23.35-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Fri Feb 15 21:37:14 2013 InstallationDate: Installed on 2012-12-13 (65 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1126858/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot
This bug also affects me. I am using Ubuntu MATE (Jammy). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1953052 Title: In Jammy sound level reset after reboot Status in alsa-utils package in Ubuntu: Confirmed Bug description: After reboot sound level is reset ignoring the level set in previous session. I manually set the sound output level at next boot the sound is set at a different level (about 70%) Expected: the sound level is persistent across power off/on What happens : sound level is set at a different level (about 70%) Note: this problem does not occur on different partitions of same PC running Ubuntu 20.04 or 21.10 corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center gnome-control-center: Installed: 1:41.1-1ubuntu1 Candidate: 1:41.1-1ubuntu1 Version table: *** 1:41.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p3-jj-1130:~$ inxi -Fx System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish) Machine: Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: Mobo: Dell model: 0C1PF2 v: A00 serial: UEFI: Dell v: 1.5.0 date: 12/17/2019 Battery: ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) volts: 11.3 min: 11.4 model: SWD-ATL3.618 DELL WJPC403 status: Discharging CPU: Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP arch: Ice Lake rev: 5 cache: L2: 6 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19046 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 710 3: 706 4: 714 5: 966 6: 712 7: 724 8: 821 Graphics: Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: kernel bus-ID: 00:02.0 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-6:3 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell driver: loaded: i915 note: n/a (using device driver) resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 21.2.2 direct render: Yes Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: snd_hda_intel v: kernel bus-ID: 00:1f.3 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.40 running: yes Network: Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell driver: r8169 v: kernel port: 3000 bus-ID: 01:00.0 IF: enp1s0 state: down mac: 98:e7:43:59:19:19 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Dell driver: ath10k_pci v: kernel bus-ID: 02:00.0 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9 Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 1-10:4 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block: hardware: no software: yes address: D8:12:65:B8:21:BA Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%) ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 512GB size: 476.94 GiB temp: 24.9 C ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: /dev/nvme0n1p3 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: /dev/nvme0n1p1 Swap: Alert: No swap data was found. Sensors: System Temperatures: cpu: 27.8 C mobo: N/A Fan Speeds (RPM): cpu: 0 Info: Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07 corrado@corrado-p3-jj-1130:~$ --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-30 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) Package: gnome-control-center 1:41.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Tags: wayland-session jammy Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug
[Desktop-packages] [Bug 1780680] Re: Older version in bionic than in xenial
** Changed in: fuse-umfuse-ext2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780680 Title: Older version in bionic than in xenial Status in fuse-umfuse-ext2 package in Ubuntu: Fix Released Status in libclc package in Ubuntu: Won't Fix Status in libdrm package in Ubuntu: Won't Fix Status in linux-meta-azure package in Ubuntu: Fix Released Status in linux-meta-gcp package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Won't Fix Status in patch package in Ubuntu: Invalid Status in python-pyvmomi package in Ubuntu: Invalid Status in snapcraft package in Ubuntu: Fix Released Status in wireless-regdb package in Ubuntu: Fix Released Bug description: These packages have an older version in artful than in xenial. fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1 libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1 libdrm 2.4.83-1 < 2.4.91-2~16.04.1 mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1 patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1 python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1 snapcraft 2.42+17.10 < 2.42.1 wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1 Some of these are older in bionic than in xenial too. Shouldn’t there be an automated check for this? (See also: bug 1780679, bug 1780681.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922047]
Firefox 96 on Gnome 41.2 is still affected. These settings seem to help though. Also the other one should be multiplier_y. > In Windows 10, with the Precision touchpad, unaccelerated scrolling deltas > are used directly. In Firefox and GTK, they are not used directly, it seems. > Also, the scrolling on X11 using XInput2 with touchpad is also unusable for > me, same with GTK. Haven't exactly tested Wayland though, but for me, it is > 1.5xish compared to X11. > > I could manage the situation for Firefox as changing > `mousewheel.default.delta_multiplier_x` and > `mousewheel.default.delta_multiplier_x` from 100 to 30, and > `mousewheel.min_line_scroll_amount` from 5 to 180. With deltas, I could > manage touchpad scrolling speed usable, and with `min_line_scroll_amount` > one, mouse doesn't be affected by the delta reduction command. These are my > findings. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1922047 Title: Touchpad scrolling is too fast Status in Mozilla Firefox: New Status in GTK+: Unknown Status in Mutter: Unknown Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk4 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: This is an issue which has troubled me for a while. Anecdotally, scrolling feels way too fast in GNOME on Wayland compared to on X11. I finally tested it semi-scientifically, and it seems like GNOME on Wayland scrolls almost exactly 1.5x faster than GNOME on X11. I tested this by testing how many lines are scrolled from a full two- finger touchpad swipe from the bottom of my touchpad to the top of my touchpad, and logged a few attempts in both X and Wayland. I kept track of the results in this spreadsheet: https://docs.google.com/spreadsheets/d/17EaBM5Pgt7GdnnzcN2Vchk4kfT7IZ6i4qZ0zpVRGLhc/edit?usp=sharing I scrolled in one of my own GTK applications (https://github.com/mortie/lograt) because it lets me easily see how many lines I scrolled. Attach is a video of one full scroll on X11 and one full scroll on Wayland. This testing was performed on a Dell XPS 13 9343, but I've also used Ubuntu on a Dell XPS 9575 where GNOME Wayland scrolling also feels way too fast. I don't have other hardware to test on. This has been an issue on both Ubuntu 20.10 and Ubuntu 21.04. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 31 11:44:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-21 (495 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-16 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1922047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942385] Re: [SOF - sof-bytcht rt5640, playback] fails after a while
In my case, it might play media for some minutes (1-5 minutes). I tried 5.10.89-051089-generic (last 5.10) linux and I didn't found this bug. Ubuntu 21.10, audio card name: sof-bytcht rt5645. -- 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/1942385 Title: [SOF - sof-bytcht rt5640, playback] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I am experiencing beep sound and audio from zoom, firefox, or vlc. It might play media for some seconds then beep. This has something to do with pipewire and sof driver and S16_LE format.( I read online). If I switch the profile Play HiFi quality Music in pavucontrol it does correct the beep sound for some few seconds then it ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bret 1249 F pulseaudio /dev/snd/pcmC0D0c: bret 1249 F...m pulseaudio /dev/snd/pcmC0D0p: bret 1249 F...m pulseaudio /dev/snd/timer: bret 1249 f pulseaudio CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Thu Sep 2 05:25:01 2021 InstallationDate: Installed on 2021-08-29 (3 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210612) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - sof-bytcht rt5640 Symptom_PulseAudioLog: Sep 02 05:24:14 toshiba systemd[826]: pulseaudio.service: Deactivated successfully. Sep 02 05:24:25 toshiba systemd[826]: pulseaudio.socket: Deactivated successfully. Symptom_Type: Sound works for a while, then breaks Title: [SOF - sof-bytcht rt5640, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/02/2015 dmi.bios.release: 5.20 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 5.20 dmi.board.name: 0700 dmi.board.vendor: FF50 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.ec.firmware.release: 5.20 dmi.modalias: dmi:bvnINSYDECorp.:bvr5.20:bd11/02/2015:br5.20:efr5.20:svnTOSHIBA:pnSATELLITEClickMiniL9W-B:pvrPDW0FE-002005EN:skuINVALID:rvnFF50:rn0700:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE Click Mini L9W-B dmi.product.sku: INVALID dmi.product.version: PDW0FE-002005EN dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1942385/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956211] [NEW] package libsane 1.0.29-0ubuntu5.2 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/60-li
Public bug reported: didn't succeed to instal ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsane 1.0.29-0ubuntu5.2 [modified: lib/udev/rules.d/60-libsane.rules] ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 3 10:41:34 2022 ErrorMessage: tentative de remplacement de « /lib/udev/rules.d/60-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 InstallationDate: Installed on 2021-02-02 (335 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: sane-backends Title: package libsane 1.0.29-0ubuntu5.2 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/60-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1956211 Title: package libsane 1.0.29-0ubuntu5.2 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/60-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 Status in sane-backends package in Ubuntu: New Bug description: didn't succeed to instal ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libsane 1.0.29-0ubuntu5.2 [modified: lib/udev/rules.d/60-libsane.rules] ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 3 10:41:34 2022 ErrorMessage: tentative de remplacement de « /lib/udev/rules.d/60-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 InstallationDate: Installed on 2021-02-02 (335 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: sane-backends Title: package libsane 1.0.29-0ubuntu5.2 [modified: lib/udev/rules.d/60-libsane.rules] failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/60-libsane.rules », qui est différent d'autres instances du paquet libsane:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1956211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
