[Desktop-packages] [Bug 1901694] Re: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series]
[39.611] (II) AIGLX: Screen 0 is not DRI2 capable [39.611] (EE) AIGLX: reverting to software rendering 16.04 is just old and you're not getting any (gfx) updates there anymore at this point -- 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/1901694 Title: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series] Status in mesa package in Ubuntu: New Bug description: Computer HP EliteBook 8460p. It uses hybrid graphics card. Processor Intel Core i5-2520M CPU @ 2.50GHz × 4; 2nd generation. The system only runs well with llvmpipe (LLVM 6.0, 256 bits) graphic software, AMD Caicos sometimes it's charged too, but the graphic display have problems and don't goes fine or fluid. Maybe there is no support for the processor graphics because It's a little bit old. I don't know how to install AMD proprietary drivers, It maybe solve the problem. I installed Ubuntu 20.04 LTS but don't works, It don't charge any graphic interface, only a black screen. I only uses the system in recovery mode. For that reason I returned to Ubuntu 16.04 LTS but my graphics don't have hardware acceleration, only software acceleration. When I tried to play (Super Tux Kart for example) I expected a berry poor graphic improvement, so I can't play It. Thanks for your time and attention! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 27 05:47:39 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2020-10-25 (1 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=es_CR:es PATH=(custom, no user) LANG=es_CR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-122-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.60 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.asset.tag: IS09189 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.60:bd03/12/2015:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 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 xserver.bootTime: Tue Oct 27 05:43:49 2020 xserver.configfile: default xserver.errors: AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1901694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
No they're not really. That's just recovery mode, required to log this bug. -- 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/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Description: Ubuntu 20.10 Release: 20.10 5.8.0-25-generic #26-Ubuntu SMP Thu Oct 15 10:30:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux After upgrading to Groovy Gorilla, my laptop hangs on the Ubuntu splash screen after login. Workaround: Press CTRL+ALT+DEL then select recovery mode for the 5.8 kernel, then select 'Resume'. Also, the screen resolution seems to be lower than normal. xorg: Installed: 1:7.7+19ubuntu15 Candidate: 1:7.7+19ubuntu15 Version table: *** 1:7.7+19ubuntu15 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 14:47:47 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:015e] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:015e] InstallationDate: Installed on 2019-01-01 (662 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Aspire 6930 ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=1fca13f7-f9c9-45fe-8e1c-3c88c19237d4 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2009 dmi.bios.vendor: Acer dmi.bios.version: v0.3238 dmi.board.name: Makalu dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv0.3238:bd07/28/2009:svnAcer:pnAspire6930:pvrNotApplicable:rvnAcer:rnMakalu:rvrNotApplicable:cvnAcer:ct1:cvrN/A: dmi.product.name: Aspire 6930 dmi.product.version: Not Applicable dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/gdm3/+bug/1901342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
** Tags added: xrandr-scaling -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1868207 Title: Fractional scaling window sizes incorrect after resume from suspend Status in Mutter: New 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 1870886] Re: Window scales to 200% after screen unlocked
Still reproducible on Groovy. It's not a laptop, it's a desktop with single monitor. Both AMD and Intel GFX have this issue. ** This bug is no longer a duplicate of bug 1868207 Fractional scaling window sizes incorrect after resume from suspend ** Summary changed: - Window scales to 200% after screen unlocked + Window scales to 200% after screen unlocked, on desktop with external monitor -- 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/1870886 Title: Window scales to 200% after screen unlocked, on desktop with external monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: System setup: - 4K screen with 200% scale factor. - System up to date with focal-proposed. Reproduce steps: 1. Idle or suspend the system. 2. Wake up the system and unlock the screen. 3. Window 200% sized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
you're using 'nomodeset' boot option which disables things, don't do that -- 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/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Description: Ubuntu 20.10 Release: 20.10 5.8.0-25-generic #26-Ubuntu SMP Thu Oct 15 10:30:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux After upgrading to Groovy Gorilla, my laptop hangs on the Ubuntu splash screen after login. Workaround: Press CTRL+ALT+DEL then select recovery mode for the 5.8 kernel, then select 'Resume'. Also, the screen resolution seems to be lower than normal. xorg: Installed: 1:7.7+19ubuntu15 Candidate: 1:7.7+19ubuntu15 Version table: *** 1:7.7+19ubuntu15 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 14:47:47 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:015e] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:015e] InstallationDate: Installed on 2019-01-01 (662 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Aspire 6930 ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=1fca13f7-f9c9-45fe-8e1c-3c88c19237d4 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2009 dmi.bios.vendor: Acer dmi.bios.version: v0.3238 dmi.board.name: Makalu dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv0.3238:bd07/28/2009:svnAcer:pnAspire6930:pvrNotApplicable:rvnAcer:rnMakalu:rvrNotApplicable:cvnAcer:ct1:cvrN/A: dmi.product.name: Aspire 6930 dmi.product.version: Not Applicable dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/gdm3/+bug/1901342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870886] Re: Window scales to 200% after screen unlocked, on desktop with external monitor
Please run this command to send us more information about the machine: apport-collect 1870886 ** Tags added: groovy -- 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/1870886 Title: Window scales to 200% after screen unlocked, on desktop with external monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: System setup: - 4K screen with 200% scale factor. - System up to date with focal-proposed. Reproduce steps: 1. Idle or suspend the system. 2. Wake up the system and unlock the screen. 3. Window 200% sized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1870886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
** Changed in: gnome-shell (Ubuntu) Status: Expired => Incomplete ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Similar error: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1886059] Re: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260]
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1886059 Title: gnome-shell crashed with assertion failure "!xcb_xlib_threads_sequence_lost" [xcb_io.c:260] Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.36.3-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/5d9a112e0c6aeddb3cf972203bede962f60d767d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Similar error: https://errors.ubuntu.com/problem/14911e4a22eec995bc364278c0490d8bfea557dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1886059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896091] Re: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions
Still broken in 5.8.0-26-generic -- 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/1896091 Title: [i915] Noise-like lines of graphics corruption when moving windows in Xorg sessions Status in Mutter: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Bug description: I left my desktop (T480s thinkpad docked to ThinkVision P24h-10) unattended for a while, and then got the error message and now have funny lines on activity, e.g. red lines flashing on top of gnome-shell bar when switching windows, or white blocks/lines around typing text. This is the second or third time it happened, reboot fixes it until the error pops up again. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-19-generic 5.8.0-19.20 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Thu Sep 17 19:14:11 2020 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN22ET65W(1.42):bd06/04/2020:br1.42:efr1.20:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L8S02D00 dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jak5052 F pulseaudio /dev/snd/controlC1: jak5052 F pulseaudio /dev/snd/pcmC1D0p: jak5052 F...m pulseaudio /dev/snd/controlC0: jak5052 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted DistroRelease: Ubuntu 20.10 HibernationDevice: RESUME=none InstallationDate: Installed on 2018-03-14 (917 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) MachineType: LENOVO 20L8S02D00 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 RelatedPackageVersions: linux-restricted-modules-5.8.0-19-generic N/A linux-backports-modules-5.8.0-19-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 06/04/2020 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET65W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L8S02D00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias:
[Desktop-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit
It exists in queue https://launchpad.net/ubuntu/focal/+queue?queue_state=1_text=network, which is network manager 1.22.10-1ubuntu2.2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1891632 Title: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit Status in OEM Priority Project: New Status in OEM Priority Project focal series: Invalid Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Focal: In Progress Bug description: [Impact] In some cases, the wow is not configured and the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable management of wake-on-LAN in NetworkManager). The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE bit. But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check. So, the management of wake-on-LAN still is done by NetworkManager. The killer 500s Wi-Fi does not want the network-manger to manager the wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The driver will manager itself.) When the network-manager managers the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS resumed from suspend. [Test Case] On a machine with killer 500s Wi-Fi and install the Qualcomm's driver. Step 1. Enter suspend (s2idle) Setp 2. Resume from suspend After resume from suspend, the Wi-Fi function still is normal. You can download the kernel and linux-firmware that backport the Qucalcomm's dirver fro focal from below link: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633 [Regression Potential] * This patch modifies the wake on lan parameters, please test that the corresponding feature still works fine with the different configuration values. 1. Magic packet test: Set Wake on Wireless to off Send magic packet to the system Ensure it does not wake up Set Wake on Wirless to on Send magic packet to the system Ensure it does wake up 2. Wi-Fi function test after resumed from suspend: After resume from suspend, the Wi-Fi should work normally. Scan APs. Connect to an AP. [Other Info] * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status check (!597) · Merge Requests · NetworkManager / NetworkManager · GitLab - https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1891632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
@Marco, What the bluetooth module on your machine? Could you please upload the vendor ID:device ID like #49? thx. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901778] Re: Thunderbird crashes on start up
thunderbird running fine on my ubuntu 20.10! someone else said not running fine on 20.10 ubuntu mate ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1901778 Title: Thunderbird crashes on start up Status in thunderbird package in Ubuntu: New Bug description: When I try to start up Thunderbird (v 1:78.3.2), a information box appears with this message : "key id="openLightningKey"" This bug happened since yesterday, with Ubuntu 20.10. It didn't happen at the beginning when I have updated to 20.10 If I start Thunderbird by a command in the Terminal, I get these messages : [calBackendLoader] Using Thunderbird's libical backend Extension error: Error while loading 'jar:file:///usr/lib/thunderbird/omni.ja!/chrome/messenger/search-extensions/twitter/manifest.json' (NS_ERROR_FILE_NOT_FOUND) resource://gre/modules/Extension.jsm:570 :: readJSON/https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901736] Re: Freeze
This sounds like either bug 1896110 or bug 1874578. Do you think? ** Summary changed: - Xorg freeze + Freeze ** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1901736 Title: Freeze Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Most of the time Ubuntu boots the dock seems to freeze and not load any icons, sometimes for up to a minute. When this happens the dock will not appear when any window is maximized. Once in a while Ubuntu loads without a problem. The dock loads instantly and has no problem behind a maximized window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 12:35:14 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 640 [8086:5926] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 640 [8086:2068] InstallationDate: Installed on 2020-09-16 (41 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC7i5BNK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=50f7562f-c44b-4a47-b1b4-02bdd6281c08 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139 dmi.board.name: NUC7i5BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31144-314 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i5BNK:pvrJ31159-315:rvnIntelCorporation:rnNUC7i5BNB:rvrJ31144-314:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BN dmi.product.name: NUC7i5BNK dmi.product.version: J31159-315 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1901736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no screens found") from dix_main()
OK, clarified somewhat now. This bug is back to being about just "no
screens found".
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("no
screens found") from dix_main()
--
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/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Feb 8 17:07:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics
Controller [17aa:21da]
InstallationDate: Installed on 2015-04-30 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 429149G
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0
panic=-1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
__libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8,
init=, fini=, rtld_fini=,
stack_end=0x7fffc9e34fc8) at libc-start.c:289
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit
code 2:
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 429149G
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Mon Feb 8 17:08:14 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 9847 does not
belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 728
vendor LGD
xserver.version: 2:1.17.3-2ubuntu2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787332] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from systemd_logind_vtenter()
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen ...") from xf86VTEnter() from
systemd_logind_vtenter()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
systemd_logind_vtenter()
--
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/1787332
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen %d\n") from xf86VTEnter() from
systemd_logind_vtenter()
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
.
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: xserver-xorg-core 2:1.19.6-1ubuntu4
ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
Uname: Linux 4.17.0-6-generic x86_64
ApportVersion: 2.20.10-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 16 14:15:46 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA
controller])
Subsystem: Lenovo HD Graphics 630 [17aa:3102]
InstallationDate: Installed on 2018-05-26 (81 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
Bus 001 Device 003: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 10M7CTO1WW
ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 7
-core
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-6-generic
root=UUID=d7ecc709-02c2-4413-b7e7-dfce1d2b3703 ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
()
()
()
xf86VTEnter ()
()
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/06/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: M16KT47A
dmi.board.name: 3102
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN 3259627060530
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
dmi.product.family: ThinkCentre M710s
dmi.product.name: 10M7CTO1WW
dmi.product.version: ThinkCentre M710s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.93-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1787332/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791981] Re: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
It looks like bug 1897530 might cover this but it's unclear. The fix for that is only in Ubuntu 20.10 so far. -- 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/1791981 Title: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in Nvidia: New Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu Release: Ubuntu 18.04.1 LTS Package version: xserver-xorg: 1:7.7+19ubuntu7.1 When my laptop resumes after suspend, the desktop session crashes and a new one is started. So each time I lose all open applications and unsaved data! The expected behavior would be obviously to restore the suspended session. I had a look through log files and found that Xorg.0.log ends with the following error lines: [ 6004.019] (II) NVIDIA(0): Setting mode "NULL" [ 6004.026] (EE) modeset(G0): failed to set mode: No space left on device [ 6004.026] (EE) Fatal server error: [ 6004.026] (EE) EnterVT failed for gpu screen 0 [ 6004.027] (EE) [ 6004.027] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 6004.027] (EE) [ 6004.065] (EE) Server terminated with error (1). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1791981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1545103] Re: Xorg crashed with SIGABRT in raise()
There's not enough information here to tell which FatalError this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1545103 Title: Xorg crashed with SIGABRT in raise() Status in xorg-server package in Ubuntu: Incomplete Bug description: Fresh install of Ubuntu MATE 16.04 daily ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.17.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Fri Feb 12 19:03:47 2016 ExecutablePath: /usr/lib/xorg/Xorg InstallationDate: Installed on 2016-02-12 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160212) ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 OsAbort () ?? () FatalError () Title: Xorg crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1545103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1545158] Re: Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no screens found")
*** This bug is a duplicate of bug 1543192 ***
https://bugs.launchpad.net/bugs/1543192
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort()
+ Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no screens
found")
--
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/1545158
Title:
Xorg crashed with SIGABRT in OsAbort() from ?? from FatalError("no
screens found")
Status in xorg-server package in Ubuntu:
New
Bug description:
I don't know what im doing how does this bug reporting work?
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
Uname: Linux 4.4.0-4-generic x86_64
.tmp.unity.support.test.1:
ApportVersion: 2.19.4-0ubuntu2
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
CrashCounter: 1
Date: Fri Feb 12 16:01:02 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: No
GraphicsCard:
Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if
00 [VGA controller])
Subsystem: Dell Sky Lake Integrated Graphics [1028:0704]
InstallationDate: Installed on 2016-02-12 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205)
MachineType: Dell Inc. XPS 13 9350
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-4-generic.efi.signed
root=UUID=81f4bcb0-5c47-4d3d-8294-1c2bff262d72 ro recovery nomodeset
Renderer: Software
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
__libc_start_main (main=0x56246d9bbf00, argc=11, argv=0x7ffe2767bf18,
init=, fini=, rtld_fini=,
stack_end=0x7ffe2767bf08) at libc-start.c:289
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 01/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 0PWNCR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.2.3:bd01/08/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0PWNCR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Fri Feb 12 16:02:41 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
xserver.version: 2:1.17.3-2ubuntu2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1545158/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543141] Re: Xorg crashed with SIGABRT in OsAbort()
There's not enough information here to tell which FatalError this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1543141 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: Incomplete Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.17.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 8 15:13:42 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2015-04-30 (283 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 429149G ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 panic=-1 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () __libc_start_main (main=0x55d6b3954f00, argc=11, argv=0x7fffef9c7a88, init=, fini=, rtld_fini=, stack_end=0x7fffef9c7a78) at libc-start.c:289 SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.66-2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160127-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Mon Feb 8 15:15:16 2016 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 970 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.17.3-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544252] Re: Xorg crashed with SIGABRT in OsAbort()
I can't see any evidence of which Xorg crash this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1544252 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: Incomplete Bug description: upgraded from chromeos to a galliumos kernel, then dist-upgrade to stock ubuntu kernel ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.17.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Wed Feb 10 14:31:34 2016 ExecutablePath: /usr/lib/xorg/Xorg InstallationDate: Installed on 2016-02-09 (1 days ago) InstallationMedia: GalliumOS 1.0beta1 "Vivid Vervet" - Release amd64 (20151109.1) ProcCmdline: /usr/lib/xorg/Xorg -nolisten tcp -core -auth /var/run/slim.auth Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () __libc_start_main (main=0x55f7df0d4f00, argc=6, argv=0x7ffdc6e3d9a8, init=, fini=, rtld_fini=, stack_end=0x7ffdc6e3d998) at libc-start.c:289 Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to xenial on 2016-02-10 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1544252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543706] Re: Xorg crashed with SIGABRT in OsAbort()
I can't tell *which* FatalError this is. ** This bug is no longer a duplicate of bug 1543192 Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from dix_main() ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1543706 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: Incomplete Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.17.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Tue Feb 9 18:52:43 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2015-04-30 (284 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 429149G ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 panic=-1 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () __libc_start_main (main=0x561b1e194f00, argc=11, argv=0x7ffe3ea4ad98, init=, fini=, rtld_fini=, stack_end=0x7ffe3ea4ad88) at libc-start.c:289 SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.66-2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160127-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Tue Feb 9 18:53:14 2016 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 4380 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.17.3-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from WakeupHandler()
I think this is the wrong bug for all of those duplicates. There's no
evidence of either of those messages here. I'll see if I can split this
into other bugs...
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from
WakeupHandler()
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError
** Summary changed:
- Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError
+ Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Description changed:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
- https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
Date: Mon Feb 8 17:07:23 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics
Controller [17aa:21da]
InstallationDate: Installed on 2015-04-30 (283 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 429149G
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic
root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0
panic=-1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
__libc_start_main (main=0x557f8180ff00, argc=11, argv=0x7fffc9e34fd8,
init=, fini=, rtld_fini=,
stack_end=0x7fffc9e34fc8) at libc-start.c:289
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit
code 2:
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/18/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET46WW (1.16 )
dmi.board.asset.tag: Not Available
dmi.board.name: 429149G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 429149G
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.66-2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20160127-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
xserver.bootTime: Mon Feb 8 17:08:14 2016
xserver.configfile: default
xserver.errors: systemd-logind: failed to get session: PID 9847 does not
belong to any known session
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 728
vendor LGD
xserver.version: 2:1.17.3-2ubuntu2
--
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/1543192
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("no screens found") from dix_main()
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
https://errors.ubuntu.com/problem/4de849dfec89af168af9cda3318221a2a654e530
---
No idea what happened.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: xserver-xorg-core 2:1.17.3-2ubuntu2
ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1858351] Re: Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from AbortServer() from FatalError("no screens found")
*** This bug is a duplicate of bug 1813897 ***
https://bugs.launchpad.net/bugs/1813897
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError()
from dix_main()
** Summary changed:
- Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("no screens found")
+ Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError() from InitOutput()
** Summary changed:
- Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError() from InitOutput()
+ Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("AddScreen/ScreenInit failed for driver %d\n")
from InitOutput()
** This bug has been marked a duplicate of bug 1813897
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("AddScreen/ScreenInit failed for driver %d\n")
--
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/1858351
Title:
Xorg crashed with SIGABRT in raise() from abort() from OsAbort() from
AbortServer() from FatalError("AddScreen/ScreenInit failed for driver
%d\n") from InitOutput()
Status in xorg-server package in Ubuntu:
New
Bug description:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
xorg-server. This problem was most recently seen with package version
2:1.20.5+git20191008-0ubuntu1, the problem page at
https://errors.ubuntu.com/problem/4c203db78dea0a68c29cbd981d4abbd4aef31851
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1858351/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276804] Re: Xorg crashed with SIGABRT in OsAbort(no screens found?)
Ubuntu 14.04 reached end of standard support in April 2019: https://wiki.ubuntu.com/Releases If you would like to continue with free support then please update to a newer Ubuntu version and tell us if the problem still occurs. If you would like to continue with Ubuntu 14.04 then there is a paid support option detailed at https://www.ubuntu.com/esm ** Changed in: xorg-server (Ubuntu) Status: New => Won't Fix -- 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/1276804 Title: Xorg crashed with SIGABRT in OsAbort(no screens found?) Status in xorg-server package in Ubuntu: Won't Fix Bug description: os started up, display immediately showed error dialog. then display flashed and title bar appeared. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Wed Feb 5 15:15:46 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:835d] InstallationDate: Installed on 2014-01-17 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131231) MachineType: Hewlett-Packard p7-1154 ProcCmdline: /usr/bin/X -hostname :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic root=UUID=324d18bb-aec8-4a28-b39c-023102955f99 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: audio pulse pulse-access video dmi.bios.date: 08/16/2011 dmi.bios.vendor: AMI dmi.bios.version: 7.07 dmi.board.name: 2ACD dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: 4CE135014F dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr7.07:bd08/16/2011:svnHewlett-Packard:pnp7-1154:pvr:rvnPEGATRONCORPORATION:rn2ACD:rvr1.01:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p7-1154 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Feb 5 15:31:58 2014 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) open /dev/fb0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1276804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276804] Re: Xorg crashed with SIGABRT in OsAbort(no screens found?)
Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 14.04 (trusty) reached end-of-life on April 28, 2017
https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/UbuntuGNOME#Support
https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004211.html
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.
** This bug is no longer a duplicate of bug 1543192
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for gpu screen %d\n") from xf86VTEnter() from
WakeupHandler()
--
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/1276804
Title:
Xorg crashed with SIGABRT in OsAbort(no screens found?)
Status in xorg-server package in Ubuntu:
Won't Fix
Bug description:
os started up, display immediately showed error dialog. then display
flashed and title bar appeared.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-core 2:1.15.0-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1
Uname: Linux 3.13.0-7-generic i686
.tmp.unity.support.test.0:
ApportVersion: 2.13.2-0ubuntu2
Architecture: i386
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CrashCounter: 1
Date: Wed Feb 5 15:15:46 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00
[VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:835d]
InstallationDate: Installed on 2014-01-17 (18 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131231)
MachineType: Hewlett-Packard p7-1154
ProcCmdline: /usr/bin/X -hostname :0 -auth /var/run/lightdm/root/:0 -nolisten
tcp vt7 -novtswitch
ProcEnviron:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic
root=UUID=324d18bb-aec8-4a28-b39c-023102955f99 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
?? ()
?? ()
SystemImageInfo: Error: [Errno 2] No such file or directory:
'system-image-cli'
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: audio pulse pulse-access video
dmi.bios.date: 08/16/2011
dmi.bios.vendor: AMI
dmi.bios.version: 7.07
dmi.board.name: 2ACD
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.01
dmi.chassis.asset.tag: 4CE135014F
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnAMI:bvr7.07:bd08/16/2011:svnHewlett-Packard:pnp7-1154:pvr:rvnPEGATRONCORPORATION:rn2ACD:rvr1.01:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: p7-1154
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.10-1ubuntu2
xserver.bootTime: Wed Feb 5 15:31:58 2014
xserver.configfile: default
xserver.errors:
Failed to load module "nvidia" (module does not exist, 0)
Failed to load module "nvidia" (module does not exist, 0)
open /dev/fb0: No such file or directory
open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.0-1ubuntu1
xserver.video_driver: nouveau
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1276804/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901695] Re: Ubuntu 20.04 Suspend resume fails if laptop lid is closed [modeset(G0): failed to set mode: No space left on device] (Razer Blade 15 laptop with nvidia proprietary
*** This bug is a duplicate of bug 1791981 ***
https://bugs.launchpad.net/bugs/1791981
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1791981, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** Tags added: focal
** This bug has been marked a duplicate of bug 1791981
X Server session crash with "No space left on device" and then "EnterVT
failed for gpu screen 0"
--
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/1901695
Title:
Ubuntu 20.04 Suspend resume fails if laptop lid is closed
[modeset(G0): failed to set mode: No space left on device] (Razer
Blade 15 laptop with nvidia proprietary driver)
Status in xorg-server package in Ubuntu:
New
Bug description:
Steps to reproduce:
- Boot docked laptop (i.e. lid closed, external monitors connected, USB
keyboard plugged in)
- Log in, click desktop menu item "Power off / logout -> suspend"
- Laptop will suspend
- Press key on USB keyboard to resume
- Resume fails - external monitor shows black screen with cursor
- (this used to work ok in Ubuntu 18.04)
Journal shows that Xorg failed:
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-0): connected
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-0): Internal TMDS
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-0): 165.0 MHz maximum pixel clock
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DFP-1: disconnected
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DFP-1: Internal DisplayPort
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DFP-1: 1440.0 MHz maximum pixel clock
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-2): connected
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-2): Internal TMDS
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
DELL 2209WA (DFP-2): 165.0 MHz maximum pixel clock
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (--) NVIDIA(GPU-0):
Oct 27 12:06:37 blade /usr/lib/gdm3/gdm-x-session[2125]: (II) NVIDIA(0):
Setting mode "HDMI-0: nvidia-auto-select @1050x1680 +2102+0
{ViewPortIn=1050x1680, ViewPortOut=1680x1050+0+0, Rotation=90}, DP-1:
nvidia-auto-select @1050x1680 +1050+0 {ViewPortIn=1050x1680,
ViewPortOut=1680x1050+0+0, Rotation=90}"
...
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) modeset(G0):
failed to set mode: No space left on device
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE)
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Fatal server error:
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) EnterVT failed
for gpu screen 0
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE)
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE)
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: Please consult the
The X.Org Foundation support
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: at
http://wiki.x.org
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: for help.
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Please also
check the log file at "/var/log/Xorg.0.log" for additional information.
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE)
Oct 27 12:06:41 blade /usr/lib/gdm3/gdm-x-session[1595]: (EE) Server
terminated with error (1). Closing log file.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1901695/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791981] Re: X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"
** Summary changed: - X Server session crash for "No space left on device" + X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" ** Summary changed: - X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" + [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" -- 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/1791981 Title: [nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0" Status in Nvidia: New Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu Release: Ubuntu 18.04.1 LTS Package version: xserver-xorg: 1:7.7+19ubuntu7.1 When my laptop resumes after suspend, the desktop session crashes and a new one is started. So each time I lose all open applications and unsaved data! The expected behavior would be obviously to restore the suspended session. I had a look through log files and found that Xorg.0.log ends with the following error lines: [ 6004.019] (II) NVIDIA(0): Setting mode "NULL" [ 6004.026] (EE) modeset(G0): failed to set mode: No space left on device [ 6004.026] (EE) Fatal server error: [ 6004.026] (EE) EnterVT failed for gpu screen 0 [ 6004.027] (EE) [ 6004.027] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 6004.027] (EE) [ 6004.065] (EE) Server terminated with error (1). Closing log file. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1791981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901694] Re: [radeon] No hardware aceleration
It appears the Xorg radeon driver is working. It's only 3D that's not working so that's Mesa. ** Summary changed: - No hardware aceleration + [radeon] No hardware aceleration ** Summary changed: - [radeon] No hardware aceleration + [radeon] No hardware acceleration ** Tags added: radeon ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) ** Summary changed: - [radeon] No hardware acceleration + [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series] -- 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/1901694 Title: [radeon] No hardware acceleration on AMD Seymour [Radeon HD 6400M/7400M Series] Status in mesa package in Ubuntu: New Bug description: Computer HP EliteBook 8460p. It uses hybrid graphics card. Processor Intel Core i5-2520M CPU @ 2.50GHz × 4; 2nd generation. The system only runs well with llvmpipe (LLVM 6.0, 256 bits) graphic software, AMD Caicos sometimes it's charged too, but the graphic display have problems and don't goes fine or fluid. Maybe there is no support for the processor graphics because It's a little bit old. I don't know how to install AMD proprietary drivers, It maybe solve the problem. I installed Ubuntu 20.04 LTS but don't works, It don't charge any graphic interface, only a black screen. I only uses the system in recovery mode. For that reason I returned to Ubuntu 16.04 LTS but my graphics don't have hardware acceleration, only software acceleration. When I tried to play (Super Tux Kart for example) I expected a berry poor graphic improvement, so I can't play It. Thanks for your time and attention! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 27 05:47:39 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2020-10-25 (1 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=es_CR:es PATH=(custom, no user) LANG=es_CR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-122-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.60 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.asset.tag: IS09189 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.60:bd03/12/2015:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 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 xserver.bootTime: Tue Oct 27 05:43:49 2020 xserver.configfile: default xserver.errors: AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1901694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901538] Re: Output Device selection messed (Line Out <-> HDMI)
No problem. If there are no more comments after 60 days then the bug will close automatically. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1901538 Title: Output Device selection messed (Line Out <-> HDMI) Status in gnome-control-center package in Ubuntu: Incomplete Bug description: [System] - Freshly installed Ubuntu 20.04.1 LTS with 3rd party software/drivers enabled - pulseaudio 1:13.99.1-1ubuntu3.7 - NVIDIA graphics card (GeForce GTX 650 Ti Boost) using nvidia-driver-450 - Monitor with build-in (stereo) speakers connected via HDMI to graphics card - External (stereo) speakers connected via audio jack to mainboard [Expected Behavior] 1. Go to "Settings" -> "Sound" -> "Output" -> "Output Device" 2. Switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" 3. The switching should enable the chosen output device. [Bug Description and Behavior] If I switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" and test the output, sound comes still from monitor speakers and not from my external speakers. [Workaround] While "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" selected, go to "Configuration" and switch from "Digital Stereo (HDMI 2) Output" to "Digital Surround 5.1 (HDMI 2) Output". Instantly "Configuration" row disappears, in Output Device "Line Out - Built-in Audio" is selected and external speakers are active. [Further comments] I'm affected by this bug and the "wrong audio output on every reboot/wake up/login" since upgrade to 20.04 but the latter may be worth another bug report or maybe you could guide me to an active bug report that isn't linked to a previous Ubuntu version and already marked as fixed. At first I thought it may be caused by failed upgrade or my system configurations, but now I tested with a freshly installed Ubuntu on a spare SSD and the problem still exists, so here I am. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 13:15:41 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-10-26 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1901538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
I would like to check to see if the problem is occurring in the kernel and not just in Xorg. Please run: grep . /sys/class/drm/*/modes > modes.txt and then attach the resulting text file here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI Status in xorg-server package in Ubuntu: Incomplete Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline
[Desktop-packages] [Bug 1901413] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901470] Re: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI
Yep, the detailed mode 2560x1440 is in the EDID returned by the monitor: Standard Timings: none Detailed mode: Clock 241.500 MHz, 598 mm x 336 mm 2560 2608 2640 2720 ( 48 32 80) 1440 1443 1448 1481 ( 3 5 33) +hsync -vsync VertFreq: 59.951 Hz, HorFreq: 88.787 kHz Display Product Serial Number: GBLMQS047683 Display Range Limits Monitor ranges (Bare Limits): 24-60 Hz V, 30-140 kHz H, max dotclock 300 MHz Display Product Name: ROG PG278QR -- 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/1901470 Title: resolution not listed in xrandr from ASUS ROG PG278QR via HDMI Status in xorg-server package in Ubuntu: Incomplete Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing...
[Desktop-packages] [Bug 1872950] Re: Nvidia 340.108 fails to install with kernels 5.5 onward
** Summary changed: - Nvidia 340.108 fails to install with kernels 5.5 and 5.6 + Nvidia 340.108 fails to install with kernels 5.5 onward ** Changed in: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided => High ** Tags added: focal groovy ** Tags removed: focal ** Tags added: rls-gg-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1872950 Title: Nvidia 340.108 fails to install with kernels 5.5 onward Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: Hi developers, thanks for your great work on porting legacy drivers to Ubuntu. Anyway I have to complain in not seeing Nvidia 340.108 driver for kernels 5.5 and 5.6 yet, leaving users stuck on kernel 5.4, because Nvidia 340.108 fails to install with kernels 5.5 and 5.6. Archlinux already has a driver for Kernel 5.6 via AUR (https://aur.archlinux.org/packages/nvidia-340xx/) and Debian SID has one for kernel 5.5. So, the question is: when will we see a new version in repositories? Bye and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1872950/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
** Changed in: gdm3 (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied Status in gdm3 package in Ubuntu: New Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Description: Ubuntu 20.10 Release: 20.10 5.8.0-25-generic #26-Ubuntu SMP Thu Oct 15 10:30:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux After upgrading to Groovy Gorilla, my laptop hangs on the Ubuntu splash screen after login. Workaround: Press CTRL+ALT+DEL then select recovery mode for the 5.8 kernel, then select 'Resume'. Also, the screen resolution seems to be lower than normal. xorg: Installed: 1:7.7+19ubuntu15 Candidate: 1:7.7+19ubuntu15 Version table: *** 1:7.7+19ubuntu15 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 14:47:47 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:015e] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:015e] InstallationDate: Installed on 2019-01-01 (662 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Aspire 6930 ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=1fca13f7-f9c9-45fe-8e1c-3c88c19237d4 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2009 dmi.bios.vendor: Acer dmi.bios.version: v0.3238 dmi.board.name: Makalu dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv0.3238:bd07/28/2009:svnAcer:pnAspire6930:pvrNotApplicable:rvnAcer:rnMakalu:rvrNotApplicable:cvnAcer:ct1:cvrN/A: dmi.product.name: Aspire 6930 dmi.product.version: Not Applicable dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/gdm3/+bug/1901342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892358] Autopkgtest regression report (systemd/245.4-4ubuntu3.3)
All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.3) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.8/5.8.0-25.26~20.04.1 (armhf) python-dbusmock/0.19-1 (armhf) lxc/1:4.0.2-0ubuntu1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#systemd [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in util-linux source package in Focal: Confirmed Bug description: [impact] autopkgtests are failing/flaky and prevent other packages from migrating to -updates [test case] check autopkgtest history [regression potential] in regard to the changed test cases, any regression would likely result in either an incorrectly passed test, or an incorrectly failed test. [scope] for systemd, this is needed for x, b, and f. tests in g appear to be mostly stable, but I've opened MR (linked from this bug) to update the tests there as well. i don't plan to update x, as it's reaching ESM in ~6 months, and backporting the test fixes is more work than just a simple code copy, since there are additional differences/changes needed in the older version of systemd (and python3). the failing/flaky tests in x have been like that forever, and people have just retried them; we can keep retrying them until x moves into ESM next year. [original description] Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/) B...B...BB. systemd-fsckd (F 37% S 0% B 10% => P 50%/) BFFFB.FF...FB.F..B. root-unittests (F 0% S 0% B 10% => P 87%/) B...B...BB. ppc64el tests-in-lxd (F 25% S 0% B 0% => P 75%/) FFFFF.F. systemd-fsckd (F 35% S 0% B 0% => P 65%/) FFF...FFFFF.F..F root-unittests (F 2% S 0% B 0% => P 97%/) ..F. s390x tests-in-lxd (F 52% S 0% B 0% => P 47%/) FFF.FFF.FF....F. timedated (F 2% S 0% B 0% => P 97%/)
[Desktop-packages] [Bug 1901413] Re: Sound Blaster Audigy 5/Rx cannot be configured as input/output
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900009] Re: Window tiled to monitor where most of the window is in instead of where the mouse is.
The fix was written by upstream, and the downstream fix is being packaged by Marco. So I'm not involved in either of those. ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Changed in: mutter (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: mutter (Ubuntu Groovy) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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/199 Title: Window tiled to monitor where most of the window is in instead of where the mouse is. Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Status in gnome-shell source package in Groovy: Invalid Status in mutter source package in Groovy: Fix Committed Bug description: Release: Ubuntu Groovy Gorilla (development branch) 20.10 Package version: 3.38.1-1ubuntu1 [ Impact ] When I tile windows using edge tiling, I want the window to tile on the same edge that I brought it to, however, if the window is mostly in monitor 1 when I try to tile it to the left (or right) edge of monitor 2, the window will tile to the left (or right) edge of monitor 2. This happens on both my computer with an Nvidia GPU on x11 and my laptop using Intel integrated graphics on Wayland. [ Test case ] - In multi-monitor setup, grab a tile edge to the side where the other monitor is - The window should not be moved to the other monitor [ Regression potential ] Windows may be tiled to the wrong monitor once created To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1894627] Re: [nvidia] Web browser distorted after hibernation/power save when idle
Please don't discuss that here. You should open a new bug by running: ubuntu-bug linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1894627 Title: [nvidia] Web browser distorted after hibernation/power save when idle Status in chromium-browser package in Ubuntu: Triaged Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Bug description: https://bugs.chromium.org/p/chromium/issues/detail?id=791913 --- my laptop goes to hibernation/power saver mode when my computer is idle. every time I bring my computer back up, the screen distorted. I have to close all my browsers. Sometimes, shut down the computer. Description: Ubuntu 20.04.1 LTS Release: 20.04 N: Unable to locate package pkgname ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 7 03:33:23 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-42-generic, x86_64: installed nvidia, 440.100, 5.4.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) [103c:8466] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti Mobile] [103c:8466] InstallationDate: Installed on 2020-06-23 (75 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) HP Wide Vision HD Camera Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=98265a4d-5439-415e-b43c-904265a8559a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2019 dmi.bios.vendor: AMI dmi.bios.version: F.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8466 dmi.board.vendor: HP dmi.board.version: 68.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.09:bd04/24/2019:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn8466:rvr68.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop dmi.product.sku: 4CC49UA#ABA dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-06-26T00:47:21.524860 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1894627/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1550779] Re: Black screen flickering and [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
** No longer affects: xorg-server (Ubuntu) -- 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/1550779 Title: Black screen flickering and [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Confirmed Bug description: Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches, looks like the graphic buffer gets screwed up - funny repetition's patterns (back in time glitches) - black screen (<1sec) - graphic errors I can influence the severity of the issue with switching windows and using certain programs, e.g. Google Maps in chrome causes this issue reproducibly dmesg | grep i915 [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5 [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.471093] i915 :00:02.0: registered panic notifier [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun linux-image-extra-4.2.0-27-generic works find ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Feb 27 20:26:07 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2016-02-11 (15 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 42912XG ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt quiet SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET69WW (1.39 ) dmi.board.asset.tag: Not Available dmi.board.name: 42912XG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42912XG dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Feb 27 20:25:23 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12359 vendor SEC xserver.version: 2:1.17.2-1ubuntu9.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
I'm using Acer Swift SF514-52T (Intel 8th Gen Core i5) on Ubuntu 20.10 - Linux kernel 5.8. The default configuration has no sound working at all. I believe it uses the SOF driver (I could be wrong) which doesn't support the Kaby Lake platform, as the issues for supporting this platform have been closed ( https://github.com/thesofproject/sof/issues/1899 ). And the proposed workaround to support this platform have been discarded also ( https://github.com/thesofproject/sof/issues/2256 ). Therefore installing the latest version or any version of the SOF driver will not solve the issue. Force enable the HDA driver (snd_hda_intel) in /etc/modprobe.d/alsa- base.conf with options snd-intel-dspcfg dsp_driver=1, the sound output works fine but the internal mic (DMIC) doesn't work. And I believe we're moving to the SOF driver which doesn't support my device. Therefore I don't expect any fix will be done in HDA driver. I tried to use Intel's SST driver as it's the only solution left. I enabled it with options snd-intel-dspcfg dsp_driver=2 but both the sound output and the internal mic (DMIC) don't work. I also report this bug in https://bugzilla.kernel.org/show_bug.cgi?id=201251 Here is my alsa-info (with options snd-intel-dspcfg dsp_driver=2): http ://alsa-project.org/db/?f=db024ae3c924d318bda813f73c73e76df36bbca2 I attached my full dmesg also. ** Bug watch added: github.com/thesofproject/sof/issues #1899 https://github.com/thesofproject/sof/issues/1899 ** Bug watch added: github.com/thesofproject/sof/issues #2256 https://github.com/thesofproject/sof/issues/2256 ** Bug watch added: Linux Kernel Bug Tracker #201251 https://bugzilla.kernel.org/show_bug.cgi?id=201251 ** Attachment added: "dmesg on Acer Swift SF514-52T running Ubuntu 20.10" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+attachment/5428164/+files/dmesg_messages -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True
[Desktop-packages] [Bug 1901340] Re: Backup doesn't automatically start when drive is inserted
Ah, OK. Maybe the previous problem with the snap was because the old session monitor was still active? Odd. But glad it worked now! So yeah, looks like the fixes in 42.3 work for your case, and it's possible the patches around encrypted & removable drives from 42.3 and 42.4 should be backported to Ubuntu 20.04. I believe this series of patches are sufficient: https://gitlab.gnome.org/World/deja-dup/-/commit/14a65235dc2466c0927579a80d760aa03d89371d https://gitlab.gnome.org/World/deja-dup/-/commit/6c6fe2c406ef0bbc4e9b1c8e08fdfe15912aed80 https://gitlab.gnome.org/World/deja-dup/-/commit/2778fc86258f1c5a2b229b64f3a28548ab9a5b01 https://gitlab.gnome.org/World/deja-dup/-/commit/92f0640dd45c443720e6f5f16db916891ad64f1b -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1901340 Title: Backup doesn't automatically start when drive is inserted Status in deja-dup package in Ubuntu: Incomplete Bug description: I have Deja Dup set up to automatically backup onto a removable drive encrypted with LUKS every day. Each morning I would get a notification saying that the backup will automatically start when the drive is connected. When I insert the drive, it is automatically unlocked since I have the password saved on the computer. But after waiting for around half an hour the backup doesn't seem to have started. When I open Deja Dup it says that the last backup was yesterday and the next backup is today. Clicking the Back Up Now button starts the backup. The drive is GPT partitioned with a single partition containing ext4 inside LUKS. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: deja-dup 42.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 11:09:42 2020 ExecutablePath: /usr/bin/deja-dup InstallationDate: Installed on 2020-10-20 (4 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: deja-dup UpgradeStatus: Upgraded to groovy on 2020-10-23 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1901340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901342] Re: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied
Yes - "after login" means after I have successfully entered my password. Also, I have not been able to locate the 'Ubuntu on Wayland' selection. -- 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/1901342 Title: Xorg sessions fail to start on Intel Core 2 T5800: modeset(0): drmSetMaster failed: Permission denied Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.10 Release: 20.10 5.8.0-25-generic #26-Ubuntu SMP Thu Oct 15 10:30:38 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux After upgrading to Groovy Gorilla, my laptop hangs on the Ubuntu splash screen after login. Workaround: Press CTRL+ALT+DEL then select recovery mode for the 5.8 kernel, then select 'Resume'. Also, the screen resolution seems to be lower than normal. xorg: Installed: 1:7.7+19ubuntu15 Candidate: 1:7.7+19ubuntu15 Version table: *** 1:7.7+19ubuntu15 500 500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 14:47:47 2020 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:015e] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:015e] InstallationDate: Installed on 2019-01-01 (662 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Aspire 6930 ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=1fca13f7-f9c9-45fe-8e1c-3c88c19237d4 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/28/2009 dmi.bios.vendor: Acer dmi.bios.version: v0.3238 dmi.board.name: Makalu dmi.board.vendor: Acer dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv0.3238:bd07/28/2009:svnAcer:pnAspire6930:pvrNotApplicable:rvnAcer:rnMakalu:rvrNotApplicable:cvnAcer:ct1:cvrN/A: dmi.product.name: Aspire 6930 dmi.product.version: Not Applicable dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/gdm3/+bug/1901342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899745] Re: [SRU] alsa-utils: let alsactl support _boot section defined in ucm
Hello Hui, or anyone else affected, Accepted alsa-utils into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa- utils/1.2.2-1ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1899745 Title: [SRU] alsa-utils: let alsactl support _boot section defined in ucm Status in HWE Next: New Status in alsa-utils package in Ubuntu: Fix Released Status in alsa-utils source package in Focal: Fix Committed Bug description: This patchset was backported from mainline alsa-utils 1.2.3, and groovy already integrated alsa-utils 1.2.3, there is no need to SRU this patchset to groovy, so only for focal. [Impact] We enabled 2 Dell soundwire audio machines, these machines depend on ucm to make the audio work, and in the ucm, the _boot section defined some amixers values for the 1st booting, these amixer values should be set to audio driver at the 1st booting, otherwise the whole audio doesn't work. [Fix] Backport some patches from mainline v1.2.3, these patches make the alsactl support _boot section in the ucm, then the systemd will call alsactl init after booting, the alsactl init will setting all amixers defined in the _boot section of ucm. [Test Case] On the Dell soundwire audio machines, After booting up, run 'amixer contents | less' to check all amixer values defined in the _boot section of ucm, all values read from driver are same as the ones in the ucm, test speaker/microphone/headset, all work well. [Regression Risk] This could introduce failure on runing 'alsactl init' for some machines, then the amixers will not be initialized correctly, users will experience all audio can't work like speaker doesn't output sound or microphone can't record sound. But this regression possibility is very low, since We have tested it both on soundwire machines and non-soundwire machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1899745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900170] Re: apport hook looks for snap profile folder in the wrong place
Hello Olivier, or anyone else affected, Accepted chromium-browser into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/chromium- browser/1:85.0.4183.83-0ubuntu0.20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: chromium-browser (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900170 Title: apport hook looks for snap profile folder in the wrong place Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Focal: Fix Committed Bug description: Since https://git.launchpad.net/~chromium-team/chromium-browser/+git /snap-from-source/commit/?id=d7e3b7f8, the default profile directory for the chromium snap was moved from $SNAP_USER_DATA to $SNAP_USER_COMMON (to mitigate the effects of bug #1616650). But the apport hook in the transitional deb package wasn't updated accordingly. [Impact] Bugs filed with `ubuntu-bug chromium-browser` have incomplete data attached. See e.g. the attachements to bug #1899356. There's a file called HookError_chromium_browser.txt with a python traceback because the profile directory wasn't found in the expected location. [Test Case] In focal, apt install chromium-browser, then run chromium at least once to ensure there is a profile directory (under $HOME/snap/chromium/common/chromium), then run `ubuntu-bug chromium- browser`. Observe that there isn't a FileNotFoundError traceback in the terminal for an unknown profile directory, and that the apport dialog with a summary of the information to be posted doesn't contain a "HookError_chromium_browser" entry. [Regression Potential] This affects only the apport hook for chromium-browser, the application itself shouldn't be affected. The hook should be verified to continue working by running the `ubuntu-bug chromium-browser` command and carefully inspecting the information that would be sent to launchpad. [Original description] ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Oct 16 18:40:02 2020 InstallationDate: Installed on 2020-09-16 (29 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Same problem using Aeropex by AfterShokz (AVRCP) headset on 20.04 (xps9310). Quick-and-dirty workaround: - download the 1.190 firmware package (http://mirrors.edge.kernel.org/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.190.tar.gz) - copy the relevant ibt firmware and parameters (sfi, ddc) to /usr/lib/firmware/intel (ibt-19-0-4 in my case) - backup of the old files highly recommended ;) - reboot, reconnect. My headset is now working both in A2DP and HFP/HSP modes. -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892643] Update Released
The verification of the Stable Release Update for libgweather has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1892643 Title: [SRU] Update libgweather to 3.36.1 Status in libgweather: Unknown Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Focal: Fix Released Status in libgweather package in Debian: Unknown Bug description: [Impact] libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36. https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS This version works around the unavailability of the NOAA weather services by using very short-term forecasts as current weather conditions. Sometimes the current weather is not available because the NOAA weather servers aren't working correctly. Version 3.36.1 fixes the unavailability of current temperature in some locations. [Test case] Make sure that gnome-weather is still working properly and the weather in gnome-shell is shown when gnome-weather is installed. [Regression potential] The regression potential is low since the changes in version 3.36.1 are small. [Other] libgweather 3.36.1 has been successfully built as a no-change backport from Groovy to Focal in my PPA and runs fine: https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter= ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 19:05:21 2020 InstallationDate: Installed on 2020-04-26 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1892643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892643] Re: [SRU] Update libgweather to 3.36.1
This bug was fixed in the package libgweather - 3.36.1-1~ubuntu20.04.1 --- libgweather (3.36.1-1~ubuntu20.04.1) focal; urgency=medium * No-change backport to focal (LP: #1892643) libgweather (3.36.1-1) unstable; urgency=medium * Team upload * New upstream release - This version works around the unavailability of the NOAA weather services by using very short-term forecasts as current weather conditions. (Closes: #968909) -- Amr Ibrahim Fri, 11 Sep 2020 18:32:10 +0200 ** Changed in: libgweather (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1892643 Title: [SRU] Update libgweather to 3.36.1 Status in libgweather: Unknown Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Focal: Fix Released Status in libgweather package in Debian: Unknown Bug description: [Impact] libgweather 3.36.1 is a bug-fix release as part of GNOME 3.36. https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS This version works around the unavailability of the NOAA weather services by using very short-term forecasts as current weather conditions. Sometimes the current weather is not available because the NOAA weather servers aren't working correctly. Version 3.36.1 fixes the unavailability of current temperature in some locations. [Test case] Make sure that gnome-weather is still working properly and the weather in gnome-shell is shown when gnome-weather is installed. [Regression potential] The regression potential is low since the changes in version 3.36.1 are small. [Other] libgweather 3.36.1 has been successfully built as a no-change backport from Groovy to Focal in my PPA and runs fine: https://launchpad.net/~amribrahim1987/+archive/ubuntu/ppa/+packages?field.name_filter=libgweather_filter=published_filter= ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgweather-3-16 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 23 19:05:21 2020 InstallationDate: Installed on 2020-04-26 (119 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: libgweather UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libgweather/+bug/1892643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901778] [NEW] Thunderbird crashes on start up
Public bug reported: When I try to start up Thunderbird (v 1:78.3.2), a information box appears with this message : "key id="openLightningKey"" This bug happened since yesterday, with Ubuntu 20.10. It didn't happen at the beginning when I have updated to 20.10 If I start Thunderbird by a command in the Terminal, I get these messages : [calBackendLoader] Using Thunderbird's libical backend Extension error: Error while loading 'jar:file:///usr/lib/thunderbird/omni.ja!/chrome/messenger/search-extensions/twitter/manifest.json' (NS_ERROR_FILE_NOT_FOUND) resource://gre/modules/Extension.jsm:570 :: readJSON/https://bugs.launchpad.net/bugs/1901778 Title: Thunderbird crashes on start up Status in thunderbird package in Ubuntu: New Bug description: When I try to start up Thunderbird (v 1:78.3.2), a information box appears with this message : "key id="openLightningKey"" This bug happened since yesterday, with Ubuntu 20.10. It didn't happen at the beginning when I have updated to 20.10 If I start Thunderbird by a command in the Terminal, I get these messages : [calBackendLoader] Using Thunderbird's libical backend Extension error: Error while loading 'jar:file:///usr/lib/thunderbird/omni.ja!/chrome/messenger/search-extensions/twitter/manifest.json' (NS_ERROR_FILE_NOT_FOUND) resource://gre/modules/Extension.jsm:570 :: readJSON/https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1901778/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901776] [NEW] emacs snap has many errors on startup - how to report snap-related bugs?
Public bug reported: [This is a reposting of Bug#1898083, which I reported against Emacs. I don't know what package to report for Emacs snap bugs, so I am initially guessing that the package should be "snap" in the form. If "snap" is wrong, please reassign it to the appropriate package, which apparently is not "emacs".] I just upgraded to Ubuntu 20.04 and my first shell command was 'emacs'. The response was: Command 'emacs' not found, but can be installed with: sudo snap install emacs # version 27.1, or sudo apt install e3 # version 1:2.71-2 sudo apt install emacs-gtk # version 1:26.3+1-1ubuntu2 sudo apt install emacs-lucid # version 1:26.3+1-1ubuntu2 sudo apt install emacs-nox # version 1:26.3+1-1ubuntu2 sudo apt install jove # version 4.17.2.7-1 See 'snap info emacs' for additional versions. So I tried the first command 'sudo snap install emacs'. So I tried it: $ sudo snap install emacs [sudo] password for eggert: error: This revision of snap "emacs" was published using classic confinement and thus may perform arbitrary system changes outside of the security sandbox that snaps are usually confined to, which may put your system at risk. If you understand and want to proceed repeat the command including --classic. That didn't look promising, but I was stubborn, and continued as follows: $ sudo snap install --classic emacs emacs 27.1 from Alex Murray (alexmurray) installed Great! Now I can run Emacs. But the experience was not good at all: $ emacs notes (emacs:5050): Gtk-WARNING **: 09:40:34.782: Theme parsing error: gtk.css:1521:23: 'font-feature-settings' is not a valid property name (emacs:5050): Gtk-WARNING **: 09:40:34.786: Theme parsing error: gtk.css:3460:25: 'font-feature-settings' is not a valid property name (emacs:5050): Gtk-WARNING **: 09:40:34.787: Theme parsing error: gtk.css:3922:23: 'font-feature-settings' is not a valid property name Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/10-hinting-slight.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/10-hinting-slight.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/10-scale-bitmap-fonts.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/11-lcdfilter-default.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 4: unknown element "its:rules" Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 5: unknown element "its:translateRule" Fontconfig error: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 5: invalid attribute 'translate' Fontconfig error: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 5: invalid attribute 'selector' Fontconfig error: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 6: invalid attribute 'xmlns:its' Fontconfig error: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 6: invalid attribute 'version' Fontconfig warning: "/etc/fonts/conf.d/20-unhint-small-vera.conf", line 8: unknown element "description" Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 4: unknown element "its:rules" Fontconfig warning:
Re: [Desktop-packages] [Bug 1894627] Re: [nvidia] Web browser distorted after hibernation/power save when idle
Hi Daniel, I know this is off topic but I am having wifi throughput issues. all other devices that connected to my wireless are getting 150 - 200+ Mbps download speed. I have an HP OMEN gaming laptop that cannot get pass 80mbps to download speed. Can you help me out with how to report this? On Mon, Oct 26, 2020 at 7:15 PM Daniel van Vugt <1894...@bugs.launchpad.net> wrote: > You don't need to shut down. I already gave a workaround in comment #23: > > Close and reopen Chrome after resuming from suspend/hibernation. Then > use Ctrl+Shift+T to restore your previous tabs. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1894627 > > Title: > [nvidia] Web browser distorted after hibernation/power save when idle > > Status in chromium-browser package in Ubuntu: > Triaged > Status in nvidia-graphics-drivers-340 package in Ubuntu: > Won't Fix > Status in nvidia-graphics-drivers-440 package in Ubuntu: > Won't Fix > > Bug description: > https://bugs.chromium.org/p/chromium/issues/detail?id=791913 > > --- > > my laptop goes to hibernation/power saver mode when my computer is idle. > every time I bring my computer back up, the screen distorted. I have to > close all my browsers. Sometimes, shut down the computer. > > Description: Ubuntu 20.04.1 LTS > Release: 20.04 > N: Unable to locate package pkgname > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 > Uname: Linux 5.4.0-45-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/gpus/:01:00.0' > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.suspend: suspend hibernate resume > .proc.driver.nvidia.suspend_depth: default modeset uvm > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 > 08:45:51 UTC 2020 >GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) > ApportVersion: 2.20.11-0ubuntu27.8 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Mon Sep 7 03:33:23 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DkmsStatus: >nvidia, 440.100, 5.4.0-42-generic, x86_64: installed >nvidia, 440.100, 5.4.0-45-generic, x86_64: installed > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 > [VGA controller]) > Subsystem: Hewlett-Packard Company UHD Graphics 630 (Mobile) > [103c:8466] >NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev > a1) (prog-if 00 [VGA controller]) > Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Ti > Mobile] [103c:8466] > InstallationDate: Installed on 2020-06-23 (75 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 > (20200423) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 002: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd > (Foxlink) HP Wide Vision HD Camera >Bus 001 Device 003: ID 8087:0aaa Intel Corp. >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: HP OMEN by HP Laptop > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic > root=UUID=98265a4d-5439-415e-b43c-904265a8559a ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 04/24/2019 > dmi.bios.vendor: AMI > dmi.bios.version: F.09 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: 8466 > dmi.board.vendor: HP > dmi.board.version: 68.21 > dmi.chassis.type: 10 > dmi.chassis.vendor: HP > dmi.chassis.version: Chassis Version > dmi.modalias: > dmi:bvnAMI:bvrF.09:bd04/24/2019:svnHP:pnOMENbyHPLaptop:pvr:rvnHP:rn8466:rvr68.21:cvnHP:ct10:cvrChassisVersion: > dmi.product.family: 103C_5335KV HP OMEN > dmi.product.name: OMEN by HP Laptop > dmi.product.sku: 4CC49UA#ABA > dmi.sys.vendor: HP > modified.conffile..etc.default.apport: ># set this to 0 to disable apport, or to 1 to enable it ># you can temporarily override this with ># sudo service apport start force_start=1 >enabled=0 > mtime.conffile..etc.default.apport: 2020-06-26T00:47:21.524860 > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.nvidia-graphics-drivers:
[Desktop-packages] [Bug 1901552] Re: Unrecoverable failure in required component org.gnome.Shell.desktop
The vpn client is not causing the timeout. However, I found a lot of kerberos errors in the auth.log and syslog upon subsequent attempts at solving this issue. (Tue Oct 27 10:54:53 2020) [[sssd[ldap_child[9515 [ldap_child_get_tgt_sync] (0x0010): Failed to init credentials: Preauthentication failed (Tue Oct 27 10:54:53 2020) [[sssd[ldap_child[9516 [ldap_child_get_tgt_sync] (0x0010): Failed to init credentials: Client 'wllnxrxxx...@domain.com' not found in Kerberos database I'm trying to figure out the correct configuration for sssd + realmd + kerberos to be able to join my computer to the AD domain. -- 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/1901552 Title: Unrecoverable failure in required component org.gnome.Shell.desktop Status in gnome-settings-daemon package in Ubuntu: New Bug description: A Lenovo P53 is installed with ubuntu 18.04.5 LTS. Graphics Intel UHD Graphics 630 (main display), nvidia quadro RTX 5000 also installed but not used for main display. Laptop is domain joined. When logging to the local ubuntu user, there is no problem detected. Then, if we log out and try to login with a domain user, gnome crashes. From what I can see in the logs, the user is authenticated correctly, but then in the instantiation of the session, gnome.shell.desktop faces an unrecoverable failure. From auth.log ``` pam_sss(gdm-password:auth): authentication success; logname= uid=0 euid=0 tty=/dev/tty1 ruser= rhost= user=u...@na.cie.com Oct 23 16:27:28 WLLNXPFX gdm-password]: pam_unix(gdm-password:session): session opened for user u...@na.cie.com by (uid=0) Oct 23 16:27:28 WLLNXPFX systemd-logind[1200]: New session 17 of user u...@na.cie.com. ``` From syslog ``` Oct 23 10:17:42 WLLNXPFX gnome-session[1914]: gnome-session-binary[1914]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 23 10:17:42 WLLNXPFX gnome-session[1914]: gnome-session-binary[1914]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 23 10:17:42 WLLNXPFX gnome-session-binary[1914]: CRITICAL: We failed, but the fail whale is dead. Sorry Oct 23 10:17:42 WLLNXPFX at-spi-bus-launcher[2026]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Oct 23 10:17:42 WLLNXPFX at-spi-bus-launcher[2026]: after 21 requests (21 known processed) with 0 events remaining. ``` I will include the full syslog and auth.log to this bug. Please let me know if any other log could be useful to troubleshoot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1901552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901759] [NEW] scp-dbus-service.py crashed with SIGSEGV in __new_sem_wait_fast()
Public bug reported: sadly I don't know how to reproduce this crash, it happened suddenly while I was browsing on the Internet ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: system-config-printer-common 1.5.12-0ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: E [27/Oct/2020:15:47:08 +0100] [CGI] ippfind (PID 13599) stopped with status 1! E [27/Oct/2020:15:47:08 +0100] [cups-deviced] PID 13586 (driverless) stopped with status 1! CurrentDesktop: XFCE Date: Tue Oct 27 16:15:17 2020 ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py ExecutableTimestamp: 1602240671 InstallationDate: Installed on 2020-04-28 (182 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterpreterPath: /usr/bin/python3.8 Lpstat: device for Generic-CUPS-BRF-Printer: cups-brf:/ device for MG2500: cnijbe://Canon/?port=usb=8EC02C device for MG2500-series: usb://Canon/MG2500%20series?serial=8EC02C=1 MachineType: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD PackageArchitecture: all Papersize: a4 PpdFiles: MG2500-series: Canon MG2500 series Ver.4.00 Generic-CUPS-BRF-Printer: Canon MultiPASS C2500 Foomatic/bjc600 (recommended) MG2500: Canon MG2500 series Ver.4.00 ProcCmdline: /usr/bin/python3 /usr/share/system-config-printer/scp-dbus-service.py ProcCwd: /home/davide ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=512841ce-43ad-462f-ae39-89ea8684065f ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: system-config-printer StacktraceTop: __new_sem_wait_fast (definitive_result=0, sem=0x0) at sem_waitcommon.c:137 __new_sem_wait (sem=0x0) at sem_wait.c:39 PyThread_acquire_lock () () () UpgradeStatus: Upgraded to groovy on 2020-10-20 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 11/29/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K30AD_M31AD_M51AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd11/29/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnK30AD_M31AD_M51AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnK30AD_M31AD_M51AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: K30AD_M31AD_M51AD dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-10-23T13:57:01.282362 separator: ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash groovy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1901759 Title: scp-dbus-service.py crashed with SIGSEGV in __new_sem_wait_fast() Status in system-config-printer package in Ubuntu: New Bug description: sadly I don't know how to reproduce this crash, it happened suddenly while I was browsing on the Internet ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: system-config-printer-common 1.5.12-0ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: E [27/Oct/2020:15:47:08 +0100] [CGI] ippfind (PID 13599) stopped with status 1! E [27/Oct/2020:15:47:08 +0100] [cups-deviced] PID 13586 (driverless) stopped with status 1! CurrentDesktop: XFCE Date: Tue Oct 27 16:15:17 2020 ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py ExecutableTimestamp: 1602240671 InstallationDate: Installed on 2020-04-28 (182 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterpreterPath: /usr/bin/python3.8 Lpstat: device for Generic-CUPS-BRF-Printer: cups-brf:/ device for MG2500: cnijbe://Canon/?port=usb=8EC02C device for MG2500-series: usb://Canon/MG2500%20series?serial=8EC02C=1 MachineType: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD PackageArchitecture: all Papersize: a4 PpdFiles: MG2500-series: Canon MG2500 series Ver.4.00
[Desktop-packages] [Bug 1901759] Re: scp-dbus-service.py crashed with SIGSEGV in __new_sem_wait_fast()
** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1901759 Title: scp-dbus-service.py crashed with SIGSEGV in __new_sem_wait_fast() Status in system-config-printer package in Ubuntu: New Bug description: sadly I don't know how to reproduce this crash, it happened suddenly while I was browsing on the Internet ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: system-config-printer-common 1.5.12-0ubuntu3 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CupsErrorLog: E [27/Oct/2020:15:47:08 +0100] [CGI] ippfind (PID 13599) stopped with status 1! E [27/Oct/2020:15:47:08 +0100] [cups-deviced] PID 13586 (driverless) stopped with status 1! CurrentDesktop: XFCE Date: Tue Oct 27 16:15:17 2020 ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py ExecutableTimestamp: 1602240671 InstallationDate: Installed on 2020-04-28 (182 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterpreterPath: /usr/bin/python3.8 Lpstat: device for Generic-CUPS-BRF-Printer: cups-brf:/ device for MG2500: cnijbe://Canon/?port=usb=8EC02C device for MG2500-series: usb://Canon/MG2500%20series?serial=8EC02C=1 MachineType: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD PackageArchitecture: all Papersize: a4 PpdFiles: MG2500-series: Canon MG2500 series Ver.4.00 Generic-CUPS-BRF-Printer: Canon MultiPASS C2500 Foomatic/bjc600 (recommended) MG2500: Canon MG2500 series Ver.4.00 ProcCmdline: /usr/bin/python3 /usr/share/system-config-printer/scp-dbus-service.py ProcCwd: /home/davide ProcEnviron: LANGUAGE=it_IT PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-26-generic root=UUID=512841ce-43ad-462f-ae39-89ea8684065f ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: system-config-printer StacktraceTop: __new_sem_wait_fast (definitive_result=0, sem=0x0) at sem_waitcommon.c:137 __new_sem_wait (sem=0x0) at sem_wait.c:39 PyThread_acquire_lock () () () UpgradeStatus: Upgraded to groovy on 2020-10-20 (7 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 11/29/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K30AD_M31AD_M51AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0402:bd11/29/2013:br4.6:svnASUSTeKCOMPUTERINC.:pnK30AD_M31AD_M51AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnK30AD_M31AD_M51AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: K30AD_M31AD_M51AD dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-10-23T13:57:01.282362 separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1901759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901736] Re: Xorg freeze
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1901736 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Most of the time Ubuntu boots the dock seems to freeze and not load any icons, sometimes for up to a minute. When this happens the dock will not appear when any window is maximized. Once in a while Ubuntu loads without a problem. The dock loads instantly and has no problem behind a maximized window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 12:35:14 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 640 [8086:5926] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 640 [8086:2068] InstallationDate: Installed on 2020-09-16 (41 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC7i5BNK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=50f7562f-c44b-4a47-b1b4-02bdd6281c08 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139 dmi.board.name: NUC7i5BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31144-314 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i5BNK:pvrJ31159-315:rvnIntelCorporation:rnNUC7i5BNB:rvrJ31144-314:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BN dmi.product.name: NUC7i5BNK dmi.product.version: J31159-315 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1901736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901736] [NEW] Xorg freeze
You have been subscribed to a public bug: Most of the time Ubuntu boots the dock seems to freeze and not load any icons, sometimes for up to a minute. When this happens the dock will not appear when any window is maximized. Once in a while Ubuntu loads without a problem. The dock loads instantly and has no problem behind a maximized window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 27 12:35:14 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Plus Graphics 640 [8086:5926] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Plus Graphics 640 [8086:2068] InstallationDate: Installed on 2020-09-16 (41 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel(R) Client Systems NUC7i5BNK ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=50f7562f-c44b-4a47-b1b4-02bdd6281c08 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BNKBL357.86A.0080.2019.0725.1139 dmi.board.name: NUC7i5BNB dmi.board.vendor: Intel Corporation dmi.board.version: J31144-314 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBNKBL357.86A.0080.2019.0725.1139:bd07/25/2019:svnIntel(R)ClientSystems:pnNUC7i5BNK:pvrJ31159-315:rvnIntelCorporation:rnNUC7i5BNB:rvrJ31144-314:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: BN dmi.product.name: NUC7i5BNK dmi.product.version: J31159-315 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu wayland-session -- Xorg freeze https://bugs.launchpad.net/bugs/1901736 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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
The standalone patch #217 is working for MSFT0001:00 04F3:3140 but isn't working perfectly for MSFT0001:00 06CB:7F28. The MSFT0001:00 06CB:7F28 touchpad frequently locks into scroll mode when using multitouch gestures. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Fix Committed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05
[Desktop-packages] [Bug 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures
Still not working in Ubuntu 20.10 with Firefox 82. -- 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/1697122 Title: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu version: Kubuntu 17.04 Firefox version: 53.0.3+build1-0ubuntu0.17.04.2 In Firefox, two-finger scroll gestures on a touchpad are interpreted as scroll wheel rotations, and the content scrolls three lines at a time. This is inappropriate behavior for touchpad scrolling; it should scroll pixel-by-pixel. Firefox already has the ability to do this, you just need to turn it on by running the program with MOZ_USE_XINPUT2=1 in the environment: for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to /etc/environment or something like that. Turning on this behavior yields a large usability improvement for laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be permanently added to the packaging such that it's always present when Firefox runs. This is what Fedora does, and it results in a much improved experience for the laptop user. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1697122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896878] Re: Doesn't compile for groovy
This patch needa the /kernel/ path prefixes removed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1896878 Title: Doesn't compile for groovy Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: dkms.conf can be changed to just use PATCH[0]="kernel-5.7.patch" PATCH[1]="buildfix_kernel_5.8.patch" with patches from archlinux: https://aur.archlinux.org/cgit/aur.git/tree/buildfix_kernel_5.8.patch?h=nvidia-340xx and https://gitlab.manjaro.org/packages/extra/linux57-extramodules/nvidia-340xx/-/raw/master/kernel-5.7.patch?inline=false Except that the kernel-5.7 patch needs to be modified to remove the dkms.conf section therein, and the kernel/ paths for files needs to be removed. A fixed kernel-5.7.patch file is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896878] Re: Doesn't compile for groovy
Note also a patch for kernel 5.9 there: https://aur.archlinux.org/cgit/aur.git/tree/0003-kernel-5.9.patch?h =nvidia-340xx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1896878 Title: Doesn't compile for groovy Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: dkms.conf can be changed to just use PATCH[0]="kernel-5.7.patch" PATCH[1]="buildfix_kernel_5.8.patch" with patches from archlinux: https://aur.archlinux.org/cgit/aur.git/tree/buildfix_kernel_5.8.patch?h=nvidia-340xx and https://gitlab.manjaro.org/packages/extra/linux57-extramodules/nvidia-340xx/-/raw/master/kernel-5.7.patch?inline=false Except that the kernel-5.7 patch needs to be modified to remove the dkms.conf section therein, and the kernel/ paths for files needs to be removed. A fixed kernel-5.7.patch file is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1896878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901752] [NEW] Can’t connect to a specific Wi-Fi network with wpa_supplicant
Public bug reported: This is the error I get if I try to connect to a specific Wi-Fi network on Ubuntu 20.10 with wpa_supplicant: Error: Connection activation failed: (7) Secrets were required, but not provided. If I use iwd instead, everything works fine. I also can connect to other networks with wpa_supplicant. I had the same issue with the Live USB. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: wpasupplicant 2:2.9-1ubuntu8 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: i3 Date: Tue Oct 27 20:55:39 2020 InstallationDate: Installed on 2020-10-26 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1901752 Title: Can’t connect to a specific Wi-Fi network with wpa_supplicant Status in wpa package in Ubuntu: New Bug description: This is the error I get if I try to connect to a specific Wi-Fi network on Ubuntu 20.10 with wpa_supplicant: Error: Connection activation failed: (7) Secrets were required, but not provided. If I use iwd instead, everything works fine. I also can connect to other networks with wpa_supplicant. I had the same issue with the Live USB. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: wpasupplicant 2:2.9-1ubuntu8 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: i3 Date: Tue Oct 27 20:55:39 2020 InstallationDate: Installed on 2020-10-26 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1901752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824260] Re: wrong kerning in SS-5 PDF form fields
Ok, I changed the Ubuntu patch in accordance with your suggestion. Maybe a bit better... As regards your upstream issue, you probably increase the chances that it gets attention if you submit a merge request. ** Patch removed: "fontconfig_lp1824260.debdiff" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1824260/+attachment/5427587/+files/fontconfig_lp1824260.debdiff ** Patch added: "fontconfig_lp1824260.debdiff" https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1824260/+attachment/5428033/+files/fontconfig_lp1824260.debdiff ** Also affects: fontconfig via https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/262 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1824260 Title: wrong kerning in SS-5 PDF form fields Status in Fontconfig: Unknown Status in Poppler: New Status in fontconfig package in Ubuntu: In Progress Bug description: What I expected to happen: I am filling out the SS-5 Social Security Administration form (see attached). I entered "John Jacob Smith" into the "First", "Full Middle Name", and "Last" fields on page 5. What happened instead: I can enter the text without issue, but some of the letters are wrongly positioned, i.e. the kerning is wrong. For example, the letter "i" overlaps with the letter "m" in "Smith" (see attached image). It looks like the font in the fields might be displaying a variable width font when it is supposed to be a fixed-wdith font. Discussion: Since this bug is also present in xpdf and Okular (but not mupdf), I'm guessing this isn't a bug in Evince itself. However, I am reporting it here as a courtesy to other users (since Evince is the default PDF reader) and because I'm not sure which dependency is responsible. (I'm also not sure if it's a direct dependency problem or if it's something else like a font configuration issue.) Here is the output for pdffonts ss-5.pdf: name type encoding emb sub uni object ID - --- --- --- - IHPIKC+ArialMT CID TrueType Identity-H yes yes yes824 0 ArialMT TrueType WinAnsi no no no 826 0 Arial-BoldMT TrueType WinAnsi no no no 828 0 CourierStd Type 1WinAnsi no no no 145 0 HelveticaType 1WinAnsi no no no 197 0 MyriadPro-RegularType 1WinAnsi no no no 198 0 ZapfDingbats Type 1ZapfDingbats no no no 199 0 I asked about this in an Ask Ubuntu question nearly a year ago, but received no response, so I am reporting a bug now instead: https://askubuntu.com/questions/1031235/wrong-letter-positioning-and- font-in-pdf-form Ubuntu version: Description: Ubuntu 18.04.2 LTS Release: 18.04 evince version: $ apt-cache policy evince evince: Installed: 3.28.4-0ubuntu1 Candidate: 3.28.4-0ubuntu1 Version table: *** 3.28.4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 10 21:27:11 2019 InstallationDate: Installed on 2018-12-12 (119 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/1824260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901538] Re: Output Device selection messed (Line Out <-> HDMI)
OK, so deletion of pulse config helped. First deletion only temporarly and the weird behavior came back after some switching. But after the second one it seems to be permanently fixed and I can't reproduce the faulty behavior. So I assume it can be seen as fixed?! If it happens again and is reproducible, I'll report again. Thank you for your help! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1901538 Title: Output Device selection messed (Line Out <-> HDMI) Status in gnome-control-center package in Ubuntu: Incomplete Bug description: [System] - Freshly installed Ubuntu 20.04.1 LTS with 3rd party software/drivers enabled - pulseaudio 1:13.99.1-1ubuntu3.7 - NVIDIA graphics card (GeForce GTX 650 Ti Boost) using nvidia-driver-450 - Monitor with build-in (stereo) speakers connected via HDMI to graphics card - External (stereo) speakers connected via audio jack to mainboard [Expected Behavior] 1. Go to "Settings" -> "Sound" -> "Output" -> "Output Device" 2. Switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" 3. The switching should enable the chosen output device. [Bug Description and Behavior] If I switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" and test the output, sound comes still from monitor speakers and not from my external speakers. [Workaround] While "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" selected, go to "Configuration" and switch from "Digital Stereo (HDMI 2) Output" to "Digital Surround 5.1 (HDMI 2) Output". Instantly "Configuration" row disappears, in Output Device "Line Out - Built-in Audio" is selected and external speakers are active. [Further comments] I'm affected by this bug and the "wrong audio output on every reboot/wake up/login" since upgrade to 20.04 but the latter may be worth another bug report or maybe you could guide me to an active bug report that isn't linked to a previous Ubuntu version and already marked as fixed. At first I thought it may be caused by failed upgrade or my system configurations, but now I tested with a freshly installed Ubuntu on a spare SSD and the problem still exists, so here I am. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 13:15:41 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-10-26 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1901538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897185] Re: Laptop docked with lid closed, goes to sleep immediately on login
Daniel, this seems consistent: so long as I don't load the Dropbox app, I haven't seen the suspend. I don't know if this is the cause but regardless the Dropbox app may help in reproducing this issue? Thanks... -- 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/1897185 Title: Laptop docked with lid closed, goes to sleep immediately on login Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Ubuntu 20.04's software updater just applied quite a few updates affecting grub and nvidia. The modules should show in the report just submitted. Also, updates to initramfs had just installed a few days ago. Kudos in that these updates fixed two login/startup issues: I'd been affected by the compression change for initramfs and had started getting the spinning ubuntu circle on the logon splash screen, apparently due to an nvidia driver conflict. I'd turned the splash screen to nosplash, and have now been able to set it back to splash. Both of those issues now appear to be fixed. BUT now when I start Ubuntu with the T570 laptop docked, lid closed, external display and keyboard via the dock: as soon as I enter the login password and press enter, the system goes into suspend. If I then press the dock power button again, the system will resume and proceed normally. It seems that the new startup modules don't realize that the machine is docked; and/or that it erroneously now "detects" the closed lid as a change in lid state during startup, triggering suspend. Prior to today's updates, this was not an issue. I would appreciate seeing this corrected. Thank you. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Sep 24 18:15:31 2020 InstallationDate: Installed on 2020-06-22 (94 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427981/+files/WifiSyslog.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427980/+files/UdevDb.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] Re: Sound Blaster Audigy 5/Rx cannot be configured as input/output
@Daniel van Vugt: thanks for checking my bug request. I apologise for the missing information: I've just executed the apport-collect and I wish all the necessary information to be attached. -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427979/+files/PulseList.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427982/+files/acpidump.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427978/+files/ProcModules.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427977/+files/ProcInterrupts.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427976/+files/ProcEnviron.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427975/+files/ProcCpuinfoMinimal.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427969/+files/Dependencies.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427973/+files/Lsusb-t.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427974/+files/Lsusb-v.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427972/+files/Lsusb.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427971/+files/Lspci-vt.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427967/+files/CRDA.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427970/+files/Lspci.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427968/+files/CurrentDmesg.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ale1149 F pulseaudio /dev/snd/controlC1: ale1149 F pulseaudio /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20 InstallationDate: Installed on 2020-08-29 (59 days ago) InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] PackageArchitecture: amd64 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 RfKill: Tags: ulyana third-party-packages Uname: Linux 5.4.0-52-generic x86_64 UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.80 dmi.board.name: Z97 Extreme6 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901413/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901413] Re: Sound Blaster Audigy 5/Rx cannot be configured as input/output
apport information ** Tags added: apport-collected third-party-packages ulyana ** Description changed: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the sound but the microphones are greyed out in the audio panel and I can't use it in any application. Instead if I select "Input "Analog Stereo"" I can record the audio but I can't hear any output! The volumes are turned up according also to a previous post I did related to similar issue I had in the past. The only workaround found so far is to execute: "pacmd load-module module-alsa-source device=hw:1,0". Please find attached "alsa-info" report. Everything was working fine in Min 19.3 but not in Mint 20 (based on Ubuntu 20.04): DISTRIB_ID=LinuxMint DISTRIB_RELEASE=20 DISTRIB_CODENAME=ulyana DISTRIB_DESCRIPTION="Linux Mint 20 Ulyana" snd_emu10k1 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.10 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ale1149 F pulseaudio + /dev/snd/controlC1: ale1149 F pulseaudio + /dev/snd/pcmC1D0p: ale1149 F...m pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 20 + InstallationDate: Installed on 2020-08-29 (59 days ago) + InstallationMedia: Linux Mint 20 "Ulyana" - Release amd64 20200624 + IwConfig: + enp3s0no wireless extensions. + + lono wireless extensions. + MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. + NonfreeKernelModules: nvidia_modeset nvidia + Package: pulseaudio 1:13.99.1-1ubuntu3.7 [origin: Ubuntu] + PackageArchitecture: amd64 + ProcFB: 0 VESA VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=115b8bd7-9195-4e50-b759-835b1a63a5e7 ro quiet splash + ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-52-generic N/A + linux-backports-modules-5.4.0-52-generic N/A + linux-firmware1.187.3 + RfKill: + + Tags: ulyana third-party-packages + Uname: Linux 5.4.0-52-generic x86_64 + UnreportableReason: Questo non è un pacchetto ufficiale di Linux. Rimuovere tutti i pacchetti di terze parti, quindi riprovare. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/06/2018 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: P2.80 + dmi.board.name: Z97 Extreme6 + dmi.board.vendor: ASRock + dmi.chassis.asset.tag: To Be Filled By O.E.M. + dmi.chassis.type: 3 + dmi.chassis.vendor: To Be Filled By O.E.M. + dmi.chassis.version: To Be Filled By O.E.M. + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd03/06/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: + dmi.product.family: To Be Filled By O.E.M. + dmi.product.name: To Be Filled By O.E.M. + dmi.product.sku: To Be Filled By O.E.M. + dmi.product.version: To Be Filled By O.E.M. + dmi.sys.vendor: To Be Filled By O.E.M. + modified.conffile..etc.pulse.default.pa: [modified] + mtime.conffile..etc.pulse.default.pa: 2020-10-25T14:57:41.721069 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1901413/+attachment/5427966/+files/AlsaInfo.txt -- 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/1901413 Title: Sound Blaster Audigy 5/Rx cannot be configured as input/output Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I have Sound Blaster Audigy 5/Rx, using the well known snd_emu10k1, but I cannot use it as both input and output device: it's working either as output or as input but not as input/output. I have installed "pavucontrol", when opening it in "configure" there are different options: Output "Analog Stereo" Output "Digital Stereo (IEC958)" Output "Surround 5.1" Output "Surround 4.1" Output "Surround 2.1" Output "Surround 7.1" Output "Surround 5.0" Output "Surround 4.0" Input "Analog Stereo" Input "Digital Stereo (IEC958)" If I pick one of the "output" I can hear the
[Desktop-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration
Hello Christian, or anyone else affected, Accepted systemd into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: systemd (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1892358 Title: autopkgtest success rate dropped inhibiting proposed migration Status in build-essential package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Invalid Status in iputils package in Ubuntu: Invalid Status in kbd package in Ubuntu: Invalid Status in linux-meta package in Ubuntu: Invalid Status in ntpsec package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in util-linux package in Ubuntu: Invalid Status in linux-meta source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in build-essential source package in Focal: Confirmed Status in linux-meta source package in Focal: New Status in qemu source package in Focal: Confirmed Status in systemd source package in Focal: Fix Committed Status in util-linux source package in Focal: Confirmed Bug description: [impact] autopkgtests are failing/flaky and prevent other packages from migrating to -updates [test case] check autopkgtest history [regression potential] in regard to the changed test cases, any regression would likely result in either an incorrectly passed test, or an incorrectly failed test. [scope] for systemd, this is needed for x, b, and f. tests in g appear to be mostly stable, but I've opened MR (linked from this bug) to update the tests there as well. i don't plan to update x, as it's reaching ESM in ~6 months, and backporting the test fixes is more work than just a simple code copy, since there are additional differences/changes needed in the older version of systemd (and python3). the failing/flaky tests in x have been like that forever, and people have just retried them; we can keep retrying them until x moves into ESM next year. [original description] Hi, we had such cases in the past like bug 1817721 for bionic and maybe bug 1892130 is about the same as well. There were more but I didn't want to search for all of them - what I checked is that there are no open ones clearly pointing out the recent further drop in already flaky subtests. In particular the tests "tests-in-lxd" and "systemd-fsckd" were known to be flaky before, but got even worse. Here stats of the last 40 runs, it might be a coincidences that this is after 246-2ubuntu1 landed. Could as well be any other change groovy amd64 tests-in-lxd (F 42% S 0% B 10% => P 45%/) BFFFBFF.B.F.F...FBF build-login(F 0% S 0% B 10% => P 87%/) B...B...BB. unit-config(F 0% S 0% B 10% => P 87%/) B...B...BB. networkd-testpy(F 0% S 0% B 10% => P 87%/) B...B...BB. boot-and-services (F 0% S 0% B 10% => P 87%/) B...B...BB. boot-smoke (F 0% S 0% B 10% => P 87%/) B...B...BB. logind (F 0% S 0% B 10% => P 87%/) B...B...BB. storage(F 0% S 0% B 10% => P 87%/) B...B...BB. upstream (F 35% S 0% B 10% => P 52%/) ..FFB.FFF.FFBFF.B.F.F..FFBF udev (F 0% S 0% B 10% => P 87%/)
[Desktop-packages] [Bug 1261048] Re: [Upstream] Wrong results from rounding functions for large argument
** Changed in: df-libreoffice Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1261048 Title: [Upstream] Wrong results from rounding functions for large argument Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:4.1.3-0ubuntu3 Candidate: 1:4.1.3-0ubuntu3 Version table: *** 1:4.1.3-0ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status I am using Ubuntu 12.04.3 LTS and within that LibreOffice 3.5.7.2, Build ID: 350m1(Build:2) but this is also reproducible in LO Trunk 4.3.0.0.alpha0+ on Windows Vista: What is expected to happen at a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261048/+attachment/3942054/+files/LibreOfficeRoundingIssues.ods && localc --nologo LibreOfficeRoundingIssues Is that for cell D5 is it 0. What happens instead is that it is 5. This would be an issue with Calc numerical precision, as the actual outcome of 5 is also the same with Excel. WORKAROUND: Use gnumeric: apt-cache policy gnumeric gnumeric: Installed: 1.12.9-1 Candidate: 1.12.9-1 Version table: *** 1.12.9-1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status --- ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MarkForUpload: True Package: libreoffice 1:3.5.7-0ubuntu5 PackageArchitecture: i386 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-35.50~precise1-generic 3.8.13.13 Tags: precise running-unity Uname: Linux 3.8.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1261048/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261048]
WORKSFORME with Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 12; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1261048 Title: [Upstream] Wrong results from rounding functions for large argument Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:4.1.3-0ubuntu3 Candidate: 1:4.1.3-0ubuntu3 Version table: *** 1:4.1.3-0ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status I am using Ubuntu 12.04.3 LTS and within that LibreOffice 3.5.7.2, Build ID: 350m1(Build:2) but this is also reproducible in LO Trunk 4.3.0.0.alpha0+ on Windows Vista: What is expected to happen at a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261048/+attachment/3942054/+files/LibreOfficeRoundingIssues.ods && localc --nologo LibreOfficeRoundingIssues Is that for cell D5 is it 0. What happens instead is that it is 5. This would be an issue with Calc numerical precision, as the actual outcome of 5 is also the same with Excel. WORKAROUND: Use gnumeric: apt-cache policy gnumeric gnumeric: Installed: 1.12.9-1 Candidate: 1.12.9-1 Version table: *** 1.12.9-1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status --- ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MarkForUpload: True Package: libreoffice 1:3.5.7-0ubuntu5 PackageArchitecture: i386 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-35.50~precise1-generic 3.8.13.13 Tags: precise running-unity Uname: Linux 3.8.0-35-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1261048/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899025] Re: Thunderbird 78.3.2 snap translations issue during 1st launch after update
Confirmed with 78.3.2 -> 78.3.3 -> 78.4.0 . The TB menu is translated including this first launch, though. ** Attachment added: "Capture d’écran de 2020-10-27 17-36-59.png" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899025/+attachment/5427936/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202020-10-27%2017-36-59.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1899025 Title: Thunderbird 78.3.2 snap translations issue during 1st launch after update Status in thunderbird package in Ubuntu: New Bug description: When I updated today from 78.3.1 to 78.3.2, after the first launch of the updated 78.3.2, I got some untranslated strings (Inbox in mailboxes folder list, e.g.). After the 2nd launch, all became normal. AFAICR, it was the case during previous updates too. Not a big deal, though... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1899025/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900009] Re: Window tiled to monitor where most of the window is in instead of where the mouse is.
Hello Christian, or anyone else affected, Accepted mutter into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.38.1-2ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- 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/199 Title: Window tiled to monitor where most of the window is in instead of where the mouse is. Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: In Progress Status in gnome-shell source package in Groovy: Invalid Status in mutter source package in Groovy: Fix Committed Bug description: Release: Ubuntu Groovy Gorilla (development branch) 20.10 Package version: 3.38.1-1ubuntu1 [ Impact ] When I tile windows using edge tiling, I want the window to tile on the same edge that I brought it to, however, if the window is mostly in monitor 1 when I try to tile it to the left (or right) edge of monitor 2, the window will tile to the left (or right) edge of monitor 2. This happens on both my computer with an Nvidia GPU on x11 and my laptop using Intel integrated graphics on Wayland. [ Test case ] - In multi-monitor setup, grab a tile edge to the side where the other monitor is - The window should not be moved to the other monitor [ Regression potential ] Windows may be tiled to the wrong monitor once created To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878293] Re: xterm resize is wonky
Hello John, or anyone else affected,
Accepted mutter into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/3.38.1-2ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: mutter (Ubuntu Groovy)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-groovy
--
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/1878293
Title:
xterm resize is wonky
Status in Mutter:
Unknown
Status in mutter package in Ubuntu:
In Progress
Status in xterm package in Ubuntu:
Invalid
Status in mutter source package in Groovy:
Fix Committed
Status in xterm source package in Groovy:
Invalid
Bug description:
[ Impact ]
When I try to resize an xterm window the same way,
this happens instead: as the mouse is moved, the upper-right corner
does move, but it doesn't track with the mouse pointer like it should.
Meanwhile, the lower-left corner also moves (it should have remained anchored
in its original x-y position on the screen).
[ Test case ]
- Start Xterm
- Resize the window from its top/left corner
- It should resize normally, and not act as shown in
https://gitlab.gnome.org/GNOME/mutter/uploads/3c19763b7748ce76b0ba2958cde7636b/Screencast_from_02-04-19_14_03_24.webm
[ Regression potential ]
Windows resizing might not work correctly
---
% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04 LTS
Release:20.04
Codename: focal
% wmctrl -m
Name: GNOME Shell
Class: N/A
PID: N/A
Window manager's "showing the desktop" mode: OFF
Terms:
window has four sides: top, bottom, left, and right
when referring to corners, "upper" means "top", and "lower" means "bottom",
so the four corners are upper-right, lower-right, lower-left, and upper-left.
wonky: works wrong, as detailed below ("cases that work wrong...")
Description:
I can resize a gnome-terminal window, everything works fine.
(Grab it, using the mouse, by the upper-right corner (click-and-hold);
the size changes as the mouse is moved, because the position
of the upper-right corner follows the mouse. (Only the upper-right corner
moves.))
But when I try to resize an xterm window the same way,
this happens instead: as the mouse is moved, the upper-right corner
does move, but it doesn't track with the mouse pointer like it should.
Meanwhile, the lower-left corner also moves (it should have remained anchored
in its original x-y position on the screen).
Cases that work correctly:
If the xterm window is grabbed by the lower-right corner and resized, this
case works properly.
If the xterm window is grabbed by the bottom edge and resized, this case
works properly.
If the xterm window is grabbed by the right edge and resized, this case works
properly.
Cases that work wrong ("wonky"):
If the xterm window is grabbed by the left edge and resized, then the
opposite (i.e. right) edge (incorrectly) migrates.
If the xterm window is grabbed by the top edge and resized, then the opposite
(i.e. bottom) edge (incorrectly) migrates.
If the xterm window is grabbed by the upper-right corner and resized, then
the window (incorrectly) migrates.
If the xterm window is grabbed by the lower-left corner and resized, then the
window (incorrectly) migrates.
If the xterm window is grabbed by the upper-left corner and resized, then the
window (incorrectly) migrates.
ProblemType: BugDistroRelease: Ubuntu 20.04
Package: xterm 353-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory:
'/proc/driver/nvidia/gpus/:01:00.0'
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
Hello Martin, or anyone else affected, Accepted mutter into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.38.1-2ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-groovy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Groovy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: In Progress Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
That's very good news, although there is no fonts-specific change/fix in that revision. That revision uses LZO compression, which trades snap size (from ~172MB to 252MB) for startup speed. I'm glad this improves the situation so significantly! I am also working on a specific fix for font cache generation (using the gnome-3-28 snapcraft extension to build the snap), so I'll keep this bug open to track progress on this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Confirmed Bug description: I upgraded from Focal to Groovy, and now the first launch of the Chromium snap after a reboot is taking much longer than before. On my main home laptop it takes over 30 seconds, while under Focal I don't remember it taking more than 10 seconds. I tried another computer I could erase. On Groovy that computer takes nearly a minute to launch the Chromium snap after rebooting. Then I clean installed Focal on the same machine, and the Chromium snap takes just under 10 seconds to launch after a reboot. For both I installed all updates, and I let the computer sit idle for a few minutes after rebooting to try to rule out other activity. I haven’t noticed the change for any other snap, although I don’t use any that I ever noticed as much of a launch delay as Chromium. (VS Code for one doesn’t seem slower — certainly not taking nearly a minute — but I haven't done a real comparison like for Chromium.) ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 21:29:20 2020 InstallationDate: Installed on 2020-04-01 (202 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Snap: chromium 87.0.4280.20 (latest/beta) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875056] Re: locate-pointer (w/ ctrl key) not working
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/1875056 Title: locate-pointer (w/ ctrl key) not working Status in gnome-shell package in Ubuntu: Confirmed Bug description: It was working for an hour and then stopped. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 19:09:37 2020 InstallationDate: Installed on 2020-03-31 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) SourcePackage: gnome-settings-daemon 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/1875056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901694] Re: No hardware aceleration
** 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/1901694 Title: No hardware aceleration Status in xorg package in Ubuntu: New Bug description: Computer HP EliteBook 8460p. It uses hybrid graphics card. Processor Intel Core i5-2520M CPU @ 2.50GHz × 4; 2nd generation. The system only runs well with llvmpipe (LLVM 6.0, 256 bits) graphic software, AMD Caicos sometimes it's charged too, but the graphic display have problems and don't goes fine or fluid. Maybe there is no support for the processor graphics because It's a little bit old. I don't know how to install AMD proprietary drivers, It maybe solve the problem. I installed Ubuntu 20.04 LTS but don't works, It don't charge any graphic interface, only a black screen. I only uses the system in recovery mode. For that reason I returned to Ubuntu 16.04 LTS but my graphics don't have hardware acceleration, only software acceleration. When I tried to play (Super Tux Kart for example) I expected a berry poor graphic improvement, so I can't play It. Thanks for your time and attention! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 27 05:47:39 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2020-10-25 (1 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=es_CR:es PATH=(custom, no user) LANG=es_CR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-122-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.60 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.asset.tag: IS09189 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.60:bd03/12/2015:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 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 xserver.bootTime: Tue Oct 27 05:43:49 2020 xserver.configfile: default xserver.errors: AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1901694/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901694] [NEW] No hardware aceleration
You have been subscribed to a public bug: Computer HP EliteBook 8460p. It uses hybrid graphics card. Processor Intel Core i5-2520M CPU @ 2.50GHz × 4; 2nd generation. The system only runs well with llvmpipe (LLVM 6.0, 256 bits) graphic software, AMD Caicos sometimes it's charged too, but the graphic display have problems and don't goes fine or fluid. Maybe there is no support for the processor graphics because It's a little bit old. I don't know how to install AMD proprietary drivers, It maybe solve the problem. I installed Ubuntu 20.04 LTS but don't works, It don't charge any graphic interface, only a black screen. I only uses the system in recovery mode. For that reason I returned to Ubuntu 16.04 LTS but my graphics don't have hardware acceleration, only software acceleration. When I tried to play (Super Tux Kart for example) I expected a berry poor graphic improvement, so I can't play It. Thanks for your time and attention! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-122.124~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.24 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Oct 27 05:47:39 2020 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e] InstallationDate: Installed on 2020-10-25 (1 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=es_CR:es PATH=(custom, no user) LANG=es_CR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-122-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.60 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.4E dmi.chassis.asset.tag: IS09189 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.60:bd03/12/2015:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 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 xserver.bootTime: Tue Oct 27 05:43:49 2020 xserver.configfile: default xserver.errors: AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.4 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- No hardware aceleration https://bugs.launchpad.net/bugs/1901694 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 1899270] Re: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously
Thanks Barry! ** Description changed: After pressing F11 there's a text box at the top of the screen with the message Press F11 to Exit, etc. Usually this goes away by itself after a few seconds. Now it flashes continuously and won't clear. Pressing F11 again quits full screen mode, but the tab is still flashing in some way and the whole browser is now unstable and not usable. Chrome: Version 86.0.4240.75 (Official Build) (64-bit) - System: Ubuntu Studio, + System: Ubuntu Studio, Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal ** Description changed: After pressing F11 there's a text box at the top of the screen with the message Press F11 to Exit, etc. Usually this goes away by itself after a few seconds. Now it flashes continuously and won't clear. Pressing F11 again quits full screen mode, but the tab is still flashing in some way and the whole browser is now unstable and not usable. Chrome: Version 86.0.4240.75 (Official Build) (64-bit) System: Ubuntu Studio, Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal + + upstream bug: + https://bugs.chromium.org/p/chromium/issues/detail?id=1142850 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1899270 Title: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously Status in chromium-browser package in Ubuntu: Confirmed Bug description: After pressing F11 there's a text box at the top of the screen with the message Press F11 to Exit, etc. Usually this goes away by itself after a few seconds. Now it flashes continuously and won't clear. Pressing F11 again quits full screen mode, but the tab is still flashing in some way and the whole browser is now unstable and not usable. Chrome: Version 86.0.4240.75 (Official Build) (64-bit) System: Ubuntu Studio, Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal upstream bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1142850 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900783] Re: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot
On my test computer at least, today's snap revision 1373 seems to have solved it. Running `snap run --trace-exec chromium` on a cold boot I get Slowest 10 exec calls during snap run: 0.237s snap-update-ns 0.400s /usr/lib/snapd/snap-confine 0.087s /snap/chromium/1373/snap/command-chain/snapcraft-runner 0.590s /snap/chromium/1373/bin/desktop-launch 0.065s /usr/bin/snapctl 0.114s /snap/chromium/1373/bin/chromium.launcher 0.159s /usr/bin/dbus-send 0.286s /usr/bin/xdg-settings 3.609s /proc/self/exe 5.238s /snap/chromium/1373/usr/lib/chromium-browser/chrome Total time: 6.515s -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1900783 Title: [snap] On Groovy, Chromium snap takes much longer to load the first time after reboot Status in chromium-browser package in Ubuntu: Confirmed Bug description: I upgraded from Focal to Groovy, and now the first launch of the Chromium snap after a reboot is taking much longer than before. On my main home laptop it takes over 30 seconds, while under Focal I don't remember it taking more than 10 seconds. I tried another computer I could erase. On Groovy that computer takes nearly a minute to launch the Chromium snap after rebooting. Then I clean installed Focal on the same machine, and the Chromium snap takes just under 10 seconds to launch after a reboot. For both I installed all updates, and I let the computer sit idle for a few minutes after rebooting to try to rule out other activity. I haven’t noticed the change for any other snap, although I don’t use any that I ever noticed as much of a launch delay as Chromium. (VS Code for one doesn’t seem slower — certainly not taking nearly a minute — but I haven't done a real comparison like for Chromium.) ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Oct 20 21:29:20 2020 InstallationDate: Installed on 2020-04-01 (202 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Snap: chromium 87.0.4280.20 (latest/beta) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to groovy on 2020-10-17 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1900783/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897281] Re: evince suicides in 20.04 but not in 18.04
Since "I ain't got no" third party yet, I quit and switched to Kubuntu 20.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1897281 Title: evince suicides in 20.04 but not in 18.04 Status in evince package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Evince does a suicide trip after unsuccessfully trying to open a CBR file. After a while it is killed. Here is my terminal output: $ evince TheCartoons.cbr Killed $ And between the line "$ evince TheCartoons.cbr" and the final "Killed", are passing many minutes. Please note that I started my report in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060 not knowing exactly what "expired" there means. I did "apport-collect 1785060" there, too. Please note also that my error message (see above) is quite different from seb128 in bug 1785060. In fact, there is no error message just the statement "Killed". What gets me is that in 18.04 it is working so smooth and fast and that in 20.04 it is such a mess! P.S. I do not know whether this helps, but with Debian 11 Xfce (Buster sid, testing), evince loads and opens this CBR file correctly, albeit slowly, but okular (installed in Buster sid) yields a similar error message like that of seb128 with evince in bug 1785060: "Could not open file TheCartoons.cbr. The version of unrar on your system is not suitable for opening comicbooks" Inverted world ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785060] Re: Evince cannot open cbr-files based on rar v5
Solution ;-) at gthe end of https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897281?comments=all -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1785060 Title: Evince cannot open cbr-files based on rar v5 Status in evince package in Ubuntu: Expired Bug description: Trying to open a cbr-Archive based on rar v5 leads to "Der Dateityp RAR-Archiv (application/vnd.rar) wird nicht unterstützt." CBR-Files based on other rar-Types, e.g. rarv4 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900812] Re: pulseaudio crashed with SIGSEGV in pa_sink_move_streams_to_default_sink() from report_jack_state() from mixer_class_event() from hctl_elem_event_handler() from snd
The autopkgtest issue got retried and cleared off now, there is one error on e.u.c from the new version but it seems rather a report glitch (still old version active at the time of reporting) so I'm going to tag verified ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- 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/1900812 Title: pulseaudio crashed with SIGSEGV in pa_sink_move_streams_to_default_sink() from report_jack_state() from mixer_class_event() from hctl_elem_event_handler() from snd_hctl_elem_throw_event() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Groovy: Fix Committed Bug description: * Impact There is a segfault issue started with the recent update * Test case We don't have specific steps to trigger the issue so test for regression and verify that reports stop on https://errors.ubuntu.com/problem/31c6bfaf0ac65939a763307ca3d3a4f27f38e9f0 * Regression potential The regression was created by a fix for gnome-control-center device selection issues, check that the settings still work correctly, allowing to change devices and showing the active one as selected To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1900812/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899270] Re: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously
Filed ... https://bugs.chromium.org/p/chromium/issues/detail?id=1142850 :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1899270 Title: Chrome on Ubuntu, press F11 for full screen and the message flashes continuously Status in chromium-browser package in Ubuntu: Confirmed Bug description: After pressing F11 there's a text box at the top of the screen with the message Press F11 to Exit, etc. Usually this goes away by itself after a few seconds. Now it flashes continuously and won't clear. Pressing F11 again quits full screen mode, but the tab is still flashing in some way and the whole browser is now unstable and not usable. Chrome: Version 86.0.4240.75 (Official Build) (64-bit) System: Ubuntu Studio, Distributor ID: Ubuntu Description: Ubuntu 20.04.1 LTS Release: 20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1899270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900009] Re: Window tiled to monitor where most of the window is in instead of where the mouse is.
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Groovy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- 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/199 Title: Window tiled to monitor where most of the window is in instead of where the mouse is. Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: In Progress Status in gnome-shell source package in Groovy: Invalid Status in mutter source package in Groovy: In Progress Bug description: Release: Ubuntu Groovy Gorilla (development branch) 20.10 Package version: 3.38.1-1ubuntu1 [ Impact ] When I tile windows using edge tiling, I want the window to tile on the same edge that I brought it to, however, if the window is mostly in monitor 1 when I try to tile it to the left (or right) edge of monitor 2, the window will tile to the left (or right) edge of monitor 2. This happens on both my computer with an Nvidia GPU on x11 and my laptop using Intel integrated graphics on Wayland. [ Test case ] - In multi-monitor setup, grab a tile edge to the side where the other monitor is - The window should not be moved to the other monitor [ Regression potential ] Windows may be tiled to the wrong monitor once created To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons()
** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
