[Desktop-packages] [Bug 1774242] Re: Wacom touchscreens should disable gestures
** Changed in: xf86-input-wacom (Ubuntu) Importance: Undecided => Medium ** Changed in: xf86-input-wacom (Ubuntu Bionic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1774242 Title: Wacom touchscreens should disable gestures Status in OEM Priority Project: In Progress Status in xf86-input-wacom package in Ubuntu: Fix Released Status in xf86-input-wacom source package in Bionic: In Progress Bug description: [Impact] From the original bug: "The result is that on my Yoga 920, in a plain X11 session (running openbox in my case), the touchscreen acts like a broken mouse: there is no multi-touch capability in Qt Quick applications, and clicking isn't quite right either." [Test case] Install the update, note that the touchscreen behaviour is better. [Regression potential] From the upstream commit: "Note that this change will effectively cause a feature regression for users of other environments that do *not* have their own gesture engines (Cinnamon, KDE, MATE, XFCE, etc.). Users will want to add an xorg.conf.d snippet with `Option "Gesture" "on"` to bring back the functionality." but at least I (tjaalton) haven't heard of any complaints since we've disabled gestures in focal (Nov 21st), so the warning might be a bit too pessimistic about the impact. -- /usr/share/X11/xorg.conf.d/70-wacom.conf as shipped, has this: Section "InputClass" Identifier "Wacom touchscreen class" MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4" MatchDevicePath "/dev/input/event*" MatchIsTouchscreen "true" Driver "wacom" EndSection The result is that on my Yoga 920, in a plain X11 session (running openbox in my case), the touchscreen acts like a broken mouse: there is no multi-touch capability in Qt Quick applications, and clicking isn't quite right either. I also verified it with Peter Hutterer's old cairo-based mt-touch test program. I suspect we will get some users mistakenly writing up Qt bugs about this if you don't ship a fix. (Seems to me that already happened at least once, actually.) Yes, the touchscreen is made by Wacom, but wacom_drv.so has historically been only for Wacom tablets and in-screen stylus digitizers, and IMO that continues to be the case. libinput is a much better choice of driver for this hardware (so is evdev for that matter), so I changed it to Driver "libinput" and got it working. (Wayland uses libinput, so in a wayland session, touch already works fine in Qt apps on this hardware.) I'm one of the Qt Quick maintainers, most concerned with touch handling, and I've also written some of the Qt xcb code for dealing with XInput touch and tablet devices. So if you think that there's something wrong with Qt, such that it should still work anyway to use a wacom driver for a Wacom touchscreen, let me know. These AES devices are still new to me (that's why I got a Yoga, to try it out). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu1 [modified: usr/share/X11/xorg.conf.d/70-wacom.conf] ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 30 19:40:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
[Desktop-packages] [Bug 1868702] Re: No cursor on DisplayLink screen after login to Wayland sesion in Ubuntu 20.04
** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1868702 Title: No cursor on DisplayLink screen after login to Wayland sesion in Ubuntu 20.04 Status in mutter package in Ubuntu: Incomplete Bug description: Cursor is not visible on screen connected via DisplayLink usb3 docking stations. It is working fine when the display is first time attached after login to Wayland Gnome session. Then after logout it disappears. On other hand cursor is working fine in XServer session. Steps to reproduce: 0. Install DisplayLink driver from https://www.displaylink.com/downloads/ubuntu 1. Boot with DisplayLink device unplugged 2. Plug the device on login screen. -> screen should be added and cursor should work on it. 3. Login to Gnome on Wayland (Ubuntu on wayland option) Expected: Cursor should is working on screen attached via DisplayLink device Got: Cursor is invisible Reproduces with Ubuntu 20.04 Gnome/Wayland mutter version: mutter/focal 3.35.91-1ubuntu1 Reproducible on wide range of laptops, e.g XPS 13 9343 The problem is most likely related to pre-existing /dev/driX devices, as when using the hotplug path everything is fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1868702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869122] Re: mutter 3.36.0-2ubuntu1 changelog incorrectly mentions LP: #1862308
** Changed in: mutter (Ubuntu) Assignee: Iain Lane (laney) => (unassigned) ** Changed in: mutter (Ubuntu) Status: New => Triaged -- 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/1869122 Title: mutter 3.36.0-2ubuntu1 changelog incorrectly mentions LP: #1862308 Status in mutter package in Ubuntu: Triaged Bug description: mutter 3.36.0-2ubuntu1 changelog mentions wrong bug ID: * d/p/clutter-master-clock-default-Sync-timelines-to-hardware-v.patch: - Improves smoothness and reduce input-to-output latency levels (LP: #1862308) That last line should be deleted. Actually there is no Launchpad bug for that patch. Original proposal: https://salsa.debian.org/3v1n0-guest/mutter/-/merge_requests/1/diffs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819572] Re: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1819572 Title: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction Status in Ubuntu: Expired Status in network-manager package in Ubuntu: Expired Bug description: Hardware: Dell Vostro 5568 (CID 201606-22344) [Steps To Reproduce] 1. Install cosmic on this machine 2. Connect to the internet with ethernet 3. do-release-upgrade [Expected Result] Upgrade completes. The wired connection is ready to access the internet. [Actual Result] - The ethernet interface has an IP address assigned by the associated DHCP (checked by "ip -a") - "ping 8.8.8.8" will get "Destination Host Unreachable" [More Information] I tried the same steps on different machine-distro matrix[1] and could only reproduce the issue on this machine. [1] distro are: xenial-to-bionic, bionic-to-cosmic, cosmic-to-disco --- [Logs] - /var/log tarball of the system: the attachment 201606-22344-network- manager-nplusone-190312.var-log.tar.gz - Collected by "ubuntu-bug network-manager": /media/tai271828/certsd/201606-22344-network-manager- nplusone-190312.ubuntu.bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1819572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819572] Re: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1819572 Title: do-release-upgrade from cosmic to disco make the network of this specific machine malfunction Status in Ubuntu: Expired Status in network-manager package in Ubuntu: Expired Bug description: Hardware: Dell Vostro 5568 (CID 201606-22344) [Steps To Reproduce] 1. Install cosmic on this machine 2. Connect to the internet with ethernet 3. do-release-upgrade [Expected Result] Upgrade completes. The wired connection is ready to access the internet. [Actual Result] - The ethernet interface has an IP address assigned by the associated DHCP (checked by "ip -a") - "ping 8.8.8.8" will get "Destination Host Unreachable" [More Information] I tried the same steps on different machine-distro matrix[1] and could only reproduce the issue on this machine. [1] distro are: xenial-to-bionic, bionic-to-cosmic, cosmic-to-disco --- [Logs] - /var/log tarball of the system: the attachment 201606-22344-network- manager-nplusone-190312.var-log.tar.gz - Collected by "ubuntu-bug network-manager": /media/tai271828/certsd/201606-22344-network-manager- nplusone-190312.ubuntu.bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1819572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860664] Re: upgrate to snapd wipes out all user settings
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1860664
Title:
upgrate to snapd wipes out all user settings
Status in chromium-browser package in Ubuntu:
Expired
Bug description:
Ubuntu 19.10. apt-get upgrade. I'm warned that chromium from now on
required snapd and will only be implemented as snap packages. I complete the
upgrade, start chromium-browser and
- config settings are gone
- bookmarks are gone
- history is gone
- languages are gone
- addons are gone
- extensions are gone
- saved passwords are gone
Maybe it's as simple as moving some directory in my $HOME to a new
location, but since this is a snapd I worry that I'd have to pull
apart the snap package to insert things like dictionaries, and repeat
this effort every time snapd updates the package (which it does
silently! I'd only know if the software breaks!)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 79.0.3945.79-0ubuntu0.19.10.2
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8.3
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Jan 23 08:21:08 2020
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/xubuntu--vg-root ext4 451G 366G 62G 86% /
tmpfstmpfs 3.9G 70M 3.9G 2% /dev/shm
/dev/mapper/xubuntu--vg-root ext4 451G 366G 62G 86% /
InstallationDate: Installed on 2016-06-05 (1327 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: ASUSTeK Computer Inc. G73Sw
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-29-generic
root=/dev/mapper/xubuntu--vg-root ro nosplash nmi_watchdog=0 vga=773
acpi_osi=Linux
Snap.Changes:
ID Status Spawn Ready Summary
2Done2020-01-23T08:07:05-05:00 2020-01-23T08:12:26-05:00 Install
"chromium" snap
4Done2020-01-23T08:12:26-05:00 2020-01-23T08:12:28-05:00 Connect
chromium:password-manager-service to snapd:password-manager-service
Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.117
(04f0a055010adab4484f7497fbfdbf312c307f1d-refs/branch-heads/3945@{#1019})
Snap.ChromiumVersion: Chromium 79.0.3945.117 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to eoan on 2019-11-09 (74 days ago)
dmi.bios.date: 02/10/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G73Sw.205
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G73Sw
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.:bvrG73Sw.205:bd02/10/2011:svnASUSTeKComputerInc.:pnG73Sw:pvr1.0:rvnASUSTeKComputerInc.:rnG73Sw:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: G73Sw
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2018-03-20T22:16:27.108498
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1860664/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869122] Re: mutter 3.36.0-2ubuntu1 changelog incorrectly mentions LP: #1862308
I can't figure out where to propose a fix for this. It looks like the official branch isn't being used yet?... https://salsa.debian.org/gnome- team/mutter/-/blob/ubuntu/master/debian/changelog ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) -- 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/1869122 Title: mutter 3.36.0-2ubuntu1 changelog incorrectly mentions LP: #1862308 Status in mutter package in Ubuntu: New Bug description: mutter 3.36.0-2ubuntu1 changelog mentions wrong bug ID: * d/p/clutter-master-clock-default-Sync-timelines-to-hardware-v.patch: - Improves smoothness and reduce input-to-output latency levels (LP: #1862308) That last line should be deleted. Actually there is no Launchpad bug for that patch. Original proposal: https://salsa.debian.org/3v1n0-guest/mutter/-/merge_requests/1/diffs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869122] [NEW] mutter 3.36.0-2ubuntu1 changelog incorrectly mentions LP: #1862308
Public bug reported: mutter 3.36.0-2ubuntu1 changelog mentions wrong bug ID: * d/p/clutter-master-clock-default-Sync-timelines-to-hardware-v.patch: - Improves smoothness and reduce input-to-output latency levels (LP: #1862308) That last line should be deleted. Actually there is no Launchpad bug for that patch. Original proposal: https://salsa.debian.org/3v1n0-guest/mutter/-/merge_requests/1/diffs ** Affects: mutter (Ubuntu) Importance: Low Assignee: Iain Lane (laney) Status: New ** Tags: focal ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1869122 Title: mutter 3.36.0-2ubuntu1 changelog incorrectly mentions LP: #1862308 Status in mutter package in Ubuntu: New Bug description: mutter 3.36.0-2ubuntu1 changelog mentions wrong bug ID: * d/p/clutter-master-clock-default-Sync-timelines-to-hardware-v.patch: - Improves smoothness and reduce input-to-output latency levels (LP: #1862308) That last line should be deleted. Actually there is no Launchpad bug for that patch. Original proposal: https://salsa.debian.org/3v1n0-guest/mutter/-/merge_requests/1/diffs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869035] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of packag
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869035 Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 Status in pulseaudio package in Ubuntu: New Bug description: i wanted to install wine 5.0 and there is errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.22 Architecture: amd64 Date: Wed Mar 25 16:57:57 2020 DuplicateSignature: package:libpulse0:(not installed) Unpacking libpulse0:i386 (1:8.0-0ubuntu3.10) ... dpkg: error processing archive /var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3.10_i386.deb (--unpack): trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 InstallationDate: Installed on 2017-09-28 (908 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1869035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869042] Re: all monitor scaling fails due to overlapping monitors
** Tags added: xrandr-scaling -- 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/1869042 Title: all monitor scaling fails due to overlapping monitors Status in mutter package in Ubuntu: New Bug description: After an upgrade with focal-proposed this morning, I am unable to set any scaling for any of my monitors without the monitor turning blank for 15 seconds and reverting to 100% scaling. I am using X11 with gnome and proprietary nvidia drivers on Focal. I have 3 monitors attached, all 4K, and my usual setup is to enable fractional scaling, and set all 3 monitors to 150% scaling. Now however, I cannot change the monitors to use any scaling, and even if I disconnect 2 of the monitors to only have a single monitor I still cannot use scaling. Finally note I am just using the Settings window, I haven't fiddled with xrandr at all manually. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:24:05 2020 InstallationDate: Installed on 2019-07-05 (264 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868396] Re: Xorg crashed with SIGABRT in nvidia_drv.so
** Summary changed: - crashes or freezes with nividia/xorg + Xorg crashed with SIGABRT in nvidia_drv.so ** Package changed: xorg-server (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) ** Tags added: nvidia -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1868396 Title: Xorg crashed with SIGABRT in nvidia_drv.so Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: I have plugged in my Dell precision 5530 laptop a 4k HDMI screen. Using it with 200% zoom makes xorg crash. I have used proprietary 430, and changed to recommended proprietary 435 nvidia driver. As the system was still very unstable (no to say unusable) I had a go with 440 from ppa. I also ensured that my system was up to date doing a sudo apt-get update and upgrade. I was suprised to discover a few packages that needed an upgrade although I had previously used the Software Updater tool. Maybe I was doing something wrong. Anyway, with these updates and the newer 440 driver, I have successfully worked a day (sparsely) without problem, and using only 100% zoom. As a test, I decided to try to set the zoom to 200% (through devices > display, and I have only the external display enabled). After several minutes, I clicked on the « full screen » icon to maximize a shell, and the PC froze. It was so close to my change in the zoom ratio, that I suspect this is related. dmesg shew me that NVRM had a problem : [97501.301998] NVRM: GPU at PCI::01:00: GPU-dee28f75-4083-96a8-1a0b-491b6109101a [97501.302000] NVRM: Xid (PCI::01:00): 32, pid=493, Channel ID 0018 intr 0004 [97501.302134] NVRM: Xid (PCI::01:00): 32, pid=2052, Channel ID 0018 intr 0020 [97501.317307] NVRM: Xid (PCI::01:00): 69, pid=902, Class Error: ChId 001b, Class 902d, Offset 0250, Data 55d3, ErrorCode 000c pid 493 is gone pid 2052 is xorg stan 2052 2050 1 mars20 tty200:25:38 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 pid 902 is nvidia driver root 902 2 0 mars20 ? 00:02:59 [irq/163-nvidia] ppid 2052 is 2050 : stan 2050 2004 0 mars20 tty200:00:00 /usr/lib/gdm3/gdm-x-session --run-script env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --systemd --session=ubuntu After such an event, the previous days, the system became unstable, and I have got problems with other devices such as audio and network. If I run the manufacturer self-check test, everything is fine. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 18:36:53 2020 DistUpgraded: 2019-11-04 11:06:46,434 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: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.3.0-42-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2019-04-26 (329 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2262d308-663c-47c3-9e75-b34611c8df1d ro nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-11-04 (138 days ago) dmi.bios.date:
[Desktop-packages] [Bug 1869012] Re: [nvidia] Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1868396 *** https://bugs.launchpad.net/bugs/1868396 ** Summary changed: - Xorg freeze + [nvidia] Xorg crashed with SIGABRT ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) ** This bug has been marked a duplicate of bug 1868396 crashes or freezes with nividia/xorg -- 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/1869012 Title: [nvidia] Xorg crashed with SIGABRT Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: Well, that is maybe a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1868396 More crash info in : https://errors.ubuntu.com/oops/4dd7bfc4-6ea1 -11ea-98a4-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 15:04:06 2020 DistUpgraded: 2019-11-04 11:06:46,434 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: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.3.0-42-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2019-04-26 (333 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2262d308-663c-47c3-9e75-b34611c8df1d ro nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-11-04 (142 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868990] Re: Various actions produce images of applications running on all work-spaces on the current work-space
I think this is another form of bug 1868911 / bug 1868896 which are really both the same issue. ** Changed in: mutter (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed -- 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/1868990 Title: Various actions produce images of applications running on all work- spaces on the current work-space Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Invalid Bug description: I'm running Ubuntu 20.04 with two displays and four static workspaces. After upgrading various GNOME components to version 3.36.0-2ubuntu1 I'm seeing the following with several applications open of four desktops: 1) 'Alt-F2 r ' restarts GNOME Shell but displays an image of all currently running applications on the current desktop. Moving to another desktop corrects the problem. Similar to bug 1819890 which was closed as fixed for this release. 2) With Thunderbird running on 'Workspace 2', any attempt to open a menu produces an image of applications running on other desktops underneath Thunderbird. 3) Above also applies when using Libreoffice and HomeBank so probably applies to any application that displays a menubar. I'm unsure of which package to report this against so reporting against mutter and adding gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:42:05 2020 InstallationDate: Installed on 2019-05-17 (313 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2019-11-08 (137 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1868990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1868474 Title: Lenovo ThinkPad P73 touchpad does not work *after* installation Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1519228] Re: Drop obsolete dh_installinit --upstart-only option
** Changed in: lxc (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1519228 Title: Drop obsolete dh_installinit --upstart-only option Status in avahi package in Ubuntu: Fix Released Status in console-setup package in Ubuntu: Fix Released Status in cups package in Ubuntu: Fix Released Status in dcbd package in Ubuntu: Fix Released Status in debhelper package in Ubuntu: Fix Released Status in hostname package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in nfs-utils package in Ubuntu: Fix Released Status in nis package in Ubuntu: Fix Released Status in rfkill package in Ubuntu: Fix Released Status in xdiagnose package in Ubuntu: Fix Released Bug description: dh_installinit's --upstart-only option has been a deprecated no-op for a long time. Drop the remaining usage of it in packages so that we can get rid of this delta. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1519228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868480] Re: gnome mouse (trackpad ) and keyboard freezes [JS ERROR: Exception in callback for signal: StatusChanged: Error: value is out of range for Argument 'inte
Fix released... in some package. ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868480 Title: gnome mouse (trackpad ) and keyboard freezes [JS ERROR: Exception in callback for signal: StatusChanged: Error: value is out of range for Argument 'interval' (type guint32)] Status in Ubuntu: Fix Released Bug description: My Thinkpad ist working since years without this problem. Since last Friday, after a reboot, I got mouse and keyboard freezed. I reboot multiple time to analyse the problem. Google as a friend shows me that some problems are reported and I learned a lot but no solution for me. I find out that the problem occurs after 3 to 10 minutes of mouse and keyboard inactivity the mouse and keyboard freezes. If I always working with the mouse or the keyboard no freeze, still for hours. The problem is still reproducible by mouse and keyboard inactivity. This I figured out: - Strg+Alt+Del helps but all work are lost - klicking application (multiple points) entering some character an klicking application again helps some time - closing the lid and opening it after about 30 seconds helps, but requires password. I changed in /etc/gdm3/custom.conf #Enable=true to Enable=true and reboot. Login and wait till freeze, wait, close lid, and open lid. I run journalctl -b >aalog.txt (I have it attached) and analysed it. I found that every freeze time there is an error: Mär 22 15:19:41 BN591 gnome-shell[2978]: JS ERROR: Exception in callback for signal: StatusChanged: Error: value is out of range for Argument 'interval' (type guint32) timeout_source@resource:///org/gnome/gjs/modules/mainloop.js:65:13 Result of uname -a Linux BN591 5.0.0-37-generic #40~18.04.1-Ubuntu SMP Thu Nov 14 12:06:39 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Result of gnome-shell --version GNOME Shell 3.28.4 apt-cache policy gnome* is in the attached file Any thing else I can deliver to solve the problem Thanks and regards Rainer ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 16:25:39 2020 DisplayManager: gdm3 EcryptfsInUse: Yes 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/1868480/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868614] Re: Login starts at native resolution before visibly switching to the configured resolution
I have no idea where it is implemented. Just shotgunning the only package that I thought might be relevant. But actually that should include mutter... ** Package changed: gnome-settings-daemon (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1868614 Title: Login starts at native resolution before visibly switching to the configured resolution Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: This happens on Ubuntu 19.10 and still happening on Ubuntu 20.04 Let me give a little background My laptop (Razer Stealth) has a built in display with default 3840 by 2160. I currently have it set up to 1920 by 1080, as it drains the battery faster using the higher resolution. At login, the resolution show at 1920 by 1080, but after entering the password, the screen changes the resolution back to the default (3840 by 2160), but once the desktop of the user loads it changes back to 1920 by 1080. The change of resolution can be noticeable because the size of the mouse pointer becomes much smaller when logging in. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2020-03-17 08:21:46,611 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.4, 5.3.0-42-generic, x86_64: installed virtualbox, 6.1.4, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. Skylake GT2 [HD Graphics 520] [1a58:674d] InstallationDate: Installed on 2019-09-28 (178 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) MachineType: Razer Blade Stealth Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=3eed045c-673f-4583-9b55-d04adb18adc3 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: wayland-session focal ubuntu reproducible Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-03-17 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: ABCDEF dmi.board.name: SKYBAY dmi.board.vendor: INTEL Corporation dmi.board.version: Default string dmi.chassis.asset.tag: ABCDEF dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/30/2015:svnRazer:pnBladeStealth:pvr1.04:rvnINTELCorporation:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.name: Blade Stealth dmi.product.sku: RZ09-01682E24 dmi.product.version: 1.04 dmi.sys.vendor: Razer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868780] Re: [virtio] Xubuntu 20.04 - Blank screen after login
Please: 1. Reproduce the blank screen again and then immediately reboot. So the blank screen was the last issue near the end of the system log... 2. Now log in any way that avoids the blank screen so you can open a terminal and run: journalctl -b-1 > prevboot.txt 3. Attach the file 'prevboot.txt' here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1868780 Title: [virtio] Xubuntu 20.04 - Blank screen after login Status in xorg-server package in Ubuntu: Incomplete Bug description: Both on Xubuntu 20.04 23rd March and 24th March daily build. Using Martin Wimpress QuickEMU setup. Installation part of xubuntu is working fine. But after install and reboot, you get the login box. I type in the password for the user and then just get a black screen and mouse cursor, no other error boxes or gui. Have tested my QuickEMU setup on ubuntu-mate and do not see this issue, only on Xubuntu daily builds do I see this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Mar 24 16:40:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] InstallationDate: Installed on 2020-03-24 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=4b1c21e9-1325-435b-9ade-04263b901e6d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1868780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865845] Re: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers
** Changed in: gnome-control-center (Ubuntu Focal) Status: Incomplete => Triaged ** Changed in: gnome-control-center (Ubuntu Focal) Status: Triaged => In Progress -- 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/1865845 Title: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: In Progress Bug description: There is no progress information shows to user while enrolling fingerprint if the number of required enrollment steps is greater than 10. It might confuse user thinking it as freeze failure. Also it's not possible to enroll more than one finger. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. And this also introduce some critical issue of step 6 that user page in settings failed forever. However if the enrollment succeeds: 7. If trying to add a new fingerprint, the user is forced to delete its enrolled prints So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. 3. Allow to enroll more fingers As per this, GNOME design has produced some artwork that we want to implement to fix all these issues: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18 There will be few new strings, although most of the action events are already covered by the fprintd translations. UI will change quite a lot, but the current documentation [1] should not be affected by the change, being quite generic, but in case it might be updated to be clearer. [1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867944] Re: Bluetooth A2DP audio device disconnect automatically after long time using (almost 49mins)
Thanks. Fix Released... somewhere. ** Package changed: pulseaudio (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1867944 Title: Bluetooth A2DP audio device disconnect automatically after long time using (almost 49mins) Status in Ubuntu: Fix Released Bug description: After upgrading Ubuuntu 18.04 LTS to 20.04 , when I watching Netflix(by Firefox) videos with my bluetooth speaker (Lasonic i931BT), I found that almost every 49mins ,the video suddenly slow down and then sound stop transmitting to my speaker. It shouldn't happen. I check the pulseaudio mixer's output device. My speaker dissappeared. Only "Dummy Output " showed. (As the screenshot ) Everytime, I need go to bluetooth manager to disconnect the speaker, and wait it automatically connects again. Sometimes it works, but sometimes does not. I need to reboot to fix it (Power off the speak won't help ). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-bluetooth 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-lowlatency 5.4.24 Uname: Linux 5.4.0-18-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 18 23:13:06 2020 InstallationDate: Installed on 2020-03-10 (8 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Alpha amd64 (20200130) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06TCOP dmi.board.asset.tag: Tag 12345 dmi.board.name: ZX Series dmi.board.vendor: COPELION INTERNATIONAL INC. dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: COPELION INTERNATIONAL INC. dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06TCOP:bd10/14/2019:svnCOPELIONINTERNATIONALINC.:pnZXSeries:pvrNotApplicable:rvnCOPELIONINTERNATIONALINC.:rnZXSeries:rvrNotApplicable:cvnCOPELIONINTERNATIONALINC.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: ZX Series dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: COPELION INTERNATIONAL INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1867944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] Re: Lenovo ThinkPad P73 touchpad does not work *after* installation
This looks relevant: [ 6.732] (II) event6 - ETPS/2 Elantech Touchpad: device is a touchpad [ 6.732] (II) config/udev: Adding input device ETPS/2 Elantech Touchpad (/dev/input/mouse1) [ 6.732] (II) No input driver specified, ignoring this device. [ 10652.396] (II) config/udev: Adding input device Telink Wireless Receiver Mouse (/dev/input/mouse2) [ 10652.396] (II) No input driver specified, ignoring this device. ** Summary changed: - 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 + Lenovo ThinkPad P73 touchpad does not work *after* installation ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1868474 Title: Lenovo ThinkPad P73 touchpad does not work *after* installation Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1865845] Re: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers
** Description changed: - there is no progress information shows to user while enrolling fingerprint. + There is no progress information shows to user while enrolling fingerprint if the number of required enrollment steps is greater than 10. It might confuse user thinking it as freeze failure. + + Also it's not possible to enroll more than one finger. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. + And this also introduce some critical issue of step 6 that user page in + settings failed forever. + + However if the enrollment succeeds: + 7. If trying to add a new fingerprint, the user is forced to delete its enrolled prints + So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. + 3. Allow to enroll more fingers - And this also introduce some critical issue of step 6 that user page in - settings failed forever. + As per this, GNOME design has produced some artwork that we want to implement to fix all these issues: + - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18 - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + There will be few new strings, although most of the action events are + already covered by the fprintd translations. + + UI will change quite a lot, but the current documentation [1] should not + be affected by the change, being quite generic, but in case it might be + updated to be clearer. + + [1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html + + + + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) - InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) - SourcePackage: gnome-control-center + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1865845 Title: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: In Progress Bug description: There is no progress information shows to user while enrolling fingerprint if the number of required enrollment steps is greater than 10. It might confuse user thinking it as freeze failure. Also it's not possible to enroll more than one finger. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. And this also introduce some critical issue of step 6 that user page in settings failed forever. However if the enrollment succeeds: 7. If trying to add a new fingerprint, the user is forced to delete its enrolled prints So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. 3. Allow to enroll more fingers As per this, GNOME design has produced some artwork that we want to implement to fix all these issues: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18 There will be few new strings, although most of the action events are already covered by the fprintd translations. UI will change quite a lot, but the current documentation [1] should not be affected by the change, being quite generic, but in case it might be updated to be clearer. [1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64
[Desktop-packages] [Bug 1866228] Re: Gnome shell extensions are badly broken
Thanks for the reply. This sounds somewhat inconclusive, though it does sound like things are not "badly" broken now. I suggest we close this bug and then any additional issues found going forward should get their own separate new bugs, by running: ubuntu-bug gnome-shell ** 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/1866228 Title: Gnome shell extensions are badly broken Status in gnome-shell package in Ubuntu: Invalid Bug description: Hi, After an upgrade this morning, the following things are not working: - Earlier the Application key brought up something called "Activities", which happens now via ApplicationA or SuperA, the microsoft key - I can not find and search for extensions in the "Software" application. There are just a few addons/extensions, gstreamer ones, fonts and some input - any attempt at removing an installed extension results in a "you have no permission" error, without asking for a password. Apparently gnome-shell is crashing in the background, i'll attach logs if the tool does not. - The Tweak app shows a warning triangle next to the "Dash to panel" extension, by clicking on it the "Extension" thing starts up which shows nothing. - If I install the dash-to-panel extension from a package the top bar does not appears properly, the icons, workplace switcher etc all crumpled into the top left corne,r overlapping each other, thus being mostly unusable. I think that the extensions are not yet upgraded to gnome-shell 3.35, but I have no way to check it. I also have no trivial way to downgrade gnome shell to 3.34. Please advise. Thanks, tg ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 19:59:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-19 (46 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-02-26 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1024186] Re: Setting up fingerprint reader is clunky
fprintd is now installed by default, so we can close this ** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released -- 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/1024186 Title: Setting up fingerprint reader is clunky Status in gnome-control-center package in Ubuntu: Fix Released Bug description: There seems to be no easy way to set up a fingerprint reader (in this case, aes2501). According to an older tutorial* there should be an option in the User Accounts window to set it up, but something like that was not present in my 12.04 installation. Anyway, I ended up doing manually: 1) sudo apt-get install libfprint0 libpam-fprint 2) pam_fprint_enroll 3) sudo pam-auth-update Not that hard actually, but as the drivers from the fprint project seem to work quite well, having a straightforward graphical configuration would be the icing on the cake. *) https://help.ubuntu.com/11.04/ubuntu-help/session-fingerprint.html ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Fri Jul 13 06:25:15 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1024186/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865845] Re: [UIFe] No UI indication for fingerprint enrolling progress
** Summary changed: - No UI indication for fingerprint enrolling progress + [UIFe] No UI indication for fingerprint enrolling progress ** Summary changed: - [UIFe] No UI indication for fingerprint enrolling progress + [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers -- 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/1865845 Title: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Incomplete Status in gnome-control-center source package in Focal: Incomplete Bug description: there is no progress information shows to user while enrolling fingerprint. It might confuse user thinking it as freeze failure. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. And this also introduce some critical issue of step 6 that user page in settings failed forever. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865838] Re: no error displayed on failed fingerprint authentification
** Also affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Changed in: fprintd (Ubuntu Focal) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865838 Title: no error displayed on failed fingerprint authentification Status in gdm: Unknown Status in OEM Priority Project: New Status in fprintd package in Ubuntu: Triaged Status in gdm3 package in Ubuntu: Triaged Status in fprintd source package in Focal: Triaged Status in gdm3 source package in Focal: Triaged Bug description: from journalctl, gdm-fingerprint shows error there after retried 5 times of fingerprint login failed, so I open this issue here. Steps to reproduce issue: 1. enroll fingerprint for your right index finger. 2. logout 3. login and try login by incorrect finger e.g. middle finger 4. after 5 times retry. There's no error popup, then re-try index finger still no any message remind users they can not try fingerprint anymore. It will confuse user. Suggest behavior: 1. Each time user try fingerprint failed, show error message to remind user. 2. When user exceed 5 time errors, show error message to remind user input password instead. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 15:32:00 2020 InstallationDate: Installed on 2020-03-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865838/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849249] Re: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL)
Still happens every time in gnome-shell 3.36.0-2ubuntu1 / geany 1.36-1build1. -- 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/1849249 Title: gnome-shell crashed with SIGABRT: mutter:ERROR:../src/core/window.c:4841:set_workspace_state: assertion failed: (workspace == NULL) Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/8317377ffa8b8148baa481d490fd876111eb3c4b gnome-shell crashes with this bug every time that: * I am editing a file in geany * I open the Find window (CTRL-F) and it opens on another monitor * I type in some un-findable text in the find window and press ENTER (or click the Next button) The system beeps to indicate that the text isn't found, but then crashes. Note especially that the find window must be on the other monitor - if it's on the same monitor as geany, gnome-shell doesn't crash. (Note: I originally thought that if I moved the find window to the other window and then searched, gnome-shell crashed, but I think what happens is a) I open the window, b) I move it, search for something, and it works, c) I close it and re-open it - it then opens on the other monitor and searching will crash gnome-shell.) gnome-shell restarts, but the crash causes data loss, as most of the running applications don't reappear when it restarts. In case it's relevant, I have a laptop screen set at 2048x1152 and an external monitor configured to be above it at 2560x1440. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 Uname: Linux 5.4.0-050400rc4-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 10:37:36 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1570619894 InstallationDate: Installed on 2019-07-01 (112 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 () at /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868505] Re: Only snaps are shown - no apps from the archive
I've tracked this down to network-manager-pptp-gnome - without this package you get this issue - install the package and all is well. So this should be a dependency of gnome-software? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1868505 Title: Only snaps are shown - no apps from the archive Status in gnome-software package in Ubuntu: Confirmed Bug description: Using 21 March 20.04 Ubuntu Budgie daily - minimal install The only applications shown on the front page are snaps - cannot search or show for any archive apps. launching gnome-software from the command line I see 22:53:28:0287 XbSilo xb_builder_ensure: assertion 'error == NULL || *error == NULL' failed 22:53:28:0302 Gs enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, desktop-menu-path, hardcoded-blacklist, modalias, odrs, packagekit-refine, rewrite-resource, snap, packagekit-history, provenance, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata 22:53:28:0302 Gs disabled plugins: dpkg, dummy, repos, appstream 22:53:31:0903 Gs Only 0 apps for recent list, hiding 22:53:32:0165 GLib g_variant_new_variant: assertion 'value != NULL' failed 22:53:32:0165 GLib g_variant_new_variant: assertion 'value != NULL' failed 22:53:32:0166 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 22:53:32:0167 Gs not handling error failed for action refine: Invalid string value converting to GVariant So why are dpkg, dummy, repos, appstream disabled? How can they be enabled? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Mar 22 22:56:40 2020 InstallationDate: Installed on 2020-03-21 (1 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200320) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1868505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869102] [NEW] Minor translation fix needed for en_US
Public bug reported: Entry 210 (https://translations.launchpad.net/ubuntu/focal/+source/remmina/+pots/remmina/en_GB/210/+translate) currently reads: "SSH passphrase is empty, it should not." instead of "SSH passphrase is empty, it should not be." Located in ../src/remmina_ssh.c:255 cheers, Ant ** Affects: remmina (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1869102 Title: Minor translation fix needed for en_US Status in remmina package in Ubuntu: New Bug description: Entry 210 (https://translations.launchpad.net/ubuntu/focal/+source/remmina/+pots/remmina/en_GB/210/+translate) currently reads: "SSH passphrase is empty, it should not." instead of "SSH passphrase is empty, it should not be." Located in ../src/remmina_ssh.c:255 cheers, Ant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1869102/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836455] Re: openvpn gnome applet: Could not find source connection
Please, give a workaround or solve this bug. Actually it's not possible to activare a vpn (eg. l2tp) without a gui ... and my raspberry does not have a gui! thank you. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1836455 Title: openvpn gnome applet: Could not find source connection Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 Packages: network-manager-openvpn (1.8.2-1). network-manager-openvpn-gnome (1.8.2-1). All operation system updates by current date was installed. I use a vpn applet to connect to my vpn server. I import the configuration from my ovpn-file. Everything was fine. After system updates installation vpn won't works with the gnome vpn applet: /var/log/syslog: Jul 13 19:53:22 alex-pc NetworkManager[2185]: [1563036802.6358] audit: op="connection-activate" uuid="0c66b073-67d4 -425c-b4cf-1910460e073a" name="x1" pid=12760 uid=1000 result="fail" reason="Could not find source connection." I found that the bug is very old(!): https://bugzilla.gnome.org/show_bug.cgi?id=704595 I tried to import the openvpn configuration manually into the openvpn applet with the same result. But if I use my openvpn from cli - everything is fine. Help me please! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1836455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847618] Re: im-config ignores input methods other than xim in my current locale
This bug was fixed in the package im-config - 0.44-1ubuntu1 --- im-config (0.44-1ubuntu1) focal; urgency=medium * Merge with Debian unstable, remaining changes: - d/maintscript: Remove /etc/profile.d/input-method-config.sh - d/p/01-ubuntu-default-mode.patch - d/p/reverse-Remove-imconfig_find_files_with_prefixpath_glob.patch * d/p/reverse-Remove-imconfig_find_files_with_prefixpath_glob.patch: - Reverse new approach for setting env variables im-config (0.44-1) unstable; urgency=medium * Clean up imconfig_find_files_with_prefixpath_glob. [ Boyuan Yang ] * Add initial configuration data for fcitx5 support. [ Gunnar Hjalmarsson ] * im-launch.1: Fix a typo in the man page. (LP: #1851997) * xinputrc.common.in: Use LC_ALL=C for dpkg-query to ensure English output. (LP: #1847618) -- Gunnar Hjalmarsson Wed, 25 Mar 2020 22:44:00 +0100 ** Changed in: im-config (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1847618 Title: im-config ignores input methods other than xim in my current locale Status in im-config package in Ubuntu: Fix Released Bug description: I use Ubuntu 16.04.6 LTS. I can not reach other input methods such as ibus, fcitx in my current locale which is LANGUAGE=tr_TR.UTF-8. It's not listed in unity-control-center>Language Support>Keyboard Input Method System. If I launch unity-control-center from terminal which is using different locale "LANGUAGE=en_US.utf8 unity-control-center" then there is no problem, all of the installed input methods are in the list. I also tested "python3 /usr/lib/python3/dist-packages/LanguageSelector/ImConfig.py" it also ignores input methods other than xim and none. If I export "LANGUAGE=en_US.utf8" it lists all the other input methods. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1847618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851997] Re: Typo in im-launch(1) man page
This bug was fixed in the package im-config - 0.44-1ubuntu1 --- im-config (0.44-1ubuntu1) focal; urgency=medium * Merge with Debian unstable, remaining changes: - d/maintscript: Remove /etc/profile.d/input-method-config.sh - d/p/01-ubuntu-default-mode.patch - d/p/reverse-Remove-imconfig_find_files_with_prefixpath_glob.patch * d/p/reverse-Remove-imconfig_find_files_with_prefixpath_glob.patch: - Reverse new approach for setting env variables im-config (0.44-1) unstable; urgency=medium * Clean up imconfig_find_files_with_prefixpath_glob. [ Boyuan Yang ] * Add initial configuration data for fcitx5 support. [ Gunnar Hjalmarsson ] * im-launch.1: Fix a typo in the man page. (LP: #1851997) * xinputrc.common.in: Use LC_ALL=C for dpkg-query to ensure English output. (LP: #1847618) -- Gunnar Hjalmarsson Wed, 25 Mar 2020 22:44:00 +0100 ** Changed in: im-config (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1851997 Title: Typo in im-launch(1) man page Status in im-config package in Ubuntu: Fix Released Bug description: im-launch(1) says: im-launch - launch input method end execute session program but should say: im-launch - launch input method and execute session program (s/end/and/) This is an upstream bug[1] which should be reported to Debian, but frankly I'm not up to dealing with the Debian BTS at the moment. [1]: https://salsa.debian.org/input-method-team/im- config/blob/24779d612f14c5f6c32ae789c7e7091fd859e7ec/im-launch.1#L5 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: im-config 0.34-1ubuntu1.3 ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18 Uname: Linux 4.15.0-66-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: i3 Date: Sun Nov 10 15:04:15 2019 InstallationDate: Installed on 2018-08-13 (453 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: im-config UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1851997/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868919] Re: Cheese refuses to use webcam
yes, it does, works with vlc. v4l2-ctl also detects it properly. interestingly enough, firefox and zoom also detect it properly, but grab only black frames. chromium fails to detect the webcam at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1868919 Title: Cheese refuses to use webcam Status in cheese package in Ubuntu: Incomplete Bug description: Hi, I have a USB webcam attached to my ubuntu machine: Bus 001 Device 002: ID 0c45:600d Microdia TwinkleCam USB camera this device uses gspca_sonixb: gilbahat@meadow:~$ lsmod | grep gspca gspca_sonixb 20480 0 gspca_main 24576 1 gspca_sonixb videobuf2_vmalloc 20480 1 gspca_main videobuf2_v4l2 24576 1 gspca_main videobuf2_common 49152 2 gspca_main,videobuf2_v4l2 videodev 225280 4 gspca_main,videobuf2_v4l2,videobuf2_common,gspca_sonixb the device passes v4l2 tests: $ v4l2-ctl -d /dev/video0 --all Driver Info: Driver name : sonixb Card type: USB camera Bus info : usb-:00:14.0-1 Driver version : 5.4.24 Capabilities : 0x8521 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x0521 Video Capture Read/Write Streaming Extended Pix Format Priority: 2 Video input : 0 (sonixb: ok) Format Video Capture: Width/Height : 352/288 Pixel Format : 'S910' (GSPCA SN9C10X) Field : None Bytes per Line: 352 Size Image: 126720 Colorspace: sRGB Transfer Function : Default (maps to sRGB) YCbCr/HSV Encoding: Default (maps to ITU-R 601) Quantization : Default (maps to Full Range) Flags : Streaming Parameters Video Capture: Frames per second: invalid (0/0) Read buffers : 2 User Controls brightness 0x00980900 (int): min=0 max=255 step=1 default=127 value=127 flags=slider exposure 0x00980911 (int): min=0 max=1023 step=1 default=66 value=66 flags=inactive gain_automatic 0x00980912 (bool) : default=1 value=1 flags=update gain 0x00980913 (int): min=0 max=31 step=1 default=15 value=15 flags=inactive the device even works with vlc when opened as a v4l2 capture device and picture is detected and displayed. however, cheese just insists there is no webcam installed, even when run with -d /dev/video0 on the command line. system details: $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ dpkg -l | grep cheese ii cheese 3.34.0-1build1 amd64tool to take pictures and videos from your webcam expected behaviour: /dev/video0 appears on the list of usable devices and cheese uses it observed behaviour: cheese complains about no video devices being available. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-23 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: cheese 3.34.0-1build1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 Tags: focal gstreamer-error Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/09/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0074.2018.0709.1332 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-413 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0074.2018.0709.1332:bd07/09/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-413:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1868919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869086] [NEW] Firmware upgrade always notifies to reboot the device even on immediate failure
Public bug reported: If the firmware update request fails because of a network error or because the AC power is not plugged, or any other problem, gnome- software shows an error in an in-app notification, while sends a resident notification to gnome-shell that requests the user to restart the system, even if this is not really required. See the attached screenshot. ** Affects: gnome-software (Ubuntu) Importance: Medium Status: Triaged ** Tags: rls-ff-incoming ** Attachment added: "Screenshot from 2020-03-25 22-46-36.png" https://bugs.launchpad.net/bugs/1869086/+attachment/5341693/+files/Screenshot%20from%202020-03-25%2022-46-36.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869086 Title: Firmware upgrade always notifies to reboot the device even on immediate failure Status in gnome-software package in Ubuntu: Triaged Bug description: If the firmware update request fails because of a network error or because the AC power is not plugged, or any other problem, gnome- software shows an error in an in-app notification, while sends a resident notification to gnome-shell that requests the user to restart the system, even if this is not really required. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1869086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868919] Re: Cheese refuses to use webcam
Thanks, it doesn't seem to find the device for some reason. Does the webcam work in other softwares? Also note that the -d option doesn't take a device path, see https://gitlab.gnome.org/GNOME/cheese/-/issues/4 ** Bug watch added: gitlab.gnome.org/GNOME/cheese/-/issues #4 https://gitlab.gnome.org/GNOME/cheese/-/issues/4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1868919 Title: Cheese refuses to use webcam Status in cheese package in Ubuntu: Incomplete Bug description: Hi, I have a USB webcam attached to my ubuntu machine: Bus 001 Device 002: ID 0c45:600d Microdia TwinkleCam USB camera this device uses gspca_sonixb: gilbahat@meadow:~$ lsmod | grep gspca gspca_sonixb 20480 0 gspca_main 24576 1 gspca_sonixb videobuf2_vmalloc 20480 1 gspca_main videobuf2_v4l2 24576 1 gspca_main videobuf2_common 49152 2 gspca_main,videobuf2_v4l2 videodev 225280 4 gspca_main,videobuf2_v4l2,videobuf2_common,gspca_sonixb the device passes v4l2 tests: $ v4l2-ctl -d /dev/video0 --all Driver Info: Driver name : sonixb Card type: USB camera Bus info : usb-:00:14.0-1 Driver version : 5.4.24 Capabilities : 0x8521 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x0521 Video Capture Read/Write Streaming Extended Pix Format Priority: 2 Video input : 0 (sonixb: ok) Format Video Capture: Width/Height : 352/288 Pixel Format : 'S910' (GSPCA SN9C10X) Field : None Bytes per Line: 352 Size Image: 126720 Colorspace: sRGB Transfer Function : Default (maps to sRGB) YCbCr/HSV Encoding: Default (maps to ITU-R 601) Quantization : Default (maps to Full Range) Flags : Streaming Parameters Video Capture: Frames per second: invalid (0/0) Read buffers : 2 User Controls brightness 0x00980900 (int): min=0 max=255 step=1 default=127 value=127 flags=slider exposure 0x00980911 (int): min=0 max=1023 step=1 default=66 value=66 flags=inactive gain_automatic 0x00980912 (bool) : default=1 value=1 flags=update gain 0x00980913 (int): min=0 max=31 step=1 default=15 value=15 flags=inactive the device even works with vlc when opened as a v4l2 capture device and picture is detected and displayed. however, cheese just insists there is no webcam installed, even when run with -d /dev/video0 on the command line. system details: $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ dpkg -l | grep cheese ii cheese 3.34.0-1build1 amd64tool to take pictures and videos from your webcam expected behaviour: /dev/video0 appears on the list of usable devices and cheese uses it observed behaviour: cheese complains about no video devices being available. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-23 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: cheese 3.34.0-1build1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 Tags: focal gstreamer-error Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/09/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0074.2018.0709.1332 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-413 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0074.2018.0709.1332:bd07/09/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-413:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1868919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865169] Re: volume and light not working in Gnome Shell 3.35
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gjs (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1865169 Title: volume and light not working in Gnome Shell 3.35 Status in GNOME Shell: Unknown Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: After upgrading to GNOME shell 3.35, the speaker icon in top bar is missing and both volume and light sliders are set to 0. Changing volume and light from keyboard works, but has no effect in gnome shell dropdown. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-16.19-generic 5.4.22 Uname: Linux 5.4.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 18:57:54 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (118 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1865169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868780] Re: [virtio] Xubuntu 20.04 - Blank screen after login
Not found anymore .crash files. But I have found a workaround. To reproduce the fix: - Boot up the xubuntu machine in QuickEMU (Martin Wimpress QEMU script) - Get to the login screen - Change the session from Xubuntu to Xfce - Type in password and Enter and the desktop appears as normal. If Xubuntu session is selected I get the black screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1868780 Title: [virtio] Xubuntu 20.04 - Blank screen after login Status in xorg-server package in Ubuntu: Incomplete Bug description: Both on Xubuntu 20.04 23rd March and 24th March daily build. Using Martin Wimpress QuickEMU setup. Installation part of xubuntu is working fine. But after install and reboot, you get the login box. I type in the password for the user and then just get a black screen and mouse cursor, no other error boxes or gui. Have tested my QuickEMU setup on ubuntu-mate and do not see this issue, only on Xubuntu daily builds do I see this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Mar 24 16:40:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] InstallationDate: Installed on 2020-03-24 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=4b1c21e9-1325-435b-9ade-04263b901e6d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1868780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868919] Re: Cheese refuses to use webcam
I have stdout for a run with GST_DEBUG but I don't have instructions to locate the real CheeseDebug.txt.gz , I don't suspect that's all there is to it i'm afraid. ** Attachment added: "stderr.txt" https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1868919/+attachment/5341660/+files/stderr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1868919 Title: Cheese refuses to use webcam Status in cheese package in Ubuntu: Incomplete Bug description: Hi, I have a USB webcam attached to my ubuntu machine: Bus 001 Device 002: ID 0c45:600d Microdia TwinkleCam USB camera this device uses gspca_sonixb: gilbahat@meadow:~$ lsmod | grep gspca gspca_sonixb 20480 0 gspca_main 24576 1 gspca_sonixb videobuf2_vmalloc 20480 1 gspca_main videobuf2_v4l2 24576 1 gspca_main videobuf2_common 49152 2 gspca_main,videobuf2_v4l2 videodev 225280 4 gspca_main,videobuf2_v4l2,videobuf2_common,gspca_sonixb the device passes v4l2 tests: $ v4l2-ctl -d /dev/video0 --all Driver Info: Driver name : sonixb Card type: USB camera Bus info : usb-:00:14.0-1 Driver version : 5.4.24 Capabilities : 0x8521 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x0521 Video Capture Read/Write Streaming Extended Pix Format Priority: 2 Video input : 0 (sonixb: ok) Format Video Capture: Width/Height : 352/288 Pixel Format : 'S910' (GSPCA SN9C10X) Field : None Bytes per Line: 352 Size Image: 126720 Colorspace: sRGB Transfer Function : Default (maps to sRGB) YCbCr/HSV Encoding: Default (maps to ITU-R 601) Quantization : Default (maps to Full Range) Flags : Streaming Parameters Video Capture: Frames per second: invalid (0/0) Read buffers : 2 User Controls brightness 0x00980900 (int): min=0 max=255 step=1 default=127 value=127 flags=slider exposure 0x00980911 (int): min=0 max=1023 step=1 default=66 value=66 flags=inactive gain_automatic 0x00980912 (bool) : default=1 value=1 flags=update gain 0x00980913 (int): min=0 max=31 step=1 default=15 value=15 flags=inactive the device even works with vlc when opened as a v4l2 capture device and picture is detected and displayed. however, cheese just insists there is no webcam installed, even when run with -d /dev/video0 on the command line. system details: $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ dpkg -l | grep cheese ii cheese 3.34.0-1build1 amd64tool to take pictures and videos from your webcam expected behaviour: /dev/video0 appears on the list of usable devices and cheese uses it observed behaviour: cheese complains about no video devices being available. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-23 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: cheese 3.34.0-1build1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 Tags: focal gstreamer-error Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/09/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0074.2018.0709.1332 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-413 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0074.2018.0709.1332:bd07/09/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-413:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1868919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868919] Re: Cheese refuses to use webcam
** Attachment added: "jctl.log" https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1868919/+attachment/5341661/+files/jctl.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1868919 Title: Cheese refuses to use webcam Status in cheese package in Ubuntu: Incomplete Bug description: Hi, I have a USB webcam attached to my ubuntu machine: Bus 001 Device 002: ID 0c45:600d Microdia TwinkleCam USB camera this device uses gspca_sonixb: gilbahat@meadow:~$ lsmod | grep gspca gspca_sonixb 20480 0 gspca_main 24576 1 gspca_sonixb videobuf2_vmalloc 20480 1 gspca_main videobuf2_v4l2 24576 1 gspca_main videobuf2_common 49152 2 gspca_main,videobuf2_v4l2 videodev 225280 4 gspca_main,videobuf2_v4l2,videobuf2_common,gspca_sonixb the device passes v4l2 tests: $ v4l2-ctl -d /dev/video0 --all Driver Info: Driver name : sonixb Card type: USB camera Bus info : usb-:00:14.0-1 Driver version : 5.4.24 Capabilities : 0x8521 Video Capture Read/Write Streaming Extended Pix Format Device Capabilities Device Caps : 0x0521 Video Capture Read/Write Streaming Extended Pix Format Priority: 2 Video input : 0 (sonixb: ok) Format Video Capture: Width/Height : 352/288 Pixel Format : 'S910' (GSPCA SN9C10X) Field : None Bytes per Line: 352 Size Image: 126720 Colorspace: sRGB Transfer Function : Default (maps to sRGB) YCbCr/HSV Encoding: Default (maps to ITU-R 601) Quantization : Default (maps to Full Range) Flags : Streaming Parameters Video Capture: Frames per second: invalid (0/0) Read buffers : 2 User Controls brightness 0x00980900 (int): min=0 max=255 step=1 default=127 value=127 flags=slider exposure 0x00980911 (int): min=0 max=1023 step=1 default=66 value=66 flags=inactive gain_automatic 0x00980912 (bool) : default=1 value=1 flags=update gain 0x00980913 (int): min=0 max=31 step=1 default=15 value=15 flags=inactive the device even works with vlc when opened as a v4l2 capture device and picture is detected and displayed. however, cheese just insists there is no webcam installed, even when run with -d /dev/video0 on the command line. system details: $ lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 $ dpkg -l | grep cheese ii cheese 3.34.0-1build1 amd64tool to take pictures and videos from your webcam expected behaviour: /dev/video0 appears on the list of usable devices and cheese uses it observed behaviour: cheese complains about no video devices being available. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-23 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: cheese 3.34.0-1build1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 Tags: focal gstreamer-error Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/09/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0074.2018.0709.1332 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-413 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0074.2018.0709.1332:bd07/09/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-413:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1868919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
** Also affects: codelite (Ubuntu) Importance: Undecided Status: New ** Tags removed: fixed-in-3.35.90 fixed-upstream -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Confirmed Status in Mutter: Fix Released Status in codelite package in Ubuntu: New Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in codelite source package in Eoan: New Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Status in codelite source package in Focal: New Status in libreoffice source package in Focal: Triaged Status in mutter source package in Focal: Fix Released Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868705] Re: Update deja-dup to 40.6
This bug was fixed in the package deja-dup - 40.6-1 --- deja-dup (40.6-1) unstable; urgency=medium * New upstream release -- Sebastien Bacher Tue, 24 Mar 2020 21:19:59 +0100 ** Changed in: deja-dup (Ubuntu) Status: Triaged => Fix Released -- 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/1868705 Title: Update deja-dup to 40.6 Status in deja-dup package in Ubuntu: Fix Released Status in deja-dup source package in Focal: Fix Released Status in deja-dup package in Debian: Unknown Bug description: Please update deja-dup to 40.6. It is a bug-fix release. https://gitlab.gnome.org/World/deja-dup/-/blob/master/NEWS.md 40.6 Fixes a bug that prevented backing up to Google Drive accounts with unlimited quotas Updated translations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1868705/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865170] Re: lid close simply turns off laptop screen
Nevermind, I just saw the rfkill changelog. Since I'm no longer able to reproduce the bug, should it be closed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
[Desktop-packages] [Bug 1865170] Re: lid close simply turns off laptop screen
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1865170/+attachment/5341643/+files/dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] Re: lid close simply turns off laptop screen
** Attachment added: "apt.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1865170/+attachment/5341642/+files/apt.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1865170] Re: lid close simply turns off laptop screen
It seems that one of the updates that just happened via apt might have fixed the issue? attached is dmesg log... does it look like expected behavior? My fans are properly turning off, and when I open my laptop lid, I'm not getting the delayed sleep mode. BIOS update I'm not sure exactly which package solved it. I've attached the most recent list of packages upgraded by apt, as well. I'm curious if it's the rfkill update that solved it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019
[Desktop-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
@dgadomski if you have time, could you check this and upload a fixed package? Since this is autopkgtest test failure only, it will probably need block-proposed-eoan tag. I'm not sure if this is needed for bionic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: New Status in network-manager source package in Artful: Won't Fix Status in network-manager source package in Disco: Won't Fix Status in network-manager source package in Eoan: New Status in network-manager source package in Focal: New Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Potential] No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout. [Other Info] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1868782] Re: PCI/internal sound card not detected "dummy output"
*** This bug is a duplicate of bug 1864061 *** https://bugs.launchpad.net/bugs/1864061 Thank you Hui Wang for your help. >Please add "options snd-hda-intel dmic_detect=0" in the /etc/modprobe.d/alsa-base.conf, then the legacy hda driver will work as before. I can confirm, this solved both the sound problem as well as suspend problem. Peace, Phil On 3/24/20 6:52 PM, Hui Wang wrote: > *** This bug is a duplicate of bug 1864061 *** > https://bugs.launchpad.net/bugs/1864061 > > Please try 5.3.0-43 kernel. > > > ** This bug has been marked a duplicate of bug 1864061 > PCI/internal sound card not detected -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1868782 Title: PCI/internal sound card not detected "dummy output" Status in alsa-driver package in Ubuntu: New Bug description: On 22 March, 2020 I ran the latest update as requested by the computer. After rebooting, as requested, I no longer have sound & the only sound output is "Dummy Output". No sound card is detected but i have a Multimedia Audio Controller Intel Corp Device 9dc8(rev30) installed. After running Ubuntu-bug in terminal I get: ProblemType: Bug DistroRelease: Ubuntu 18.04.4 Package: alsa-base 1.0.25+dfsg-Oubuntu5 Apport Version: 2.20.9-Obuntu7.12 Manufacturer: Acer Product Name: Swift SF314-56 Product Version: V1.10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 11:25:53 2020 InstallationDate: Installed on 2019-09-18 (188 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd02/22/2019:svnAcer:pnSwiftSF314-56:pvrV1.10:rvnWL:rnStrongbow_WL:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868990] Re: Various actions produce images of applications running on all work-spaces on the current work-space
Already reported upstream : https://gitlab.gnome.org/GNOME/mutter/-/issues/1138 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1138 https://gitlab.gnome.org/GNOME/mutter/-/issues/1138 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1138 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868990 Title: Various actions produce images of applications running on all work- spaces on the current work-space Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 20.04 with two displays and four static workspaces. After upgrading various GNOME components to version 3.36.0-2ubuntu1 I'm seeing the following with several applications open of four desktops: 1) 'Alt-F2 r ' restarts GNOME Shell but displays an image of all currently running applications on the current desktop. Moving to another desktop corrects the problem. Similar to bug 1819890 which was closed as fixed for this release. 2) With Thunderbird running on 'Workspace 2', any attempt to open a menu produces an image of applications running on other desktops underneath Thunderbird. 3) Above also applies when using Libreoffice and HomeBank so probably applies to any application that displays a menubar. I'm unsure of which package to report this against so reporting against mutter and adding gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:42:05 2020 InstallationDate: Installed on 2019-05-17 (313 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2019-11-08 (137 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1868990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
This is still broken in 20.04 mutter 3.36.0 ** Summary changed: - [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 + [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Confirmed Status in Mutter: Fix Released Status in libreoffice package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in libreoffice source package in Eoan: Triaged Status in mutter source package in Eoan: Triaged Status in libreoffice source package in Focal: Triaged Status in mutter source package in Focal: Fix Released Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1577198] Re: Imported gpg keys do not show up in Seahorse 3.18.0
Ok! So the bug is still here but for me a little bit different. Being on
Ubuntu 19.10 with its own Gnome the situation is the following.
Originally the system has just 'gpg' not 'gpg2' BUT basically the
original 'gpg' is 'gpg2' as it's version is 'gpg (GnuPG) 2.2.12'. After
installing gpg2 there is no so much change it just gave me a symlink
from 'gpg2' to the system original 'gpg'. So basically now on 19.10 the
2 gpg is the same.
Let's check the keyring thingie. It is not too surprising that both of
them use the same home dir: 'Home: /home/{user}/.gnupg' and of course
the same keyring: /home/{user}/.gnupg/pubring.kbx. And because between
the 2 thing there is any differences.
So what about Seahorse. Ubuntu 19.10 has 'Seahorse 3.32.2'. If I import
a key from CLI through 'gpg' or 'gpg2' the key will be available int the
mentioned keyring and CLI gpg can use it. But if I import the key from
the Seahorse GUI the result what you all mentioned. Seems succeed but
after the 'successfully imported' message there is no new key in
Seahorse. Moreover the successfully imported key is also not in the gpg
keyring verifying from CLI. Seahorse tells the everything ok on the
import but the corresponding key is nowhere.
BUT! if you restart your gnome user session, VOILA the missing key
appearing in Seahorse.
Sadly restarting the seahorse daemon not do the work so we really need
to logout and login again.
This is very interesting as seems Seahorse not use directly the gpg
keyring (something like PAM in Samba processes what otherwise I never
understand completely), but a maintainer process sync their content.
So what I (we) know now that Seahorse simply not use gpg keyring as I
simply import anything in vain in Seahorse that not appear in gpg
keyring verified from CLI (and as the topic bug tells it also sadly not
appear in Seahorse itself:D but in this case who know were are
they?!...). Also in vain, if I imported anything in CLI gpg, the result
is perfect in CLI gpg, but not appear in Seahorse.
And partly therefore the other thing is the conclusion, that Seahorse
use 2 different backend for itself and those both are different from CLI
gpg keyring (what is not so nice). One backend is used by the GUI and
another is in real processes. And what I can see that the 2 backend sync
each other at user login (something like as PAM with Samba).
Very interesting working method and it would be really nice to have a
fix on it as the current result is more then uncomfortable. But if at
least the GUI could communicate this also would be more than nothing.
Thanks for your attention and efforts also in advance!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to seahorse in Ubuntu.
https://bugs.launchpad.net/bugs/1577198
Title:
Imported gpg keys do not show up in Seahorse 3.18.0
Status in seahorse:
New
Status in seahorse package in Ubuntu:
Triaged
Bug description:
After clean install of Ubuntu-Gnome 16.04 LTS I tried to import all my
previous exported gpg keys. Although it seems the keys are imported,
they do not show up in seahorse (Passwords and Keys). Also Evolution
did not find to proper keys to decrypt messages.
It seems however that the keys have been imported under gpg1 in stead
of gpg2. This can also be confirmed with the list command (gpg --list-
key and gpg2 -- list-keys).
Importing all keys by command (gpg2 --import Multiple_Keys.asc) seems
to work.
See also the same problem already reported by Andreas Happe on:
https://www.snikt.net/blog/2016/02/27/evolution-seahorse-gpg-gpg2-woes/
To manage notifications about this bug go to:
https://bugs.launchpad.net/seahorse/+bug/1577198/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826159] Re: gsd-print-notifications assert failure: free(): invalid pointer
I seem to be getting both IPv4 & IPv6 with same hostname, so then printer does
not connect.
I turned off IPv6 and now it works, but have to release it every time.
sudo nano /etc/cups/cups-browsed.conf
Changed to use only IPv4
# IPBasedDeviceURIs IPv4
IPBasedDeviceURIs IPv4
fred@fred-Z170N-focal:~$ apt show cups
Package: cups
Version: 2.3.1-9ubuntu1
Priority: optional
https://github.com/OpenPrinting/cups-filters/issues/22
https://github.com/lathiat/avahi/issues/125
** Bug watch added: github.com/OpenPrinting/cups-filters/issues #22
https://github.com/OpenPrinting/cups-filters/issues/22
** Bug watch added: github.com/lathiat/avahi/issues #125
https://github.com/lathiat/avahi/issues/125
--
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/1826159
Title:
gsd-print-notifications assert failure: free(): invalid pointer
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Bug description:
This problem occurs since upgrade to disco dingo. Have not seen this
in earlier releases. It seems to be related to printers in the gnome
settings.
janw-LIFEBOOK-AH532-G21{janw}(79)% lsb_release -rd
Description: Ubuntu 19.04
Release: 19.04
apt-cache policy gnome-settings-daemon
gnome-settings-daemon:
Installerad: 3.32.0-1ubuntu1
Kandidat:3.32.0-1ubuntu1
Versionstabell:
*** 3.32.0-1ubuntu1 500
500 http://se.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gnome-settings-daemon 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AssertionMessage: free(): invalid pointer
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 23 22:16:13 2019
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-print-notifications
InstallationDate: Installed on 2018-02-20 (427 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-print-notifications
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=sv_SE.UTF-8
SHELL=/bin/tcsh
Signal: 6
SourcePackage: gnome-settings-daemon
StacktraceTop:
__libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f247b810952
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
malloc_printerr (str=str@entry=0x7f247b80ea9b "free(): invalid pointer") at
malloc.c:5352
_int_free (av=, p=, have_lock=)
at malloc.c:4181
()
g_list_foreach () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gsd-print-notifications assert failure: free(): invalid pointer
UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
mtime.conffile..etc.apport.crashdb.conf: 2019-04-24T11:16:47.806271
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1826159/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869059] [NEW] Button 2 of my ThinkPad X1 Yoga's stylus is not detected
Public bug reported: This also happened on Eoan, but I never had the chance to report the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwacom2 1.1-2build3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Mar 25 13:12:20 2020 DistUpgraded: 2020-03-21 19:59:50,804 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8324, 5.3.0-42-generic, x86_64: installed backport-iwlwifi, 8324, 5.4.0-18-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics [17aa:2292] InstallationDate: Installed on 2020-01-19 (66 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20SA0002US ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7 SourcePackage: libwacom UpgradeStatus: Upgraded to focal on 2020-03-21 (3 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: libwacom (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal has-workaround reproducible single-occurrence ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1869059 Title: Button 2 of my ThinkPad X1 Yoga's stylus is not detected Status in libwacom package in Ubuntu: New Bug description: This also happened on Eoan, but I never had the chance to report the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwacom2 1.1-2build3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Mar 25 13:12:20 2020 DistUpgraded: 2020-03-21 19:59:50,804 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8324, 5.3.0-42-generic, x86_64: installed backport-iwlwifi, 8324, 5.4.0-18-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics [17aa:2292] InstallationDate: Installed on 2020-01-19 (66 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20SA0002US ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7 SourcePackage: libwacom UpgradeStatus: Upgraded to focal on 2020-03-21 (3 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Desktop-packages] [Bug 1869022] Re: unity-settings-daemon shipping org.gnome schema
** Branch linked: lp:~laney/unity-settings-daemon/drop-gnome-schema -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1869022 Title: unity-settings-daemon shipping org.gnome schema Status in unity-settings-daemon package in Ubuntu: New Bug description: In com.canonical.unity-settings-daemon.peripherals.wacom we have: ["", "", ""] which is squatting on gnome's namespace, and makes g-s-d's own schema get ignored. I think probably a c+p error so I'll just fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1869022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Hi all, I have the same laptop HP ZBook 15 G6 and my mike is not recognised too. I'm using ubuntu 18.04 kernel version 5.3.0-28-generic, and with the newer kernels my whole sound card is not recognised. If you look at this documentation http://h20195.www2.hp.com/v2/getpdf.aspx/4AA7-6280ENW.pdf page 12 , they say: "11 Audio output via speakers function. Audio input via built-in microphone is currently not functional due to a missing driver. Please check with your distro vendor for the availability of the snd-sof-pci driver in ALSA." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869021] Re: desktop dash search clicking on a snap application leads to error page in software centre
looks similar to bug #1844699 ** Summary changed: - desktop dash search clicking on application leads to error page in software centre + desktop dash search clicking on a snap application leads to error page in software centre -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869021 Title: desktop dash search clicking on a snap application leads to error page in software centre Status in snap-store: New Status in gnome-software package in Ubuntu: New Status in gnome-software source package in Bionic: New Status in gnome-software source package in Eoan: New Status in gnome-software source package in Focal: New Bug description: Reproduction Steps: - search for a snap application you don't have installed in the "dash" - click that snap application - You will be led to an errored page in the software center. It looks "blank" for me - From there you can click back and usually click on the first item, and things are fine. What I would have expected to happen: - when I click the application, it takes me to software center to the application directly This is happening on Bionic with the latest updates, and on Focal as of today (2020-03-25) To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1869021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869021] Re: desktop dash search clicking on application leads to error page in software centre
** Changed in: gnome-software (Ubuntu Focal) Assignee: (unassigned) => Ken VanDine (ken-vandine) ** Changed in: gnome-software (Ubuntu Eoan) Assignee: (unassigned) => Ken VanDine (ken-vandine) ** Changed in: gnome-software (Ubuntu Bionic) Assignee: (unassigned) => Ken VanDine (ken-vandine) ** Changed in: snap-store Assignee: (unassigned) => Ken VanDine (ken-vandine) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869021 Title: desktop dash search clicking on a snap application leads to error page in software centre Status in snap-store: New Status in gnome-software package in Ubuntu: New Status in gnome-software source package in Bionic: New Status in gnome-software source package in Eoan: New Status in gnome-software source package in Focal: New Bug description: Reproduction Steps: - search for a snap application you don't have installed in the "dash" - click that snap application - You will be led to an errored page in the software center. It looks "blank" for me - From there you can click back and usually click on the first item, and things are fine. What I would have expected to happen: - when I click the application, it takes me to software center to the application directly This is happening on Bionic with the latest updates, and on Focal as of today (2020-03-25) To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1869021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869042] Re: all monitor scaling fails due to overlapping monitors
Attaching monitors.xml since it doesn't seem that apport picked it up ** Attachment added: "~/.config/monitors.xml from my system" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+attachment/5341610/+files/monitors.xml -- 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/1869042 Title: all monitor scaling fails due to overlapping monitors Status in mutter package in Ubuntu: New Bug description: After an upgrade with focal-proposed this morning, I am unable to set any scaling for any of my monitors without the monitor turning blank for 15 seconds and reverting to 100% scaling. I am using X11 with gnome and proprietary nvidia drivers on Focal. I have 3 monitors attached, all 4K, and my usual setup is to enable fractional scaling, and set all 3 monitors to 150% scaling. Now however, I cannot change the monitors to use any scaling, and even if I disconnect 2 of the monitors to only have a single monitor I still cannot use scaling. Finally note I am just using the Settings window, I haven't fiddled with xrandr at all manually. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:24:05 2020 InstallationDate: Installed on 2019-07-05 (264 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869042] [NEW] all monitor scaling fails due to overlapping monitors
Public bug reported: After an upgrade with focal-proposed this morning, I am unable to set any scaling for any of my monitors without the monitor turning blank for 15 seconds and reverting to 100% scaling. I am using X11 with gnome and proprietary nvidia drivers on Focal. I have 3 monitors attached, all 4K, and my usual setup is to enable fractional scaling, and set all 3 monitors to 150% scaling. Now however, I cannot change the monitors to use any scaling, and even if I disconnect 2 of the monitors to only have a single monitor I still cannot use scaling. Finally note I am just using the Settings window, I haven't fiddled with xrandr at all manually. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:24:05 2020 InstallationDate: Installed on 2019-07-05 (264 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1869042 Title: all monitor scaling fails due to overlapping monitors Status in mutter package in Ubuntu: New Bug description: After an upgrade with focal-proposed this morning, I am unable to set any scaling for any of my monitors without the monitor turning blank for 15 seconds and reverting to 100% scaling. I am using X11 with gnome and proprietary nvidia drivers on Focal. I have 3 monitors attached, all 4K, and my usual setup is to enable fractional scaling, and set all 3 monitors to 150% scaling. Now however, I cannot change the monitors to use any scaling, and even if I disconnect 2 of the monitors to only have a single monitor I still cannot use scaling. Finally note I am just using the Settings window, I haven't fiddled with xrandr at all manually. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:24:05 2020 InstallationDate: Installed on 2019-07-05 (264 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1869042/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869035] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of packag
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869035 Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 Status in pulseaudio package in Ubuntu: New Bug description: i wanted to install wine 5.0 and there is errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.22 Architecture: amd64 Date: Wed Mar 25 16:57:57 2020 DuplicateSignature: package:libpulse0:(not installed) Unpacking libpulse0:i386 (1:8.0-0ubuntu3.10) ... dpkg: error processing archive /var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3.10_i386.deb (--unpack): trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 InstallationDate: Installed on 2017-09-28 (908 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1869035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869035] Re: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of packag
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1869035 Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 Status in pulseaudio package in Ubuntu: New Bug description: i wanted to install wine 5.0 and there is errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpulse0 (not installed) ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.22 Architecture: amd64 Date: Wed Mar 25 16:57:57 2020 DuplicateSignature: package:libpulse0:(not installed) Unpacking libpulse0:i386 (1:8.0-0ubuntu3.10) ... dpkg: error processing archive /var/cache/apt/archives/libpulse0_1%3a8.0-0ubuntu3.10_i386.deb (--unpack): trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 ErrorMessage: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 InstallationDate: Installed on 2017-09-28 (908 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: pulseaudio Title: package libpulse0 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/pulse/client.conf', which is different from other instances of package libpulse0:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1869035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868925] Re: Workspaces not spanning displays
*** This bug is a duplicate of bug 1868911 *** https://bugs.launchpad.net/bugs/1868911 Yes, I believe it did appear in the last week. -- 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/1868925 Title: Workspaces not spanning displays Status in gnome-shell package in Ubuntu: New Bug description: Windows are not spanning displays. When in the GNOME overview (not actually sure what it is called, when you press the super key it shows you all your windows in the current workspace and shows the various workspaces as well) ONLY the windows in that work space appear, but when you go back to the normal GNOME view the windows not on the primary monitor appear (as if workspaces were set to not span displays). I apologize about my confusing description--I do not know the GNOME terminology. If clarification is needed let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 00:32:02 2020 DisplayManager: gdm3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 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/1868925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
** Tags added: champagne -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Triaged Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
@racb, it’s been committed to the upstream package in Debian; just a sync is needed. ** Package changed: wpasupplicant (Ubuntu) => wpa (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Triaged Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
Speaking of which, it would be great if this patch was dropped: - debian/patches/session-ticket.patch: disable the TLS Session Ticket extension to fix auth with 802.1x PEAP on some hardware. This has been superseded by upstream changes a couple of releases ago and is no longer needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Triaged Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867908] [NEW] Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
You have been subscribed to a public bug: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. ** Affects: wpa (Ubuntu) Importance: Undecided Status: Triaged ** Tags: patch -- Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length https://bugs.launchpad.net/bugs/1867908 You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa 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 1869021] Re: desktop dash search clicking on application leads to error page in software centre
** Also affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: gnome-software (Ubuntu Eoan) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869021 Title: desktop dash search clicking on application leads to error page in software centre Status in snap-store: New Status in gnome-software package in Ubuntu: New Status in gnome-software source package in Bionic: New Status in gnome-software source package in Eoan: New Status in gnome-software source package in Focal: New Bug description: Reproduction Steps: - search for a snap application you don't have installed in the "dash" - click that snap application - You will be led to an errored page in the software center. It looks "blank" for me - From there you can click back and usually click on the first item, and things are fine. What I would have expected to happen: - when I click the application, it takes me to software center to the application directly This is happening on Bionic with the latest updates, and on Focal as of today (2020-03-25) To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1869021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868505] Re: Only snaps are shown - no apps from the archive
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1868505 Title: Only snaps are shown - no apps from the archive Status in gnome-software package in Ubuntu: Confirmed Bug description: Using 21 March 20.04 Ubuntu Budgie daily - minimal install The only applications shown on the front page are snaps - cannot search or show for any archive apps. launching gnome-software from the command line I see 22:53:28:0287 XbSilo xb_builder_ensure: assertion 'error == NULL || *error == NULL' failed 22:53:28:0302 Gs enabled plugins: desktop-categories, fwupd, os-release, packagekit, packagekit-local, packagekit-offline, packagekit-proxy, packagekit-refine-repos, packagekit-refresh, packagekit-upgrade, packagekit-url-to-app, desktop-menu-path, hardcoded-blacklist, modalias, odrs, packagekit-refine, rewrite-resource, snap, packagekit-history, provenance, systemd-updates, generic-updates, provenance-license, icons, key-colors, key-colors-metadata 22:53:28:0302 Gs disabled plugins: dpkg, dummy, repos, appstream 22:53:31:0903 Gs Only 0 apps for recent list, hiding 22:53:32:0165 GLib g_variant_new_variant: assertion 'value != NULL' failed 22:53:32:0165 GLib g_variant_new_variant: assertion 'value != NULL' failed 22:53:32:0166 Gs not GsPlugin error g-io-error-quark:35: Invalid string value converting to GVariant 22:53:32:0167 Gs not handling error failed for action refine: Invalid string value converting to GVariant So why are dpkg, dummy, repos, appstream disabled? How can they be enabled? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sun Mar 22 22:56:40 2020 InstallationDate: Installed on 2020-03-21 (1 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200320) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1868505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869022] [NEW] unity-settings-daemon shipping org.gnome schema
Public bug reported: In com.canonical.unity-settings-daemon.peripherals.wacom we have: ["", "", ""] which is squatting on gnome's namespace, and makes g-s-d's own schema get ignored. I think probably a c+p error so I'll just fix it. ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1869022 Title: unity-settings-daemon shipping org.gnome schema Status in unity-settings-daemon package in Ubuntu: New Bug description: In com.canonical.unity-settings-daemon.peripherals.wacom we have: ["", "", ""] which is squatting on gnome's namespace, and makes g-s-d's own schema get ignored. I think probably a c+p error so I'll just fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1869022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1866228] Re: Gnome shell extensions are badly broken
Hi, Upgrading was not an option, the broken system was removed, but I did a full os upgrade, and the "bundled" extensions seems to work. I filed another report via the crash detector, it seems that additional packages are needed to configure the extensions. Also a bunch of extensions are not available for 3.36, but that's someone else's job. Thanks for the followup, and for the work. gj On Wed, 25 Mar 2020 at 10:01, Daniel van Vugt wrote: > > Thanks Rocko. > > Gipsz, please update your system: > > sudo apt update > sudo apt full-upgrade > > and then reboot. Then tell us which one (if any) of the issues you > mentioned you would like this bug to be about. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1866228 > > Title: > Gnome shell extensions are badly broken > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Hi, > > After an upgrade this morning, the following things are not working: > - Earlier the Application key brought up something called "Activities", > which happens now via ApplicationA or SuperA, the microsoft key > - I can not find and search for extensions in the "Software" application. > There are just a few addons/extensions, gstreamer ones, fonts and some input > - any attempt at removing an installed extension results in a "you have no > permission" error, without asking for a password. Apparently gnome-shell is > crashing in the background, i'll attach logs if the tool does not. > - The Tweak app shows a warning triangle next to the "Dash to panel" > extension, by clicking on it the "Extension" thing starts up which shows > nothing. > - If I install the dash-to-panel extension from a package the top bar does > not appears properly, the icons, workplace switcher etc all crumpled into the > top left corne,r overlapping each other, thus being mostly unusable. > > I think that the extensions are not yet upgraded to gnome-shell 3.35, > but I have no way to check it. I also have no trivial way to downgrade > gnome shell to 3.34. > > Please advise. > > Thanks, > > tg > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-shell 3.35.91-1ubuntu2 > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > Uname: Linux 5.4.0-14-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu18 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Thu Mar 5 19:59:26 2020 > DisplayManager: gdm3 > InstallationDate: Installed on 2020-01-19 (46 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 > SourcePackage: gnome-shell > UpgradeStatus: Upgraded to focal on 2020-02-26 (7 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866228/+subscriptions -- we do what we must because we can -- 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/1866228 Title: Gnome shell extensions are badly broken Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, After an upgrade this morning, the following things are not working: - Earlier the Application key brought up something called "Activities", which happens now via ApplicationA or SuperA, the microsoft key - I can not find and search for extensions in the "Software" application. There are just a few addons/extensions, gstreamer ones, fonts and some input - any attempt at removing an installed extension results in a "you have no permission" error, without asking for a password. Apparently gnome-shell is crashing in the background, i'll attach logs if the tool does not. - The Tweak app shows a warning triangle next to the "Dash to panel" extension, by clicking on it the "Extension" thing starts up which shows nothing. - If I install the dash-to-panel extension from a package the top bar does not appears properly, the icons, workplace switcher etc all crumpled into the top left corne,r overlapping each other, thus being mostly unusable. I think that the extensions are not yet upgraded to gnome-shell 3.35, but I have no way to check it. I also have no trivial way to downgrade gnome shell to 3.34. Please advise. Thanks, tg ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 19:59:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-19 (46 days ago) InstallationMedia:
[Desktop-packages] [Bug 1868944] Re: cups-pk-helper-mechanism crashed with signal 5
For me the problem is that for me the printer detection when clicking "Add" in the g-c-c Printers section works correctly. I do not get a crash pop-up and I get a list of available printers. If you use system-config-printer and try to add a print queue with it, does it work? Or do you also get a crash? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-pk-helper in Ubuntu. https://bugs.launchpad.net/bugs/1868944 Title: cups-pk-helper-mechanism crashed with signal 5 Status in cups-pk-helper package in Ubuntu: Incomplete Bug description: Crashed during printer discovery. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-pk-helper 0.2.6-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Wed Mar 25 11:01:10 2020 ExecutablePath: /usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism InstallationDate: Installed on 2014-07-15 (2080 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) ProcCmdline: /usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism ProcEnviron: Signal: 5 SourcePackage: cups-pk-helper StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-pk-helper-mechanism crashed with signal 5 UpgradeStatus: Upgraded to focal on 2018-03-24 (731 days ago) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-pk-helper/+bug/1868944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868116] Re: QEMU monitor no longer works
same seems to happen on Fedora 32. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1868116 Title: QEMU monitor no longer works Status in QEMU: New Status in qemu package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: New Bug description: Repro: VTE $ meson _build && ninja -C _build && ninja -C _build install qemu: $ ../configure --python=/usr/bin/python3 --disable-werror --disable-user --disable-linux-user --disable-docs --disable-guest-agent --disable-sdl --enable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt --disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi --disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir --disable-seccomp --disable-glusterfs --disable-tpm --disable-numa --disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs --disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma --disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock --disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user --disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs --disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat --disable-qed --disable-parallels --disable-sheepdog --disable-avx2 --disable-nettle --disable-gnutls --disable-capstone --disable-tools --disable-libpmem --disable-iconv --disable-cap-ng $ make Test: $ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH ./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive media=cdrom,file=http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso - switch to monitor with CTRL+ALT+2 - try to enter something Affects head of both usptream git repos. --- original bug --- It was observed that the QEMU console (normally accessible using Ctrl+Alt+2) accepts no input, so it can't be used. This is being problematic because there are cases where it's required to send commands to the guest, or key combinations that the host would grab (as Ctrl-Alt-F1 or Alt-F4). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu 1:4.2-3ubuntu2 Uname: Linux 5.6.0-rc6+ x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 12:16:31 2020 Dependencies: InstallationDate: Installed on 2017-06-13 (1009 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND qemu-system-x86 Sl+ 1000 1000 34275 25235 29.2 qemu-system-x86_64 -m 4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel kvm -device nec-usb-xhci -serial vc -serial stdio -hda /home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio kvm-nx-lpage-re S0 0 34284 2 0.0 [kvm-nx-lpage-re] kvm-pit/34275 S0 0 34286 2 0.0 [kvm-pit/34275] MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 zswap.enabled=1 zswap.zpool=z3fold resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 SourcePackage: qemu UpgradeStatus: Upgraded to focal on 2019-12-22 (87 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1868116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868990] Re: Various actions produce images of applications running on all work-spaces on the current work-space
Copy/paste fail, I meant gnome-shell 3.36.0-2ubuntu1. -- 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/1868990 Title: Various actions produce images of applications running on all work- spaces on the current work-space Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 20.04 with two displays and four static workspaces. After upgrading various GNOME components to version 3.36.0-2ubuntu1 I'm seeing the following with several applications open of four desktops: 1) 'Alt-F2 r ' restarts GNOME Shell but displays an image of all currently running applications on the current desktop. Moving to another desktop corrects the problem. Similar to bug 1819890 which was closed as fixed for this release. 2) With Thunderbird running on 'Workspace 2', any attempt to open a menu produces an image of applications running on other desktops underneath Thunderbird. 3) Above also applies when using Libreoffice and HomeBank so probably applies to any application that displays a menubar. I'm unsure of which package to report this against so reporting against mutter and adding gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:42:05 2020 InstallationDate: Installed on 2019-05-17 (313 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2019-11-08 (137 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868990] Re: Various actions produce images of applications running on all work-spaces on the current work-space
I'm hitting this too with the last upgrade that brought in gnome-shell 3.4.1-0ubuntu2. Happens both in Xorg and Wayland sessions. ** Tags added: champagne -- 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/1868990 Title: Various actions produce images of applications running on all work- spaces on the current work-space Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 20.04 with two displays and four static workspaces. After upgrading various GNOME components to version 3.36.0-2ubuntu1 I'm seeing the following with several applications open of four desktops: 1) 'Alt-F2 r ' restarts GNOME Shell but displays an image of all currently running applications on the current desktop. Moving to another desktop corrects the problem. Similar to bug 1819890 which was closed as fixed for this release. 2) With Thunderbird running on 'Workspace 2', any attempt to open a menu produces an image of applications running on other desktops underneath Thunderbird. 3) Above also applies when using Libreoffice and HomeBank so probably applies to any application that displays a menubar. I'm unsure of which package to report this against so reporting against mutter and adding gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:42:05 2020 InstallationDate: Installed on 2019-05-17 (313 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2019-11-08 (137 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868990] Re: Various actions produce images of applications running on all work-spaces on the current work-space
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868990 Title: Various actions produce images of applications running on all work- spaces on the current work-space Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 20.04 with two displays and four static workspaces. After upgrading various GNOME components to version 3.36.0-2ubuntu1 I'm seeing the following with several applications open of four desktops: 1) 'Alt-F2 r ' restarts GNOME Shell but displays an image of all currently running applications on the current desktop. Moving to another desktop corrects the problem. Similar to bug 1819890 which was closed as fixed for this release. 2) With Thunderbird running on 'Workspace 2', any attempt to open a menu produces an image of applications running on other desktops underneath Thunderbird. 3) Above also applies when using Libreoffice and HomeBank so probably applies to any application that displays a menubar. I'm unsure of which package to report this against so reporting against mutter and adding gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:42:05 2020 InstallationDate: Installed on 2019-05-17 (313 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2019-11-08 (137 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869013] [NEW] [Regression] Provide bigger sizes of all legacy icons
Public bug reported: Steps to reproduce the problem: 1. Install transmission, geany, pdfarranger, meld 2. Look at the tiny toolbar icons 3. Switch between Yaru and Humanity icon themes 4. Observe the icon size difference between Yaru and Humanity See the attached screencast. Notice that Humanity provides bigger icons, which look much better. Notice that Transmission uses a mix of Humanity and legacy Yaru icons, which does not look nice nor consistent. In my humble opinion, Humanity icons look much better. Software that presents the issue: All gtk2 and gtk3 apps, which don't use symbolic icons. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-icon 20.04.4 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 15:36:40 2020 Dependencies: InstallationDate: Installed on 2020-01-21 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru Importance: Unknown Status: Unknown ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Yaru-legacy_Humanity.webm" https://bugs.launchpad.net/bugs/1869013/+attachment/5341512/+files/Yaru-legacy_Humanity.webm ** Bug watch added: github.com/ubuntu/yaru/issues #2108 https://github.com/ubuntu/yaru/issues/2108 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/2108 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1869013 Title: [Regression] Provide bigger sizes of all legacy icons Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: New Bug description: Steps to reproduce the problem: 1. Install transmission, geany, pdfarranger, meld 2. Look at the tiny toolbar icons 3. Switch between Yaru and Humanity icon themes 4. Observe the icon size difference between Yaru and Humanity See the attached screencast. Notice that Humanity provides bigger icons, which look much better. Notice that Transmission uses a mix of Humanity and legacy Yaru icons, which does not look nice nor consistent. In my humble opinion, Humanity icons look much better. Software that presents the issue: All gtk2 and gtk3 apps, which don't use symbolic icons. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-icon 20.04.4 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 15:36:40 2020 Dependencies: InstallationDate: Installed on 2020-01-21 (63 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1869013/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868990] Re: Various actions produce images of applications running on all work-spaces on the current work-space
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868990 Title: Various actions produce images of applications running on all work- spaces on the current work-space Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 20.04 with two displays and four static workspaces. After upgrading various GNOME components to version 3.36.0-2ubuntu1 I'm seeing the following with several applications open of four desktops: 1) 'Alt-F2 r ' restarts GNOME Shell but displays an image of all currently running applications on the current desktop. Moving to another desktop corrects the problem. Similar to bug 1819890 which was closed as fixed for this release. 2) With Thunderbird running on 'Workspace 2', any attempt to open a menu produces an image of applications running on other desktops underneath Thunderbird. 3) Above also applies when using Libreoffice and HomeBank so probably applies to any application that displays a menubar. I'm unsure of which package to report this against so reporting against mutter and adding gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 11:42:05 2020 InstallationDate: Installed on 2019-05-17 (313 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2019-11-08 (137 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868944] Re: cups-pk-helper-mechanism crashed with signal 5
Yes, it's via the printer section of gnome-control-center and it always crashes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-pk-helper in Ubuntu. https://bugs.launchpad.net/bugs/1868944 Title: cups-pk-helper-mechanism crashed with signal 5 Status in cups-pk-helper package in Ubuntu: Incomplete Bug description: Crashed during printer discovery. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-pk-helper 0.2.6-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 Date: Wed Mar 25 11:01:10 2020 ExecutablePath: /usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism InstallationDate: Installed on 2014-07-15 (2080 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) ProcCmdline: /usr/lib/x86_64-linux-gnu/cups-pk-helper-mechanism ProcEnviron: Signal: 5 SourcePackage: cups-pk-helper StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: cups-pk-helper-mechanism crashed with signal 5 UpgradeStatus: Upgraded to focal on 2018-03-24 (731 days ago) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-pk-helper/+bug/1868944/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869012] [NEW] Xorg freeze
Public bug reported: Well, that is maybe a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1868396 More crash info in : https://errors.ubuntu.com/oops/4dd7bfc4-6ea1-11ea- 98a4-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 15:04:06 2020 DistUpgraded: 2019-11-04 11:06:46,434 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: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.3.0-42-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since a couple weeks or more GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2019-04-26 (333 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2262d308-663c-47c3-9e75-b34611c8df1d ro nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-11-04 (142 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan freeze third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1869012 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Well, that is maybe a duplicate of https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1868396 More crash info in : https://errors.ubuntu.com/oops/4dd7bfc4-6ea1 -11ea-98a4-fa163e102db1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.6 Architecture:
[Desktop-packages] [Bug 1868396] Re: crashes or freezes with nividia/xorg
New crash report : https://errors.ubuntu.com/oops/4dd7bfc4-6ea1-11ea- 98a4-fa163e102db1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1868396 Title: crashes or freezes with nividia/xorg Status in xorg-server package in Ubuntu: New Bug description: I have plugged in my Dell precision 5530 laptop a 4k HDMI screen. Using it with 200% zoom makes xorg crash. I have used proprietary 430, and changed to recommended proprietary 435 nvidia driver. As the system was still very unstable (no to say unusable) I had a go with 440 from ppa. I also ensured that my system was up to date doing a sudo apt-get update and upgrade. I was suprised to discover a few packages that needed an upgrade although I had previously used the Software Updater tool. Maybe I was doing something wrong. Anyway, with these updates and the newer 440 driver, I have successfully worked a day (sparsely) without problem, and using only 100% zoom. As a test, I decided to try to set the zoom to 200% (through devices > display, and I have only the external display enabled). After several minutes, I clicked on the « full screen » icon to maximize a shell, and the PC froze. It was so close to my change in the zoom ratio, that I suspect this is related. dmesg shew me that NVRM had a problem : [97501.301998] NVRM: GPU at PCI::01:00: GPU-dee28f75-4083-96a8-1a0b-491b6109101a [97501.302000] NVRM: Xid (PCI::01:00): 32, pid=493, Channel ID 0018 intr 0004 [97501.302134] NVRM: Xid (PCI::01:00): 32, pid=2052, Channel ID 0018 intr 0020 [97501.317307] NVRM: Xid (PCI::01:00): 69, pid=902, Class Error: ChId 001b, Class 902d, Offset 0250, Data 55d3, ErrorCode 000c pid 493 is gone pid 2052 is xorg stan 2052 2050 1 mars20 tty200:25:38 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 pid 902 is nvidia driver root 902 2 0 mars20 ? 00:02:59 [irq/163-nvidia] ppid 2052 is 2050 : stan 2050 2004 0 mars20 tty200:00:00 /usr/lib/gdm3/gdm-x-session --run-script env GNOME_SHELL_SESSION_MODE=ubuntu /usr/bin/gnome-session --systemd --session=ubuntu After such an event, the previous days, the system became unstable, and I have got problems with other devices such as audio and network. If I run the manufacturer self-check test, everything is fine. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 18:36:53 2020 DistUpgraded: 2019-11-04 11:06:46,434 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: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.3.0-42-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-42-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:087d] Subsystem: Dell GP107GLM [Quadro P2000 Mobile] [1028:087d] InstallationDate: Installed on 2019-04-26 (329 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Precision 5530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=2262d308-663c-47c3-9e75-b34611c8df1d ro nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-11-04 (138 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version:
[Desktop-packages] [Bug 1868999] Re: Characters in the web browser do not work
Thanks for the feedback. Feel free to re-open if the problem surfaces again. ** Changed in: firefox (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/1868999 Title: Characters in the web browser do not work Status in firefox package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Bug description: I updated my ubuntu 20.04 (03-25-2020) and I can't write in Firefox or Chrome. In all other GNOME applications it works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 Uname: Linux 5.4.27-050427-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1725 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 10:03:04 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (478 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.0.1 dev enx000ec6c82c3f proto dhcp metric 100 169.254.0.0/16 dev enx000ec6c82c3f scope link metric 1000 192.168.0.0/24 dev enx000ec6c82c3f proto kernel scope link src 192.168.0.101 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=74.0/20200309095159 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (478 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
Also reported to Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954885 ** Bug watch added: Debian Bug tracker #954885 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954885 ** Also affects: libmtp (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954885 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in libmtp package in Debian: Unknown Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868999] Re: Characters in the web browser do not work
** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868999 Title: Characters in the web browser do not work Status in firefox package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Invalid Bug description: I updated my ubuntu 20.04 (03-25-2020) and I can't write in Firefox or Chrome. In all other GNOME applications it works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 Uname: Linux 5.4.27-050427-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1725 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 10:03:04 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (478 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.0.1 dev enx000ec6c82c3f proto dhcp metric 100 169.254.0.0/16 dev enx000ec6c82c3f scope link metric 1000 192.168.0.0/24 dev enx000ec6c82c3f proto kernel scope link src 192.168.0.101 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=74.0/20200309095159 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (478 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] nvidia-settings.txt
apport information ** Attachment added: "nvidia-settings.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341484/+files/nvidia-settings.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341485/+files/xdpyinfo.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341477/+files/ProcCpuinfoMinimal.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341478/+files/ProcInterrupts.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] Re: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73
apport information ** Tags added: apport-collected has-workaround reproducible ubuntu ** Description changed: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' - So it's a bug for me but one I can work around and should be fixed - before 20.04 goes live. + So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. + --- + ProblemType: Bug + .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' + .proc.driver.nvidia.registry: Binary: "" + .proc.driver.nvidia.suspend: suspend hibernate resume + .proc.driver.nvidia.suspend_depth: default modeset uvm + .proc.driver.nvidia.version: + NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 + GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) + ApportVersion: 2.20.11-0ubuntu21 + Architecture: amd64 + BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' + CompositorRunning: None + CurrentDesktop: ubuntu:GNOME + DistUpgraded: Fresh install + DistroCodename: focal + DistroRelease: Ubuntu 20.04 + DistroVariant: ubuntu + DkmsStatus: + nvidia, 440.64, 5.4.0-14-generic, x86_64: installed + nvidia, 440.64, 5.4.0-18-generic, x86_64: installed + ExtraDebuggingInterest: Yes + GraphicsCard: + NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) +Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] + InstallationDate: Installed on 2020-03-21 (3 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) + MachineType: LENOVO 20QRCTO1WW + NonfreeKernelModules: nvidia_modeset nvidia + Package: xorg 1:7.7+19ubuntu14 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 + Tags: focal ubuntu reproducible has-workaround + Uname: Linux 5.4.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/08/2020 + dmi.bios.vendor: LENOVO + dmi.bios.version: N2NET35W (1.20 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20QRCTO1WW + dmi.board.vendor: LENOVO + dmi.board.version: SDK0Q40104 WIN + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: None + dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad P73 + dmi.product.name: 20QRCTO1WW + dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 + dmi.product.version: ThinkPad P73 + dmi.sys.vendor: LENOVO + version.compiz: compiz N/A + version.libdrm2: libdrm2 2.4.100-4 + version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 + version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 + version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A + version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Attachment added: ".proc.driver.nvidia.params.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341466/+files/.proc.driver.nvidia.params.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0:
[Desktop-packages] [Bug 1868474] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341482/+files/XorgLogOld.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341483/+files/Xrandr.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341481/+files/XorgLog.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341480/+files/UdevDb.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341479/+files/ProcModules.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341473/+files/Lsusb-v.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] NvidiaBugReportLog.txt
apport information ** Attachment added: "NvidiaBugReportLog.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341475/+files/NvidiaBugReportLog.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341474/+files/MonitorsUser.xml.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341476/+files/ProcCpuinfo.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341471/+files/Lsusb.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341472/+files/Lsusb-t.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341470/+files/Lspci.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868474] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1868474/+attachment/5341469/+files/DpkgLog.txt -- 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/1868474 Title: 20.04 Xorg doesn't detect/load Elantech mouse driver on Lenovo P73 Status in xorg package in Ubuntu: Incomplete Bug description: The installation scripts loads the correct drivers so the touch pad and pointer works during the install. However after the install neither work. I've worked around it by using a wireless USB from Vilros for mouse input while logging in. Then issuing (found on https://askubuntu.com/questions/1143663): sudo 'echo -n "elantech">/sys/bus/serio/devices/serio1/protocol' So it's a bug for me but one I can work around and should be fixed before 20.04 goes live. --- ProblemType: Bug .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-18-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [10de:1eb5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU104GLM [Quadro RTX 5000 Mobile / Max-Q] [17aa:229b] InstallationDate: Installed on 2020-03-21 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) MachineType: LENOVO 20QRCTO1WW NonfreeKernelModules: nvidia_modeset nvidia Package: xorg 1:7.7+19ubuntu14 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=d38adcbd-2ba3-4d84-84b7-388b5f55daa7 ro psmouse.elantech_smbus=0 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Tags: focal ubuntu reproducible has-workaround Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/08/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET35W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0Q40104 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2NET35W(1.20):bd01/08/2020:svnLENOVO:pn20QRCTO1WW:pvrThinkPadP73:rvnLENOVO:rn20QRCTO1WW:rvrSDK0Q40104WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P73 dmi.product.name: 20QRCTO1WW dmi.product.sku: LENOVO_MT_20QR_BU_Think_FM_ThinkPad P73 dmi.product.version: ThinkPad P73 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
