[Desktop-packages] [Bug 1898910] Re: gnome-shell crashes with [St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed()
It looks fairly likely that https://gitlab.gnome.org/World/ShellExtensions/desktop- icons/-/merge_requests/191 already fixed the only possible root cause of this. I can't be sure because I still can't reproduce it. Regardless, the related gnome-shell fix should prevent all possible forms of the same mistake from crashing the shell: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1507 ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Groovy) Status: Confirmed => Won't Fix ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898910 Title: gnome-shell crashes with [St:ERROR:../src/st/st- bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL)] called from DesktopGrid::_backgroundDestroyed() [desktopGrid.js:206] Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in gnome-shell source package in Groovy: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Groovy: Won't Fix Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Won't Fix Bug description: [Impact] Gnome Shell crashes at random times. https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 [Test Case] None known. [Where problems could occur] The proposed fix is from the stable upstream gnome-shell branch so potential problems could arise from the usual risk of patching stable branches resulting in new regressions. [Other Info] See also bug 1898005 --- Ubuntu on Wayland crashes when you try to change the resolution even if your display supports the Version: 3.38.0-1ubuntu2 Release: 20.10 Groovy Gorilla (development branch) What I expected to happen 1. Login to Wayland 2. Change the resolution 3. Go on with my day What actually happened 1. Login to Wayland 2. Change the resolution 3. Wait a minute to get kicked to the gdm login screen 4. Now I am here. ProblemType: CrashDistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 7 12:55:35 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-10-07 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910455] Re: Thunar and Nautilus USB drive ejecting takes long time
thanks, the log doesn't seem to have any useful clue though :-/ it's probably not a nautilus bug if other browsers have the same issue ** Changed in: nautilus (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1910455 Title: Thunar and Nautilus USB drive ejecting takes long time Status in nautilus package in Ubuntu: New Bug description: Every time i use PNY usb flash drive, when I am trying to eject it, even if i did not store anything, it shows message "Writing data to a device, do not disconnect". This message freezes the window for a half of a minute or so. This issue affects both Thunar and Nautilus, on both Ubuntu 20.04 and Ubuntu Studio 20.04. The similar issue is documented in the bug #1762595, but the message on the board with that bug states that anyone encountering it should file a new bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
** Changed in: gnome-shell (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: gnome-shell (Ubuntu Groovy)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Also affects: gnome-shell (Ubuntu Hirsute)
Importance: High
Assignee: Daniel van Vugt (vanvugt)
Status: Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
Status in Mutter:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell source package in Groovy:
Fix Committed
Status in gnome-shell source package in Hirsute:
Fix Released
Status in gnome-shell package in Debian:
Unknown
Bug description:
[ Impact ]
Launching terminator crashes gnome-shell
[ Test case ]
- Launch terminator
- GNOME Shell should not crash
In any case these errors should not be reported anymore with gnome-shell
3.38.2-1ubuntu1~20.10.1:
- https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd
- https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605
[ Regression potential ]
A window could not be animated on size change.
---
Launching terminator crashes gnome-shell, happens on two separate
machines.
ProblemType: CrashDistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 18:05:57 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1600706451
InstallationDate: Installed on 2019-10-14 (350 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/tjaalton
ProcEnviron:
LANG=fi_FI.UTF-8
PATH=(custom, user)
SHELL=/bin/zsh
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
Signal: 5SourcePackage: gnome-shell
StacktraceTop:
g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_structured_array()
UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 507089]
I can answer for 68.10.0 that the problem does not occur anymore (but our setup changed since then, additionally using kerberos) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/507089 Title: Thunderbird 3 (Shredder) always segfaults on startup with LDAP auth in nsswitch Status in SeaMonkey: New Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird If nsswitch.conf is set with: passwd: compat ldap group: compat ldap shadow: compat ldap My ldap config does work as I'm using it for login authentication. thunderbird-3.0 always segfaults: 0 %> thunderbird-3.0 Segmentation fault 0 %> thunderbird-3.0 --g-fatal-warnings Segmentation fault 139 %> thunderbird-3.0 -options Segmentation fault 139 %> thunderbird-3.0 -safe-mode Segmentation fault 139 %> thunderbird-3.0 -ProfileManager Segmentation fault 139 %> ...even with no .thunderbird-30 dir: %> thunderbird-3.0 -ProfileManager *INFO* No /users/bedge/.thunderbird-3.0 detected. Create it from /users/bedge/.mozilla-thunderbird Segmentation fault 0 9:12:52 bedge@ice ~ 139 %> Changing nsswitch back to NIS works: passwd: compat nis group: compat nis shadow: compat nis 1 %> dpkg -l thunderbird\* Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===-===-== ii thunderbird 2.0.0.23+build1+nobinonly-0 mail/news client with RSS and integrated spam filter support ii thunderbird-3.0 3.0~rc3~micahg+nobinonly-0u mail/news client with RSS and integrated spam filter support ii thunderbird-3.0-gnome-suppo 3.0~rc3~micahg+nobinonly-0u Support for Gnome in Mozilla Thunderbird 3.0 ii thunderbird-dispmua 1.6.4.3-1ubuntu1Display Mail User Agent extension (transitional package) ii thunderbird-gnome-support 2.0.0.23+build1+nobinonly-0 Support for Gnome in Mozilla Thunderbird ii thunderbird-locale-en-gb1:2.0.0.14+1-0ubuntu2 Thunderbird English language/region package ii thunderbird-nostalgy0.2.16+svn151-1ubuntu1 keyboard shortcut extension for thunderbird ii thunderbird-quickfile 0.17.0.0011-0ubuntu4faster mail filing for the Thunderbird mail client ii thunderbird-traybiff1.2.3-4.2ubuntu2traybiff - new mail alert for thunderbird WORKAROUND: Installing the nscd package solves this issue in most cases. To manage notifications about this bug go to: https://bugs.launchpad.net/seamonkey/+bug/507089/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911079] Re: Unable to click top right corner of screen
Also, is the bug in gnome-shell or in Unity? Both seem to be mentioned here. Can you please attach a screenshot of the whole screen when the problem is occuring? ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1911079 Title: Unable to click top right corner of screen Status in Ubuntu: Incomplete Bug description: Dead zone ~10% of the top corner how ever I can click above the side tool bar it is like some invisible box is nested on top of my window ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 Uname: Linux 5.10.0-051000-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jan 12 10:55:21 2021 DisplayManager: lightdm InstallationDate: Installed on 2020-12-03 (39 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 ShellJournal: -- Logs begin at Fri 2020-12-04 07:06:30 AEST, end at Tue 2021-01-12 10:55:09 AEST. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1911036 Title: GDK/GTK app crash when performing drag operation Status in Ubuntu: Incomplete Bug description: For many months now, whenever any mouse drag is attempted in an application using the gtk tool kit, the application immediately crashes. I've noticed this at least in Firefox and thunar. It also occurs when displaying these applications from a Virtualbox machine or from another server running something other than Ubuntu. The VM was running CentOS 8 and the remote server was running Mageia. Both Firefox and thunar run fine with Mageia's Xorg. It seems like the issue may be with the Xorg server on Ubuntu. I tried setting the GDK_SYNCHRONIZE variable to various settings but was unable to produce further debug output. The only other debug output I was able to gather is when running thunar with the --gtk- debug parameter (attached). I also tried running thunar with GDB but without recompiling it, it doesn't produce much information other than it's stopping in glib. Let me know what other information I can provide. (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ExceptionHandler::GenerateDump cloned child 110611 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. [1]+ Trace/breakpoint trap (core dumped) firefox (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) $ ldd /bin/thunar linux-vdso.so.1 (0x7ffc0c8cc000) libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 (0x7fdbb548c000) libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 (0x7fdbb544f000) libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 (0x7fdbb5442000) libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 (0x7fdbb5437000) libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000) libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000) libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 (0x7fdbb53f3000) libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 (0x7fdbb4c42000) libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 (0x7fdbb4b3d000) libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x7fdbb4b13000) libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 (0x7fdbb49f) libgdk_pixbuf-2.0.so.0 =>
[Desktop-packages] [Bug 1911079] Re: Unable to click top right corner of screen
Do you mean top right or top left corner? The bug title says "right" but the screenshot shows "left". -- 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/1911079 Title: Unable to click top right corner of screen Status in Ubuntu: Incomplete Bug description: Dead zone ~10% of the top corner how ever I can click above the side tool bar it is like some invisible box is nested on top of my window ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 Uname: Linux 5.10.0-051000-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jan 12 10:55:21 2021 DisplayManager: lightdm InstallationDate: Installed on 2020-12-03 (39 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 ShellJournal: -- Logs begin at Fri 2020-12-04 07:06:30 AEST, end at Tue 2021-01-12 10:55:09 AEST. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1911079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911030] Re: graphical flashes on a raspi 4
** Tags added: raspi raspi-gfx ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Summary changed: - graphical flashes on a raspi 4 + Graphical flashes on a raspi 4 -- 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/1911030 Title: Graphical flashes on a raspi 4 Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Using gnome-shell - activities - see attached video Graphics flash - more prominent with more than one app running. If you install ubuntu-budgie-desktop and simply move through the menu categories the flashing is even more prominent. I'm guessing this is xorg related - but I do note the recent mesa uplift has made things worse ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu55 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 16:49:14 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ImageMediaBuild: 20201225 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1911030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911024] Re: segfault crash after fresh restart
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1911024 Title: segfault crash after fresh restart Status in gnome-shell package in Ubuntu: Incomplete Bug description: segfault not located in a known VMA region (needed readable region)! destination rdi ok ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 Uname: Linux 5.10.4-051004-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 15:52:40 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-30 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.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/1911024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910455] Re: Thunar and Nautilus USB drive ejecting takes long time
Sorry about that. Here is a new log that is not truncated. ** Attachment added: "new_log.txt" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910455/+attachment/5451936/+files/new_log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1910455 Title: Thunar and Nautilus USB drive ejecting takes long time Status in nautilus package in Ubuntu: Incomplete Bug description: Every time i use PNY usb flash drive, when I am trying to eject it, even if i did not store anything, it shows message "Writing data to a device, do not disconnect". This message freezes the window for a half of a minute or so. This issue affects both Thunar and Nautilus, on both Ubuntu 20.04 and Ubuntu Studio 20.04. The similar issue is documented in the bug #1762595, but the message on the board with that bug states that anyone encountering it should file a new bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910559] Re: GDM3: Black screen with blinking cursor
OK, thanks. If the problem returns then we can reopen the bug. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1910559 Title: GDM3: Black screen with blinking cursor Status in gnome-shell package in Ubuntu: Invalid Bug description: About a month ago, GDM ceased to work. I opened another issue here https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717 but due to me using oibaf's ppa it was considered prudent to discard that issue and re-open after I removed the ppa and restored Ubuntu's dist packages. Upon boot, gdm goes to a black screen with a cursor. This screen flickers to show the underlying tty and on each flicker the cursor position resets to the bottom right. It will do this a number of times until GDM dies and I'm left on a tty. I can start my window manager (sway) without issue from the console still and everything functions normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: sway Date: Thu Jan 7 15:55:43 2021 SourcePackage: gdm3 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/1910559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909732] Re: unable to login to desktop manager after suspend
All of those bullet points are related :) ** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) ** Summary changed: - unable to login to desktop manager after suspend + Gnome Shell freezes for 2 minutes on unlock when mobile phone is connected (log shows gvfsd PTP errors) -- 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/1909732 Title: Gnome Shell freezes for 2 minutes on unlock when mobile phone is connected (log shows gvfsd PTP errors) Status in gnome-shell package in Ubuntu: Incomplete Bug description: After my laptop suspends I am unable to login back in again. I type in my password then everything freezes - I can drop to a terminal and run sudo service gdm restart this gives me access again to my laptop - though obviously everything I was working on has been closed down and potentially lost. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-02-16 (318 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: gdm3 3.38.1-2ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Tags: groovy Uname: Linux 5.8.0-33-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-11-16 (44 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911079] [NEW] Unable to click top right corner of screen
Public bug reported: Dead zone ~10% of the top corner how ever I can click above the side tool bar it is like some invisible box is nested on top of my window ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 Uname: Linux 5.10.0-051000-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jan 12 10:55:21 2021 DisplayManager: lightdm InstallationDate: Installed on 2020-12-03 (39 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 ShellJournal: -- Logs begin at Fri 2020-12-04 07:06:30 AEST, end at Tue 2021-01-12 10:55:09 AEST. -- -- No entries -- SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal uec-images ** Attachment added: "Screenshot from 2021-01-12 10-58-57.png" https://bugs.launchpad.net/bugs/1911079/+attachment/5451927/+files/Screenshot%20from%202021-01-12%2010-58-57.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1911079 Title: Unable to click top right corner of screen Status in gnome-shell package in Ubuntu: New Bug description: Dead zone ~10% of the top corner how ever I can click above the side tool bar it is like some invisible box is nested on top of my window ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 Uname: Linux 5.10.0-051000-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jan 12 10:55:21 2021 DisplayManager: lightdm InstallationDate: Installed on 2020-12-03 (39 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 ShellJournal: -- Logs begin at Fri 2020-12-04 07:06:30 AEST, end at Tue 2021-01-12 10:55:09 AEST. -- -- No entries -- 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/1911079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1817286] Re: Some Media Keys (Not all) and custom keyboard shortcuts irregulary don't work after boot/reboot
*** This bug is a duplicate of bug 1818978 *** https://bugs.launchpad.net/bugs/1818978 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1817286 Title: Some Media Keys (Not all) and custom keyboard shortcuts irregulary don't work after boot/reboot Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: After boot or reboot some media keys (Volume Up/Down) don't work, but others do (e.g. Brightnes Up/Down). Custom Keyboard Shortcuts then don't work at all. When a non working media key oder shortcut is pressed the following message appears in syslog: gsd-media-keys[2016]: Could not find accelerator for accel id 169 This happens irregulary. Sometimes everything works, sometimes it doesn't work as described above until next reboot. This might be a regression of https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1659517 Ubuntu Version: Ubuntu 18.04.2 LTS gnome-settings-daemon Version: 3.28.1-0ubuntu1.1 Kernel: 4.18.0-15-generic Architecture: amd64 CurrentDesktop: Budgie:GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1817286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896334] Re: SRU 3.36.6
I have gnome-shell 3.36.7-0ubuntu0.20.04.1 installed from focal-proposed for three weeks now and my two-monitor setup is working great. I also have the gnome-shell-extensions-gpaste (from Ubuntu universe) and the gsconnect extension (from https://extensions.gnome.org/extension/1319/gsconnect/) installed and running without any problems. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-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/1896334 Title: SRU 3.36.6 Status in gnome-shell package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Committed Status in yaru-theme source package in Focal: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/gnome-shell/-/commits/3.36.6 Since the theme side of the project in ubuntu is shipped via Yaru theme, that project is included in the SRU. The changes involving yaru here are ONLY gnome-shell upstream changes applied to the Yaru sources, as per this we can consider them also part of the GNOME release. In fact: - Ubuntu's GNOME shell uses a Yaru theme based on upstream gnome-shell This theme basically takes the shell's data/ directory, applies some diffs and generates a gresource file out of it, that it's then loaded on startup (in place of the upstream one). - GNOME Shell applied some fixes to the theme (se its data/ directory diffs) - In order to get those fixes in Ubuntu main session we have to sync the upstream changes applied to such dir to yaru's src/gnome-shell path - You can easily compare the diffs applied there to match the ones happening in its upstream counterpart. The yaru-theme's `gnome-shell/upstream` directory is just for documentation and to allow three way merges when updating to new versions of gnome-shell, and it is not used for generating the final packages at all [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been fixes in popup-grab handling, gdm view fixes, lockscreen display changes in some hw, extensions updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1896334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903764] Re: [SRU] Update gnome-shell to 3.36.7 in Focal
I have gnome-shell 3.36.7-0ubuntu0.20.04.1 installed from focal-proposed for three weeks now and my two-monitor setup is working great. I have also the gnome-shell-extensions-gpaste installed and running without any problems. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-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/1903764 Title: [SRU] Update gnome-shell to 3.36.7 in Focal Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Focal: Fix Committed Bug description: [Impact] This is the current GNOME 3.36.x stable update, including some fixes and translation updates. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix potential stack overflow in libcroco [Michael; !1404] * Fix system action search regressions [Florian; #3169] * Fix week number alignment when using font-scaling [Joonas; !1415] * Misc. bug fixes and cleanups [Bastien, Carlos, Florian, Daniel [!1444, !1451, #2230, !1423] Contributors: Michael Catanzaro, Carlos Garnacho, Joonas Henriksson, Florian Müllner, Bastien Nocera, Daniel van Vugt Translators: Marek Černocký [cs] 3.36.6 == * Fix lock screen on systems without GLSL shader support [Zephaniah; #3071] * Fix app icon scaling regression on HiDPI displays [Sebastian; !1420] Contributors: Sebastian Keller, Zephaniah E. Loss-Cutler-Hull Translators: Goran Vidović [hr], Balázs Úr [hu] 3.36.5 == * Fix extension updates when many extensions are installed [Jeremias; !1363] * Fix missing icons in on-screen keyboard [Emre; #2631, #3007] * Fix delay when showing calendar events [Sebastian; #2992] * Fix app picker regressions on small displays [Sebastian; #2234, !1375, !1378] * Fix top bar navigation when NumLock is active [Olivier; #550] * Delay login animation until wallpaper has loaded [Michael; #734996] * Revert changes that caused mispositioning in overview in multi-monitor setups [Robert; #2971] * Reset auth prompt on login screen on VT switch before fade in [Ray; #2997] * Fix stuck grab when destroying open popup menu [Florian; #3022] * Misc. bug fixes and cleanups [Florian, Carlos, Andre, Jonas; !1357, !1371, !1381, #3037, #3005, !1386, !1390] Contributors: Michael Catanzaro, Jonas Dreßler, Olivier Fourdan, Carlos Garnacho, Sebastian Keller, Robert Mader, Andre Moreira Magalhaes, Florian Müllner, Jeremias Ortega, Ray Strode, Emre Uyguroglu Translators: Boyuan Yang [zh_CN], Rafael Fontenelle [pt_BR] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. The verification is going to include checking those extensions before and after the update to ensure the SRU isn't creating regressions https://launchpadlibrarian.net/511426552/gse [Regression potential] There have been fixes in various places: system actions search in different languages, alignment of week numbers in calendar menu, lock screen, scaling of app icons on Hi-dpi displays, extension updates, missing icons in OSK and showing calendar events in calendar menu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 19:40:03 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-26 (198 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.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/1903764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911072] [NEW] LibreOffice Impress OpenGL transitions flickering only on Ubuntu Gnome
Public bug reported: When I'm using the standard Ubuntu installation with Gnome DE, LibreOffice Impress transitions that require OpenGL do not work. To reproduce the bug: 1) Create a presentation using LO Impress 2) Add an OpenGL transition (e.g. Fade In) 3) Start the presentation 4) The transition will be flickering in a very weird manner I am currently using Ubuntu 20.10 with Nvidia drivers and the gtk3 VCL plugin. However, this issue has existed since at least Ubuntu 19.10, which was when I first experienced it. This is a long-standing bug that might to be related with the way drivers/OpenGL/Gnome are set-up on Ubuntu. See the following bug report on LibreOffice's Bugzilla page: https://bugs.documentfoundation.org/show_bug.cgi?id=131610 The weirdest thing is that I also run Kubuntu 20.10 on the same machine and on Kubuntu all transitions work perfectly fine. That's why I think it may have something to do with Gnome on Ubuntu. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1911072 Title: LibreOffice Impress OpenGL transitions flickering only on Ubuntu Gnome Status in libreoffice package in Ubuntu: New Bug description: When I'm using the standard Ubuntu installation with Gnome DE, LibreOffice Impress transitions that require OpenGL do not work. To reproduce the bug: 1) Create a presentation using LO Impress 2) Add an OpenGL transition (e.g. Fade In) 3) Start the presentation 4) The transition will be flickering in a very weird manner I am currently using Ubuntu 20.10 with Nvidia drivers and the gtk3 VCL plugin. However, this issue has existed since at least Ubuntu 19.10, which was when I first experienced it. This is a long-standing bug that might to be related with the way drivers/OpenGL/Gnome are set-up on Ubuntu. See the following bug report on LibreOffice's Bugzilla page: https://bugs.documentfoundation.org/show_bug.cgi?id=131610 The weirdest thing is that I also run Kubuntu 20.10 on the same machine and on Kubuntu all transitions work perfectly fine. That's why I think it may have something to do with Gnome on Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1911072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903230] Re: Mutter release 3.36.7
I have mutter 3.36.7+git20201123-0.20.04.1 installed from focal-proposed for over two weeks now and gnome-shell, with two monitors, is running great without any problems. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1903230 Title: Mutter release 3.36.7 Status in mutter package in Ubuntu: Won't Fix Status in mutter source package in Focal: Fix Committed Bug description: We should release mutter 3.36.7 to focal, for bug 1900906, bug 1894596 and ...? [Impact] This is the current GNOME 3.36.x stable update, including some fixes (especially crashes and memory leaks) and translation updates. https://gitlab.gnome.org/GNOME/mutter/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix Night Light updates after DPMS [Jonas, Benjamin; #1392] * Fix IM handling on X11 [Carlos; #1413] * Fix resizing of attached modal dialogs on wayland [Jonas; !1446] * Fix jumps when resizing windows using discrete steps [Jonas; #1447] * Fixed crashes [Marco; !1371, #1345] * Plugged Memory leaks [Ray; !1449, !1451] * Misc. bug fixes and cleanups [Jonas, Carlos, Robert; !1218, !1460, !1463] Contributors: Marco Trevisan (Treviño), Benjamin Berg, Carlos Garnacho, Robert Mader, Ray Strode, Jonas Ådahl Translators: Juliano de Souza Camargo [pt] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. [Regression potential] There have been fixes in nightlight mode, IM handling in X11 and resizing windows in Wayland. All of those should not regress after the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
MSFT0001:00 06CB:7F28 Touchpad works with kernel but it's very difficult
to do a middle click using the default hid-i2c driver. middle click and
right click works better with i2c-hid_standalone.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
*kernel above 5.9
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
[Desktop-packages] [Bug 1880512] Re: cups apparmor profile denied sys_nice
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups-filters (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1880512 Title: cups apparmor profile denied sys_nice Status in cups-filters package in Ubuntu: Confirmed Bug description: May 24 17:02:54 dinar-comp kernel: [ 6432.118240] audit: type=1400 audit(1590328974.037:195): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=27786 comm="cups-browsed" capability=23 capname="sys_nice" this messages started to appear after upgrade ubuntu from 19.10 to 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1880512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861408] Re: firefox apparmor messages
messages, while starting firefox, after updating ubuntu to 20.10:
Jan 11 23:26:48 dinar-comp kernel: [ 181.634648] audit: type=1400
audit(1610396808.475:44): apparmor="DENIED" operation="open" profile="firefox"
name="/proc/2003/cgroup" pid=2003 comm="firefox" requested_mask="r"
denied_mask="r" fsuid=1000 ouid=1000
Jan 11 23:26:48 dinar-comp kernel: [ 181.989310] audit: type=1400
audit(1610396808.831:45): apparmor="DENIED" operation="connect"
profile="firefox" name="/tmp/.X11-unix/X0" pid=2207 comm="MainThread"
requested_mask="w" denied_mask="w" fsuid=1000 ouid=0
i added these rules:
@{PROC}/[0-9]*/cgroup r,
/tmp/.X11-unix/X0 w,
then, after enabling them and ff restart:
Jan 11 23:45:25 dinar-comp kernel: [ 1298.595946] audit: type=1400
audit(1610397925.435:79): apparmor="DENIED" operation="open"
profile="firefox" name="/sys/fs/cgroup/cpu,cpuacct/cpu.cfs_quota_us"
pid=2437 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000
ouid=0
i added this rule:
/sys/fs/cgroup/cpu,cpuacct/cpu.cfs_quota_us r,
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
Fix Released
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
[Desktop-packages] [Bug 1910792] Re: gettext 0.21-3 FTBFS on armhf
https://launchpad.net/ubuntu/+source/gettext/0.21-3ubuntu1 built successfully on armhf, but is now failing to build on i386 and riscv64 because of missing dependencies (emacs). ** Summary changed: - gettest 0.21-3 FTBFS on armhf + gettext 0.21-3 FTBFS on armhf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1910792 Title: gettext 0.21-3 FTBFS on armhf Status in gettext package in Ubuntu: In Progress Bug description: gettext 0.21-3 currently in hirsute-proposed reliably fails to build from source on armhf. I'm attaching a failed build log. This upstream commit (https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=175e0bc72808d564074c4adcc72aeadb74adfcc6) in the embedded copy of gnulib should fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1910792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908825] Re: Nvidia 340.108: Garbled graphics after resume
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1908825 Title: Nvidia 340.108: Garbled graphics after resume Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: On my Thinkpad T61 using Nvidia 340.108 driver, I regularly see graphics distortions returning from suspend. (Not completely sure if it also appears after screen lock.) See attached screen shots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1908825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910763] Re: Steam Proton fails with Kernel 5.8.0-36 Ubuntu 20.04.1
Maybe it depends on the Nvidia driver that you had before the install of the patch, but it is a supposition, I don't know, sorry. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1910763 Title: Steam Proton fails with Kernel 5.8.0-36 Ubuntu 20.04.1 Status in evince package in Ubuntu: New Bug description: Yesterday, I updated my Ubuntu 20.04.1 LTS and obtained the new official kernel (with the update) 5.8.0-36. With this kernel I have got a lot of problems with some games with Steam Proton. For example, with the Kernel 5.4.0-59 all works well, I could play Cyberpunk 2077 and Far Cry 5 without problems. Now, with the kernel 5.8.0-36 I can't play Cyberpunk 2077 and I have got low fps in some areas with Far Cry 5, obtaining for example 7-8 fps in the cinematic scene of faith. Some games doesn't start with the new kernel. Some people need this new kernel due to they have got new hardware pieces which are supported with this new kernel. Regards and thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 8 15:35:36 2021 InstallationDate: Installed on 2020-04-24 (258 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910763] Re: Steam Proton fails with Kernel 5.8.0-36 Ubuntu 20.04.1
I changed my motherboard and reinstalled Ubuntu 20.04.1 LTS and it works well with the new kernel 5.8.0-34. Maybe the problem is the update patch when you have got the system installed. I remembered that I had got problems with the Nvidia 460 Driver, but It was maybe caused due to I had got a socket of the motherboard broken and it read bad my data generating a corrupted system. But, I don't discard that the problem maybe still in the patch. With fresh reinstall It works well, but it is not a good solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1910763 Title: Steam Proton fails with Kernel 5.8.0-36 Ubuntu 20.04.1 Status in evince package in Ubuntu: New Bug description: Yesterday, I updated my Ubuntu 20.04.1 LTS and obtained the new official kernel (with the update) 5.8.0-36. With this kernel I have got a lot of problems with some games with Steam Proton. For example, with the Kernel 5.4.0-59 all works well, I could play Cyberpunk 2077 and Far Cry 5 without problems. Now, with the kernel 5.8.0-36 I can't play Cyberpunk 2077 and I have got low fps in some areas with Far Cry 5, obtaining for example 7-8 fps in the cinematic scene of faith. Some games doesn't start with the new kernel. Some people need this new kernel due to they have got new hardware pieces which are supported with this new kernel. Regards and thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 8 15:35:36 2021 InstallationDate: Installed on 2020-04-24 (258 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910455] Re: Thunar and Nautilus USB drive ejecting takes long time
the log is truncated horizontally, could you get a new one doing $ journalctl -b 0 > log the log file should have the proper formating -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1910455 Title: Thunar and Nautilus USB drive ejecting takes long time Status in nautilus package in Ubuntu: Incomplete Bug description: Every time i use PNY usb flash drive, when I am trying to eject it, even if i did not store anything, it shows message "Writing data to a device, do not disconnect". This message freezes the window for a half of a minute or so. This issue affects both Thunar and Nautilus, on both Ubuntu 20.04 and Ubuntu Studio 20.04. The similar issue is documented in the bug #1762595, but the message on the board with that bug states that anyone encountering it should file a new bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910766] Re: Problem restarting with new Kernel 5.8.0-36
I have Ubuntu 20.04.1 LTS and after upgrade to latest kernel, I got same errors as @Victor. It started by Firefox random crashes. And then my development IDE followed these crashes. And finally I was not able to restart my computer. It was staying in black screen. After doing a diagnostic check on bios, I saw that my RAM is controls are failing. I bought a new RAM and continue my life now. But still getting black screen on restart. Sorry, no evidence. Maybe its coincidence. But though worth to sharing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1910766 Title: Problem restarting with new Kernel 5.8.0-36 Status in evince package in Ubuntu: Invalid Bug description: I have installed the last Ubuntu 20.04.1 LTS update and It installed the new kernel 5.8.0-36. I have got some problems with this kernel. For example, when I reboot my PC, sometimes it doesn't start and stay in the msdos window that you watch at the beginning when you switch on the PC (It's the window that shows your motherboard, disk ready, etc). Another problems is that when I use Mozilla Firefox 84.0.2 64 bits, I have got some crashes randomly when I open a new tab (the crash is only in the new tab, not in all Firefox program). Please fix this kernel. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 8 15:40:54 2021 InstallationDate: Installed on 2020-04-24 (258 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905062] Re: Format device does nothing in nautilus
*** This bug is a duplicate of bug 1853784 *** https://bugs.launchpad.net/bugs/1853784 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1905062 Title: Format device does nothing in nautilus Status in nautilus package in Ubuntu: Confirmed Bug description: I have two different external USB hard drives attached. Each of them has just one partition. The devices/partitions are visible in nautilus on the left hand side. I want to format them, so I do a right click on the device/partition in nautilus and select "Format...". In response, NOTHING happens. It's the same thing with both partitions. My expectation would be that a window opens allowing me for different options of formatting, like file system type and encryption options. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14 Uname: Linux 5.8.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 17:53:32 2020 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.window-state' b'initial-size' b'(2225, 1216)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2020-11-14 (5 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
If this adds clarity, these messages for me appear when I switch language keyboard layout. Funny thing, is that when I switch layout, either with META-SPACE or from the panel applet, when using the laptop keyword, the layout stays the same. If I start typing from the external keyboard, the keyboard switches back to English. For example * start with keyboard layout in English * from the laptop keyboard hit META-Spacebar * the layout indicator switches to Italian layout syslog shows a series of WM warnings like `Jan 11 10:10:57 x gnome- shell[2533]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).` * type keys on the laptop internal keyboard to verify the layout is indeed Italian * then type on external keyboard * syslog shows a new series of WM warnings, identical to the previous series * the keyboard layout is now back to English, while the applet indicator is still showing Italian layout Any clue? -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) No error. 4) Error in Ubuntu Logs App. Sender: gnome-shell Message: 4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 GMT-0600 (CST) 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Audit Session: 2 Priority: 6 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910455] Re: Thunar and Nautilus USB drive ejecting takes long time
The output of the command is attached ** Attachment added: "log.txt" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910455/+attachment/5451854/+files/log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1910455 Title: Thunar and Nautilus USB drive ejecting takes long time Status in nautilus package in Ubuntu: Incomplete Bug description: Every time i use PNY usb flash drive, when I am trying to eject it, even if i did not store anything, it shows message "Writing data to a device, do not disconnect". This message freezes the window for a half of a minute or so. This issue affects both Thunar and Nautilus, on both Ubuntu 20.04 and Ubuntu Studio 20.04. The similar issue is documented in the bug #1762595, but the message on the board with that bug states that anyone encountering it should file a new bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911036] [NEW] GDK/GTK app crash when performing drag operation
Public bug reported: For many months now, whenever any mouse drag is attempted in an application using the gtk tool kit, the application immediately crashes. I've noticed this at least in Firefox and thunar. It also occurs when displaying these applications from a Virtualbox machine or from another server running something other than Ubuntu. The VM was running CentOS 8 and the remote server was running Mageia. Both Firefox and thunar run fine with Mageia's Xorg. It seems like the issue may be with the Xorg server on Ubuntu. I tried setting the GDK_SYNCHRONIZE variable to various settings but was unable to produce further debug output. The only other debug output I was able to gather is when running thunar with the --gtk-debug parameter (attached). I also tried running thunar with GDB but without recompiling it, it doesn't produce much information other than it's stopping in glib. Let me know what other information I can provide. (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ExceptionHandler::GenerateDump cloned child 110611 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. [1]+ Trace/breakpoint trap (core dumped) firefox (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) $ ldd /bin/thunar linux-vdso.so.1 (0x7ffc0c8cc000) libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 (0x7fdbb548c000) libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 (0x7fdbb544f000) libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 (0x7fdbb5442000) libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 (0x7fdbb5437000) libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000) libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000) libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 (0x7fdbb53f3000) libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 (0x7fdbb4c42000) libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 (0x7fdbb4b3d000) libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x7fdbb4b13000) libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 (0x7fdbb49f) libgdk_pixbuf-2.0.so.0 => /lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000) libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 (0x7fdbb49b4000) libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 (0x7fdbb4996000) libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x7fdbb4947000) libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x7fdbb4766000) libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7fdbb4706000) libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7fdbb45dd000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdbb43e9000) libgmodule-2.0.so.0 => /lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x7fdbb43e3000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fdbb4294000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fdbb4271000) libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7fdbb4244000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fdbb4239000) libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x7fdbb421f000) libX11.so.6 => /lib/x86_64-linux-gnu/libX11.so.6 (0x7fdbb40e2000) libstartup-notification-1.so.0 =>
[Desktop-packages] [Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display
Johan and also iMac, thank you... I was trying to see whether this issue correlated with the type of cable between the dock and the external display; but obviously not since we're seeing it with both HDMI and DP. I'm not suggesting that a particular item such as the Dropbox app, Logitech USB driver, etc is the cause; but I'm hoping that these observations may help those of you who are trying to reproduce the issue to do so. My background is application programming, not system; so I can offer anecdotal observations and check logs but am not able to dive into the code. I do urge those of you who can to do so. This is once again progressing. This morning (and after having allowed the kernel update to 5.8.0.36.40 just a couple days ago), the system *froze* rather than going to sleep. First I lost the external display. So I opened the laptop lid (docked) and had a bizarre set of 3 or 4 error messages. Those cleared to solid black before I could get a pic. I couldn't get any response after that so had to do a hard power down. Not good! I brought the machine up standalone, let it idle a few minutes, shut it down, and put it back into the dock. Then it was back to this bug's suspend after login. This again is Ubuntu 20.04.1, now the kernel just noted, on a T570 in the classic UltraDock using an external HDMI display, external Lenovo USB keyboard, and Logitech *bluetooth* mouse. Lid closed so external display is primary. Note that the Lenovo USB mouse has developed serious scroll wheel issues: I'm not yet sure whether that is Ubuntu or hardware. My overriding concern is that Ubuntu remains unstable at best since the mid September updates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1841826 Title: Going to sleep instead of logging in while lid closed & external display Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have the above described problem, which seems to be very similar to bug #1716160 - laptop is in docking station and 2 monitors are connected (HDMI, DVI) - If the lid is closed and I boot the laptop I can input my credentials in the login screen and after hitting ENTER the laptop goes to sleep - If I then press the power button of the docking station the laptop wakes up and goes straight to the ubuntu environment w/o any user identification The device is a Lenovo T420 with classic docking station. Ubuntu 18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior independent of the graphics used. I do not know what to do now since the latest state of bug #1716160 is "fix released" and so I guess it should be part of the ubuntu version I use? Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 20:10:15 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'show-battery-percentage' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-08-13 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901580] Re: Ubuntu 20.10 doesn't include the latest version of Rygel
https://bugs.launchpad.net/ubuntu/+source/rygel/0.40.0-1 ** Changed in: rygel (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rygel in Ubuntu. https://bugs.launchpad.net/bugs/1901580 Title: Ubuntu 20.10 doesn't include the latest version of Rygel Status in rygel package in Ubuntu: Fix Released Bug description: The new Ubuntu release advertises GNOME 3.38. IIUC, GNOME 3.38 should come with Rygel 0.40.0: https://download.gnome.org/core/3.38/3.38.0/NEWS Rygel 0.38.3 is pretty out of date, 0.39.1 (released in July) contains a number of important fixes. As an aside, at least a couple of bug reports here on launchpad should already be marked as fixed. Hirsute also still comes with 0.38.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rygel/+bug/1901580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
I'm confused. Isn't 5.8 line officially available? https://ubuntu.pkgs.org/20.04/ubuntu-updates-main-arm64/linux- image-5.8.0-36-generic_5.8.0-36.40~20.04.1_arm64.deb.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911030] Re: graphical flashes on a raspi 4
** Attachment added: "Video of the issue" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1911030/+attachment/5451810/+files/20210111_164733.mp4 -- 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/1911030 Title: graphical flashes on a raspi 4 Status in xorg package in Ubuntu: New Bug description: Using gnome-shell - activities - see attached video Graphics flash - more prominent with more than one app running. If you install ubuntu-budgie-desktop and simply move through the menu categories the flashing is even more prominent. I'm guessing this is xorg related - but I do note the recent mesa uplift has made things worse ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu55 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 16:49:14 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ImageMediaBuild: 20201225 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1911030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911030] [NEW] graphical flashes on a raspi 4
Public bug reported: Using gnome-shell - activities - see attached video Graphics flash - more prominent with more than one app running. If you install ubuntu-budgie-desktop and simply move through the menu categories the flashing is even more prominent. I'm guessing this is xorg related - but I do note the recent mesa uplift has made things worse ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu55 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 16:49:14 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ImageMediaBuild: 20201225 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 hirsute reproducible single-occurrence 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/1911030 Title: graphical flashes on a raspi 4 Status in xorg package in Ubuntu: New Bug description: Using gnome-shell - activities - see attached video Graphics flash - more prominent with more than one app running. If you install ubuntu-budgie-desktop and simply move through the menu categories the flashing is even more prominent. I'm guessing this is xorg related - but I do note the recent mesa uplift has made things worse ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-1011.14+21.04.1-raspi 5.8.18 Uname: Linux 5.8.0-1011-raspi aarch64 ApportVersion: 2.20.11-0ubuntu55 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 16:49:14 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: ImageMediaBuild: 20201225 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:640x480M@60 smsc95xx.macaddr=DC:A6:32:D1:3E:28 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.103-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1911030/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911024] [NEW] segfault crash after fresh restart
Public bug reported: segfault not located in a known VMA region (needed readable region)! destination rdi ok ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 Uname: Linux 5.10.4-051004-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 15:52:40 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-30 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.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/1911024 Title: segfault crash after fresh restart Status in gnome-shell package in Ubuntu: New Bug description: segfault not located in a known VMA region (needed readable region)! destination rdi ok ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 Uname: Linux 5.10.4-051004-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jan 11 15:52:40 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-12-30 (12 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.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/1911024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886092] Re: libreoffice doesn't list gpg private key for a digital signature due to apparmor
I just wanted to add that I had this issue for a while too on Ubuntu
20.04.1 LTS. None of the above solutions worked for me but what did work
was installing and using gnupg2.
Then edit /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin to use
gpg2 instead of gpg. So I edit the line /usr/bin/gpg rm to /usr/bin/gpg2
like below:
# there is abstractions/gnupg but that's just for gpg1...
profile gpg {
#include
/usr/bin/gpgconf rm,
/usr/bin/gpg2 rm,
/usr/bin/gpgsm rm,
owner @{HOME}/.gnupg/* r,
owner @{HOME}/.gnupg/random_seed rk,
}
# probably should become a subprofile like gpg above, but then it doesn't
# work either as it tries to access stuff only allowed above...
I hope this works for others too! My key generation took a while but it worked.
--
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/1886092
Title:
libreoffice doesn't list gpg private key for a digital signature due
to apparmor
Status in libreoffice package in Ubuntu:
Confirmed
Status in libreoffice source package in Focal:
Confirmed
Bug description:
LibreOffice should be able to digitally sign a document with a GPG
private key in the GPG key chain. However, the key is not listed in
the list of certificates shown following the menu File - Digital
Signatures - Digital Signatures... - Sign Document..., after, e.g.,
creating and saving a document on LibreOffice Writer.
This seems to be because apparmor doesn't allow LibreOffice to
communicate with GPG agent. /var/log/syslog shows lines like:
Jul 1 15:15:14 misoan kernel: [20238.265212] audit: type=1400
audit(1593652514.311:333): apparmor="DENIED" operation="connect"
profile="libreoffice-soffice//gpg" name="/run/user/1001/gnupg/S.gpg-
agent" pid=23725 comm="gpg" requested_mask="wr" denied_mask="wr"
fsuid=1001 ouid=1001
Locally, I could make LibreOffice show the GPG private key with the
following change against
/etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin
--- apparmor.d.20200702/usr.lib.libreoffice.program.soffice.bin
2019-10-03 10:31:21.0 -1000
+++ apparmor.d/usr.lib.libreoffice.program.soffice.bin2020-07-02
08:59:44.516754728 -1000
@@ -223,6 +223,7 @@
owner @{HOME}/.gnupg/* r,
owner @{HOME}/.gnupg/random_seed rk,
+owner /{,var/}run/user/*/** rw,
}
# probably should become a subprofile like gpg above, but then it doesn't
Tested with the following packages on Xfce4
$ lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04
$ apt-cache policy libreoffice-common | grep Installed
Installed: 1:6.4.3-0ubuntu0.20.04.1
$ apt-cache policy gpg gpg-agent | grep -B1 Installed
gpg:
Installed: 2.2.19-3ubuntu2
--
gpg-agent:
Installed: 2.2.19-3ubuntu2
$ apt-cache policy apparmor | grep Installed
Installed: 2.13.3-7ubuntu5.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1886092/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910694] Re: When saving a text file with Ctrl + S, gedit enables "Highlight current line" on its own
My Language preferences are set in this order: 1. British English (Default) 2. American English For keyboard layouts i have English (US) and Bulgarian (traditional phonetic), but usually use the English as active. For formats i have the bg_BG setting selected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1910694 Title: When saving a text file with Ctrl + S, gedit enables "Highlight current line" on its own Status in gedit package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Have some text file opened in gedit 2. Disable "Highlight current line" 3. Press Ctrl + S to save changes 4. Notice the "Highlight current line" is now enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-59.65-lowlatency 5.4.78 Uname: Linux 5.4.0-59-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 11:27:13 2021 InstallationDate: Installed on 2020-12-27 (11 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1910694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
I found the reason why the warning is displayed. It has to do with Dash- to-Dock and the keyboard shortcuts. You can install the dconf-editor, then navigate to "/org/gnome/shell/extensions/dash-to-dock/" and search for "hot-keys", "hotkeys-overlay" and "hotkeys-show-dock". Then disable the options. Now the message no longer appears. -- 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/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) No error. 4) Error in Ubuntu Logs App. Sender: gnome-shell Message: 4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 GMT-0600 (CST) 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Audit Session: 2 Priority: 6 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
Perhaps the fix is not yet considered 'stable' enough to be pushed to LTS. Just guessing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Desktop-packages] [Bug 1909941] Re: xdg-email changes break simple-scan email functionality
Hi, There are new version of this package in security-proposed [1] with the patch/update reverted, feel free to test it/check if the functionality is back. thanks [1]https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/+packages?field.name_filter=xdg- utils_filter=published_filter= -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality Status in xdg-utils package in Ubuntu: Confirmed Bug description: Observed on 16.04 to 20.04 xdg-email no longer actions "-attach filename" arguments when running thunderbird following recent security fixes to protect against malicious use from browser ( https://security-tracker.debian.org/tracker/CVE-2020-27748 and https://ubuntu.com/security/CVE-2020-27748 ) This breaks simple-scan "send by email" functionality and other applications too. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/216 https://forums.linuxmint.com/viewtopic.php?f=208=336053 https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/28 (see comments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
I can confirm that there is not yet a new 'nvidia-340' in focal-proposed. Looking at the changelogs this *should* be a very simple case of backporting existing gutsy-updates source to focal just naming it .20.04.1 on the end instead of 20.10.2, in short. I think this needs to be done promptly as affecting existing LTS desktop users with hwe metapackages installed! Would be nice to see patch support also k5.10 which is already packaged in debian, and provided in various 3rd-party-isos, but not if holding up immediate nvidia-340 update. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
That is, it updated to 5.8 line automatically during an apt update/apt upgrade. That said, is there a way to revert to version 5.4 line? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
That's weird. I have no sources that could provide a kernel. I'm attaching my sources.list. See these excerpts of dpkg.log: 2021-01-04 12:05:31 install linux-image-5.4.0-59-generic:amd64 5.4.0-59.65 2021-01-04 12:05:31 status half-installed linux-image-5.4.0-59-generic:amd64 5.4.0-59.65 2021-01-04 12:05:32 status unpacked linux-image-5.4.0-59-generic:amd64 5.4.0-59.65 ... 2021-01-07 06:33:17 install linux-image-5.8.0-34-generic:amd64 5.8.0-34.37~20.04.2 2021-01-07 06:33:17 status half-installed linux-image-5.8.0-34-generic:amd64 5.8.0-34.37~20.04.2 2021-01-07 06:33:17 status unpacked linux-image-5.8.0-34-generic:amd64 5.8.0-34.37~20.04.2 ... 2021-01-09 12:02:45 install linux-image-5.8.0-36-generic:amd64 5.8.0-36.40~20.04.1 2021-01-09 12:02:45 status half-installed linux-image-5.8.0-36-generic:amd64 5.8.0-36.40~20.04.1 2021-01-09 12:02:45 status unpacked linux-image-5.8.0-36-generic:amd64 5.8.0-36.40~20.04.1 ** Attachment added: "sources.list" https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+attachment/5451774/+files/sources.list -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 783914] Re: xdg-open ignores $BROWSER
** Changed in: xdg-utils (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/783914 Title: xdg-open ignores $BROWSER Status in xdg-utils package in Ubuntu: Confirmed Bug description: Binary package hint: xdg-utils This is on Ubuntu 11.04. xdg-open seems to be ignoring the BROWSER enviroment variable. If i'm not wrong, is using gnome-open, and i cannot configure gnome-open to use w3m, which is the browser i want to use. Wouldn't be best to honor the BROWSER variable? xdg-open should have a consistent behaviour and not change between desktops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/783914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910598] Re: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it.
Thank you for the bug report, could you add the 'journalctl -b ' from the session where you had the issue? It's unlikely that udisks wrote to disk though ** Changed in: udisks2 (Ubuntu) Importance: Undecided => Low ** Changed in: udisks2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1910598 Title: Ejecting a Blanc CD/DVD/BluRay-R disk writes to it. Status in caja package in Ubuntu: New Status in udisks2 package in Ubuntu: Incomplete Bug description: I used the "eject" contextual menu on the icon of a blank Bluray-R on the caja desktop, and I got a message saying that I need to wait for data to be written on the disc before being able to remove it safely (same message as when trying to eject an usb stick, when some data syncing is left to be done). Afterwards, when I tried to burn data to it, the app (k3b) told that the disc was not empty thus not writeable. This bug cost me a brand new Bluray-R M-Disc of 100GB, which is a quite pricey medium. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: caja 1.20.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-129.132-generic 4.15.18 Uname: Linux 4.15.0-129-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jan 7 22:42:25 2021 SourcePackage: caja UpgradeStatus: Upgraded to bionic on 2019-02-16 (691 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1910598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910455] Re: Thunar and Nautilus USB drive ejecting takes long time
Thank you for the bug report, could you include the log from 'journalctl -b 0' after triggering the issue? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1910455 Title: Thunar and Nautilus USB drive ejecting takes long time Status in nautilus package in Ubuntu: Incomplete Bug description: Every time i use PNY usb flash drive, when I am trying to eject it, even if i did not store anything, it shows message "Writing data to a device, do not disconnect". This message freezes the window for a half of a minute or so. This issue affects both Thunar and Nautilus, on both Ubuntu 20.04 and Ubuntu Studio 20.04. The similar issue is documented in the bug #1762595, but the message on the board with that bug states that anyone encountering it should file a new bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909941] Re: xdg-email changes break simple-scan email functionality
I'll revert that patch/update and issue a new one asap. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1909941 Title: xdg-email changes break simple-scan email functionality Status in xdg-utils package in Ubuntu: Confirmed Bug description: Observed on 16.04 to 20.04 xdg-email no longer actions "-attach filename" arguments when running thunderbird following recent security fixes to protect against malicious use from browser ( https://security-tracker.debian.org/tracker/CVE-2020-27748 and https://ubuntu.com/security/CVE-2020-27748 ) This breaks simple-scan "send by email" functionality and other applications too. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/216 https://forums.linuxmint.com/viewtopic.php?f=208=336053 https://gitlab.freedesktop.org/xdg/xdg-utils/-/merge_requests/28 (see comments) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/1909941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910174] Re: nautilus is slow to start
Thank you for your bug report, what's the output of this command on your system? $ dpkg -l | grep nautilus ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1910174 Title: nautilus is slow to start Status in nautilus package in Ubuntu: Incomplete Bug description: I don' t know the reason. My nautilus and gnome-tweak became slow to start. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jan 5 11:40:46 2021 InstallationDate: Installed on 2019-05-06 (610 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-11-25 (40 days ago) usr_lib_nautilus: synology-drive 6.0.2-11078 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1910174/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910694] Re: When saving a text file with Ctrl + S, gedit enables "Highlight current line" on its own
Thank you for the bug report, which locale and keyboard layout do you use? ** Changed in: gedit (Ubuntu) Importance: Undecided => Low ** Changed in: gedit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1910694 Title: When saving a text file with Ctrl + S, gedit enables "Highlight current line" on its own Status in gedit package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Have some text file opened in gedit 2. Disable "Highlight current line" 3. Press Ctrl + S to save changes 4. Notice the "Highlight current line" is now enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-59.65-lowlatency 5.4.78 Uname: Linux 5.4.0-59-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 8 11:27:13 2021 InstallationDate: Installed on 2020-12-27 (11 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1910694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910838] Re: stopped working after latest update
** Tags added: rls-ff-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1910838 Title: stopped working after latest update Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: dec 16 the following updates were installed after which gnome-shell- extension-appindicator stopped working as expected: apport (2.20.11-0ubuntu27.13) to 2.20.11-0ubuntu27.14 apport-gtk (2.20.11-0ubuntu27.13) to 2.20.11-0ubuntu27.14 firefox (83.0+build2-0ubuntu0.20.04.1) to 84.0+build3-0ubuntu0.20.04.1 firefox-locale-en (83.0+build2-0ubuntu0.20.04.1) to 84.0+build3-0ubuntu0.20.04.1 gir1.2-gnomedesktop-3.0 (3.36.3.1-0ubuntu1) to 3.36.8-0ubuntu1 gnome-desktop3-data (3.36.3.1-0ubuntu1) to 3.36.8-0ubuntu1 gnome-shell-extension-appindicator (33-1) to 33.1-0ubuntu0.20.04.1 gnome-system-monitor (3.36.0-1) to 3.36.1-0ubuntu0.20.04.1 imagemagick (8:6.9.10.23+dfsg-2.1ubuntu11.1) to 8:6.9.10.23+dfsg-2.1ubuntu11.2 imagemagick-6-common (8:6.9.10.23+dfsg-2.1ubuntu11.1) to 8:6.9.10.23+dfsg-2.1ubuntu11.2 imagemagick-6.q16 (8:6.9.10.23+dfsg-2.1ubuntu11.1) to 8:6.9.10.23+dfsg-2.1ubuntu11.2 libevdev2 (1.9.0+dfsg-1) to 1.9.0+dfsg-1ubuntu0.1 libgnome-desktop-3-19 (3.36.3.1-0ubuntu1) to 3.36.8-0ubuntu1 libinput-bin (1.15.5-1ubuntu0.1) to 1.15.5-1ubuntu0.2 libinput10 (1.15.5-1ubuntu0.1) to 1.15.5-1ubuntu0.2 libmagickcore-6.q16-6 (8:6.9.10.23+dfsg-2.1ubuntu11.1) to 8:6.9.10.23+dfsg-2.1ubuntu11.2 libmagickcore-6.q16-6-extra (8:6.9.10.23+dfsg-2.1ubuntu11.1) to 8:6.9.10.23+dfsg-2.1ubuntu11.2 libmagickwand-6.q16-6 (8:6.9.10.23+dfsg-2.1ubuntu11.1) to 8:6.9.10.23+dfsg-2.1ubuntu11.2 libwhoopsie0 (0.2.69ubuntu0.1) to 0.2.69ubuntu0.2 python3-apport (2.20.11-0ubuntu27.13) to 2.20.11-0ubuntu27.14 python3-problem-report (2.20.11-0ubuntu27.13) to 2.20.11-0ubuntu27.14 whoopsie (0.2.69ubuntu0.1) to 0.2.69ubuntu0.2 ever since this update, the HP printer driver applet (hplip-systray) reports: "No system tray detected on this system. Unable to start, exiting." this used to work before dec. 16 gnome-tweak-tool indicates that is loaded, so not sure what's going on here (have the same problem also on another ubuntu-machine) thanks, Daniel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jan 8 21:31:13 2021 InstallationDate: Installed on 2019-09-04 (492 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to focal on 2020-05-03 (251 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1910838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910877] Re: DejaDup does not display an icon in the panel
That's not a bug in deja-dup if the desktop isn't listing active applications ** Changed in: deja-dup (Ubuntu) Status: New => Invalid ** Changed in: deja-dup (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1910877 Title: DejaDup does not display an icon in the panel Status in Ubuntu MATE: New Status in deja-dup package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: New Bug description: When DejaDup is performing a backup, there is no icon in the panel on Ubuntu Mate 20.04. (There is in 18.04). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1910877/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910879] Re: Sound output settings do not update
Thank you for your bug report, could you perhaps report it directly upstream as well on https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues ? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1910879 Title: Sound output settings do not update Status in gnome-control-center package in Ubuntu: New Bug description: I have several possible sound outputs, and some require a configuration but when I select one and then choose the configuration (ie Analog surround 7.1) the sliders are not displayed until I close the window and open it again. At this moment the sliders for left/right, front/back balance are correctly displayed, but they were not displayed at first. The test button opens the correct test window though ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 10 00:59:29 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-05-25 (229 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to groovy on 2020-11-01 (69 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1910879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910763] Re: Steam Proton fails with Kernel 5.8.0-36 Ubuntu 20.04.1
Also affects me, I don't have any motherboard problems . .. ** Changed in: evince (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1910763 Title: Steam Proton fails with Kernel 5.8.0-36 Ubuntu 20.04.1 Status in evince package in Ubuntu: New Bug description: Yesterday, I updated my Ubuntu 20.04.1 LTS and obtained the new official kernel (with the update) 5.8.0-36. With this kernel I have got a lot of problems with some games with Steam Proton. For example, with the Kernel 5.4.0-59 all works well, I could play Cyberpunk 2077 and Far Cry 5 without problems. Now, with the kernel 5.8.0-36 I can't play Cyberpunk 2077 and I have got low fps in some areas with Far Cry 5, obtaining for example 7-8 fps in the cinematic scene of faith. Some games doesn't start with the new kernel. Some people need this new kernel due to they have got new hardware pieces which are supported with this new kernel. Regards and thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 8 15:35:36 2021 InstallationDate: Installed on 2020-04-24 (258 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
Thank you for the bug report, where did you get the kernel from? The focal serie doesn't have 5.8 available neither in standard nor as an upgrade -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910994] Re: autopkgtest fails frequently in groovy on armhf
** Merge proposal linked: https://code.launchpad.net/~rbalint/britney/+git/hints-ubuntu/+merge/396070 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1910994 Title: autopkgtest fails frequently in groovy on armhf Status in snapd-glib package in Ubuntu: New Bug description: https://autopkgtest.ubuntu.com/packages/s/snapd-glib/groovy/armhf https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/armhf/s/snapd- glib/20210110_213607_6d4d0@/log.gz ... Executing: snapd-glib/test-qt.test Test timed out after 300 seconds FAIL: snapd-glib/test-qt.test (Child process killed by signal 9) Running test: snapd-glib/test-markdown-qt.test # random seed: R02S8929c6fbcee911211dcbe25b8160bc06 1..13 # Start of markdown tests ... Reproduction in Canonistack with lxd shows no sigificant difference in run time when testing with and without glibc from -proposed. I assume the timeouts are results of the CI infrastructure running other tests in parallel on the same HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1910994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910994] [NEW] autopkgtest fails frequently in groovy on armhf
Public bug reported: https://autopkgtest.ubuntu.com/packages/s/snapd-glib/groovy/armhf https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/armhf/s/snapd- glib/20210110_213607_6d4d0@/log.gz ... Executing: snapd-glib/test-qt.test Test timed out after 300 seconds FAIL: snapd-glib/test-qt.test (Child process killed by signal 9) Running test: snapd-glib/test-markdown-qt.test # random seed: R02S8929c6fbcee911211dcbe25b8160bc06 1..13 # Start of markdown tests ... Reproduction in Canonistack with lxd shows no sigificant difference in run time when testing with and without glibc from -proposed. I assume the timeouts are results of the CI infrastructure running other tests in parallel on the same HW. ** Affects: snapd-glib (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to snapd-glib in Ubuntu. https://bugs.launchpad.net/bugs/1910994 Title: autopkgtest fails frequently in groovy on armhf Status in snapd-glib package in Ubuntu: New Bug description: https://autopkgtest.ubuntu.com/packages/s/snapd-glib/groovy/armhf https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/armhf/s/snapd- glib/20210110_213607_6d4d0@/log.gz ... Executing: snapd-glib/test-qt.test Test timed out after 300 seconds FAIL: snapd-glib/test-qt.test (Child process killed by signal 9) Running test: snapd-glib/test-markdown-qt.test # random seed: R02S8929c6fbcee911211dcbe25b8160bc06 1..13 # Start of markdown tests ... Reproduction in Canonistack with lxd shows no sigificant difference in run time when testing with and without glibc from -proposed. I assume the timeouts are results of the CI infrastructure running other tests in parallel on the same HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1910994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906539] Re: tex-common fails to configure in hirsute-proposed
** Changed in: tex-common (Ubuntu) Status: Incomplete => Invalid ** Changed in: tex-common (Ubuntu) Assignee: Sebastien Bacher (seb128) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1906539 Title: tex-common fails to configure in hirsute-proposed Status in tex-common package in Ubuntu: Invalid Bug description: tex-common fails to configure in hirsute-proposed: Setting up sbuild-build-depends-gcc-10-dummy (0.invalid.0) ... Processing triggers for tex-common (6.15) ... Running updmap-sys. This may take some time... done. Running mktexlsr /var/lib/texmf ... done. Building format(s) --all. This may take some time... fmtutil failed. Output has been stored in /tmp/fmtutil.a8TypC2W Please include this file if you report a bug. dpkg: error processing package tex-common (--configure): installed tex-common package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: tex-common E: Sub-process /usr/bin/dpkg returned an error code (1) apt-get failed. Package installation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1906539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908469] Re: Cannot install .deb packages opened from Firefox
The snap store as a snap isn't going to have access to the share /tmp so that would be an issue yes -- 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/1908469 Title: Cannot install .deb packages opened from Firefox Status in firefox package in Ubuntu: Confirmed Bug description: Suppose in Firefox you click a link to a .deb package. A dialog named "Opening [filename].deb" opens. If you select "Open with", then the .deb file is downloaded, placed in /tmp/mozilla_[username]0/ directory, then Software Install (as named in the Firefox dialog) is started on that .deb file. Next, Software Install loads and fails with "Failed to install file: not supported". If on the other hand, in Firefox's "Opening [filename].deb" dialog, if I select "Save File" instead, the .deb file ends up in the user's Downloads directory. Software Install works fine with the package there. I don't want to get too much into solutioning or "why". The main point of this bug is that I should not get a weird error just because I selected "Open with" instead of "Save File". This happens with a vanilla install of Ubuntu, with nothing else installed, so the product isn't working in an intuitive way. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 16 19:54:01 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-12-10 (6 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1908469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909621] Re: my gnome control center is not opeaning and working
Thank you for your bug report, what happens exactly, do you get an error? Does it close after starting? Could you start it from a command line and show the output? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1909621 Title: my gnome control center is not opeaning and working Status in gnome-control-center package in Ubuntu: Incomplete Bug description: i cannot access the control setting of ubantu 20 when i start this i cant open settings ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 30 09:23:13 2020 InstallationDate: Installed on 2020-10-29 (61 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN 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/1909621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910763] Re: Steam Proton fails with Kernel 5.8.0-36 Ubuntu 20.04.1
thanks closing the bug now ** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1910763 Title: Steam Proton fails with Kernel 5.8.0-36 Ubuntu 20.04.1 Status in evince package in Ubuntu: Invalid Bug description: Yesterday, I updated my Ubuntu 20.04.1 LTS and obtained the new official kernel (with the update) 5.8.0-36. With this kernel I have got a lot of problems with some games with Steam Proton. For example, with the Kernel 5.4.0-59 all works well, I could play Cyberpunk 2077 and Far Cry 5 without problems. Now, with the kernel 5.8.0-36 I can't play Cyberpunk 2077 and I have got low fps in some areas with Far Cry 5, obtaining for example 7-8 fps in the cinematic scene of faith. Some games doesn't start with the new kernel. Some people need this new kernel due to they have got new hardware pieces which are supported with this new kernel. Regards and thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 8 15:35:36 2021 InstallationDate: Installed on 2020-04-24 (258 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910763/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910766] Re: Problem restarting with new Kernel 5.8.0-36
** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1910766 Title: Problem restarting with new Kernel 5.8.0-36 Status in evince package in Ubuntu: Invalid Bug description: I have installed the last Ubuntu 20.04.1 LTS update and It installed the new kernel 5.8.0-36. I have got some problems with this kernel. For example, when I reboot my PC, sometimes it doesn't start and stay in the msdos window that you watch at the beginning when you switch on the PC (It's the window that shows your motherboard, disk ready, etc). Another problems is that when I use Mozilla Firefox 84.0.2 64 bits, I have got some crashes randomly when I open a new tab (the crash is only in the new tab, not in all Firefox program). Please fix this kernel. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 8 15:40:54 2021 InstallationDate: Installed on 2020-04-24 (258 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1910766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1267442] Re: Install nvidia-331 on X/K/Lubuntu results in unbootable machine
** Changed in: nvidia-prime (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1267442 Title: Install nvidia-331 on X/K/Lubuntu results in unbootable machine Status in nvidia-prime package in Ubuntu: Invalid Bug description: Install of nvidia-331 completes, assuming it edits lightdm.conf left with this - not any use if you're not using Ubuntu greeter-session=unity-greeter user-session=ubuntu display-setup-script=/sbin/prime-offload display-stopped-script=/sbin/prime-switch have to comment out the exisiting greeter and user session lines and replace with display-setup-script=/sbin/prime-offload display-stopped-script=/sbin/prime-switch user-session=xubuntu greeter-session=lightdm-gtk-greeter to get a satisfactory boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1267442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1526566] Re: xdg-open truncates URLs at the first '&'
** Changed in: xdg-utils (Ubuntu) Importance: Medium => Low ** Changed in: xdg-utils (Ubuntu) Status: Incomplete => New ** Changed in: xdg-utils (Ubuntu) Status: New => Incomplete ** Changed in: xdg-utils (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/1526566 Title: xdg-open truncates URLs at the first '&' Status in launchpadlib : Invalid Status in Xdg-utils: Confirmed Status in xdg-utils package in Ubuntu: Invalid Bug description: $ xdg-open 'http://example.com/?foo' Expected behavior: that URL opens in my browser Actual behavior: browser opens 'http://example.com/?foo' To manage notifications about this bug go to: https://bugs.launchpad.net/launchpadlib/+bug/1526566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1130137] Re: Better sound settings icons
There is an audio-headphones icon in the yaru theme now ** Changed in: adwaita-icon-theme (Ubuntu) Status: In Progress => Triaged ** Changed in: adwaita-icon-theme (Ubuntu) Importance: High => Low -- 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/1130137 Title: Better sound settings icons Status in gnome-control-center: Confirmed Status in adwaita-icon-theme package in Ubuntu: Triaged Status in gnome-control-center package in Ubuntu: Invalid Bug description: It would be nice to have speaker, headphone and mic icons instead of just the audio-card icon shown in Sound Settings today. We need the following things: * PulseAudio 3.0 [Check, released in Raring] * Gnome-control-center patch: [here: http://bazaar.launchpad.net/~diwic/gnome-control-center/new-icons/revision/543] * An audio-speaker icon [Needs to move from gnome-icon-theme-full to gnome-icon-theme] * An audio-headphones icon [Missing, there is one in oxygen-icon-theme though, but not sure if we can use it?] * An audio-handsfree icon [Missing] One possibility could be to do a symlink between audio-headphones and audio-handsfree to the audio-headset icon, if we don't get any new icons. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1130137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897754] Re: flameshot: The icon does not appear in the GNOME bar
On my ubuntu 20.04, the bug affects nextcloud desktop client, the seafile desktop client and the Rocket.Chat desktop app. Downgrading to 33-1 fixes the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1897754 Title: flameshot: The icon does not appear in the GNOME bar Status in flameshot package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: https://github.com/flameshot-org/flameshot/issues/1009 --- When upgrading from gnome-shell-extension-appindicator_33-3_all.deb to gnome-shell-extension-appindicator_34-1_all.deb the icon does not appear in the GNOME toolbar. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: flameshot 0.8.1-1 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 29 11:55:57 2020 InstallationDate: Installed on 2020-06-19 (102 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200609) SourcePackage: flameshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flameshot/+bug/1897754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
** Description changed: Description: Ubuntu 20.04.1 LTS Release: 20.04 + Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 + 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux + usb-modeswitch: - Installed: 2.5.2+repack0-2ubuntu3 - Candidate: 2.5.2+repack0-2ubuntu3 - Version table: - *** 2.5.2+repack0-2ubuntu3 500 - 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 2.5.2+repack0-2ubuntu3 + Candidate: 2.5.2+repack0-2ubuntu3 + Version table: + *** 2.5.2+repack0-2ubuntu3 500 + 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages + 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Linux ubuntu-dev 5.8.0-36-generic #40~20.04.1-Ubuntu SMP Wed Jan 6 10:15:55 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
As far as I can see from another (now closed) bug report, this has been sorted out for Ubuntu 20.10, also on Kernel 5.8. I guess we just have to be patient and the solution will be back-ported. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Desktop-packages] [Bug 1910982] Re: ZTE Modem USB stick not recognized with kernel 5.8
** Attachment added: "kernel 5.8 syslog" https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+attachment/5451735/+files/5.8-syslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910982] [NEW] ZTE Modem USB stick not recognized with kernel 5.8
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! ** Affects: usb-modeswitch (Ubuntu) Importance: Undecided Status: New ** Attachment added: "kernel 5.4 syslog" https://bugs.launchpad.net/bugs/1910982/+attachment/5451734/+files/5.4-syslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1910982 Title: ZTE Modem USB stick not recognized with kernel 5.8 Status in usb-modeswitch package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 usb-modeswitch: Installed: 2.5.2+repack0-2ubuntu3 Candidate: 2.5.2+repack0-2ubuntu3 Version table: *** 2.5.2+repack0-2ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ZTE Modem USB stick is not recognized with kernel 5.8. It works fine with kernel 5.4. Other versions not tested. 5.8 syslog shows: Jan 11 07:58:54 ubuntu-dev usb_modeswitch_dispatcher[2915]: Unable to open bind list file: No such file or directory Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: add device ID 19d2:1589 to driver option Jan 11 07:58:54 ubuntu-dev usb_modeswitch[2915]: usb_modeswitch: please report the device ID to the Linux USB developers! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1910982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 427168] Re: usb keyboard settings (repeat rate and delay) reset on plugin
I have opened a new bug here: https://bugs.launchpad.net/ubuntu/+source /gnome-settings-daemon/+bug/1910981 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/427168 Title: usb keyboard settings (repeat rate and delay) reset on plugin Status in GNOME Settings Daemon: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: I like a fairly fast repeat rate and low delay when typing. In the course of using my laptop (Dell Vostro 1500), I sometimes plug in a USB keyboard. Every time I do this, I notice that the repeat rate and delay on the USB keyboard are way slow and high, while the built-in keyboard repeat rate and delay are as I like them (fast and low). To fix this, every time I plug in the USB keyboard, I have to go to System→Preferences→Keyboard, slightly move the Speed slider, then Close the dialog. (Note that the sliders haven't changed from the last invocation of this application, just that the settings apparently need to be reapplied internally.) I believe that at least these keyboard settings (repeat rate and delay) should be universal for all keyboards. Repeatable: always. How to reproduce: 1. plug in a USB keyboard 2. Note current repeat-rate and delay. 3. Change repeat-rate and delay via System->Preferences->Keyboard 4. Unplug and re-plugin the USB keyboard. 5. Return to step 2. Possibly related bugs: Bug #295990 Bug #426176 $ uname -a Linux hani 2.6.28-15-generic #49-Ubuntu SMP Tue Aug 18 19:25:34 UTC 2009 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 9.04 Release: 9.04 Codename: jaunty To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/427168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910981] [NEW] USB Keyboard Settings (Repeat rate and delay) Reset After Resume From Sleep
Public bug reported: When using a USB keyboard, my custom Repeat Keys delay/speed settings are lost when my laptop restarts or resumes from sleep/hibernation. A temporary fix is to toggle repeat keys off and on again in the setting dialog, but this only lasts for the current session. Laptop: Apple Macbook Pro Mid 2014 running Ubuntu 20.04.1 LTS Keyboard: Filco Majestictouch 2 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1910981 Title: USB Keyboard Settings (Repeat rate and delay) Reset After Resume From Sleep Status in gnome-settings-daemon package in Ubuntu: New Bug description: When using a USB keyboard, my custom Repeat Keys delay/speed settings are lost when my laptop restarts or resumes from sleep/hibernation. A temporary fix is to toggle repeat keys off and on again in the setting dialog, but this only lasts for the current session. Laptop: Apple Macbook Pro Mid 2014 running Ubuntu 20.04.1 LTS Keyboard: Filco Majestictouch 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1910981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
During the installation from the repository : nvidia-340: Unpacking nvidia-340 (340.108-0ubuntu2) ... Setting up nvidia-340 (340.108-0ubuntu2) ... dpkg: error: version '-' has bad syntax: revision number is em pty dpkg: error: version '-' has bad syntax: revision number is em pty update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-340 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_lat itude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your _quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_t hinkpad Adding system user `nvidia-persistenced' (UID 126) ... Adding new group `nvidia-persistenced' (GID 133) ... Adding new user `nvidia-persistenced' (UID 126) with group `nv idia-persistenced' ... Not creating home directory `/'. Loading new nvidia-340-340.108 DKMS files... Building for 5.8.0-36-generic Building for architecture x86_64 Building initial module for 5.8.0-36-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/cra sh/nvidia-340.0.crash' Error! Bad return status for module build on kernel: 5.8.0-36- generic (x86_64) Consult /var/lib/dkms/nvidia-340/340.108/build/make.log for mo re information. dpkg: error processing package nvidia-340 (--configure): installed nvidia-340 package post-installation script subproc ess returned error exit status 10 Processing triggers for man-db (2.9.1-1) ... Processing triggers for libc-bin (2.31-0ubuntu9.1) ... Processing triggers for initramfs-tools (0.136ubuntu6.3) ... update-initramfs: Generating /boot/initrd.img-5.8.0-36-generic I: The initramfs will attempt to resume from /dev/sda1 I: (UUID=591167b7-e429-475e-916a-fcc4830abde5) I: Set the RESUME variable to override this. Errors were encountered while processing: nvidia-340 E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1910709 Title: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 source package in Focal: Confirmed Bug description: Last linux kernel update "linux-headers-5.8.0-34-generic" broke nvidia-340 driver and Desktop access. In make log: [...] echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.";\ echo >&2 ; [...] Full DKMS log file attacked. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-04 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. H81M-D3H NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-59-generic root=UUID=b0ed05d5-7921-451b-b62c-773b97eeca2f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd01/20/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H81M-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate:
[Desktop-packages] [Bug 1910709] Re: DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340
I am unable to install nvidia-340 driver and got the following as log in its make.log file: $ tail -n 200 /var/lib/dkms/nvidia-340/340.108/build/make.log | ^~~~ ./arch/x86/include/asm/percpu.h:131:31: warning: comparison of integer expressions of different signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare] 131 | ((val) == 1 || (val) == -1)) ? \ | ^~ ./arch/x86/include/asm/percpu.h:434:34: note: in expansion of macro ‘percpu_add_op’ 434 | #define this_cpu_add_4(pcp, val) percpu_add_op(volatile, (pcp), val) | ^ ./include/linux/percpu-defs.h:379:11: note: in expansion of macro ‘this_cpu_add_4’ 379 | case 4: stem##4(variable, __VA_ARGS__);break; \ | ^~~~ ./include/linux/percpu-defs.h:509:33: note: in expansion of macro ‘__pcpu_size_call’ 509 | #define this_cpu_add(pcp, val) __pcpu_size_call(this_cpu_add_, pcp, val) | ^~~~ ./include/linux/percpu-defs.h:519:33: note: in expansion of macro ‘this_cpu_add’ 519 | #define this_cpu_sub(pcp, val) this_cpu_add(pcp, -(typeof(pcp))(val)) | ^~~~ ./include/linux/percpu-defs.h:521:28: note: in expansion of macro ‘this_cpu_sub’ 521 | #define this_cpu_dec(pcp) this_cpu_sub(pcp, 1) |^~~~ ./include/linux/percpu-rwsem.h:106:3: note: in expansion of macro ‘this_cpu_dec’ 106 | this_cpu_dec(*sem->read_count); | ^~~~ ./arch/x86/include/asm/percpu.h:131:31: warning: comparison of integer expressions of different signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare] 131 | ((val) == 1 || (val) == -1)) ? \ | ^~ ./arch/x86/include/asm/percpu.h:492:35: note: in expansion of macro ‘percpu_add_op’ 492 | #define this_cpu_add_8(pcp, val) percpu_add_op(volatile, (pcp), val) | ^ ./include/linux/percpu-defs.h:380:11: note: in expansion of macro ‘this_cpu_add_8’ 380 | case 8: stem##8(variable, __VA_ARGS__);break; \ | ^~~~ ./include/linux/percpu-defs.h:509:33: note: in expansion of macro ‘__pcpu_size_call’ 509 | #define this_cpu_add(pcp, val) __pcpu_size_call(this_cpu_add_, pcp, val) | ^~~~ ./include/linux/percpu-defs.h:519:33: note: in expansion of macro ‘this_cpu_add’ 519 | #define this_cpu_sub(pcp, val) this_cpu_add(pcp, -(typeof(pcp))(val)) | ^~~~ ./include/linux/percpu-defs.h:521:28: note: in expansion of macro ‘this_cpu_sub’ 521 | #define this_cpu_dec(pcp) this_cpu_sub(pcp, 1) |^~~~ ./include/linux/percpu-rwsem.h:106:3: note: in expansion of macro ‘this_cpu_dec’ 106 | this_cpu_dec(*sem->read_count); | ^~~~ ./arch/x86/include/asm/percpu.h:131:31: warning: comparison of integer expressions of different signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare] 131 | ((val) == 1 || (val) == -1)) ? \ | ^~ ./arch/x86/include/asm/percpu.h:432:34: note: in expansion of macro ‘percpu_add_op’ 432 | #define this_cpu_add_1(pcp, val) percpu_add_op(volatile, (pcp), val) | ^ ./include/linux/percpu-defs.h:377:11: note: in expansion of macro ‘this_cpu_add_1’ 377 | case 1: stem##1(variable, __VA_ARGS__);break; \ | ^~~~ ./include/linux/percpu-defs.h:509:33: note: in expansion of macro ‘__pcpu_size_call’ 509 | #define this_cpu_add(pcp, val) __pcpu_size_call(this_cpu_add_, pcp, val) | ^~~~ ./include/linux/percpu-defs.h:519:33: note: in expansion of macro ‘this_cpu_add’ 519 | #define this_cpu_sub(pcp, val) this_cpu_add(pcp, -(typeof(pcp))(val)) | ^~~~ ./include/linux/percpu-defs.h:521:28: note: in expansion of macro ‘this_cpu_sub’ 521 | #define this_cpu_dec(pcp) this_cpu_sub(pcp, 1) |^~~~ ./include/linux/percpu-rwsem.h:118:3: note: in expansion of macro ‘this_cpu_dec’ 118 | this_cpu_dec(*sem->read_count); | ^~~~ ./arch/x86/include/asm/percpu.h:131:31: warning: comparison of integer expressions of different signedness: ‘unsigned int’ and ‘int’ [-Wsign-compare] 131 | ((val) == 1 || (val) == -1)) ? \ | ^~ ./arch/x86/include/asm/percpu.h:433:34: note: in expansion of macro ‘percpu_add_op’ 433 | #define this_cpu_add_2(pcp, val) percpu_add_op(volatile, (pcp), val) | ^ ./include/linux/percpu-defs.h:378:11: note: in expansion of macro ‘this_cpu_add_2’ 378 | case 2: stem##2(variable, __VA_ARGS__);break; \ | ^~~~
[Desktop-packages] [Bug 1910559] Re: GDM3: Black screen with blinking cursor
The error you posted got me thinking and I did a reinstall of libnma0 and gir1.2-nm-1.0 and now the problem went away. Somehow, something on these got foobared. I never had any networkmanager issues though. -- 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/1910559 Title: GDM3: Black screen with blinking cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: About a month ago, GDM ceased to work. I opened another issue here https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717 but due to me using oibaf's ppa it was considered prudent to discard that issue and re-open after I removed the ppa and restored Ubuntu's dist packages. Upon boot, gdm goes to a black screen with a cursor. This screen flickers to show the underlying tty and on each flicker the cursor position resets to the bottom right. It will do this a number of times until GDM dies and I'm left on a tty. I can start my window manager (sway) without issue from the console still and everything functions normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: sway Date: Thu Jan 7 15:55:43 2021 SourcePackage: gdm3 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/1910559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910559] Re: GDM3: Black screen with blinking cursor
Thank you Daniel. None of the 3 ways to get ahold of a crash report worked unfortunately. There's nothing on /var/crash even after applying the workaround (Adding 'Crash' to the problem_types list on crashdb) and https://errors.ubuntu.com/user/5955c0a85343a54d5d779518dadcd4e278745d94628b423987bea5979d44b1d2b9ed23756ac91f32035088000d8d2ae868a6c9b99b7aff70d4febf3d6df571d2 as you can see is empty. -- 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/1910559 Title: GDM3: Black screen with blinking cursor Status in gnome-shell package in Ubuntu: Incomplete Bug description: About a month ago, GDM ceased to work. I opened another issue here https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1908717 but due to me using oibaf's ppa it was considered prudent to discard that issue and re-open after I removed the ppa and restored Ubuntu's dist packages. Upon boot, gdm goes to a black screen with a cursor. This screen flickers to show the underlying tty and on each flicker the cursor position resets to the bottom right. It will do this a number of times until GDM dies and I'm left on a tty. I can start my window manager (sway) without issue from the console still and everything functions normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: sway Date: Thu Jan 7 15:55:43 2021 SourcePackage: gdm3 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/1910559/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
It looks like a trivial issue, and I do see the message flooding lots of peoples' logs. The only problem right now is that it doesn't happen at all in my development setup, so I can't test and debug it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) No error. 4) Error in Ubuntu Logs App. Sender: gnome-shell Message: 4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 GMT-0600 (CST) 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Audit Session: 2 Priority: 6 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857392] Re: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
I also keep getting my syslog spammed with Jan 11 10:05:40 Teresa gnome-shell[2673]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Jan 11 10:05:40 Teresa gnome-shell[2673]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Jan 11 10:05:40 Teresa gnome-shell[2673]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Jan 11 10:05:40 Teresa gnome-shell[2673]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Jan 11 10:05:40 Teresa gnome-shell[2673]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Somehow seems related to when I move or copy files. I had a larger folder yesterday that I moved between disks and it kept freezing the desktop every few seconds or so and then spammed the logs with these messages when it unfroze again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1857392 Title: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Gnome 3.34.1 3) No error. 4) Error in Ubuntu Logs App. Sender: gnome-shell Message: 4:49:03 PM gnome-shell: GNOME Shell started at Mon Dec 23 2019 16:48:51 GMT-0600 (CST) 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). 4:49:02 PM gnome-shell: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Audit Session: 2 Priority: 6 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1857392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910962] Re: Display freeze
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910962 Title: Display freeze Status in Ubuntu: Incomplete Bug description: Even Mouse cursor could not be moved, had to do a hard power on reset ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jan 11 16:46:58 2021 DistUpgraded: 2020-09-29 20:14:07,287 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:15a0] InstallationDate: Installed on 2017-12-02 (1135 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX310UAK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-60-generic root=UUID=e067f662-d3f0-44de-970a-ef760eeb539a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-09-29 (103 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX310UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX310UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX310UAK.312:bd04/18/2019:svnASUSTeKCOMPUTERINC.:pnUX310UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX310UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX310UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Jan 11 16:44:45 2021 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.1~20.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1910962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910962] Re: Display freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1910962 Title: Display freeze Status in Ubuntu: Incomplete Bug description: Even Mouse cursor could not be moved, had to do a hard power on reset ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jan 11 16:46:58 2021 DistUpgraded: 2020-09-29 20:14:07,287 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:15a0] InstallationDate: Installed on 2017-12-02 (1135 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX310UAK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-60-generic root=UUID=e067f662-d3f0-44de-970a-ef760eeb539a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-09-29 (103 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX310UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX310UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX310UAK.312:bd04/18/2019:svnASUSTeKCOMPUTERINC.:pnUX310UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX310UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX310UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Jan 11 16:44:45 2021 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.1~20.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1910962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1910962] [NEW] Display freeze
You have been subscribed to a public bug: Even Mouse cursor could not be moved, had to do a hard power on reset ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78 Uname: Linux 5.4.0-60-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jan 11 16:46:58 2021 DistUpgraded: 2020-09-29 20:14:07,287 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:15a0] InstallationDate: Installed on 2017-12-02 (1135 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 3938:1031 MOSART Semi. 2.4G Wireless Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX310UAK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-60-generic root=UUID=e067f662-d3f0-44de-970a-ef760eeb539a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-09-29 (103 days ago) dmi.bios.date: 04/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX310UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX310UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX310UAK.312:bd04/18/2019:svnASUSTeKCOMPUTERINC.:pnUX310UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX310UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX310UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Jan 11 16:44:45 2021 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.9-2ubuntu1.1~20.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 focal freeze ubuntu -- Display freeze https://bugs.launchpad.net/bugs/1910962 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910928] Re: Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL
I am not sure if the problem is exactly with bluez package. ** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1910928 Title: Bluetooth won't go live after suspend Lenovo Thinkbook 14 IIL Status in bluez package in Ubuntu: Incomplete Bug description: After I have installed the Ubuntu - I have noticed, that Bluetooth won't go turn on after Suspend. The only way to get it working - reboot the system. WiFi Adapter - AX201 I have tried the latest kernel (5.11.rc2) - no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1910928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
