[Desktop-packages] [Bug 1896842] Re: Update simple-scan in Ubuntu 20.04 to 3.36.6 (fixes cannot scan a page using EPSON V39 scanner)
** Summary changed:
- simple-scan cannot scan a page using EPSON V39 scanner
+ Update simple-scan in Ubuntu 20.04 to 3.36.6 (fixes cannot scan a page using
EPSON V39 scanner)
** Tags added: focal
** Description changed:
+ [ Description ]
+
+ GNOME upstream have released a new stable version of simple-scan - fixes
+ this and other issues, existing in older simple-scan 3.36.3, which is
+ currently in Ubuntu 20.04 LTS (focal):
+
+ Overview of changes in simple-scan 3.36.4
+
+ * Fix color scanning for Brother ADS 2200 and 2700 sane backend.
+ * Updated translations.
+
+ Overview of changes in simple-scan 3.36.6
+
+ * Display error message if simple-scan is unable to open simple-scan.log
+ * Fix scanning on Epson devices, when Automatic Page Size is enabled.
+
+ [ QA ]
+
+ GNOME has a micro release exception that covers this package.
+
+ https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
+
+ So we don't need to verify the fixes explicitly.
+
+ original bug report
ishabalov@black:~$ simple-scan --debug
[+0.00s] DEBUG: simple-scan.vala:1720: Starting simple-scan 3.36.3, PID=38292
[+0.00s] DEBUG: unsetenv() is not thread-safe and should not be used after
threads are created
[+0.01s] DEBUG: _g_io_module_get_default: Found default implementation dconf
(DConfSettingsBackend) for ‘gsettings-backend’
[+0.09s] DEBUG: app-window.vala:1906: Loading state from
/home/ishabalov/.cache/simple-scan/state
[+0.09s] DEBUG: app-window.vala:1885: Restoring window to 1351x672 pixels
[+0.17s] DEBUG: scanner.vala:1539: sane_init () -> SANE_STATUS_GOOD
[+0.17s] DEBUG: scanner.vala:1545: SANE version 1.0.29
[+0.17s] DEBUG: scanner.vala:1606: Requesting redetection of scan devices
[+0.17s] DEBUG: scanner.vala:828: Processing request
[+0.56s] DEBUG: app-window.vala:1981: Saving state to
/home/ishabalov/.cache/simple-scan/state
[+8.42s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
[+8.42s] DEBUG: scanner.vala:353: Device:
name="imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0"
vendor="EPSON" model="Epson_Perfection_V39" type=""
[+8.72s] DEBUG: app-window.vala:1981: Saving state to
/home/ishabalov/.cache/simple-scan/state
[+9.90s] DEBUG: simple-scan.vala:1536: Requesting scan at 300 dpi from device
'imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0'
[+9.90s] DEBUG: scanner.vala:1674: Scanner.scan
("imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0",
dpi=300, scan_mode=ScanMode.COLOR, depth=8, type=single, paper_width=0,
paper_height=0, brightness=26, contrast=46, delay=3000ms)
[+9.90s] DEBUG: scanner.vala:828: Processing request
[+10.17s] DEBUG: scanner.vala:889: sane_open
("imagescan:esci:gt-s650:usb:/sys/devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0")
-> SANE_STATUS_GOOD
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (0)
[+10.17s] DEBUG: scanner.vala:760: Option 0: type=int size=4
cap=soft-detect,advanced
- [+10.17s] DEBUG: scanner.vala:763: Description:
+ [+10.17s] DEBUG: scanner.vala:763: Description:
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (1)
[+10.17s] DEBUG: scanner.vala:760: Option 1: name='device-02-general'
title='General' type=group size=0 cap=inactive
[+10.17s] DEBUG: scanner.vala:763: Description: Basic options.
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (2)
[+10.17s] DEBUG: scanner.vala:760: Option 2: name='source' title='Document
Source' type=string size=15 values=["Document Table"] cap=soft-detect
[+10.17s] DEBUG: scanner.vala:763: Description: Document Source
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (3)
[+10.17s] DEBUG: scanner.vala:760: Option 3: name='enable-resampling'
title='Enable Resampling' type=bool size=4 cap=soft-detect,inactive,advanced
[+10.17s] DEBUG: scanner.vala:763: Description: This option provides the
user with a wider range of supported resolutions. Resolutions not supported by
the hardware will be achieved through image processing methods.
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (4)
[+10.17s] DEBUG: scanner.vala:760: Option 4: name='resolution'
title='Resolution' type=int size=4 unit=dpi min=50, max=4800, quant=0
cap=soft-select,soft-detect
[+10.17s] DEBUG: scanner.vala:763: Description: Resolution
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (5)
[+10.17s] DEBUG: scanner.vala:760: Option 5: name='scan-area' title='Scan
Area' type=string size=19 values=["Executive/Portrait", "ISO/A4/Portrait",
"ISO/A5/Portrait", "ISO/A5/Landscape", "ISO/A6/Portrait", "ISO/A6/Landscape",
"JIS/B5/Portrait", "JIS/B6/Portrait", "JIS/B6/Landscape", "Letter/Portrait",
"Manual", "Maximum"] cap=soft-select,soft-detect
[+10.17s] DEBUG: scanner.vala:763: Description: Scan Area
[+10.17s] DEBUG: scanner.vala:910: sane_get_option_descriptor (6)
[+10.17s]
[Desktop-packages] [Bug 1886021] Re: Nautilus slow after upgrade 20.04
@Glen, the issue you are describing is another one and should be reported as a new ticket -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1886021 Title: Nautilus slow after upgrade 20.04 Status in nautilus package in Ubuntu: Invalid Bug description: After I upgraded to 20.04, nautilus is very slow to open (open folder from applications, also, when I need open a file or save it) time nautilus: real 0m54,410s user 0m2,962s sys 0m0,483s Error: Error creating proxy: Errore nel chiamare StartServiceByName per org.gtk.vfs.AfcVolumeMonitor: È stato raggiunto il timeout (g-io-error-quark, 24) RuntimeError: object at 0x7f203826c910 of type ColumnExtension is not initialized Nautilus version 1:3.36.3-0ubuntu1 I tried this solution: https://askubuntu.com/questions/1161928/nautilus-files-app-takes-long-time-to-start-on-ubuntu-18-04 But it doesn't work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2015-11-20 (1690 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Package: nautilus 1:3.36.3-0ubuntu1 PackageArchitecture: amd64 Tags: third-party-packages focal Uname: Linux 5.7.1-050701-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-09 (58 days ago) UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo _MarkForUpload: True usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1886021/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903464] Re: nautilus does not allow selection of files with a frame when enabled list viev
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Please also ensure that you include the release and flavour of Ubuntu that you are using. Thank you! ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1903464 Title: nautilus does not allow selection of files with a frame when enabled list viev Status in nautilus package in Ubuntu: Incomplete Bug description: the problem manifests itself in all versions of the program and in the distribution version 20.04 and 20.10 and older To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1903464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881753] Re: Cannot scan in Photo mode with Brother MFC L3770 CDW
Could you test if this bug with color scan in Photo mode isn't fixed in simple-scan 3.36.4 or newer - I've found this in NEWS file: Overview of changes in simple-scan 3.36.4 * Fix color scanning for Brother ADS 2200 and 2700 sane backend. * Updated translations. Overview of changes in simple-scan 3.37.3 * Improve compression scale which appear during file saving, to be more intuitive. * Fix color scanning for Brother ADS 2200 and 2700 sane backend. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1881753 Title: Cannot scan in Photo mode with Brother MFC L3770 CDW Status in Simple Scan: Unknown Status in simple-scan package in Ubuntu: Confirmed Bug description: Starting simple-scan 3.28.0-0ubuntu1 (Ubuntu 18.04.4), with a Brother MFC L3770 CDW and Brother br* packages installed and configured. - If the Photo mode is selected by default, a scan will be in color (no problem). - From step1, switching to text mode, the scan is monochrome (again no problem). - From step2, switching to Photo mode, all subsequent scans will be monochrome (ARGH ;-)). Looking at simple-scan git history, I found an interesting commit (I did not go with a full git bisect). https://github.com/GNOME/simple-scan/commit/12e9c02a6cccf6b17aada9a26987007eb6d1360d I reproduced the problem on the sha1 preceeding this one. But on this sha1 (and on the current master), the problem is fixed. To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/1881753/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903457] Re: "Allow _executing file as program" has extra underscore
Thank you for your bug report, indeed that's an upstream issue and fixed now in git and should be part of the next version https://gitlab.gnome.org/GNOME/nautilus/-/commit/74e1e609 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1903457 Title: "Allow _executing file as program" has extra underscore Status in nautilus package in Ubuntu: Fix Committed Bug description: Since upgrading to Ubuntu 20.10, I'm seeing a minor typo or mistake in the Permissions tab of the file properties window. It says "Allow _executing file as program" instead of just "Allow executing file as program". For some reason, there is an additional underscore there. To reproduce, open a folder and right-click on any file. Then select "Properties". Go to the "Permissions" tab and read the label of the checkbox after the "Execute" field. I'm using the English (United States) language. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 8 19:57:01 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'initial-size' b'(1144, 721)' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-05-09 (183 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: Upgraded to groovy on 2020-11-08 (0 days ago) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1903457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
*** This bug is a duplicate of bug 1901922 *** https://bugs.launchpad.net/bugs/1901922 ** This bug has been marked a duplicate of bug 1901922 [Lenovo ThinkPad T14 Gen 1] No sound output device on startup -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903224] Re: Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3375 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3375 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3375 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/1903224 Title: Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Package: Xorg or Gnome, not really sure. Problem description: 1. I have set the Launch terminal shortcut in Settings/Keyboard shortcuts to CTRL+`. 2. I invoke the activities overview by pressing SUPER once. 3. I launch a terminal by pressing the newly set CTRL+` shortcut. What happened: two new terminal windows appeared. What is expected: launch only one terminal window. More info: This only happens when a CTRL modifier is used and the key is set to a non function (F1-F12) key. When an ALT or CTRL+ALT shortcut is used, only one window appears, as expected. Expected behaviour: launch only one terminal window while in the activities overview. What happened: two new terminal windows appeared in the activities overview. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1903224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727225] Re: Excessive window snapping while dragging, looks glitchy
** Tags added: hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727225 Title: Excessive window snapping while dragging, looks glitchy Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: Gnome Shell seems to do excessive window snapping while dragging windows. If I drag a window over the top of another, the top of both windows briefly snap together before the window drag continues. To the untrained eye this just looks like a visual glitch in the rendering and an excuse to declare gnome-shell is less smooth than other shells. It's also not useful to snap all such combinations of window edges like that, so I suggest turning some of them off. For example, don't snap the same edges of two windows when one is overlapping the other already. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 15:55:31 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-03 (175 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1727225/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
** Tags removed: fixed-in-3.36.5 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/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 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: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX 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.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 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/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903383] Re: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup
** Tags added: multimonitor -- 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/1903383 Title: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The bug occurs with any XWayland application. I tried VSCode, Chrome, Audacity, Darktable... I have two monitors with a different DPI. One is 4K HiDPI monitor and the second in LowDPI 2K monitor. I can setup 200% scale for a HiDPI monitor and 100% scale for a LowDPI. All native gnome applications are fine. The bug: when I select LowDPI monitor as a primary, XWayland applications stop scaling on a HiDPI monitor. They run 100% scale on both monitors. If I select HiDPI monitor as the primary, XWayland applications scales 200% on both monitors. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 7 12:28:53 2020 InstallationDate: Installed on 2019-11-16 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-05-02 (189 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()
Got this bug after upgrading to 20.10 Using Gnome Shell 3.38.1 and Mutter 3.38.1 Frequent crash in wayland session Especially when pressing save button dialogue gnome-shell[2119]: ** gnome-shell[2119]: St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL) gnome-shell[2119]: Bail out! St:ERROR:../src/st/st-bin.c:206:st_bin_destroy: assertion failed: (priv->child == NULL) gnome-shell[2119]: GNOME Shell crashed with signal 6 gnome-shell[2119]: == Stack trace for context 0x5645ba824140 == gnome-shell[2119]: #0 5645bae046e0 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:234 (d0258b7b> gnome-shell[2119]: #1 7ffcbfc591d0 b self-hosted:225 (1f8f4c1a5d80 @ 273) gnome-shell[2119]: #2 5645bae04648 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:234 (d0258b7b> gnome-shell[2119]: #3 5645bae045b8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:209 (d0258b7b> gnome-shell[2119]: #4 5645bae044b8 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:460 (d0258b7b> gnome-shell[2119]: #5 5645bae04418 i /usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:340 (d0258b7b -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: See also bug 1898910 --- Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-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 /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1599357] Re: [i915] WARN_ON(!encoder->crtc), more warnings and unstable X on 16.04
** Summary changed: - WARN_ON(!encoder->crtc), more warnings and unstable X on 16.04 + [i915] WARN_ON(!encoder->crtc), more warnings and unstable X on 16.04 ** Package changed: xorg (Ubuntu) => linux (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/1599357 Title: [i915] WARN_ON(!encoder->crtc), more warnings and unstable X on 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I installed ubuntu 16.04 on the vintage asus eeepc 701. However, i915 is giving me warnings on dmesg and it is unstable, specially on vt-switch (I cannot go back to X). I'll attach what dmesg shows me. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 6 00:52:20 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Mobile 915GM/GMS/910GML Express Graphics Controller [1043:82d9] Subsystem: ASUSTeK Computer Inc. Mobile 915GM/GMS/910GML Express Graphics Controller [1043:82d9] MachineType: ASUSTeK Computer INC. 701 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-28-generic root=UUID=88e47f5f-2717-42af-a83c-05a041cf9895 ro rootflags=subvol=@ quiet splash forcepae vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0910 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 701 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0910:bd03/03/2008:svnASUSTeKComputerINC.:pn701:pvrx.x:rvnASUSTeKComputerINC.:rn701:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 701 dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jul 6 00:20:43 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1599357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902758] Re: Xorg freeze
*** This bug is a duplicate of bug 1902652 *** https://bugs.launchpad.net/bugs/1902652 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1902652, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1902652 [arm64] [Libre Computer Board AML-S805X-AC] 3D rendering is very slow -- 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/1902758 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: 3D is working by compatibility mode not hardware acceleration. I need fix please ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.19.64+ aarch64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: arm64 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: XFCE Date: Tue Nov 3 17:51:49 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Lspci: ProcEnviron: LANGUAGE=en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.64+ root=UUID=ed29fecf-6335-4caf-989f-7400b169cb82 ro rootflags=subvol=@ noquiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Allwinner sun4i DRM driver" Driver "armsoc" Option "DRI2" "true" EndSection version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1902758/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902931] Re: problem with nvidia on Ubuntu 18.04.5 LTS
Please explain what the problem is in more detail. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1902931 Title: problem with nvidia on Ubuntu 18.04.5 LTS Status in Ubuntu: Incomplete Bug description: I have a recent problem after update my system, but I can't take a real update with otherr distrib' because I'm AMD architecture... Thank's a lot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 4 19:51:30 2020 DistUpgraded: 2019-10-06 10:46:29,388 DEBUG /openCache(), new cache size 61567 DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation C61 [GeForce 7025 / nForce 630a] [1849:03d6] InstallationDate: Installed on 2011-10-18 (3305 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric" - Build i386 LIVE Binary 20111013-11:02 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c040 Logitech, Inc. Corded Tilt-Wheel Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic root=UUID=a9de46df-beb4-429a-8937-c398129042b1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-10-06 (395 days ago) dmi.bios.date: 03/03/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: N68C-S UCC dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/03/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68C-SUCC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Nov 6 22:48:53 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 inputAT Raw Set 2 keyboard KEYBOARD, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1902931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895072] Re: [amdgpu] [nvidia] Resolution problem
[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1895072 Title: [amdgpu] [nvidia] Resolution problem Status in nvidia-graphics-drivers-450 package in Ubuntu: Expired Status in xserver-xorg-video-amdgpu package in Ubuntu: Expired Bug description: Resolution problem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.8.0-050800rc6-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..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 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 10 10:28:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: librealsense2-dkms, 1.3.14: added nvidia, 450.66, 5.4.0-45-generic, x86_64: installed nvidia, 450.66, 5.4.0-47-generic, x86_64: installed nvidia, 450.66, 5.8.0-050800rc6-generic, x86_64: installed GraphicsCard: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU116M [GeForce GTX 1660 Ti Mobile] [1043:17ef] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c5) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:17ef] InstallationDate: Installed on 2020-07-13 (58 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IU_GA401IU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-050800rc6-generic root=UUID=74c7b276-b0a0-4d1c-819b-f883eff6a3ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IU.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IU 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.ec.firmware.release: 3.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IU.212:bd05/08/2020:br5.16:efr3.11:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IU_GA401IU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA401IU_GA401IU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1895072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895072] Re: [amdgpu] [nvidia] Resolution problem
[Expired for nvidia-graphics-drivers-450 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1895072 Title: [amdgpu] [nvidia] Resolution problem Status in nvidia-graphics-drivers-450 package in Ubuntu: Expired Status in xserver-xorg-video-amdgpu package in Ubuntu: Expired Bug description: Resolution problem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.8.0-050800rc6-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..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 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 10 10:28:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: librealsense2-dkms, 1.3.14: added nvidia, 450.66, 5.4.0-45-generic, x86_64: installed nvidia, 450.66, 5.4.0-47-generic, x86_64: installed nvidia, 450.66, 5.8.0-050800rc6-generic, x86_64: installed GraphicsCard: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU116M [GeForce GTX 1660 Ti Mobile] [1043:17ef] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c5) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:17ef] InstallationDate: Installed on 2020-07-13 (58 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IU_GA401IU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-050800rc6-generic root=UUID=74c7b276-b0a0-4d1c-819b-f883eff6a3ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IU.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IU 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.ec.firmware.release: 3.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IU.212:bd05/08/2020:br5.16:efr3.11:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IU_GA401IU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA401IU_GA401IU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1895072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903460] Re: audio output selection not working properly anymore
Please try deleting your local sound configuration:
cd ~/.config
rm -rf pulse
Then log out and log in again. Does the problem still happen after that?
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- audio output selection not working properly anymore
+ Audio keeps coming from HDMI even after switching output to internal or
Bluetooth
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
** Changed in: pulseaudio (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1903460
Title:
Audio keeps coming from HDMI even after switching output to internal
or Bluetooth
Status in gnome-control-center package in Ubuntu:
Incomplete
Status in pulseaudio package in Ubuntu:
Incomplete
Bug description:
I have been using Ubuntu 20.04 since it was released. Suddenly, a few
days ago, the sound device output selection (gnome-control-center >
Sound > Output device) stopped work properly. It is starting as HDMI
by default (it used to be "internal" before the bug, but this is not
the question). The problem is that when i change from HDMI to another
("internal" or bluetooth) output it doesn't work anymore, the sound
keep being outputted by HDMI instead. It only works when i change HDMI
profile to 5.1, then all HDMI profiles just disappear and internal or
bluetooth audio works fine.
I don't know if it's really a bug in gnome-control-center, or i just
blaming the GUI, but I will do what is necessary to find this out.
I hope i can help improve Ubuntu reporting this. Thanks for all
developers!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.4-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 8 15:45:14 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-04-29 (193 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
LANGUAGE=pt_BR:pt:en
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=pt_BR.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1903460/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903448] Re: Starting
Thanks for the bug report. It looks like the 'nouveau' kernel driver is crashing on start-up so that's the first thing to investigate, or avoid. According to the Nvidia web site only version 340 of the official Nvidia driver supports your GPU. Please open the 'Additional Drivers' app and try to install that. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Starting + Starting takes a very long time -- 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/1903448 Title: Starting takes a very long time Status in Ubuntu: Incomplete Bug description: Take very long time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Nov 8 16:47:36 2020 DistUpgraded: 2020-10-18 17:57:46,055 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Lapsiprosessin “./xorg_fix_proprietary.py” käynnistäminen epäonnistui (Tiedostoa tai hakemistoa ei ole) (8)) DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86M [Quadro NVS 135M] [10de:042b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G86M [Quadro NVS 135M] [1028:01f9] InstallationDate: Installed on 2020-02-17 (264 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude D630 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=d79ab05c-0324-4961-8e58-27cfbf47e11a ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-18 (20 days ago) dmi.bios.date: 01/04/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0WM416 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd01/04/2010:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0WM416:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1903448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903446] Re: the process gnome-shell stay active for ever, and take 6-7 perc. of resorce, without apparent reason
Thanks for the bug report. Since we find so many bugs are caused by extensions, that's the first thing we need to look at. And you have a lot: desktop-icons@csoriano', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu- d...@ubuntu.com', 'walkpa...@walkpaper.blinkbp.github.com', 'apps-menu @gnome-shell-extensions.gcampax.github.com', 'places-menu@gnome-shell- extensions.gcampax.github.com', 'screenshot-window-sizer@gnome-shell- extensions.gcampax.github.com', 'user-theme@gnome-shell- extensions.gcampax.github.com', 'window-list@gnome-shell- extensions.gcampax.github.com', 'workspace-indicator@gnome-shell- extensions.gcampax.github.com' Please uninstall or disable all but the first three in the Extensions app and then log out and log in again. Does the problem still happen? ** Tags added: performance ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903446 Title: the process gnome-shell stay active for ever, and take 6-7 perc. of resorce, without apparent reason Status in gnome-shell package in Ubuntu: Incomplete Bug description: it take also 1 Gbyte of memory I expect not using these resoruces from my cpu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 8 23:13:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-04 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903446] Re: the process gnome-shell stay active for ever, and take 6-7 perc. of resorce, without apparent reason
Please also kill gnome-system-monitor if you have that running. It's known to cause constant CPU usage. Measure CPU usage in a terminal window by running 'top' instead. -- 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/1903446 Title: the process gnome-shell stay active for ever, and take 6-7 perc. of resorce, without apparent reason Status in gnome-shell package in Ubuntu: Incomplete Bug description: it take also 1 Gbyte of memory I expect not using these resoruces from my cpu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 8 23:13:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-04 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903383] Re: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup
Please report the bug to the developers at: https://gitlab.gnome.org/GNOME/mutter/issues and then tell us the new issue ID. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1903383 Title: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The bug occurs with any XWayland application. I tried VSCode, Chrome, Audacity, Darktable... I have two monitors with a different DPI. One is 4K HiDPI monitor and the second in LowDPI 2K monitor. I can setup 200% scale for a HiDPI monitor and 100% scale for a LowDPI. All native gnome applications are fine. The bug: when I select LowDPI monitor as a primary, XWayland applications stop scaling on a HiDPI monitor. They run 100% scale on both monitors. If I select HiDPI monitor as the primary, XWayland applications scales 200% on both monitors. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 7 12:28:53 2020 InstallationDate: Installed on 2019-11-16 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-05-02 (189 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903383] Re: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup
I'm not sure how Xwayland communicates the scale info to apps, but adding a xorg-server task anyway. Because that's the source package of Xwayland. ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- 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/1903383 Title: XWayland applications respect scale only if a scaled output is primary on a mixed-scale setup Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: The bug occurs with any XWayland application. I tried VSCode, Chrome, Audacity, Darktable... I have two monitors with a different DPI. One is 4K HiDPI monitor and the second in LowDPI 2K monitor. I can setup 200% scale for a HiDPI monitor and 100% scale for a LowDPI. All native gnome applications are fine. The bug: when I select LowDPI monitor as a primary, XWayland applications stop scaling on a HiDPI monitor. They run 100% scale on both monitors. If I select HiDPI monitor as the primary, XWayland applications scales 200% on both monitors. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.6-1ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Nov 7 12:28:53 2020 InstallationDate: Installed on 2019-11-16 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-05-02 (189 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903382] Re: unable to add online account for google, flickr, microsoft, facebook
** Tags added: groovy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1903382
Title:
unable to add online account for google, flickr, microsoft, facebook
Status in gnome-online-accounts package in Ubuntu:
New
Status in webkit2gtk package in Ubuntu:
New
Bug description:
Fresh install of groovy. When I try to add Google, Flickr or Microsoft
account, the loading window stays grey forever. When trying Facebook,
i can see the loaded page for a second then switches to grey also.
gnome-online-accounts:
Telepítve: 3.37.90-1ubuntu1
Jelölt:3.37.90-1ubuntu1
I see these messages in journal:
10:03:14 kernel: traps: WebKitWebProces[14044] trap int3 ip:7f510e1933cb
sp:7ffd7c266ba0 error:0 in libglib-2.0.so.0.6600.1[7f510e153000+8b000]
10:03:14 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
10:03:14 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
10:03:14 WebKitWebProces:variable to change this behavior. You can then
get a meaningful
10:03:14 WebKitWebProces:To debug your program, run it with the
GDK_SYNCHRONIZE environment
10:03:14 WebKitWebProces:that is, you will receive the error a while
after causing it.
10:03:14 WebKitWebProces: (Note to programmers: normally, X errors are
reported asynchronously;
10:03:14 WebKitWebProces: (Details: serial 221 error_code 2 request_code
152 (GLX) minor_code 34)
10:03:14 WebKitWebProces: The error was 'BadValue (integer parameter out of
range for operation)'.
10:03:14 WebKitWebProces: This probably reflects a bug in the program.
10:03:14 WebKitWebProces: (WebKitWebProcess:2): Gdk-ERROR **: 10:03:14.587:
The program 'WebKitWebProcess' received an X Window System error.
10:03:14 WebKitWebProces: libGL error: failed to load driver: swrast
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open swrast
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
10:03:14 WebKitWebProces: libGL error: failed to load driver: radeonsi
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open radeonsi
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
10:03:14 WebKitWebProces: libGL error: failed to load driver: radeonsi
10:03:14 WebKitWebProces: libGL error: MESA-LOADER: failed to open radeonsi
(search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri)
10:03:02 kernel: traps: eadedCompositor[14032] trap int3 ip:7f38f64183cb
sp:7f387c5fde10 error:0 in libglib-2.0.so.0.6600.1[7f38f63d8000+8b000]
10:03:02 WebKitWebProces:backtrace from your debugger if you break on the
gdk_x_error() function.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1903382/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903376] Re: Suddenly Graphic Display issue
Please also try unplugging and replugging the VGA cable. Or try a different cable entirely. ** Summary changed: - Suddenly Graphic Display issue + VGA monitor stuck at 1024x768, no EDID available -- 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/1903376 Title: VGA monitor stuck at 1024x768, no EDID available Status in xorg-server package in Ubuntu: Incomplete Bug description: i recently installed XDM (xtreme download manager) after my display changed to 1024x768 before it was good with 1336x768. i have also uninstalled it but still the problem persists ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 7 12:56:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2017] InstallationDate: Installed on 2020-08-30 (69 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=5dbd6c89-5b4e-4ab5-bc60-f67c18802fcd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BEH6110H.86A.0020.2011.0218.1538 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61WW dmi.board.vendor: Intel Corporation dmi.board.version: AAG23116-204 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H.86A.0020.2011.0218.1538:bd02/18/2011:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-204:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1903376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903376] Re: Suddenly Graphic Display issue
Thanks for the bug report. It appears the problem is that no EDID can be read from the VGA port, which means the driver does not know what kind of monitor is connected and what resolution to use: [54.968] (II) modeset(0): EDID for output VGA-1 [54.968] (II) modeset(0): Printing probed modes for output VGA-1 [54.968] (II) modeset(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) To find out if this is a Xorg problem or a general kernel problem please run: grep . /sys/class/drm/*/modes > drmmodes.txt and then attach the resulting text file here. To avoid the problem completely, try to use digital monitor connections only (DisplayPort, DVI or HDMI). ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1903376 Title: VGA monitor stuck at 1024x768, no EDID available Status in xorg-server package in Ubuntu: Incomplete Bug description: i recently installed XDM (xtreme download manager) after my display changed to 1024x768 before it was good with 1336x768. i have also uninstalled it but still the problem persists ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 7 12:56:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2017] InstallationDate: Installed on 2020-08-30 (69 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=5dbd6c89-5b4e-4ab5-bc60-f67c18802fcd ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BEH6110H.86A.0020.2011.0218.1538 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61WW dmi.board.vendor: Intel Corporation dmi.board.version: AAG23116-204 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBEH6110H.86A.0020.2011.0218.1538:bd02/18/2011:svn:pn:pvr:rvnIntelCorporation:rnDH61WW:rvrAAG23116-204:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1903376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903308] Re: gnome-shell freezes and restarts itself after login
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Tags added: nvidia ** Also affects: nvidia-graphics-drivers-455 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-455 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903308 Title: gnome-shell freezes and restarts itself after login Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-455 package in Ubuntu: Incomplete Bug description: Dear developers, After clean installation of Ubuntu 20.10, gnome-shell always freezes and then restarts itself when I try to open any application for the first time after a reboot. Also I can not find any crash log related to this occurrence. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 6 17:21:12 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-11-06 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 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/1903308/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869574] Re: User switch doesn't work on Ubuntu 19.10
Thank you for reporting this bug to Ubuntu. Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gdm3 (Ubuntu) Status: New => Won't Fix -- 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/1869574 Title: User switch doesn't work on Ubuntu 19.10 Status in gdm3 package in Ubuntu: Won't Fix Bug description: Premise: this is neither bug #1766137 (I've not mispelled my passord) nor bug #1844944 (sympthoms are exactly the same but the issue still exists even if I'm running on Gnome 3.34.2 and the bug was closed saying that the issue was fixed on Gnome 3.34.1). Package version (apt-cache policy gdm3) gdm3: Installed: 3.34.1-1ubuntu1 Candidate: 3.34.1-1ubuntu1 Version table: *** 3.34.1-1ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Prerequisites: - Use Ubuntu 19.10 - You need at least 2 users (e.g. user1 and user2) Step to reproduce: - Start your computer - At the graphical login prompt, log in with user1: user1 is able to log in, its desktop is shown - While logged into the desktop of user1, choose "Switch user" - When back at the user selection screen, choose the profile of user2 - Provide the password for user2 and attempt log in RESULT: The desktop of user2 is never shown. Instead, a purple screen is shown. If I click CTRL+ALT+F1 I go back to the tty1, select user 1, enter password and the user1's desktop is shown again. NOTE 1: The same happens when user2 was the first to log in after a reboot of the system. User2 is able to log in, and user1 is then stuck in a login loop. NOTE 2: If instead of switching user, I logoff user1 and logon user2 everything works properly but of course every time I do this I lose my user1's session (therefore the workaround is not good enough) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 29 13:18:31 2020 InstallationDate: Installed on 2020-02-15 (42 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2020-03-28T11:16:16.647797 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1869574/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903292] Re: GNOME Wayland session hangs after suspend
Please run this command to send us more information about the system: apport-collect 1903292 But also... Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Tags added: focal ** Tags added: wayland wayland-session ** Package changed: gdm (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend Status in gnome-shell package in Ubuntu: Incomplete Bug description: I'm running 20.04 LTS on an HP Envy x360 Ryzen 7 3700U with Radeon Vega Mobile. The gdm3 package is at version 3.36.3-0ubuntu0.20.04.2. When I trigger a suspend with `echo mem > /sys/power/state` the system appears to go into mem suspend correctly. Hitting a key should bring the display back with the lock screen displayed, but instead briefly brings a slightly scrambled screen to life and then the screen goes black and stays that way. The system is still up as I can SSH into it. Killing the gdm-wayland- session process then brings me back to the GDM login screen and I can start a new session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903292] [NEW] GNOME Wayland session hangs after suspend
You have been subscribed to a public bug: I'm running 20.04 LTS on an HP Envy x360 Ryzen 7 3700U with Radeon Vega Mobile. The gdm3 package is at version 3.36.3-0ubuntu0.20.04.2. When I trigger a suspend with `echo mem > /sys/power/state` the system appears to go into mem suspend correctly. Hitting a key should bring the display back with the lock screen displayed, but instead briefly brings a slightly scrambled screen to life and then the screen goes black and stays that way. The system is still up as I can SSH into it. Killing the gdm-wayland- session process then brings me back to the GDM login screen and I can start a new session. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal wayland wayland-session -- GNOME Wayland session hangs after suspend https://bugs.launchpad.net/bugs/1903292 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902969] Re: desktop freezes when changing thundebird win decorations
*** This bug is a duplicate of bug 1871262 *** https://bugs.launchpad.net/bugs/1871262 Thanks. The only relevant information I can find in there is: Nov 06 05:44:28 Sable-Complete gnome-shell[18366]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed -- 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/1902969 Title: desktop freezes when changing thundebird win decorations Status in gnome-shell package in Ubuntu: Incomplete Bug description: I noticed a bug. In Thunderbird (deb or snap) version open and right click on the tab bar and choose customization and mess around with showing title or not and close out of it the icon for TB is still in the dock. If you click on the icon it locks up the UI. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.3.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mram 2160 F pulseaudio /dev/snd/controlC0: mram 2160 F pulseaudio BuildID: 20201006011220 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 18:55:14 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-10-04 (31 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.45 metric 100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.0/20200629202523 (Out of date) Profile0 (Default) - LastVersion=78.3.2/20201006011220 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.release: 4.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AGH6120H.86A.0015.2012.0926.1822 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61AGL dmi.board.vendor: Intel Corporation dmi.board.version: G71256-202 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: sabc1 dmi.modalias: dmi:bvnIntelCorp.:bvrAGH6120H.86A.0015.2012.0926.1822:bd09/26/2012:br4.6:svnSystem76,Inc.:pnSableComplete:pvrsabc1:rvnIntelCorporation:rnDH61AGL:rvrG71256-202:cvnSystem76,Inc.:ct3:cvrsabc1: dmi.product.family: To be filled by O.E.M. dmi.product.name: Sable Complete dmi.product.sku: To be filled by O.E.M. dmi.product.version: sabc1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902969] Re: desktop freezes when changing thundebird win decorations
*** This bug is a duplicate of bug 1871262 *** https://bugs.launchpad.net/bugs/1871262 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1871262, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1871262 gnome-shell crashes in meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed -- 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/1902969 Title: desktop freezes when changing thundebird win decorations Status in gnome-shell package in Ubuntu: Incomplete Bug description: I noticed a bug. In Thunderbird (deb or snap) version open and right click on the tab bar and choose customization and mess around with showing title or not and close out of it the icon for TB is still in the dock. If you click on the icon it locks up the UI. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.3.2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mram 2160 F pulseaudio /dev/snd/controlC0: mram 2160 F pulseaudio BuildID: 20201006011220 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 4 18:55:14 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-10-04 (31 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.45 metric 100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=78.0/20200629202523 (Out of date) Profile0 (Default) - LastVersion=78.3.2/20201006011220 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2012 dmi.bios.release: 4.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: AGH6120H.86A.0015.2012.0926.1822 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61AGL dmi.board.vendor: Intel Corporation dmi.board.version: G71256-202 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: sabc1 dmi.modalias: dmi:bvnIntelCorp.:bvrAGH6120H.86A.0015.2012.0926.1822:bd09/26/2012:br4.6:svnSystem76,Inc.:pnSableComplete:pvrsabc1:rvnIntelCorporation:rnDH61AGL:rvrG71256-202:cvnSystem76,Inc.:ct3:cvrsabc1: dmi.product.family: To be filled by O.E.M. dmi.product.name: Sable Complete dmi.product.sku: To be filled by O.E.M. dmi.product.version: sabc1 dmi.sys.vendor: System76, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1902969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903224] Re: Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used
Yes Ctrl usually means open a second window to Gnome Shell and its dash/docks. That obviously shouldn't still happen with keyboard shortcuts. Please report the bug to the developers at: https://gitlab.gnome.org/GNOME/gnome-shell/issues and then tell us the new issue ID. ** Tags added: focal ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903224 Title: Pressing the launch terminal shortcut in activities view launches two terminals instead of one when CTRL modifier is used Status in gnome-shell package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 Package: Xorg or Gnome, not really sure. Problem description: 1. I have set the Launch terminal shortcut in Settings/Keyboard shortcuts to CTRL+`. 2. I invoke the activities overview by pressing SUPER once. 3. I launch a terminal by pressing the newly set CTRL+` shortcut. What happened: two new terminal windows appeared. What is expected: launch only one terminal window. More info: This only happens when a CTRL modifier is used and the key is set to a non function (F1-F12) key. When an ALT or CTRL+ALT shortcut is used, only one window appears, as expected. Expected behaviour: launch only one terminal window while in the activities overview. What happened: two new terminal windows appeared in the activities overview. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871262] Re: gnome-shell crashes in meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed
** Tags added: groovy ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1871262 Title: gnome-shell crashes in meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: GNOME Shell-Message: 20:18:17.677: Telepathy is not available, chat integration will be disabled. Gjs-Message: 20:18:18.189: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1028]: unreachable code after return statement Ubuntu AppIndicators-Message: 20:18:19.456: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.79/org/ayatana/NotificationItem/software_update_available Ubuntu AppIndicators-Message: 20:18:19.461: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.79/org/ayatana/NotificationItem/livepatch GNOME Shell-Message: 20:18:19.742: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation (gnome-shell:21601): mutter-CRITICAL **: 20:18:45.274: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Was the error I got after restarting Gnome after it froze when I closed Visual Studio Code but the right-click menu appeared for it after Ubuntu froze for a second because I had regions enabled on my touchpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Mon Apr 6 20:16:51 2020 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-format' b"'12h'" InstallationDate: Installed on 2020-04-04 (2 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-format' b"'12h'" InstallationDate: Installed on 2020-04-04 (5 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Package: gnome-shell 3.28.4-0ubuntu18.04.3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Tags: bionic Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1871262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900777] Re: [amdgpu] Screen freeze
** Package changed: ubuntu => xserver-xorg-video-amdgpu (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1900777 Title: [amdgpu] Screen freeze Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that my 2-year-old Dell laptop was the problem. However, I froze during Zoom yesterday and during coding today after fresh-installing Ubuntu 20.04 on Sunday. I also froze mid-attempt to submit a bug report after the coding freeze. Any help is appreciated. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 17:38:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-10-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA 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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1900777/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup
** Package changed: pulseaudio (Ubuntu) => alsa-lib (Ubuntu) ** Changed in: alsa-lib (Ubuntu) Status: Confirmed => In Progress ** Changed in: alsa-lib (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) -- 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/1901922 Title: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in alsa-lib package in Ubuntu: In Progress Bug description: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1901922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897965] Re: pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is valid for hw:0)
Comment #9 was directed at Gannet, not at qwe. Gannet, please uninstall pipewire and tell us if the problem persists. If it does then please run: apport-collect 1897965 If it does not, then this is bug 1902976. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete -- 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/1897965 Title: pulseaudio: Failed to load module "module-alsa-card" (No UCM verb is valid for hw:0) Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound after login. $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:46:51 EEST; 8min ago TriggeredBy: * pulseaudio.socket Main PID: 1088 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-1088 /usr/bin/pulseaudio --daemonize=no --log-target=journal `-1126 /usr/libexec/pulse/gsettings-helper Sep 30 22:46:51 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:46:51 p5q3 pulseaudio[1088]: No UCM verb is valid for hw:0 Sep 30 22:46:51 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:46:52 p5q3 pulseaudio[1088]: Failed to load module "module-alsa-card" (argument: "device_id="1" name="pci-_01_00.1" card_name="alsa_card.pci-_01_00.1" namereg_fail=false tsched=yes fixed_laten> Sep 30 22:47:11 p5q3 pulseaudio[1088]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Workaround found: 'pulseaudio -k' seems solves the problem, sound appears and working well, but some errors still present: $ LC_ALL=C systemctl --user status pulseaudio.service * pulseaudio.service - Sound Service Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2020-09-30 22:55:49 EEST; 7min ago TriggeredBy: * pulseaudio.socket Main PID: 12198 (pulseaudio) CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service |-12198 /usr/bin/pulseaudio --daemonize=no --log-target=journal `-12212 /usr/libexec/pulse/gsettings-helper Sep 30 22:55:49 p5q3 systemd[1080]: Starting Sound Service... Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:1 Sep 30 22:55:49 p5q3 pulseaudio[12198]: No UCM verb is valid for hw:0 Sep 30 22:55:49 p5q3 systemd[1080]: Started Sound Service. Sep 30 22:56:14 p5q3 pulseaudio[12198]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu11 Uname: Linux 5.8.12-050812-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene 1088 F pulseaudio eugene 1092 F pipewire-media- /dev/snd/controlC1: eugene 1092 F pipewire-media- /dev/snd/seq:eugene 1087 F pipewire CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Sep 30 22:50:58 2020 InstallationDate: Installed on 2019-04-13 (536 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-09-06 (23 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1897965/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
This bug does not exist in Ubuntu 20.04 because the code that was deleted to cause this bug is NOT deleted in Ubuntu 20.04. You are experiencing a different problem so please open a new bug. -- 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/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: Fix Released Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900777] [NEW] [amdgpu] Screen freeze
You have been subscribed to a public bug: I upgraded to a Ryzen 7, 24-RAM ASUS computer because I thought that my 2-year-old Dell laptop was the problem. However, I froze during Zoom yesterday and during coding today after fresh-installing Ubuntu 20.04 on Sunday. I also froze mid-attempt to submit a bug report after the coding freeze. Any help is appreciated. Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 17:38:31 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: amdgpu, 5.6.0.15-1098277, 5.4.0-51-generic, x86_64: installed amdgpu, 5.6.0.15-1098277, 5.4.0-52-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-51-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1352] InstallationDate: Installed on 2020-10-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513IA_M513IA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=df36462b-f672-4f1c-a8b2-060922542daf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X513IA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X513IA 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.:bvrX513IA.300:bd06/05/2020:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX513IA_M513IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX513IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X513IA_M513IA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 amdgpu apport-bug focal freeze ubuntu -- [amdgpu] Screen freeze https://bugs.launchpad.net/bugs/1900777 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu 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 1902825] Re: High CPU usage just moving the mouse
Also, let's ignore the "CPU increases with mouse movement" issue. That's normal and not a bug. ** Summary changed: - High CPU usage just moving the mouse + High CPU usage? -- 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/1902825 Title: High CPU usage? Status in gnome-shell package in Ubuntu: Incomplete Bug description: high cpu usage just moving the mouse removed appindicator extension .. the cpu load is very high. running strace -c -p while moving mouse % time seconds usecs/call callserrors syscall -- --- --- - - 36.740.103852 103 1000 8 futex 31.300.088469 8 10366 8750 recvmsg 15.530.043901 11 3925 poll 10.100.028550 10 2776 write 4.330.012232 7 1537 writev 1.600.004533 4 932 read 0.390.001092 3 337 getpid 0.000.01 0 2 getrusage 0.000.01 1 1 restart_syscall 0.000.00 0 4 mprotect -- --- --- - - 100.000.282631 20880 8758 total ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Nov 4 10:49:20 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 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/1902825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset
** Tags removed: verification-needed -- 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/1853584 Title: [SRU]Not able to adjust Audio input UI volume after connecting headset Status in gnome-control-center: Fix Released Status in OEM Priority Project: Fix Released Status in OEM Priority Project bionic series: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Released Bug description: [ Impact ] Not able to adjust Audio input UI volume if this device doesn't have a internal mic, the volume bar will be gray. [ Test Case ] 1. Boot ubuntu without any external headset connected. 2. Launch gnome-control-center and switch to Sound->Input tab. 3. Connect external headset, then you will find the input show up but can not adjust the volume. [ Regression potential ] Low. change is the workaround to active/deactivate some bugs which didn't report things in the right order. It will just have extra active/deactiveate actions in normal situation(which the machines don't have this issue). Verified on built-in and non built-in input device machines , no regression found yet. Package in this PPA: https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages Summary:Not able to adjust Audio input UI volume, it's gray Steps to reproduce: 1. Plug 3 ring earphone with mic to appropriate jack Expected result: System can be recording audio from external mic Actual result: Not able to adjust Audio input UI volume, it's gray, and no volume detected in UI, but I can recording the input audio by checkbox Failure rate:100% Note. 1. There is no internal mic, just a mic jack on the machine, this issue will happen 2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2 Note:20.04, 19.10, 19.04 are immune on the bug To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1853584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902825] Re: High CPU usage just moving the mouse
The attachment in comment #11 shows very low and often zero CPU usage, so there's no obvious bug there. Did you attach the wrong top output? -- 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/1902825 Title: High CPU usage? Status in gnome-shell package in Ubuntu: Incomplete Bug description: high cpu usage just moving the mouse removed appindicator extension .. the cpu load is very high. running strace -c -p while moving mouse % time seconds usecs/call callserrors syscall -- --- --- - - 36.740.103852 103 1000 8 futex 31.300.088469 8 10366 8750 recvmsg 15.530.043901 11 3925 poll 10.100.028550 10 2776 write 4.330.012232 7 1537 writev 1.600.004533 4 932 read 0.390.001092 3 337 getpid 0.000.01 0 2 getrusage 0.000.01 1 1 restart_syscall 0.000.00 0 4 mprotect -- --- --- - - 100.000.282631 20880 8758 total ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Wed Nov 4 10:49:20 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.1-1ubuntu1 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/1902825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903449] Re: accountsservice displays "Libvirt Qemu"
Thanks for your report! This is similar to bug #1841079 which was fixed by dropping 0020 -support-login.defs.patch. That patch should probably be dropped in bionic too. Test build without the patch available in this PPA: https://launchpad.net/~gunnarhj/+archive/ubuntu/accountsservice ** Changed in: accountsservice (Ubuntu) Importance: Undecided => Medium ** Changed in: accountsservice (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1903449 Title: accountsservice displays "Libvirt Qemu" Status in accountsservice package in Ubuntu: Triaged Bug description: Installing libvirt-manager results in account libvirt-qemu being created. This user has config in /etc/passwd like follows: libvirt-qemu:x:64055:125:Libvirt Qemu,,,:/var/lib/libvirt:/usr/sbin/nologin The "nologin" should be pretty clear signal that this account is not usable for logging in. Despite this, this account is offered in visual login (e.g. lightdm). The computation for possible user accounts is handled by package accountsservice. A workaround is to manually list this user as system user: echo -e "[User]\nSystemAccount=true" > /var/lib/AccountsService/users/libvirt-qemu However, as this user cannot be logged in (/etc/shadow contains "!" as the password hash, too) it never makes any sense to show this in login screen even without the above manual configuration. Related: bug 857651 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: accountsservice 0.6.45-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 8 16:54:24 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (672 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: accountsservice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1903449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
verified the version 1.5.12-0ubuntu3.1 in groovy-proposed, works well and didn't observe any potential regression. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged Status in OEM Priority Project: Triaged Status in OEM Priority Project focal series: New Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Focal: Fix Committed Status in system-config-printer source package in Groovy: Fix Committed Bug description: [ Impact ] After printers (non-ippusb protocal) have been disconnected, the status of cups still shows "idle" instead of "disabled", so seems the disconnected procedure hasn't worked well. [ Test Case ] 1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 20.04 machine 2. Wait for the status of cups became "Idle" (lpstat -p) 3. Unplug the cable of the printer 4. Check the status of cups again. (lpstat -p) [ Regression potential ] Very Low, if something went wrong in the change, then this issue happened again, due to this snippet will only be called during printer removed event. [Expected result] The status should show disabled. [Actual result] The status shows idle. [info] Target: HP LaserJet Pro203dw HP Officejet 100 Mobile Printer HP Officeject 200 Mobile Printer Brother HL-2250DN Samsung ML-331x Upstream Bug: https://github.com/OpenPrinting/system-config- printer/issues/182 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1893300] Re: The status of cups still shows idle when the printer has been unplugged
verified the version 1.5.12-0ubuntu1.1 in focal-proposed, works well and didn't observe any potential regression. ** Tags removed: verification-needed-focal verification-needed-groovy ** Tags added: verification-done-focal verification-done-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1893300 Title: The status of cups still shows idle when the printer has been unplugged Status in OEM Priority Project: Triaged Status in OEM Priority Project focal series: New Status in system-config-printer package in Ubuntu: Fix Released Status in system-config-printer source package in Focal: Fix Committed Status in system-config-printer source package in Groovy: Fix Committed Bug description: [ Impact ] After printers (non-ippusb protocal) have been disconnected, the status of cups still shows "idle" instead of "disabled", so seems the disconnected procedure hasn't worked well. [ Test Case ] 1. Connect the printer (non-ippusb protocal)(which isn't 070104) with any 20.04 machine 2. Wait for the status of cups became "Idle" (lpstat -p) 3. Unplug the cable of the printer 4. Check the status of cups again. (lpstat -p) [ Regression potential ] Very Low, if something went wrong in the change, then this issue happened again, due to this snippet will only be called during printer removed event. [Expected result] The status should show disabled. [Actual result] The status shows idle. [info] Target: HP LaserJet Pro203dw HP Officejet 100 Mobile Printer HP Officeject 200 Mobile Printer Brother HL-2250DN Samsung ML-331x Upstream Bug: https://github.com/OpenPrinting/system-config- printer/issues/182 PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1893300 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1746656] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log()
It looks like any call to wl_log will hit the same bucket: https://errors.ubuntu.com/problem/919f7b6d37f2b2e23bf18d4cc9fad6a6116edf82 So this bug may never be about just one issue :( ** Summary changed: - Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ["wl_display@1: error 1: invalid arguments for zwp_relative_pointer_manager_v1@15.get_relative_pointer\n"] + Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() ** Tags removed: eoan ** Tags added: focal -- 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/1746656 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler() from wl_log() Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.19.5-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/919f7b6d37f2b2e23bf18d4cc9fad6a6116edf82 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1746656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect
Actually the upstream bug link says it's definitely fixed in 3.38.2 :) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Invalid ** Tags added: fixed-in-3.38.2 fixed-upstream ** Changed in: mutter (Ubuntu) Status: Fix Released => 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/1899206 Title: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which seems to have been introduced within the past couple of weeks. I have a couple custom keyboard settings configured in Tweaktool "Additional Layout Options". These settings work great. I have a USB keyboard plugged into the machine. If I have the keyboard plugged in when I start my Gnome session, the customized keyboard layout options are correctly applied to the USB keyboard. If I unplug and reconnect the keyboard, the keyboard does will _NOT_ have the customized keyboard settings. If I restart my Gnome session (using Alt-F2 -> "r"), the customized settings are applied to the keyboard. I think this behavior is something new. Before, I was able to unplug/reconnect my keyboard and it would apply my customized keyboard settings on reconnect. Is there anything I can do to force the application of the custom keyboard tweaks on USB keyboard reconnect? Is anyone else able to reproduce this? I don't have any other machines with Ubuntu 20.04.1 to test with. Thanks! (This is also cross-posted at askubuntu: https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional- layout-options-not-working) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1899206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899206] Re: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect
Possibly fixed in mutter 3.38.2 by: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1553 ** Changed in: mutter (Ubuntu) Status: Confirmed => 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/1899206 Title: Tweaktool Keyboard “Additional Layout Options” not persisting on USB keyboard unplug/reconnect Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: I am running Ubuntu 20.04.1 with Gnome. I am seeing new behavior which seems to have been introduced within the past couple of weeks. I have a couple custom keyboard settings configured in Tweaktool "Additional Layout Options". These settings work great. I have a USB keyboard plugged into the machine. If I have the keyboard plugged in when I start my Gnome session, the customized keyboard layout options are correctly applied to the USB keyboard. If I unplug and reconnect the keyboard, the keyboard does will _NOT_ have the customized keyboard settings. If I restart my Gnome session (using Alt-F2 -> "r"), the customized settings are applied to the keyboard. I think this behavior is something new. Before, I was able to unplug/reconnect my keyboard and it would apply my customized keyboard settings on reconnect. Is there anything I can do to force the application of the custom keyboard tweaks on USB keyboard reconnect? Is anyone else able to reproduce this? I don't have any other machines with Ubuntu 20.04.1 to test with. Thanks! (This is also cross-posted at askubuntu: https://askubuntu.com/questions/1281162/tweaktool-keyboard-additional- layout-options-not-working) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1899206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899509] Re: Mouse/touchpad settings not applied on hotplug/reconnect
Possibly fixed in mutter 3.38.2 by: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1553 -- 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/1899509 Title: Mouse/touchpad settings not applied on hotplug/reconnect Status in gnome-control-center: Unknown Status in GNOME Settings Daemon: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When I plug in a touchpad via USB, my chosen scrolling and speed settings are not applied, unless I adjust them again in the settings UI. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1899509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903468] [NEW] Endless "Cache Refresh" on Software Update settings change
Public bug reported: After reapplying the some of the checkboxes under "Software & Updates" -> "Other Software" after distro upgrade, a window with title "Cache Refresh" pops and never disappears > lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 9 01:55:13 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2015-06-17 (1971 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-09-29 (40 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-11-09 01-56-54.png" https://bugs.launchpad.net/bugs/1903468/+attachment/5432426/+files/Screenshot%20from%202020-11-09%2001-56-54.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1903468 Title: Endless "Cache Refresh" on Software Update settings change Status in software-properties package in Ubuntu: New Bug description: After reapplying the some of the checkboxes under "Software & Updates" -> "Other Software" after distro upgrade, a window with title "Cache Refresh" pops and never disappears > lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-gtk 0.98.9.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Nov 9 01:55:13 2020 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2015-06-17 (1971 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.8 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2020-09-29 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1903468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1622499] Re: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', whi
Ubuntu 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1622499 Title: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/accounts.google.com.conf', which is also in package account- plugin-google 0.13+16.04.20160719-0ubuntu1 Status in One Hundred Papercuts: Confirmed Status in account-plugins package in Ubuntu: Won't Fix Status in kaccounts-providers package in Ubuntu: Confirmed Bug description: kaccounts-providers packagepackage kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package account-plugin-google 0.13+16.04.20160719-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Sep 12 08:14:14 2016 DuplicateSignature: package:kaccounts-providers:(not installed) Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.13+16.04.20160719-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package account-plugin-google 0.13+16.04.20160719-0ubuntu1 InstallationDate: Installed on 2016-09-08 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/accounts.google.com.conf', which is also in package account-plugin-google 0.13+16.04.20160719-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1622499/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again
hi! I'm here again because some package upgrade, or something else (i dont't know what) just fixed it. Now I can connect with just one click. -- 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/1879582 Title: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again Status in alsa-driver package in Ubuntu: New Bug description: I can connect to my bluetooth phone only the first time after pair the device. It works until disconnecting, (whether by turning off the phone, or putting into the case, or disconnecting in ubuntu settings), and then i turn on the phone again (or remove from the case), i cannot connect until I manually remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. If the Ubuntu/Gnome Settings is opened, i can see the status "connected" blinks, and fastly change to "disconnected". My bluetooth phone works fine with another devices. Ubuntu 20.04 LTS Laptop Acer Aspire Nitro 5 (AN515-52-5771). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: felipe 2149 F pulseaudio /dev/snd/controlC0: felipe 2149 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 19:10:35 2020 InstallationDate: Installed on 2020-04-29 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redmi AirDots_R Symptom_Type: None of the above Title: [Redmi AirDots_R, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903464] Re: nautilus does not allow selection of files with a frame when enabled list viev
** Description changed: the problem manifests itself in all versions of the program and in the - distribution version 20.04 and 20.10 + distribution version 20.04 and 20.10 and older -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1903464 Title: nautilus does not allow selection of files with a frame when enabled list viev Status in nautilus package in Ubuntu: New Bug description: the problem manifests itself in all versions of the program and in the distribution version 20.04 and 20.10 and older To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1903464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903464] [NEW] nautilus does not allow selection of files with a frame when enabled list viev
Public bug reported: the problem manifests itself in all versions of the program and in the distribution version 20.04 and 20.10 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1903464 Title: nautilus does not allow selection of files with a frame when enabled list viev Status in nautilus package in Ubuntu: New Bug description: the problem manifests itself in all versions of the program and in the distribution version 20.04 and 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1903464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
I can confirm that libasound2 from ppa:hui.wang/pa-testing works. -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi all! @Coiby Xu (coiby) When your patch will be applied to mainline kernel? When we can just update our kernels and do nothing to fix touchpad? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05
[Desktop-packages] [Bug 1903460] [NEW] audio output selection not working properly anymore
Public bug reported:
I have been using Ubuntu 20.04 since it was released. Suddenly, a few
days ago, the sound device output selection (gnome-control-center >
Sound > Output device) stopped work properly. It is starting as HDMI by
default (it used to be "internal" before the bug, but this is not the
question). The problem is that when i change from HDMI to another
("internal" or bluetooth) output it doesn't work anymore, the sound keep
being outputted by HDMI instead. It only works when i change HDMI
profile to 5.1, then all HDMI profiles just disappear and internal or
bluetooth audio works fine.
I don't know if it's really a bug in gnome-control-center, or i just
blaming the GUI, but I will do what is necessary to find this out.
I hope i can help improve Ubuntu reporting this. Thanks for all
developers!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.4-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 8 15:45:14 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-04-29 (193 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
LANGUAGE=pt_BR:pt:en
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=pt_BR.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1903460
Title:
audio output selection not working properly anymore
Status in gnome-control-center package in Ubuntu:
New
Bug description:
I have been using Ubuntu 20.04 since it was released. Suddenly, a few
days ago, the sound device output selection (gnome-control-center >
Sound > Output device) stopped work properly. It is starting as HDMI
by default (it used to be "internal" before the bug, but this is not
the question). The problem is that when i change from HDMI to another
("internal" or bluetooth) output it doesn't work anymore, the sound
keep being outputted by HDMI instead. It only works when i change HDMI
profile to 5.1, then all HDMI profiles just disappear and internal or
bluetooth audio works fine.
I don't know if it's really a bug in gnome-control-center, or i just
blaming the GUI, but I will do what is necessary to find this out.
I hope i can help improve Ubuntu reporting this. Thanks for all
developers!
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.4-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.11
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 8 15:45:14 2020
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2020-04-29 (193 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
LANGUAGE=pt_BR:pt:en
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=pt_BR.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1903460/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903457] [NEW] "Allow _executing file as program" has extra underscore
Public bug reported: Since upgrading to Ubuntu 20.10, I'm seeing a minor typo or mistake in the Permissions tab of the file properties window. It says "Allow _executing file as program" instead of just "Allow executing file as program". For some reason, there is an additional underscore there. To reproduce, open a folder and right-click on any file. Then select "Properties". Go to the "Permissions" tab and read the label of the checkbox after the "Execute" field. I'm using the English (United States) language. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 8 19:57:01 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'initial-size' b'(1144, 721)' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-05-09 (183 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: Upgraded to groovy on 2020-11-08 (0 days ago) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1 nautilus-share0.7.3-2ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Description changed: Since upgrading to Ubuntu 20.10, I'm seeing a minor typo or mistake in the Permissions tab of the file properties window. It says "Allow _executing file as program" instead of just "Allow executing file as program". For some reason, there is an additional underscore there. To reproduce, open a folder and right-click on any file. Then select "Properties". Go to the "Permissions" tab and read the label of the checkbox after the "Execute" field. + + I'm using the English (United States) language. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 8 19:57:01 2020 GsettingsChanges: - b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' - b'org.gnome.nautilus.window-state' b'initial-size' b'(1144, 721)' - b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" + b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' + b'org.gnome.nautilus.window-state' b'initial-size' b'(1144, 721)' + b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2020-05-09 (183 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: Upgraded to groovy on 2020-11-08 (0 days ago) usr_lib_nautilus: - evince3.38.0-1 - file-roller 3.38.0-1 - nautilus-extension-gnome-terminal 3.38.0-1ubuntu1 - nautilus-share0.7.3-2ubuntu3 + evince3.38.0-1 + file-roller 3.38.0-1 + nautilus-extension-gnome-terminal 3.38.0-1ubuntu1 + nautilus-share0.7.3-2ubuntu3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1903457 Title: "Allow _executing file as program" has extra underscore Status in nautilus package in Ubuntu: New Bug description: Since upgrading to Ubuntu 20.10, I'm seeing a minor typo or mistake in the Permissions tab of the file properties window. It says "Allow _executing file as program" instead of just "Allow executing file as program". For some reason, there is an additional underscore there. To reproduce, open a folder and right-click on any file. Then select "Properties". Go to the "Permissions" tab and read the label of the checkbox after the "Execute" field. I'm using the English (United States) language. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus
[Desktop-packages] [Bug 1901157] Re: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all
Hi, installing older packages sudo dpkg -i libasound2_1.2.2-2.1ubuntu2_amd64.deb libasound2-data_1.2.2-2.1ubuntu2_all.deb fixed sound issues on my Lenovo Ideapad 5 14are05 with Ryzen 4500u. Please release fix asap, this is a huge bug (to lose sound after update). -- 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/1901157 Title: [Raven/Raven2/FireFlight/Renoir AMD Ryzen] No Sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: After Upgrading to Ubuntu 20.10 (From 20.04) I noticed, that my Audio Output didn't work anymore. Switching between different Kernel Versions (Mainline 5.8.16 and Ubuntu Stock 5.8.0-25, 5.4.0-52) doesn't change that. Even on a fresh 20.10 Livesystem i get the exact same problem (On 20.04 Livesystem it works) An Output of "$ lspci -nnk | grep -A2 Audio" shows that the Output device uses the wrong Kernel Module (Audio Input is working since it uses the correct kernel module and driver) 07:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:1637] Subsystem: Lenovo Device [17aa:5081] Kernel modules: snd_hda_intel -- 07:00.5 Multimedia controller [0480]: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor [1022:15e2] (rev 01) Subsystem: Lenovo Raven/Raven2/FireFlight/Renoir Audio Processor [17aa:5081] Kernel driver in use: snd_rn_pci_acp3x Kernel modules: snd_pci_acp3x, snd_rn_pci_acp3x 07:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller [1022:15e3] Subsystem: Lenovo Family 17h (Models 10h-1fh) HD Audio Controller [17aa:5081] Kernel modules: snd_hda_intel Affected Device is a ThinkPad T14 with an AMD Ryzen 4750U ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.8.16-050816-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 23 10:17:36 2020 InstallationDate: Installed on 2020-10-15 (7 days ago) InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:acp failed Symptom_Card: Webcam Vitade AF - USB 2.0 Camera Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: moritz 2175 F pulseaudio /dev/snd/pcmC1D0c: moritz 2175 F...m pulseaudio /dev/snd/controlC0: moritz 2175 F pulseaudio /dev/snd/pcmC0D0c: moritz 2175 F...m pulseaudio Symptom_Type: No sound at all Title: [acp - acp, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UD0013GE dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UD0013GE:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD0013GE:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UD0013GE dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-23T01:18:30.406924 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1901157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup
Upstream notes that these remaining errors should be resolved once we are on alsa-lib 1.2.4. -- 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/1901922 Title: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1901922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901922] Re: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup
Upstream notes that some errors are still not resolved by this fix: Nov 8 18:34:15 determinist pulseaudio[2219]: error: failed to import hw:0 (empty configuration) Nov 8 18:34:15 determinist pulseaudio[2219]: error: failed to import HD-Audio Generic (empty configuration) However these errors do not directly impact functionality of sound input and output. -- 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/1901922 Title: [Lenovo ThinkPad T14 Gen 1] No sound output device on startup Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: After logging in, only a dummy device is available for audio playback (resulting in no audible playback). When running "pactl load-module module-detect" the sound card shows up, and playback works as expected. If pulseaudio is restarted with "pulseaudio -k" the playback device disappears again. Running the above command get things working again. If I change the following section in /etc/pulse/default.pa from: ### Automatically load driver modules depending on the hardware available .ifexists module-udev-detect.so load-module module-udev-detect .else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect .endif To: ### Automatically load driver modules depending on the hardware available #.ifexists module-udev-detect.so #load-module module-udev-detect #.else ### Use the static hardware detection module (for systems that lack udev support) load-module module-detect #.endif Things start working as they should after running "pulseaudio -k". ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Oct 28 17:21:02 2020 InstallationDate: Installed on 2020-10-23 (4 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2020 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1BET40W(1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UDCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1BET40W(1.09):bd08/07/2020:br1.9:efr1.9:svnLENOVO:pn20UDCTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20UDCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20UDCTO1WW dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1901922/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi everyone! I have the same problem with my touchpad on Lenovo Ideapad Gaming 3 15ARH05 under Pop!_OS. My touchpad device number is slightly different: MSFT0001:00 06CB:CE2D I've applied a patch in comment #179 (I assumed that's the most fitting solution for me) and it works now! Thank you people for trying to fix this. Anyway the comments now are very long and confusing. And I'm not sure if I used the best solution. So if anyone can point to something better, let me know. Also let me know how to help with pushing this to official kernel. I've posted an issue to Pop OS Github repo. I'll also add a comment about my workarounds there. Have a nice day! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name:
[Desktop-packages] [Bug 1757280] Re: Night Light only works on one Monitor
Hi Guys, Bug present on Ubuntu Groovy. gnome-shell-common 3.38.1-1ubuntu1 gnome-control-center 1:3.38.1-1ubuntu1 DVI-D-0 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 477mm x 268mm DP-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 598mm x 336mm Night mode enabled but it's only set on DVI-D-0 and missing from DP-0 -- 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/1757280 Title: Night Light only works on one Monitor Status in gnome-control-center: Expired Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: Hi If I activate the Night Light mode with an external monitor connected, the mode is only on the external monitor activated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompositorRunning: None Date: Tue Mar 20 23:12:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:224b] InstallationDate: Installed on 2018-03-19 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180319) MachineType: LENOVO 20HF0016MZ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET45W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HF0016MZ dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET45W(1.24):bd02/26/2018:svnLENOVO:pn20HF0016MZ:pvrThinkPadT470s:rvnLENOVO:rn20HF0016MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HF0016MZ dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1757280/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903448] Re: Starting
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1903448 Title: Starting Status in xorg package in Ubuntu: New Bug description: Take very long time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Nov 8 16:47:36 2020 DistUpgraded: 2020-10-18 17:57:46,055 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Lapsiprosessin “./xorg_fix_proprietary.py” käynnistäminen epäonnistui (Tiedostoa tai hakemistoa ei ole) (8)) DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86M [Quadro NVS 135M] [10de:042b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G86M [Quadro NVS 135M] [1028:01f9] InstallationDate: Installed on 2020-02-17 (264 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude D630 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=d79ab05c-0324-4961-8e58-27cfbf47e11a ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-18 (20 days ago) dmi.bios.date: 01/04/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0WM416 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd01/04/2010:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0WM416:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1903448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903448] [NEW] Starting
You have been subscribed to a public bug: Take very long time ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Nov 8 16:47:36 2020 DistUpgraded: 2020-10-18 17:57:46,055 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Lapsiprosessin “./xorg_fix_proprietary.py” käynnistäminen epäonnistui (Tiedostoa tai hakemistoa ei ole) (8)) DistroCodename: focal DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86M [Quadro NVS 135M] [10de:042b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G86M [Quadro NVS 135M] [1028:01f9] InstallationDate: Installed on 2020-02-17 (264 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude D630 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=d79ab05c-0324-4961-8e58-27cfbf47e11a ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-18 (20 days ago) dmi.bios.date: 01/04/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0WM416 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd01/04/2010:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0WM416:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Starting https://bugs.launchpad.net/bugs/1903448 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903449] [NEW] accountsservice displays "Libvirt Qemu"
Public bug reported: Installing libvirt-manager results in account libvirt-qemu being created. This user has config in /etc/passwd like follows: libvirt-qemu:x:64055:125:Libvirt Qemu,,,:/var/lib/libvirt:/usr/sbin/nologin The "nologin" should be pretty clear signal that this account is not usable for logging in. Despite this, this account is offered in visual login (e.g. lightdm). The computation for possible user accounts is handled by package accountsservice. A workaround is to manually list this user as system user: echo -e "[User]\nSystemAccount=true" > /var/lib/AccountsService/users/libvirt-qemu However, as this user cannot be logged in (/etc/shadow contains "!" as the password hash, too) it never makes any sense to show this in login screen even without the above manual configuration. Related: bug 857651 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: accountsservice 0.6.45-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 8 16:54:24 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (672 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: accountsservice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1903449 Title: accountsservice displays "Libvirt Qemu" Status in accountsservice package in Ubuntu: New Bug description: Installing libvirt-manager results in account libvirt-qemu being created. This user has config in /etc/passwd like follows: libvirt-qemu:x:64055:125:Libvirt Qemu,,,:/var/lib/libvirt:/usr/sbin/nologin The "nologin" should be pretty clear signal that this account is not usable for logging in. Despite this, this account is offered in visual login (e.g. lightdm). The computation for possible user accounts is handled by package accountsservice. A workaround is to manually list this user as system user: echo -e "[User]\nSystemAccount=true" > /var/lib/AccountsService/users/libvirt-qemu However, as this user cannot be logged in (/etc/shadow contains "!" as the password hash, too) it never makes any sense to show this in login screen even without the above manual configuration. Related: bug 857651 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: accountsservice 0.6.45-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-lowlatency 5.4.65 Uname: Linux 5.4.0-52-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 8 16:54:24 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (672 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: accountsservice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1903449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879247] Re: [27C6:538D] goodix fingerprint is not supported.
** Bug watch added: gitlab.freedesktop.org/libfprint/libfprint/-/issues #196 https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/196 ** Also affects: libfprint via https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/196 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1879247 Title: [27C6:538D] goodix fingerprint is not supported. Status in libfprint: Unknown Status in OEM Priority Project: New Status in libfprint package in Ubuntu: Confirmed Bug description: it's waiting IHV driver ready. both proprietary driver and open-sourced driver not support this device yet. Links of the platforms have the module: https://certification.ubuntu.com/catalog/component/27c6:538d ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libfprint-2-tod1 1:1.90.1+tod1-0ubuntu4 ProcVersionSignature: Ubuntu 5.6.0-1010.10+lp1876707-oem 5.6.10 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 18 13:59:54 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X24 InstallationDate: Installed on 2020-05-17 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: libfprint UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1879247/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903445] [NEW] package firefox 82.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
Public bug reported: Package fails to update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firefox 82.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.11 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uuu1845 F pulseaudio /dev/snd/controlC1: uuu1845 F pulseaudio /dev/snd/pcmC1D0p: uuu1845 F...m pulseaudio /dev/snd/timer: uuu1845 f pulseaudio BuildID: 20201027185343 CasperMD5CheckResult: skip Channel: Unavailable Date: Sun Nov 8 19:33:33 2020 DpkgTerminalLog: dpkg: error processing package firefox (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ForcedLayersAccel: False InstallationDate: Installed on 2020-10-24 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 82.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1903445 Title: package firefox 82.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in firefox package in Ubuntu: New Bug description: Package fails to update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: firefox 82.0.2+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.11 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uuu1845 F pulseaudio /dev/snd/controlC1: uuu1845 F pulseaudio /dev/snd/pcmC1D0p: uuu1845 F...m pulseaudio /dev/snd/timer: uuu1845 f pulseaudio BuildID: 20201027185343 CasperMD5CheckResult: skip Channel: Unavailable Date: Sun Nov 8 19:33:33 2020 DpkgTerminalLog: dpkg: error processing package firefox (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ForcedLayersAccel: False InstallationDate: Installed on 2020-10-24 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 82.0.2+build1-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias:
[Desktop-packages] [Bug 1903446] [NEW] the process gnome-shell stay active for ever, and take 6-7 perc. of resorce, without apparent reason
Public bug reported: it take also 1 Gbyte of memory I expect not using these resoruces from my cpu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 8 23:13:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-04 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1903446 Title: the process gnome-shell stay active for ever, and take 6-7 perc. of resorce, without apparent reason Status in gnome-shell package in Ubuntu: New Bug description: it take also 1 Gbyte of memory I expect not using these resoruces from my cpu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 8 23:13:43 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-04 (34 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876991] Re: Touchpad started appearing both as a touchpad and as a mouse input devices after upgrade to 20.04
A workaround that works for me is to disable mouse using `xinput
--disable 11` and enable touchpad `xinput --enable 10`. Use `xinput
--list` to find out the id of the devices.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1876991
Title:
Touchpad started appearing both as a touchpad and as a mouse input
devices after upgrade to 20.04
Status in xserver-xorg-input-synaptics package in Ubuntu:
Confirmed
Bug description:
It was working perfectly on 18.04 with 5.3 kernel but after upgrade to
20.04 it's becoming disabled because there is a "mouse" attached which
is the same touchpad detected incorrectly, xinput --list showing both
⎜ ↳ MSFT0001:00 06CB:7E7E Mouse id=11 [slave pointer (2)]
⎜ ↳ MSFT0001:00 06CB:7E7E Touchpadid=12 [slave pointer (2)]
The first line was definitely not present before, I know it because I
use it when in openbox session.
There is also a number of questions on AskUbuntu that look like results of
the same problem at first glance:
https://askubuntu.com/q/1231873/20275
https://askubuntu.com/q/1235067/20275
https://askubuntu.com/q/1234975/20275
and two global search results for the same touchpad model ("MSFT0001:00
06CB:7E7E Mouse") that show the same problem in unrelated contexts:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953405
https://bbs.archlinux.org/viewtopic.php?id=240723
I also have these errors in kernel log, may be related, weren't present
previously:
psmouse serio1: Failed to deactivate mouse on isa0060/serio1: -5
psmouse serio1: Failed to enable mouse on isa0060/serio1
psmouse serio1: Failed to disable mouse on isa0060/serio1
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed May 6 00:09:45 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 27c6:5301 Shenzhen Goodix Technology Co.,Ltd.
Fingerprint Reader
Bus 001 Device 002: ID 1bcf:28c1 Sunplus Innovation Technology Inc.
Integrated_Webcam_HD
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Vostro 5471
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic
root=/dev/mapper/ocz-root ro quiet libata.force=1.00:noncq
resume=/dev/mapper/ocz-swap_1 crashkernel=384M-2G:128M,2G-:256M
SourcePackage: xserver-xorg-input-synaptics
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.0
dmi.board.name: 05F5VX
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.asset.tag: Zahoriya
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.9.0:bd07/25/2018:svnDellInc.:pnVostro5471:pvr:rvnDellInc.:rn05F5VX:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Vostro
dmi.product.name: Vostro 5471
dmi.product.sku: 0830
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1876991/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878241] Re: On every boot, a message appears that my wireless printer has been added
*** This bug is a duplicate of bug 1725955 *** https://bugs.launchpad.net/bugs/1725955 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1878241 Title: On every boot, a message appears that my wireless printer has been added Status in cups package in Ubuntu: Confirmed Bug description: I have a Brother HL 3170CDW printer on my wifi network. Every time I boot Ubuntu, a notification appears at the top of the login screen saying that "The printer Brother_HL_3170CDW_series has been added". I would expect this to happen only one time. This is a nuisance/cosmetic issue only -- the printer is not actually added multiple times. It only appears once in the Printers section of Settings. To be clear, I have not installed any drivers or printer-related software other than what is supplied in the default Focal 20.04 installation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 09:17:34 2020 InstallationDate: Installed on 2020-05-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lpstat: device for Brother_HL_3170CDW_series: implicitclass://Brother_HL_3170CDW_series/ MachineType: Razer Blade Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Brother_HL_3170CDW_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Brother_HL_3170CDW_series.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/16/2019 dmi.bios.vendor: Razer dmi.bios.version: 1.05 dmi.board.name: Razer CH20 dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr1.05:bd05/16/2019:svnRazer:pnBlade:pvr2.04:rvnRazer:rnRazerCH20:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582002 Razer Blade dmi.product.name: Blade dmi.product.sku: RZ09-02888E92 dmi.product.version: 2.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1878241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Definitely! The attached output was compiled from 5.4.0-52 with the patch listed in 171. ** Attachment added: "gpio-config-and-dsdt.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5432324/+files/gpio-config-and-dsdt.tar.xz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
[Desktop-packages] [Bug 1885953] Re: color-cc-panel calls gcm-calibrate which was removed from package
The issue is still present in Ubuntu 20.10 as well. -- 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/1885953 Title: color-cc-panel calls gcm-calibrate which was removed from package Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 gnome-control-center: 1:3.36.2-0ubuntu1 Trying to calibrate a scanner clicking on "Calibrate" button tries to launch /usr/bin/gcm-calibrate which is not present in the actual gnome-color-manager package. I expected a calibration window to be opened. Nothing happened. Launching gnome-control-center from terminal returned: (gnome-control-center:10648): color-cc-panel-WARNING **: 21:31:06.478: failed to run calibrate: Ezin izan da “/usr/bin/gcm-calibrate” prozesu haurra exekutatu (No such file or directory) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 1 21:38:16 2020 InstallationDate: Installed on 2020-06-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=eu_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1885953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901789] Re: Release upgrade 20.04 -> 20.10 removed input method from ibus
Good. I understand from some other bug reports that in 20.04 (ibus 1.5.22) German was denoted as 'xkb:de::ger', and in 20.10 (ibus 1.5.23) that was changed to 'xkb:de::deu'. You can see what it currently looks like for you via this command: gsettings get org.freedesktop.ibus.general preload-engines So the first time you logged in after the upgrade, your saved value 'xkb:de::ger' was not understood and thus ignored. The name was changed only for a small number of XKB layouts, of which German was one. Ideally there should have been some transition code to deal with the change. Let's await the reaction to the upstream issue. ** Changed in: ibus (Ubuntu) Importance: Undecided => Low ** Changed in: ibus (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1901789 Title: Release upgrade 20.04 -> 20.10 removed input method from ibus Status in ibus: New Status in ibus package in Ubuntu: Confirmed Bug description: What happened: === I'm using iBus as input "method" with - Japanese (Anthy) // primary - German set up. I upgraded from ubuntu 20.04 to 20.10. EXPECTED: No changes regarding input. ACTUAL: German input method was removed lsb_release -rd === Description: Ubuntu 20.10 Release: 20.10 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.12 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Oct 28 11:10:04 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to groovy on 2020-10-24 (3 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1901789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1453514] Re: Highlighted text in pdf files is not shown on prints
To add to my point 2: the same effect happens when using `pdftocairo` in command line, so maybe the current issue is not about Evince. It remains the problem with annotations created in Evince that just disappear on printing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1453514 Title: Highlighted text in pdf files is not shown on prints Status in Evince: New Status in evince package in Ubuntu: Confirmed Bug description: Highghted text in pdf files is shown correctly in the viewer, but not in the print preview & the printouts, there only a yellow bar (the highlighting) is visible, and the actual text is behind it (since it is selectable in the print preview). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: evince 3.14.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 10 12:11:42 2015 ExecutablePath: /usr/bin/evince-previewer InstallationDate: Installed on 2015-05-06 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1453514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1453514] Re: Highlighted text in pdf files is not shown on prints
In fact, there seem to be multiple issues with printing annotations (at least text highlighting). This is about Evince 3.36.7 and Okular 20.08.2. 1. If a highlighting annotation is created in Evince, it is visible when the file is opened with Evince, Okular, or Xournal++, but it disappears on printing to PDF file from any of these programs, and it disappears on exporting to PDF from Xournal++. (I believe it also disappears on actual printing.) 2. If a highlighting annotation is created in Okular, it is visible in Evince, Okular, and Xournal++, but when printing to PDF from Evince or Xournal++, the first highlighting is ok, but all the others hide the text that is supposed to be highlighted. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1453514 Title: Highlighted text in pdf files is not shown on prints Status in Evince: New Status in evince package in Ubuntu: Confirmed Bug description: Highghted text in pdf files is shown correctly in the viewer, but not in the print preview & the printouts, there only a yellow bar (the highlighting) is visible, and the actual text is behind it (since it is selectable in the print preview). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: evince 3.14.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 10 12:11:42 2015 ExecutablePath: /usr/bin/evince-previewer InstallationDate: Installed on 2015-05-06 (3 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1453514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
