[Desktop-packages] [Bug 1868332] Re: Scrolling jumps after switching tabs
** 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/1868332 Title: Scrolling jumps after switching tabs Status in xorg package in Ubuntu: New Bug description: The bug has to do with mouse scrolling and switching windows; I do not know which package it is part of. The problem arises when I have two windows of two different applications open, such as Google Chrome and a text editor. To reproduce the error, I have Google Chrome open initially, then I switch tabs (using the shortcut Alt-Tab) to the text editor, then scroll around on the text editor. When I Alt-Tab back to Google Chrome, my first scroll leads to the page jumping by a large amount either up or down before resuming regular mouse scrolling. It is only this initial scroll after switching tabs that jumps like this. It also happens regardless of whether I use a mouse or the touch pad. I also notice, given the same scenario, if I scroll up on the text editor, the Google Chrome initial scroll jump will be upward. If I scroll down on the text editor, the Chrome jump will be downward. If I scroll a lot in the text editor, the Chrome jump will be large. If I scroll a small amount in the text editor, the Chrome jump will be small. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 17:17:39 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b9] InstallationDate: Installed on 2020-01-26 (54 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=7cfa547e-7b38-4467-9a1c-5f581ce738c1 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: AMI dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 1WU65AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1868332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868332] [NEW] Scrolling jumps after switching tabs
You have been subscribed to a public bug: The bug has to do with mouse scrolling and switching windows; I do not know which package it is part of. The problem arises when I have two windows of two different applications open, such as Google Chrome and a text editor. To reproduce the error, I have Google Chrome open initially, then I switch tabs (using the shortcut Alt-Tab) to the text editor, then scroll around on the text editor. When I Alt-Tab back to Google Chrome, my first scroll leads to the page jumping by a large amount either up or down before resuming regular mouse scrolling. It is only this initial scroll after switching tabs that jumps like this. It also happens regardless of whether I use a mouse or the touch pad. I also notice, given the same scenario, if I scroll up on the text editor, the Google Chrome initial scroll jump will be upward. If I scroll down on the text editor, the Chrome jump will be downward. If I scroll a lot in the text editor, the Chrome jump will be large. If I scroll a small amount in the text editor, the Chrome jump will be small. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 17:17:39 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b9] InstallationDate: Installed on 2020-01-26 (54 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 13-ae0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=7cfa547e-7b38-4467-9a1c-5f581ce738c1 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: AMI dmi.bios.version: F.24 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 83B9 dmi.board.vendor: HP dmi.board.version: 56.43 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.24:bd01/07/2019:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.43:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-ae0xx dmi.product.sku: 1WU65AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- Scrolling jumps after switching tabs https://bugs.launchpad.net/bugs/1868332 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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
Hi Kai Heng Feng, Sorry for delaying this for long. I already check and it already enable but in log file still not. I think there is something not meet with the configuration. Please see log file. Thanks and regards, ** Attachment added: "prevboot4.txt" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860754/+attachment/5339588/+files/prevboot4.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN 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.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU 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.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/linux/+bug/1860754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868353] [NEW] regression: Bose SL III works in bionic but not in focal
Public bug reported: blueman-manager successfully pairs and connects to the Bose SL III in both bionic and in focal. in bionic, the Bose SL III then immediately shows up in pavucontrol. in focal, it remains absent. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Fri Mar 20 19:53:54 2020 InstallationDate: Installed on 2020-03-15 (5 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1868353 Title: regression: Bose SL III works in bionic but not in focal Status in pulseaudio package in Ubuntu: New Bug description: blueman-manager successfully pairs and connects to the Bose SL III in both bionic and in focal. in bionic, the Bose SL III then immediately shows up in pavucontrol. in focal, it remains absent. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Fri Mar 20 19:53:54 2020 InstallationDate: Installed on 2020-03-15 (5 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200314) ProcEnviron: LC_TIME=en_DK.utf8 TERM=screen PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: J9ETA2WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20C6008SUS dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrJ9ETA2WW(2.28):bd06/20/2018:svnLENOVO:pn20C6008SUS:pvrThinkPadEdgeE540:rvnLENOVO:rn20C6008SUS:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E540 dmi.product.name: 20C6008SUS dmi.product.sku: LENOVO_MT_20C6_BU_Think_FM_ThinkPad Edge E540 dmi.product.version: ThinkPad Edge E540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868319] Re: PCI/internal sound card not detected
5.3.0-42.34-generic has regression, please try with 5.3.0-43 kernel. -- 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/1868319 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Any time now, the sound card was deactivated, and it appears as a "Dummy device". I searched many forums about it, but nothing works. I'll be grateful if a program exists that I could install for sound card recognition. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 16:13:53 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 054J60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868330] Re: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work
Please manually install alsa-ucm-conf package and reboot. This package will be put into the 20.04 image soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1868330 Title: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work Status in alsa-driver package in Ubuntu: New Bug description: On Focal Fossa the microphone is recognised but doesn't work. Chromium shows the microphone as present but off, and if it is renabled it goes off again after a couple of seconds. Chromium logs this error: [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th chromium_chromium.desktop[9531]: [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation is nullptr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1687 F pulseaudio /dev/snd/pcmC0D0p: user 1687 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 23:03:01 2020 InstallationDate: Installed on 2020-03-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868352] [NEW] grub2 2.04-1ubuntu12.2 breaks boot on some machines
Public bug reported: 2.04-1ubuntu12.2 broke boot on my machine. It doesn't work with kernels that don't have CONFIG_EFI_STUB=y configured. This really needs to fall back to the old mode if EFI handover is not supported by the kernel. Also, after using a kernel with CONFIG_EFI_STUB=y it still failed to boot one of my machines with root specified by UUID. I was able to workaround it by manually specifying the boot device with /dev/nvme0n1p2 at the grub menu, and then specifying GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.10-customskl x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Mar 20 21:19:01 2020 DistUpgraded: 2019-10-26 18:15:16,011 DEBUG running apport_crash() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: zfs, 0.8.3, 5.5.10-customskl, x86_64: installed zfs, 0.8.3, 5.5.9-customskl, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:872f] InstallationDate: Installed on 2012-12-04 (2664 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.5.10-customskl root=/dev/nvme0n1p2 ro rootflags=subvol=@ drm_kms_helper.edid_firmware=DP-1:edid/monoprice_28_4k.edid SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-26 (146 days ago) dmi.bios.date: 10/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2203 dmi.board.asset.tag: Default string dmi.board.name: ROG MAXIMUS X HERO (WI-FI AC) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2203:bd10/07/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGMAXIMUSXHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4~yasi1~19.10 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1~yasi1~19.10 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1~yasi1~19.10 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 N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20191209.2226.f66d3954-0ubuntu0+yasi1~19.10 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan fonts kubuntu regression-update third-party-packages ubuntu ** Tags added: regression-update -- 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/1868352 Title: grub2 2.04-1ubuntu12.2 breaks boot on some machines Status in xorg package in Ubuntu: New Bug description: 2.04-1ubuntu12.2 broke boot on my machine. It doesn't work with kernels that don't have CONFIG_EFI_STUB=y configured. This really needs to fall back to the old mode if EFI handover is not supported by the kernel. Also, after using a kernel with CONFIG_EFI_STUB=y it still failed to boot one of my machines with root specified by UUID. I was able to workaround it by manually specifying the boot device with /dev/nvme0n1p2 at the grub menu, and then specifying GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 Uname: Linux 5.5.10-customskl x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Fri Mar 20 21:19:01 2020 DistUpgraded: 2019-10-26 18:15:16,011 DEBUG running apport_crash() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: zfs, 0.8.3, 5.5.10-customskl, x86_64: installed zfs, 0.8.3, 5.5.9-customskl, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:872f]
[Desktop-packages] [Bug 1868335] [NEW] Sync colord 1.4.4-2 (main) from Debian unstable (main)
Public bug reported: Please sync colord 1.4.4-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * No-change rebuild with fixed binutils on arm64. * Omit colord-sensor-argyll on i386. The change to omit colord-sensor-argyll on i386 was adopted in Debian. Changelog entries since current focal version 1.4.4-1ubuntu2: colord (1.4.4-2) unstable; urgency=medium * Team upload. * Bump debhelper to 12 and install the daemons in /usr/libexec * debian/rules: Explicitly disable systemd and udev on non-linux architectures * debian/control: Bump Standards-Version to 4.5.0 (no further changes) * debian/control: Drop docbook-utils from build-dep, this doesn't seems necessary and add xsltproc instead * debian/control: Mark the -dev and gir packages as Multi-arch: same * Omit colord-sensor-argyll on Ubuntu/i386. Thanks to Steve Langasek (Closes: #948540) * debian/control: Set Rules-Requires-Root: no * debian/watch: Use https:// instead of http:// * d/p/tests-Make-the-build-reproductible.patch: Make the build reproductible * debian/gbp.conf: Set upstream-vcs-tag and make sure patches are not numbered -- Laurent Bigonville Fri, 20 Mar 2020 15:50:36 +0100 ** Affects: colord (Ubuntu) Importance: Wishlist Status: New ** Changed in: colord (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1868335 Title: Sync colord 1.4.4-2 (main) from Debian unstable (main) Status in colord package in Ubuntu: New Bug description: Please sync colord 1.4.4-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * No-change rebuild with fixed binutils on arm64. * Omit colord-sensor-argyll on i386. The change to omit colord-sensor-argyll on i386 was adopted in Debian. Changelog entries since current focal version 1.4.4-1ubuntu2: colord (1.4.4-2) unstable; urgency=medium * Team upload. * Bump debhelper to 12 and install the daemons in /usr/libexec * debian/rules: Explicitly disable systemd and udev on non-linux architectures * debian/control: Bump Standards-Version to 4.5.0 (no further changes) * debian/control: Drop docbook-utils from build-dep, this doesn't seems necessary and add xsltproc instead * debian/control: Mark the -dev and gir packages as Multi-arch: same * Omit colord-sensor-argyll on Ubuntu/i386. Thanks to Steve Langasek (Closes: #948540) * debian/control: Set Rules-Requires-Root: no * debian/watch: Use https:// instead of http:// * d/p/tests-Make-the-build-reproductible.patch: Make the build reproductible * debian/gbp.conf: Set upstream-vcs-tag and make sure patches are not numbered -- Laurent Bigonville Fri, 20 Mar 2020 15:50:36 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1868335/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868333] Re: Volume and screen brightness sliders are not updated on the status menu
As an additional info: this is a regression after updating to 20.04, the sliders worked fine on 19.10. -- 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/1868333 Title: Volume and screen brightness sliders are not updated on the status menu Status in gnome-shell package in Ubuntu: New Bug description: On boot, the volume and screen brightness sliders on the status menu are at their minimum value, despite both volume and screen brightness being set at a different level (as expected, the same levels they were on last shutdown). Changing volume or brightness with keyboard shortcuts change the setting, but the sliders on the status menu are no updated. The sliders are functional when modified by dragging with the mouse, but their position remains fixed despite changing the settings afterwards by keyboard. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 21:34:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (756 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-01 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868333] [NEW] Volume and screen brightness sliders are not updated on the status menu
Public bug reported: On boot, the volume and screen brightness sliders on the status menu are at their minimum value, despite both volume and screen brightness being set at a different level (as expected, the same levels they were on last shutdown). Changing volume or brightness with keyboard shortcuts change the setting, but the sliders on the status menu are no updated. The sliders are functional when modified by dragging with the mouse, but their position remains fixed despite changing the settings afterwards by keyboard. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 21:34:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (756 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-01 (19 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - Volume and screen brightness sliders are not update on the status menu + Volume and screen brightness sliders are not updated on the status menu -- 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/1868333 Title: Volume and screen brightness sliders are not updated on the status menu Status in gnome-shell package in Ubuntu: New Bug description: On boot, the volume and screen brightness sliders on the status menu are at their minimum value, despite both volume and screen brightness being set at a different level (as expected, the same levels they were on last shutdown). Changing volume or brightness with keyboard shortcuts change the setting, but the sliders on the status menu are no updated. The sliders are functional when modified by dragging with the mouse, but their position remains fixed despite changing the settings afterwards by keyboard. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 21:34:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (756 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-01 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868331] Re: tracker-store crashed with SIGSEGV in tracker_data_commit_transaction()
*** This bug is a duplicate of bug 1843083 *** https://bugs.launchpad.net/bugs/1843083 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1843083, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1868331/+attachment/5339508/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1868331/+attachment/5339510/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1868331/+attachment/5339514/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1868331/+attachment/5339515/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1868331/+attachment/5339516/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1868331/+attachment/5339517/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1868331/+attachment/5339518/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1843083 tracker-store crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1868331 Title: tracker-store crashed with SIGSEGV in tracker_data_commit_transaction() Status in tracker package in Ubuntu: New Bug description: Error on boot ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: tracker 2.3.1-3build1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Mar 21 02:02:45 2020 ExecutablePath: /usr/lib/tracker/tracker-store ProcCmdline: /usr/lib/tracker/tracker-store SegvAnalysis: Segfault happened at: 0x55ea1dd73243:cmpq $0x0,0x8(%rdi) PC (0x55ea1dd73243) ok source "$0x0" ok destination "0x8(%rdi)" (0x0008) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: ?? () ?? () tracker_data_commit_transaction () from /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so ?? () from /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so ?? () Title: tracker-store crashed with SIGSEGV in tracker_data_commit_transaction() UpgradeStatus: Upgraded to focal on 2020-03-13 (7 days ago) UserGroups: adm cdrom dialout dip fax floppy lpadmin lxd plugdev sambashare sudo tape video separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1868331/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868330] Re: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work
I've tried audacity and firefox too and no sound can be recorded. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1868330 Title: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work Status in alsa-driver package in Ubuntu: New Bug description: On Focal Fossa the microphone is recognised but doesn't work. Chromium shows the microphone as present but off, and if it is renabled it goes off again after a couple of seconds. Chromium logs this error: [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th chromium_chromium.desktop[9531]: [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation is nullptr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1687 F pulseaudio /dev/snd/pcmC0D0p: user 1687 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 23:03:01 2020 InstallationDate: Installed on 2020-03-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868330] [NEW] Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work
Public bug reported: On Focal Fossa the microphone is recognised but doesn't work. Chromium shows the microphone as present but off, and if it is renabled it goes off again after a couple of seconds. Chromium logs this error: [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th chromium_chromium.desktop[9531]: [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation is nullptr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1687 F pulseaudio /dev/snd/pcmC0D0p: user 1687 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 23:03:01 2020 InstallationDate: Installed on 2020-03-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712 ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1868330 Title: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work Status in alsa-driver package in Ubuntu: New Bug description: On Focal Fossa the microphone is recognised but doesn't work. Chromium shows the microphone as present but off, and if it is renabled it goes off again after a couple of seconds. Chromium logs this error: [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th chromium_chromium.desktop[9531]: [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation is nullptr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1687 F pulseaudio /dev/snd/pcmC0D0p: user 1687 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 23:03:01 2020 InstallationDate: Installed on 2020-03-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available
[Desktop-packages] [Bug 1868296] Re: gnome-tweaks UI breaks on lower resolution
** Also affects: gnome-tweaks Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868296 Title: gnome-tweaks UI breaks on lower resolution Status in GNOME Tweaks: New Status in gnome-shell package in Ubuntu: New Bug description: On 1366 * 768 resolution of my laptop (Dell E7259) gnome-tweaks UI breaks and some parts of it go missing. After maximizing the window, it works as normal again. Ubuntu versions I tried and had this problem: 1. Ubuntu 19.10 2. Ubuntu 20.20 daily iso Ubuntu versions I tried and do not have this problem: 1. ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-tweaks/+bug/1868296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868319] [NEW] PCI/internal sound card not detected
Public bug reported: Any time now, the sound card was deactivated, and it appears as a "Dummy device". I searched many forums about it, but nothing works. I'll be grateful if a program exists that I could install for sound card recognition. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 16:13:53 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 054J60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1868319 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Any time now, the sound card was deactivated, and it appears as a "Dummy device". I searched many forums about it, but nothing works. I'll be grateful if a program exists that I could install for sound card recognition. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 16:13:53 2020 InstallationDate: Installed on 2020-03-19 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 054J60 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd08/08/2019:svnDellInc.:pnG33590:pvr:rvnDellInc.:rn054J60:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3590 dmi.product.sku: 0949 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868319/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session
XWayland does not have this issue for me. -- 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/1853199 Title: Ctrl + c (copy) anywhere some times crashes gnome session Status in gnome-shell package in Ubuntu: Incomplete Bug description: Copy text anwyhere (browser, terminal) crashes user session and shows login screen. It may take few login attempts to actually login back. I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is always ON but tv is ON amd OFF as needed. Every time I turn tv ON and try to do something and use ctrl + c it would restart gnome session. After login it seem to work fine and ctrl+c does not break anything. Then the next day the similar thing happens. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 19 20:55:37 2019 DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 [1297:4057] InstallationDate: Installed on 2019-07-21 (121 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Shuttle Inc. XH270 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago) dmi.bios.date: 01/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.02 dmi.board.asset.tag: Default string dmi.board.name: FH270 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: X dmi.product.name: XH270 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle 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.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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-07-21 (213 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 Tags: eoan Uname: Linux 5.3.0-29-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-26 (116 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868296] [NEW] gnome-tweaks UI breaks on lower resolution
Public bug reported: On 1366 * 768 resolution of my laptop (Dell E7259) gnome-tweaks UI breaks and some parts of it go missing. After maximizing the window, it works as normal again. Ubuntu versions I tried and had this problem: 1. Ubuntu 19.10 2. Ubuntu 20.20 daily iso Ubuntu versions I tried and do not have this problem: 1. ubuntu 18.04 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot of the broken UI of gnome-tweaks" https://bugs.launchpad.net/bugs/1868296/+attachment/5339449/+files/Screenshot%20from%202020-03-20%2019-07-25.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1868296 Title: gnome-tweaks UI breaks on lower resolution Status in gnome-shell package in Ubuntu: New Bug description: On 1366 * 768 resolution of my laptop (Dell E7259) gnome-tweaks UI breaks and some parts of it go missing. After maximizing the window, it works as normal again. Ubuntu versions I tried and had this problem: 1. Ubuntu 19.10 2. Ubuntu 20.20 daily iso Ubuntu versions I tried and do not have this problem: 1. ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867829] Re: Unable to access settings on extensions in Gnome Tweaks
*** This bug is a duplicate of bug 1866146 *** https://bugs.launchpad.net/bugs/1866146 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867829 Title: Unable to access settings on extensions in Gnome Tweaks Status in gnome-shell package in Ubuntu: Confirmed Bug description: 20.04 Ubuntu updated 20200317 Expected: Open Gnome Tweaks and go to Extensions, Click on settings wheel next to an installed extensions and settings will open. Actual: Open Gnome Tweaks and go to Extensions, Click on settings wheel next to an installed extension and nothing opens. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 17 13:49:42 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-01-15 (62 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200106) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868268] Re: Cannot Print with Brother Brother QL-700 Label Printer, it's a big problem
** Package changed: ubuntu => cups (Ubuntu)
--
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/1868268
Title:
Cannot Print with Brother Brother QL-700 Label Printer, it's a big
problem
Status in cups package in Ubuntu:
New
Bug description:
imprimante frère ql-700 imprimante d'étiquettes
205/5000
J'ai l'air d'être reconnu mais quand j'essaie d'imprimer un fichier édité
avec des glabels je ne peux pas le faire, cela me montre une première
impression d'infobulle, et une deuxième impression terminée, mais il ne réagit
pas
it's my log files
Page 1 ():
{ 'cups_ connection_ échec' : Faux}
Page 2 (<. Résoudre les problèmes CheckLocalServe . RPublishing
CheckLocalServe objet rPublishing à 0x7f122989e280>):
{ 'local_ server_ exporting_ imprimantes' : False}
Page 3 ():
{'cups_dest': ,
'cups_instance': None,
'cups_queue': 'Brother- QL-700 ',
' cups_ queue_listed ': Vrai}
Page 4 ():
{ 'cups_ device_ uri_scheme' : 'usb',
'cups_ printer_ dict': { 'appareil uri': « usb: // Brother / QL- 700? serial
= 000B7Z702725 ' ,
' imprimante- info ':' Brother QL-700 ',
' imprimante- est-partagé ' : Vrai,
' imprimante- emplacement ' :' puce- HP-Pavilion-
Power-Desktop- 580-0xx ' ,
'imprimante -marque-et- modèle': 'Brother QL-700 CUPS
v1.4',
message-d'état ' :' ',
' raisons- d'état- imprimante ' : [' aucun '],
' type d'imprimante ': 8523844,
' support d'imprimante -uri ' :' ipp: // localhost /
printers / Brother- QL -700' },
'cups_ printer_ à distance' : Faux,
'is_cups_class': Faux,
'local_ cups_queue_ attributs' : { 'charset- configured' : 'utf-8',
'charset- soutenu' : [ 'us-ascii' ,
'utf-8'],
'couleur prise en charge' : False,
'compressi on-supported' : ['aucun', 'gzip'],
'copies- default' : 1,
'copies- supported' : (1, ),
'cups- version' : '2.3.1',
'device- uri': 'usb: // Brother / QL-700?
serial = 000B7Z702725 ' ,
' document- format- default ' :' application
/ octet-stream ' ,
' document- format- supported ' : ['
application / octet-stream ' ,
' application
/ pdf ',
' application
/ postscript ' ,
'application /
vnd.
'application /
vnd.cups- command' ,
'application /
vnd.cups- pdf',
'application /
vnd.cups- pdf-banner' ,
'application /
vnd.cups- postscript' ,
'application /
vnd.cups- raster ' ,
' application
/ vnd.cups- raw ',
' application
/ x-cshell ' ,
' application
/ x-csource ' ,
' application
/ x-perl ' ,
' application
/ x-shell ' ,
' image / gif
',
'image /
jpeg',
'image / png
',
' image
/pwg-raster ' ,
' image / tiff
',
' image / urf
',
' image /
x-bitmap ' ,
' image /
x-photocd ' ,
' image /
x-portable- anymap ' ,
' image /
x-portable- bitmap ' ,
' image /
x-portable- graymap ' ,
[Desktop-packages] [Bug 1868268] [NEW] Cannot Print with Brother Brother QL-700 Label Printer, it's a big problem
You have been subscribed to a public bug:
imprimante frère ql-700 imprimante d'étiquettes
205/5000
J'ai l'air d'être reconnu mais quand j'essaie d'imprimer un fichier édité avec
des glabels je ne peux pas le faire, cela me montre une première impression
d'infobulle, et une deuxième impression terminée, mais il ne réagit pas
it's my log files
Page 1 ():
{ 'cups_ connection_ échec' : Faux}
Page 2 (<. Résoudre les problèmes CheckLocalServe . RPublishing CheckLocalServe
objet rPublishing à 0x7f122989e280>):
{ 'local_ server_ exporting_ imprimantes' : False}
Page 3 ():
{'cups_dest': ,
'cups_instance': None,
'cups_queue': 'Brother- QL-700 ',
' cups_ queue_listed ': Vrai}
Page 4 ():
{ 'cups_ device_ uri_scheme' : 'usb',
'cups_ printer_ dict': { 'appareil uri': « usb: // Brother / QL- 700? serial =
000B7Z702725 ' ,
' imprimante- info ':' Brother QL-700 ',
' imprimante- est-partagé ' : Vrai,
' imprimante- emplacement ' :' puce- HP-Pavilion-
Power-Desktop- 580-0xx ' ,
'imprimante -marque-et- modèle': 'Brother QL-700 CUPS
v1.4',
message-d'état ' :' ',
' raisons- d'état- imprimante ' : [' aucun '],
' type d'imprimante ': 8523844,
' support d'imprimante -uri ' :' ipp: // localhost /
printers / Brother- QL -700' },
'cups_ printer_ à distance' : Faux,
'is_cups_class': Faux,
'local_ cups_queue_ attributs' : { 'charset- configured' : 'utf-8',
'charset- soutenu' : [ 'us-ascii' , 'utf-8'],
'couleur prise en charge' : False,
'compressi on-supported' : ['aucun', 'gzip'],
'copies- default' : 1,
'copies- supported' : (1, ),
'cups- version' : '2.3.1',
'device- uri': 'usb: // Brother / QL-700?
serial = 000B7Z702725 ' ,
' document- format- default ' :' application /
octet-stream ' ,
' document- format- supported ' : ['
application / octet-stream ' ,
' application /
pdf ',
' application /
postscript ' ,
'application /
vnd.
'application /
vnd.cups- command' ,
'application /
vnd.cups- pdf',
'application /
vnd.cups- pdf-banner' ,
'application /
vnd.cups- postscript' ,
'application /
vnd.cups- raster ' ,
' application /
vnd.cups- raw ',
' application /
x-cshell ' ,
' application /
x-csource ' ,
' application /
x-perl ' ,
' application /
x-shell ' ,
' image / gif ',
'image / jpeg',
'image / png ',
' image
/pwg-raster ' ,
' image / tiff
',
' image / urf ',
' image /
x-bitmap ' ,
' image /
x-photocd ' ,
' image /
x-portable- anymap ' ,
' image /
x-portable- bitmap ' ,
' image /
x-portable- graymap ' ,
' image /
x-portable- pixmap ' ,
' image /
x-sgi-rgb ' ,
' image /
x-sun-raster ' ,
' image /
x-xbitmapmap ' ,
'image /
x-xpixmap' ,
[Desktop-packages] [Bug 1868216] Re: Please include updated Lithuanian, French and Polish translations from upstream
Thanks for your report. I won't add any translation updates separately, though. Please note that beta is not a deadline for translations. But I will probably do an upload soon before final release with either version 3.36.1 or a git snapshot. ** Changed in: gnome-getting-started-docs (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-getting-started-docs (Ubuntu) Status: New => Triaged ** Changed in: gnome-getting-started-docs (Ubuntu) Milestone: None => ubuntu-20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-getting-started-docs in Ubuntu. https://bugs.launchpad.net/bugs/1868216 Title: Please include updated Lithuanian, French and Polish translations from upstream Status in gnome-getting-started-docs package in Ubuntu: Triaged Bug description: Please include updated Lithuanian, French and Polish translations from upstream: https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/ It is important to do ASAP because Ubuntu will be in Beta freeze very soon - Beta will be released at April 2nd. See https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/-/commits/master for more information. Also I'm attaching Lithuanian, French and Polish translations from GIT to this bugreport, please include :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1868216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
Ubuntu 19.10 with kernel 5.3.0-43-generic works as well WiFi interface is not detected but it is an other issue Thanks once more -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Fix Released Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
Thanks for the update Zbigniew. ** Changed in: alsa-driver (Ubuntu) Status: Confirmed => Fix Released -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Fix Released Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
btw. I'm using Ubuntu 20.04 with kernel 5.4.0-18-generic -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] Re: [Dell Vostro 5590] PCI/internal sound card not detected
Problem solved. After upgrading linux-firmware to version 1.187 both input and output work as expected. Thanks a lot. -- 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/1867474 Title: [Dell Vostro 5590] PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865298] Re: [FFe] Request for update: HPLIP 3.20.3
Made it into the release of Focal, closing. ** Changed in: hplip (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1865298 Title: [FFe] Request for update: HPLIP 3.20.3 Status in hplip package in Ubuntu: Fix Released Bug description: Version 3.20.3 of HPLIP was released in March supporting these new printers: HP Neverstop Laser MFP 1200n HP Neverstop Laser MFP 1201n HP Neverstop Laser MFP 1200nw HP Neverstop Laser MFP 1202nw HP Laser NS MFP 1005n HP Neverstop Laser 1000n HP Neverstop Laser 1001nw HP Laser NS 1020n HP ScanJet Pro 2000 s2 HP ScanJet Pro 3000 s4 HP ScanJet Pro N4000 snw1 HP ScanJet Enterprise Flow 5000 s5 HP ScanJet Enterprise Flow N7000 snw1 Version 3.20.2 of HPLIP was released in February but had a severe bug (bug 1866291) making many users not able to print. The bug is fixed in version 3.20.3. 3.20.2 got withdrawn on HP's web site. To extend the range of hardware devices supported in Focal we should get this HPLIP 3.20.3 into Focal. There is no file containing information about what has been changed or added in version 3.20.3 compared to 3.19.12. There is also no public version control system where one could see the changes. The only information is that the devices listed above are newly supported in 3.20.3. HPLIP 3.20.3 got already packaged for Debian Unstable and there is no Ubuntu-specific change left which is not contained in the Debian package. Therefore I request the sync of the Debian package (hplip_3.20.3+dfsg0-1) into Focal. I have tested this Debian package of HPLIP 3.20.3 now and it seems that it is working so far. I can print and scan both via network and USB and also start GUI tools like hp-toolbox and hp-setup. hp-toolbox correctly lists jobs, settable options, and ink levels and with hp- setup I was able to create print queues for my printer. My printer is the HP OfficeJet Pro 8730 which is already supported for a longer time and I do not see any difference, especially no regression compared to older versions of HPLIP. Logs of the package build with pbuilder and of the package update on a Focal system are attached. See comments below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1865298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868085] Re: Bug related to the new kernel version 5.3.0-42-generic
** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1868085 Title: Bug related to the new kernel version 5.3.0-42-generic Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hi all, After an update of Ubuntu kernel (version 5.3.0-42-generic) I can't have sound any more. No soundcards are detected any I have a "dummy output" in the sound pannel in settings. Furthermore I can't resume from sleep anymore. Output of ALSA Information script: !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Wed Mar 18 14:46:19 UTC 2020 !!Linux Distribution !!-- Ubuntu 18.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=bionic !!DMI Information !!--- Manufacturer: HP Product Name: HP ZBook 15u G6 Product Version: Firmware Version: R70 Ver. 01.03.04 Board Vendor: HP Board Name:8549 !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/HPIC000C:00/status 15 /sys/bus/acpi/devices/HPQ6001:00/status15 /sys/bus/acpi/devices/IFX0785:00/status15 /sys/bus/acpi/devices/INT3400:00/status15 /sys/bus/acpi/devices/INT3403:00/status15 /sys/bus/acpi/devices/INT3403:01/status15 /sys/bus/acpi/devices/INT340E:00/status15 /sys/bus/acpi/devices/INT34BB:00/status15 /sys/bus/acpi/devices/INT3F0D:00/status15 /sys/bus/acpi/devices/LNXPOWER:00/status 15 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0B00:00/status15 /sys/bus/acpi/devices/PNP0C02:00/status3 /sys/bus/acpi/devices/PNP0C02:01/status3 /sys/bus/acpi/devices/PNP0C02:05/status3 /sys/bus/acpi/devices/PNP0C09:00/status15 /sys/bus/acpi/devices/PNP0C0A:00/status31 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PRP1:00/status 11 /sys/bus/acpi/devices/SYNA3092:00/status 15 /sys/bus/acpi/devices/USBC000:00/status15 /sys/bus/acpi/devices/device:04/status 15 /sys/bus/acpi/devices/device:27/status 15 /sys/bus/acpi/devices/device:28/status 15 /sys/bus/acpi/devices/device:4c/status 15 !!Kernel Information !!-- Kernel release:5.3.0-42-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-42-generic Library version:1.1.3 Utilities version: 1.1.3 !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- --- no soundcards --- !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:9dc8] (rev 11) Subsystem: Hewlett-Packard Company Device [103c:8549] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!ALSA Device nodes !!- crw-rw 1 root audio 116, 1 Mar 18 14:45 /dev/snd/seq crw-rw 1 root audio 116, 33 Mar 18 14:44 /dev/snd/timer !!Aplay/Arecord output !! APLAY aplay: device_list:270: no soundcards found... ARECORD arecord:
[Desktop-packages] [Bug 1730612] Re: Enable Remote desktop feature during build
Pipewire is packaged now, can we get it enabled? -- 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/1730612 Title: Enable Remote desktop feature during build Status in Default settings and artwork for Baltix OS: New Status in mutter package in Ubuntu: Triaged Bug description: Currently there are no way to use Remote Desktop (Desktop sharing) and Screen Recording in Ubuntu 17.10 Wayland (default) session because Remote desktop feature isn't enabled during build :( Please use --enable-remote-desktop during build, see https://wiki.gnome.org/Projects/Mutter/RemoteDesktop Currently in mutter 3.26.1 and 3.26.2 (Artful and Bionic) build log I see this: mutter-3.26.1 [..] Wayland: yes Native (KMS) backend: yes EGLDevice:yes Remote desktop: no To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868260] [NEW] Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement
Public bug reported: Based on Energy Star Computers Specification Version 8.0[1] Table 3: Power Management Requirements (page 10) The energy star spec requests - The machine shall enter Sleep/Alternative Low Power Mode after no more than 30 minutes of user inactivity. (suspend) - The machine shall enter Display Sleep Mode shall be set to activate after no more than 15 minutes of user inactivity. The default settings in focal are - The machine will enter Sleep/Alternative Low Power Mode in 20 minutes with battery[2] - The machine is always on with the AC[2] - Enter Display Sleep Mode in 5 minutes[3] OEM device team suggested to change org.gnome.settings- daemon.plugins.power sleep-inactive-ac-timeout to 1200 (20 minutes) as default to meet the Power Management Requirements of Energy Star Computers Specification Version 8.0. [1] Computers Specification Version 8.0 | | ENERGY STAR - https://www.energystar.gov/products/spec/computers_version_8_0_pd [2] % gsettings list-recursively org.gnome.settings-daemon.plugins.power|grep sleep- org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 1200 [3] % gsettings list-recursively org.gnome.desktop.session org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 ** Affects: oem-priority Importance: High Assignee: Rex Tsai (chihchun) Status: New ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => Rex Tsai (chihchun) -- 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/1868260 Title: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement Status in OEM Priority Project: New Status in gnome-settings-daemon package in Ubuntu: New Bug description: Based on Energy Star Computers Specification Version 8.0[1] Table 3: Power Management Requirements (page 10) The energy star spec requests - The machine shall enter Sleep/Alternative Low Power Mode after no more than 30 minutes of user inactivity. (suspend) - The machine shall enter Display Sleep Mode shall be set to activate after no more than 15 minutes of user inactivity. The default settings in focal are - The machine will enter Sleep/Alternative Low Power Mode in 20 minutes with battery[2] - The machine is always on with the AC[2] - Enter Display Sleep Mode in 5 minutes[3] OEM device team suggested to change org.gnome.settings- daemon.plugins.power sleep-inactive-ac-timeout to 1200 (20 minutes) as default to meet the Power Management Requirements of Energy Star Computers Specification Version 8.0. [1] Computers Specification Version 8.0 | | ENERGY STAR - https://www.energystar.gov/products/spec/computers_version_8_0_pd [2] % gsettings list-recursively org.gnome.settings-daemon.plugins.power|grep sleep- org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 1200 [3] % gsettings list-recursively org.gnome.desktop.session org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1868260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868131] Re: [Toshiba NB250] Integrated speakers always muted
Writes down all circumstances - with the same hardware it is reproducible. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1868131 Title: [Toshiba NB250] Integrated speakers always muted Status in pulseaudio package in Ubuntu: Confirmed Bug description: Speakers are muted at boot and remains muted after plug and unplug headphones. Only can be activated from alsamixer, unmuting the headphones while the headphones are unplugged. Both speakers and headphones muting seems to be controlled in the Headphones area using alsamixer. Same problem in pulseaudio 1:11.1-1ubuntu7.4 on Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic. I've "solved" it Linux Mint 19.3 Tricia in a not very good way, keeping automute activated in alsamixer, modifiyng /usr/share/pulseaudio/alsa-mixer/paths/analog-output-headphones.conf and executing a bash script at boot (sonido.sh) with the command "amixer set -c 0 Headphone unmute 100%" in order to prevent the speakers being muted. There are some issues reported to pulseaudio manteiners. Not the same but related: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/256 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/540 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu1881 F pulseaudio CasperVersion: 1.427 CurrentDesktop: XFCE Date: Thu Mar 19 15:58:26 2020 LiveMediaBuild: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.60 dmi.board.name: PAV10 DDR2 dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.60:bd07/30/2010:svnTOSHIBA:pnTOSHIBANB250:pvrPLL2XE-005003AS:rvnTOSHIBA:rnPAV10DDR2:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ dmi.product.name: TOSHIBA NB250 dmi.product.sku: 012345678912345678912345678 dmi.product.version: PLL2XE-005003AS dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1868131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865379] Re: Raspberry Pi 4 fails to wake at login prompt
This morning that system has stopped booting. I am not sure why. I can
try and pull the SD card out and get the ID for the error report. If
not, then I will need to pull all this information again from the second
system that is displaying the same behavior.
--
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/1865379
Title:
Raspberry Pi 4 fails to wake at login prompt
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
Eoan) fails to wake from sleep when no user is logged in and the
screen is sitting at the gdm login prompt.
This has happened on two different systems. One system uses the
official RPi 7 inch touchscreen via (LCD DSI Display Connector). The
other system has a 10 inch non-touchscreen from SunFounder via (Micro
HDMI).
Nothing wakes the Pi: Keyboard, mouse, or touchscreen.
After a user logs in and the screen locks on sleep the system wakes
just fine with a lock screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Uname: Linux 5.4.0-1001-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
Date: Sun Mar 1 20:03:12 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1865379/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868252] Re: Xorg crashed with SIGSEGV in miPointerSetPosition()
*** This bug is a duplicate of bug 1846221 *** https://bugs.launchpad.net/bugs/1846221 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1846221, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1868252/+attachment/5339327/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1868252/+attachment/5339330/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1868252/+attachment/5339341/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1868252/+attachment/5339343/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1868252/+attachment/5339344/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1868252/+attachment/5339345/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1868252/+attachment/5339346/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1846221 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1868252 Title: Xorg crashed with SIGSEGV in miPointerSetPosition() Status in xorg-server package in Ubuntu: New Bug description: On reboot after updates, then a crash. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 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: Fri Mar 20 09:45:38 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:124d] InstallationDate: Installed on 2020-02-16 (32 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) MachineType: ASUSTeK COMPUTER INC. X550CA ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=3f952580-bb63-4f1a-bc9a-681243c4f18d ro SegvAnalysis: Segfault happened at: 0x56108d616d97 : mov 0x2c(%rax),%edx PC (0x56108d616d97) ok source "0x2c(%rax)" (0x002c) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xorg-server StacktraceTop: miPointerSetPosition () () () GetPointerEvents () QueuePointerEvents () Title: Xorg crashed with SIGSEGV in miPointerSetPosition() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CA 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.:bvrX550CA.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
[Desktop-packages] [Bug 1868158] Re: Reopen issue 1666681
> also that bug is a duplicate as you knew when opening it, the fact that the > issue has been > wontfixed is not a reason to create extra work for others by registered a new > ticket I can't reopen that one and comments seem to be ignored, that's why I created a new one. What you should do then is mark this one as duplicate and reopen the original one. Anyway, who cares, Ubuntu is beyond help. -- 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/1868158 Title: Reopen issue 181 Status in nautilus package in Ubuntu: Won't Fix Bug description: Issue 181 needs to be reopened and fixed. Just see the latest comments. For fuck's sake. That issue has made Ubuntu completely unusable to the point that I have stopped upgrading since Ubuntu 16.04. Ubuntu should also consider dropping Nautilus altogether, because the existence of this issue (which is a design decision that the upstream developers defend) demonstrates that it's maintained by a bunch of idiots. Either you fork from it or you pick a decent file manager that is not spiraling into complete dementia. Anyway, in the shorter term, it seems that there are working patches available to mitigate this disgrace. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 19 19:52:02 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'192' b'org.gnome.nautilus.window-state' b'geometry' b"'1296x917+1232+81'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (2351 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702493] Re: package libvdpau1 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other instances of packag
in ubuntu19.10 I install wine5.0 the same error appear.
widon@widon-ubuntu:~$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
linux-headers-5.3.0-18 linux-headers-5.3.0-18-generic
linux-image-5.3.0-18-generic linux-modules-5.3.0-18-generic
linux-modules-extra-5.3.0-18-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
libvdpau1
The following NEW packages will be installed:
libvdpau1
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
84 not fully installed or removed.
Need to get 0 B/25.5 kB of archives.
After this operation, 109 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = "zh_CN:zh",
LC_ALL = (unset),
LANG = "en.US"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
(Reading database ... 222146 files and directories currently installed.)
Preparing to unpack .../libvdpau1_1.2-1ubuntu1_amd64.deb ...
Unpacking libvdpau1:amd64 (1.2-1ubuntu1) ...
dpkg: error processing archive
/var/cache/apt/archives/libvdpau1_1.2-1ubuntu1_amd64.deb (--unpack):
trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different from
other instances of package libvdpau1:amd64
Errors were encountered while processing:
/var/cache/apt/archives/libvdpau1_1.2-1ubuntu1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
How can I fix it?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libvdpau in Ubuntu.
https://bugs.launchpad.net/bugs/1702493
Title:
package libvdpau1 (not installed) failed to install/upgrade: trying to
overwrite shared '/etc/vdpau_wrapper.cfg', which is different from
other instances of package libvdpau1:amd64
Status in libvdpau package in Ubuntu:
Confirmed
Bug description:
I dont know anything about the bug but cannot install any software
from the store
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libvdpau1 (not installed)
ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-58-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
BootLog:
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Jul 5 19:57:11 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DuplicateSignature:
package:libvdpau1:(not installed)
Unpacking libvdpau1:amd64 (1.1.1-3ubuntu1) ...
dpkg: error processing archive
/var/cache/apt/archives/libvdpau1_1.1.1-3ubuntu1_amd64.deb (--unpack):
trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is different
from other instances of package libvdpau1:amd64
ErrorMessage: trying to overwrite shared '/etc/vdpau_wrapper.cfg', which is
different from other instances of package libvdpau1:amd64
GraphicsCard:
Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09)
(prog-if 00 [VGA controller])
Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:390b]
InstallationDate: Installed on 2017-07-03 (1 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
MachineType: LENOVO 80E5
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-58-generic
root=UUID=61cec50e-42cb-4052-8934-d3e5748260d2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.2
apt 1.2.20
SourcePackage: libvdpau
Title: package libvdpau1 (not installed) failed to install/upgrade: trying to
overwrite shared '/etc/vdpau_wrapper.cfg', which is different from other
instances of package libvdpau1:amd64
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/23/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: B0CN93WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo G50-80
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G50-80
dmi.modalias:
dmi:bvnLENOVO:bvrB0CN93WW:bd07/23/2015:svnLENOVO:pn80E5:pvrLenovoG50-80:rvnLENOVO:rnLenovoG50-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoG50-80:
dmi.product.name: 80E5
dmi.product.version: Lenovo G50-80
dmi.sys.vendor: LENOVO
[Desktop-packages] [Bug 1865298] Re: [FFe] Request for update: HPLIP 3.20.3
Synced 3.20.3+dfsg0-1 from Debian unstable. ** Changed in: hplip (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1865298 Title: [FFe] Request for update: HPLIP 3.20.3 Status in hplip package in Ubuntu: Fix Committed Bug description: Version 3.20.3 of HPLIP was released in March supporting these new printers: HP Neverstop Laser MFP 1200n HP Neverstop Laser MFP 1201n HP Neverstop Laser MFP 1200nw HP Neverstop Laser MFP 1202nw HP Laser NS MFP 1005n HP Neverstop Laser 1000n HP Neverstop Laser 1001nw HP Laser NS 1020n HP ScanJet Pro 2000 s2 HP ScanJet Pro 3000 s4 HP ScanJet Pro N4000 snw1 HP ScanJet Enterprise Flow 5000 s5 HP ScanJet Enterprise Flow N7000 snw1 Version 3.20.2 of HPLIP was released in February but had a severe bug (bug 1866291) making many users not able to print. The bug is fixed in version 3.20.3. 3.20.2 got withdrawn on HP's web site. To extend the range of hardware devices supported in Focal we should get this HPLIP 3.20.3 into Focal. There is no file containing information about what has been changed or added in version 3.20.3 compared to 3.19.12. There is also no public version control system where one could see the changes. The only information is that the devices listed above are newly supported in 3.20.3. HPLIP 3.20.3 got already packaged for Debian Unstable and there is no Ubuntu-specific change left which is not contained in the Debian package. Therefore I request the sync of the Debian package (hplip_3.20.3+dfsg0-1) into Focal. I have tested this Debian package of HPLIP 3.20.3 now and it seems that it is working so far. I can print and scan both via network and USB and also start GUI tools like hp-toolbox and hp-setup. hp-toolbox correctly lists jobs, settable options, and ink levels and with hp- setup I was able to create print queues for my printer. My printer is the HP OfficeJet Pro 8730 which is already supported for a longer time and I do not see any difference, especially no regression compared to older versions of HPLIP. Logs of the package build with pbuilder and of the package update on a Focal system are attached. See comments below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1865298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865298] Re: [FFe] Request for update: HPLIP 3.20.3
Seeing the regression introduced in 3.20.2 I feel a bit uneasy bumping the version so late in the cycle, but I guess it's been around already for people to find the obvious bugs. I approve of this FFe - please sync 3.20.3 as soon as possible. ** Changed in: hplip (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1865298 Title: [FFe] Request for update: HPLIP 3.20.3 Status in hplip package in Ubuntu: Triaged Bug description: Version 3.20.3 of HPLIP was released in March supporting these new printers: HP Neverstop Laser MFP 1200n HP Neverstop Laser MFP 1201n HP Neverstop Laser MFP 1200nw HP Neverstop Laser MFP 1202nw HP Laser NS MFP 1005n HP Neverstop Laser 1000n HP Neverstop Laser 1001nw HP Laser NS 1020n HP ScanJet Pro 2000 s2 HP ScanJet Pro 3000 s4 HP ScanJet Pro N4000 snw1 HP ScanJet Enterprise Flow 5000 s5 HP ScanJet Enterprise Flow N7000 snw1 Version 3.20.2 of HPLIP was released in February but had a severe bug (bug 1866291) making many users not able to print. The bug is fixed in version 3.20.3. 3.20.2 got withdrawn on HP's web site. To extend the range of hardware devices supported in Focal we should get this HPLIP 3.20.3 into Focal. There is no file containing information about what has been changed or added in version 3.20.3 compared to 3.19.12. There is also no public version control system where one could see the changes. The only information is that the devices listed above are newly supported in 3.20.3. HPLIP 3.20.3 got already packaged for Debian Unstable and there is no Ubuntu-specific change left which is not contained in the Debian package. Therefore I request the sync of the Debian package (hplip_3.20.3+dfsg0-1) into Focal. I have tested this Debian package of HPLIP 3.20.3 now and it seems that it is working so far. I can print and scan both via network and USB and also start GUI tools like hp-toolbox and hp-setup. hp-toolbox correctly lists jobs, settable options, and ink levels and with hp- setup I was able to create print queues for my printer. My printer is the HP OfficeJet Pro 8730 which is already supported for a longer time and I do not see any difference, especially no regression compared to older versions of HPLIP. Logs of the package build with pbuilder and of the package update on a Focal system are attached. See comments below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1865298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827199] Re: firefox doesn't honour custom interface font when default language is Chinese
This bug still exist in ubuntu19.10 -- 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/1827199 Title: firefox doesn't honour custom interface font when default language is Chinese Status in firefox package in Ubuntu: Confirmed Bug description: I use ubuntu19.04, gnome 3.32.1, gnome tweak version 3.32.0, firefox version 66.0.3 In ubuntu18.04, firefox menu font can be set by gnome-tweak, but in ubuntu19.04 firefox menu font can not set by gnome tweak now.(The default menu font for firefox is too big and ugly I think) I don't know how to set firefox menu font now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1827199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1847712] Re: Desktop icons vanishing when in Activities Overview is jarring and looks ugly
** Changed in: gnome-shell (Ubuntu Focal) Status: In Progress => 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/1847712 Title: Desktop icons vanishing when in Activities Overview is jarring and looks ugly Status in gnome-shell-extension-desktop-icons: New Status in Ubuntu UX: New Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Focal: Fix Committed Bug description: Desktop icons vanishing and reappearing when in Activities Overview is jarring and looks ugly. Suggestions: * Don't hide them in AO, because they will be well shaded anyway; or * Fade them out and in smoothly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-desktop-icons 19.01.4-1 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Uname: Linux 5.3.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Fri Oct 11 14:24:42 2019 InstallationDate: Installed on 2019-05-02 (162 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190501) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1847712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868216] Re: Please include updated Lithuanian, French and Polish translations from upstream
** Attachment added: "French translation from gnome-getting-started-docs upstream" https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1868216/+attachment/5339238/+files/fr.po.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-getting-started-docs in Ubuntu. https://bugs.launchpad.net/bugs/1868216 Title: Please include updated Lithuanian, French and Polish translations from upstream Status in gnome-getting-started-docs package in Ubuntu: New Bug description: Please include updated Lithuanian, French and Polish translations from upstream: https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/ It is important to do ASAP because Ubuntu will be in Beta freeze very soon - Beta will be released at April 2nd. See https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/-/commits/master for more information. Also I'm attaching Lithuanian, French and Polish translations from GIT to this bugreport, please include :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1868216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868216] Re: Please include updated Lithuanian, French and Polish translations from upstream
** Attachment added: "Polish translation from gnome-getting-started-docs upstream" https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1868216/+attachment/5339237/+files/pl.po.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-getting-started-docs in Ubuntu. https://bugs.launchpad.net/bugs/1868216 Title: Please include updated Lithuanian, French and Polish translations from upstream Status in gnome-getting-started-docs package in Ubuntu: New Bug description: Please include updated Lithuanian, French and Polish translations from upstream: https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/ It is important to do ASAP because Ubuntu will be in Beta freeze very soon - Beta will be released at April 2nd. See https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/-/commits/master for more information. Also I'm attaching Lithuanian, French and Polish translations from GIT to this bugreport, please include :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1868216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868216] [NEW] Please include updated Lithuanian, French and Polish translations from upstream
Public bug reported: Please include updated Lithuanian, French and Polish translations from upstream: https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/ It is important to do ASAP because Ubuntu will be in Beta freeze very soon - Beta will be released at April 2nd. See https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/-/commits/master for more information. Also I'm attaching Lithuanian, French and Polish translations from GIT to this bugreport, please include :) ** Affects: gnome-getting-started-docs (Ubuntu) Importance: Undecided Status: New ** Tags: patch-accepted-upstream ** Attachment added: "Lithuanian translation from gnome-getting-started-docs upstream" https://bugs.launchpad.net/bugs/1868216/+attachment/5339236/+files/lt.po.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-getting-started-docs in Ubuntu. https://bugs.launchpad.net/bugs/1868216 Title: Please include updated Lithuanian, French and Polish translations from upstream Status in gnome-getting-started-docs package in Ubuntu: New Bug description: Please include updated Lithuanian, French and Polish translations from upstream: https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/ It is important to do ASAP because Ubuntu will be in Beta freeze very soon - Beta will be released at April 2nd. See https://gitlab.gnome.org/GNOME/gnome-getting-started-docs/-/commits/master for more information. Also I'm attaching Lithuanian, French and Polish translations from GIT to this bugreport, please include :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-getting-started-docs/+bug/1868216/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868207] Re: Fractional scaling window sizes incorrect after resume from suspend
** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1868207 Title: Fractional scaling window sizes incorrect after resume from suspend Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: LP bug as requested at https://gitlab.gnome.org/GNOME/mutter/issues/1122 From the summary there: With fractional scaling enabled, after resume from suspend, maximised & half tiled windows have been resized/scaled so they are too large for the screen, and as a result no longer fit on the screen. Not sure if it also happens to windows that aren't in either of these states, I rarely have any. Further, most but not all windows are scaled like this. Epiphany and Terminal definitely are, maybe XWindows clients like Emacs aren't? Under 3.34, shell/mutter seemed to notice this and would visibly snap the window sizes back to what they should be. Under 3.36, that no longer seems to happen - the windows stay too big and I need to manually fix them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.35.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 20 16:54:48 2020 InstallationDate: Installed on 2018-08-13 (584 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-03-07 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1868207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868207] [NEW] Fractional scaling window sizes incorrect after resume from suspend
Public bug reported: LP bug as requested at https://gitlab.gnome.org/GNOME/mutter/issues/1122 >From the summary there: With fractional scaling enabled, after resume from suspend, maximised & half tiled windows have been resized/scaled so they are too large for the screen, and as a result no longer fit on the screen. Not sure if it also happens to windows that aren't in either of these states, I rarely have any. Further, most but not all windows are scaled like this. Epiphany and Terminal definitely are, maybe XWindows clients like Emacs aren't? Under 3.34, shell/mutter seemed to notice this and would visibly snap the window sizes back to what they should be. Under 3.36, that no longer seems to happen - the windows stay too big and I need to manually fix them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.35.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 20 16:54:48 2020 InstallationDate: Installed on 2018-08-13 (584 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-03-07 (12 days ago) ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #1122 https://gitlab.gnome.org/GNOME/mutter/issues/1122 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/1122 Importance: Unknown Status: Unknown -- 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/1868207 Title: Fractional scaling window sizes incorrect after resume from suspend Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: LP bug as requested at https://gitlab.gnome.org/GNOME/mutter/issues/1122 From the summary there: With fractional scaling enabled, after resume from suspend, maximised & half tiled windows have been resized/scaled so they are too large for the screen, and as a result no longer fit on the screen. Not sure if it also happens to windows that aren't in either of these states, I rarely have any. Further, most but not all windows are scaled like this. Epiphany and Terminal definitely are, maybe XWindows clients like Emacs aren't? Under 3.34, shell/mutter seemed to notice this and would visibly snap the window sizes back to what they should be. Under 3.36, that no longer seems to happen - the windows stay too big and I need to manually fix them. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.35.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 20 16:54:48 2020 InstallationDate: Installed on 2018-08-13 (584 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-03-07 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1868207/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
