[Desktop-packages] [Bug 1872266] [NEW] Activities missing stuff when using dual monitors
Public bug reported: This is mostly just cosmetic, but when I use a second monitor with my laptop, and click the Activities in the upper left-hand corner, it looks like it is missing the bottom half of the icons for the applications, and perhaps other things I'm searching for. See the screenshot attached. It looks fine when I'm using only the builtin monitor on the laptop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 22:16:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-19 (359 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "dual_screen_launcher_view_issue.png" https://bugs.launchpad.net/bugs/1872266/+attachment/5352339/+files/dual_screen_launcher_view_issue.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872266 Title: Activities missing stuff when using dual monitors Status in gnome-shell package in Ubuntu: New Bug description: This is mostly just cosmetic, but when I use a second monitor with my laptop, and click the Activities in the upper left-hand corner, it looks like it is missing the bottom half of the icons for the applications, and perhaps other things I'm searching for. See the screenshot attached. It looks fine when I'm using only the builtin monitor on the laptop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 22:16:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-19 (359 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872258] Re: GS injects invalid metadata, causing "AppStream cache update completed, but some metadata was ignored"
** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1872258 Title: GS injects invalid metadata, causing "AppStream cache update completed, but some metadata was ignored" Status in gnome-software package in Ubuntu: Triaged Bug description: Hi! GNOME Software currently injects invalid AppStream metadata in Focal, causing a complaint message like "AppStream cache update completed, but some metadata was ignored due to errors." on every APT update. This can be fixed by applying this patch from upstream and Debian, which was present in GNOME's release candidate but was accidentally reverted: https://salsa.debian.org/gnome-team/gnome-software/-/blob/05553c1bfa2124a12e3afe5c63de510310377036/debian/patches/02_fix-appstream-featured-data.patch Debian already ships this patch. Thanks for considering! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
** Attachment added: "boot messages with plymouth debugging messages" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5352286/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. This problem is not reproduced if using nosplash. I have installed 20.04 to this laptop. Thinkpad T480, i7, intel graphics. Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. The fsck step does not commence. In recovery mood, I can log in. With no external monitors attached, it works. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 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.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop)
** Summary changed: - booting with splash hangs when external monitors are connected (pure intel laptop) + booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) ** Description changed: + I think this is a problem with the splash boot loader. This problem is + not reproduced if using nosplash. - I think this is a problem with the splash boot loader. + I have installed 20.04 to this laptop. Thinkpad T480, i7, intel + graphics. - I have installed 20.04 to this laptop. Clean install, not an upgrade. + Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. - I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. + I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. The fsck step does not commence. + In recovery mood, I can log in. - I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. + + With no external monitors attached, it works. + + I am used to having such problems with Nvidia graphics is involved, but + this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed - tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed + acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed + tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: - Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Lenovo UHD Graphics 620 [17aa:225d] + Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 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.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- 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/1872159 Title: booting with splash hangs when external monitors are connected (pure intel 8th gen laptop) Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. This problem is not reproduced if using nosplash. I have installed 20.04 to this laptop. Thinkpad T480, i7, intel graphics. Clean install of 20.04 beta, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at
[Desktop-packages] [Bug 1872258] [NEW] GS injects invalid metadata, causing "AppStream cache update completed, but some metadata was ignored"
Public bug reported: Hi! GNOME Software currently injects invalid AppStream metadata in Focal, causing a complaint message like "AppStream cache update completed, but some metadata was ignored due to errors." on every APT update. This can be fixed by applying this patch from upstream and Debian, which was present in GNOME's release candidate but was accidentally reverted: https://salsa.debian.org/gnome-team/gnome-software/-/blob/05553c1bfa2124a12e3afe5c63de510310377036/debian/patches/02_fix-appstream-featured-data.patch Debian already ships this patch. Thanks for considering! ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: Triaged ** Tags: patch ** Tags added: patch ** Summary changed: - Injects invalid metadata, causing "AppStream cache update completed, but some metadata was ignored due to errors." + GS injects invalid metadata, causing "AppStream cache update completed, but some metadata was ignored" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1872258 Title: GS injects invalid metadata, causing "AppStream cache update completed, but some metadata was ignored" Status in gnome-software package in Ubuntu: Triaged Bug description: Hi! GNOME Software currently injects invalid AppStream metadata in Focal, causing a complaint message like "AppStream cache update completed, but some metadata was ignored due to errors." on every APT update. This can be fixed by applying this patch from upstream and Debian, which was present in GNOME's release candidate but was accidentally reverted: https://salsa.debian.org/gnome-team/gnome-software/-/blob/05553c1bfa2124a12e3afe5c63de510310377036/debian/patches/02_fix-appstream-featured-data.patch Debian already ships this patch. Thanks for considering! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872258/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872256] [NEW] Unable to play DVD disc / The playback of this move requires a DVD source plugin which is not installed.
Public bug reported: I am unable to play DVD discs. Followed the usual Ubuntu process, but the issue persists. Nothing aforementioned in https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044 helps. Ubuntu 20.04 beta. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgstreamer1.0-0 1.16.2-2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 02:09:35 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2020-04-06 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1872256 Title: Unable to play DVD disc / The playback of this move requires a DVD source plugin which is not installed. Status in gstreamer1.0 package in Ubuntu: New Bug description: I am unable to play DVD discs. Followed the usual Ubuntu process, but the issue persists. Nothing aforementioned in https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1809044 helps. Ubuntu 20.04 beta. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgstreamer1.0-0 1.16.2-2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 02:09:35 2020 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2020-04-06 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1872256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected (pure intel laptop)
** Summary changed: - booting with splash hangs when external monitors are connected + booting with splash hangs when external monitors are connected (pure intel laptop) -- 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/1872159 Title: booting with splash hangs when external monitors are connected (pure intel laptop) Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 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.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 62430] Re: rhythmbox doesn't support .pls and .m3u files
Perhaps they've decided to take a page from insurance and big corps facing class action lawsuits: delay until the plaintiffs die (or lose interest or give up). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/62430 Title: rhythmbox doesn't support .pls and .m3u files Status in Rhythmbox: New Status in desktop-file-utils package in Ubuntu: Fix Released Status in rhythmbox package in Ubuntu: Triaged Bug description: Binary package hint: rhythmbox The problem is, RhythmBox doesn't support playlists loaded externally. So when a user chooses "open this file" in firefox, rhythmbox pops up and nothing happens. I think the same goes for .m3u playlists. On the other hand, it's a shame rhythmbox doesn't support external playlists well... It makes it unusable when it comes to internet radios and stuff like that :/ To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/62430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872053] Re: Local mail is never checked
Well, my approach was very simple : mail notification in terminal has worked for decades, I used in the 2000s, so why not use it again if it suits me ? It is not mandatory to "reinvent the wheel" for an old need. Anyway, I already tried to use /var/mail/$USER in my graphical email client (Thunderbird) : trust me it's very buggy. (Mail is only checked at start, sometimes "read-only", sometimes it becomes duplicated) But I will gladly examine any other graphical solution, provided it's (almost) as lightweight as the terminal one :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround : Put export MAIL=/var/mail/$USER in ~/.bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872230] Re: With any US international layout left Ctrl key does not work
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/1872230 Title: With any US international layout left Ctrl key does not work Status in gnome-shell package in Ubuntu: Confirmed Bug description: I am using 20.04 Focal. I am using a US international keyboard layout with dead keys, so that I can enter text in many different languages. After I had rebooted my system today and so loaded the newest GNOME Shell, the left Ctrl key stopped working in the terminal windows and also in emacs, while the right Ctrl still works. To get the left Ctrl working again I have to switch to a plain US English keyboard layout, without dead keys. I have also tried the different alternatives of US International keyboard layouts, each of them seems to work as intended but the left Ctrl key is not working. Only with plain US English layout I get the left Ctrl working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872247] [NEW] activities overview area is too small on the primary display
Public bug reported: Precondition: the desktop is set to span 2 displays (or maybe more but I only have 2 displays). When the activities overview is invoked (e.g., after pressing the 'windows' key), the area where you see window thumbnails and search results is too short on the primary display. It is OK on the secondary display. The bug occurs if: - Display mode is "Join Displays" - The physical display setup has the primary display under the secondary display. As per the settings/display application, assuming display 1 is set to be the primary display, the bug will occur with the following physical display setup: 2 1 <-- (primary is display 1 and it's the one at the bottom) It doesn't matter which of the two displays is set to be the primary display. If display number 2 is set to be the primary one, and the physical display setup is like this: 1 2 <-- (primary is display 2 and it's the one at the bottom) then the bug also occurs. The bug doesn't occur in other physical display setups (e.g., side by side, or the primary on top). The bug doesn't occur when the display mode is "Mirror" or "Single Display". --- lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.36.1-4ubuntu1 Candidate: 3.36.1-4ubuntu1 Version table: *** 3.36.1-4ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-desktop3 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot of the whole desktop. Primary is display 1, at the bottom." https://bugs.launchpad.net/bugs/1872247/+attachment/5352208/+files/Screenshot%20from%202020-04-11%2023-10-04.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1872247 Title: activities overview area is too small on the primary display Status in gnome-desktop3 package in Ubuntu: New Bug description: Precondition: the desktop is set to span 2 displays (or maybe more but I only have 2 displays). When the activities overview is invoked (e.g., after pressing the 'windows' key), the area where you see window thumbnails and search results is too short on the primary display. It is OK on the secondary display. The bug occurs if: - Display mode is "Join Displays" - The physical display setup has the primary display under the secondary display. As per the settings/display application, assuming display 1 is set to be the primary display, the bug will occur with the following physical display setup: 2 1 <-- (primary is display 1 and it's the one at the bottom) It doesn't matter which of the two displays is set to be the primary display. If display number 2 is set to be the primary one, and the physical display setup is like this: 1 2 <-- (primary is display 2 and it's the one at the bottom) then the bug also occurs. The bug doesn't occur in other physical display setups (e.g., side by side, or the primary on top). The bug doesn't occur when the display mode is "Mirror" or "Single Display". --- lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 apt-cache policy gnome-shell gnome-shell: Installed: 3.36.1-4ubuntu1 Candidate: 3.36.1-4ubuntu1 Version table: *** 3.36.1-4ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1872247/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871807] Re: Installed fonts are not available for selection
gnome-terminal lists the fonts that are monospace according to pango_font_family_is_monospace(). The font as well as Pango should be examined why this one isn't believed to be a monospace one. That being said, you can still set this font using dconf-editor, by setting /org/gnome/terminal/legacy/profiles:/:/font. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1871807 Title: Installed fonts are not available for selection Status in gnome-terminal package in Ubuntu: New Bug description: I have installed the following font from nerd fonts using gnome-fonts by double clicking the file and selecting install. https://github.com/ryanoasis/nerd-fonts/blob/master/patched-fonts/FiraCode/Medium/complete/Fura%20Code%20Medium%20Nerd%20Font%20Complete%20Mono.otf The font doesn't appear in gnome terminal custom font selector. I'm running the following system Linux admin2-ThinkPad-X1-Carbon-7th 5.3.0-40-generic #32~18.04.1-Ubuntu SMP Mon Feb 3 14:05:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux And using gnome terminal 3.28.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1871807/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872053] Re: Local mail is never checked
I'd take one step back and ask the question: Why would anyone one a graphical system need to run a terminal emulator in order to get notified about new mail? What if someone uses all kinds of other applications (web browser, document editor, photo viewer, music player...), just not a terminal, why wouldn't they be notified? The right approach is not to fix whatever happens inside the terminal emulator, the right approach is to have a graphical indicator on the desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround : Put export MAIL=/var/mail/$USER in ~/.bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872241] Re: evolution-addressbook-factory crashed with signal 5 in g_thread_new()
*** This bug is a duplicate of bug 1858320 *** https://bugs.launchpad.net/bugs/1858320 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1858320, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872241/+attachment/5352162/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1872241/+attachment/5352164/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1872241/+attachment/5352168/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1872241/+attachment/5352169/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1872241/+attachment/5352170/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872241/+attachment/5352171/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872241/+attachment/5352172/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1858320 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1872241 Title: evolution-addressbook-factory crashed with signal 5 in g_thread_new() Status in evolution-data-server package in Ubuntu: New Bug description: it was crashing in the background, without me actively doing anything with the addressbook ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.28.5-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 8 16:27:54 2020 ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory InstallationDate: Installed on 2017-10-13 (911 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory Signal: 5 SourcePackage: evolution-data-server StacktraceTop: g_thread_new () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 e_data_factory_spawn_subprocess_backend () at /usr/lib/x86_64-linux-gnu/libebackend-1.2.so.10 () at /usr/lib/x86_64-linux-gnu/libedata-book-1.2.so.25 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: evolution-addressbook-factory crashed with signal 5 in g_thread_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1872241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872242] [NEW] HDA Intel PCH on samsung laptop: Headphones not working, speakers are ok
Public bug reported: Speakers in my samsung laptop are ok, but headphones don't work (no sound). Using Ubuntu 18.04 defaults. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sartojr1936 F pulseaudio /dev/snd/controlC0: sartojr1936 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:47:32 2020 InstallationDate: Installed on 2020-01-14 (88 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1377 F pulseaudio sartojr1936 F pulseaudio /dev/snd/controlC0: gdm1377 F pulseaudio sartojr1936 F pulseaudio Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [760XBE, Realtek ALC256, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02REZ.040.190610.FL:bd06/10/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn760XBE:pvrP02REZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP760XBE-XW1BR:rvrSGL9947A0Y-C01-G003-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook 7 Series dmi.product.name: 760XBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREZ dmi.product.version: P02REZ dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-11T15:48:00.584083 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: - Speakers in my samsung laptop are ok, but hearphones are muted. Using + Speakers in my samsung laptop are ok, but headphones are muted. Using Ubuntu 18.04 defaults. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: sartojr1936 F pulseaudio - /dev/snd/controlC0: sartojr1936 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: sartojr1936 F pulseaudio + /dev/snd/controlC0: sartojr1936 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:47:32 2020 InstallationDate: Installed on 2020-01-14 (88 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: - LANGUAGE=pt_BR:pt:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=pt_BR.UTF-8 - SHELL=/bin/bash + LANGUAGE=pt_BR:pt:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pt_BR.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Áudio interno - HDA Intel PCH Symptom_DevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: gdm1377 F pulseaudio - sartojr1936 F pulseaudio - /dev/snd/controlC0: gdm1377 F pulseaudio - sartojr1936 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: gdm1377 F pulseaudio + sartojr1936 F pulseaudio + /dev/snd/controlC0: gdm1377 F pulseaudio + sartojr1936 F pulseaudio Symptom_Jack: Black Headphone Out, Right Symptom_Type: No sound at all Title: [760XBE, Realtek ALC256, Black Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02REZ.040.190610.FL dmi.board.asset.tag: No Asset Tag dmi.board.name: NP760XBE-XW1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9947A0Y-C01-G003-S0001+10.0.17763
[Desktop-packages] [Bug 1870057] Re: Ensure we collect failed reverted state
This bug was fixed in the package zsys - 0.4.3 --- zsys (0.4.3) focal; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Fix GC collection of failed revert or incomplete boots and add tests for them (LP: #1870057, #1870054) * Account filesystem datasets in GC bucket policy budget, as it was leading to under budget results once cleaned up. * Fix warning when mounting source is set to default (LP: #1870052) * Fix some issues in go-libzfs: - it was not assigning the correct dataset type, leading to a segfault if the user has a zfs volume in a pool. - Perf enhancements by only loading our needed properties to reduce the amount of C performed calls. * Enhance apt hook: - Only display output and errors if running on ZFS systems (LP: #1868523, #1870304). - Suppress the 20 minutes grace period and only prevent multiple snapshots when unattended-upgrades is running. * Transition from 19.10: change the userdata user properties on first boot for machines installed from 19.10 without zsys installed. * Add apport hook. * Fix various mispells, simplify some code and remove some ineffective assignements. * Fix error message typos. * Fix generator check on CI, update bug template and update CI to use Go 1.14 in preparation of focal switch to 1.14. -- Didier Roche Wed, 08 Apr 2020 14:42:21 +0200 ** Changed in: zsys (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1870057 Title: Ensure we collect failed reverted state Status in zsys package in Ubuntu: Fix Released Bug description: Two kind of datasets we should collect in the GC: - root and children datasets if reverting failed (initramfs cloned -> failed in generator) - states that don’t have a valid LastUsed To evaluate: - main dataset for a machine is never cleaned up, so ok - only consider (and ensure that we set this) zsys / datasets and children - maybe consider creation date if no LastUsed set? (to avoid race between creation, like on another machine and immediate collect) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1870057/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868523] Re: "ERROR couldn't save system state: Current machine isn't Zsys, nothing to create" on non zsys system shouldn’t be visible
This bug was fixed in the package zsys - 0.4.3 --- zsys (0.4.3) focal; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Fix GC collection of failed revert or incomplete boots and add tests for them (LP: #1870057, #1870054) * Account filesystem datasets in GC bucket policy budget, as it was leading to under budget results once cleaned up. * Fix warning when mounting source is set to default (LP: #1870052) * Fix some issues in go-libzfs: - it was not assigning the correct dataset type, leading to a segfault if the user has a zfs volume in a pool. - Perf enhancements by only loading our needed properties to reduce the amount of C performed calls. * Enhance apt hook: - Only display output and errors if running on ZFS systems (LP: #1868523, #1870304). - Suppress the 20 minutes grace period and only prevent multiple snapshots when unattended-upgrades is running. * Transition from 19.10: change the userdata user properties on first boot for machines installed from 19.10 without zsys installed. * Add apport hook. * Fix various mispells, simplify some code and remove some ineffective assignements. * Fix error message typos. * Fix generator check on CI, update bug template and update CI to use Go 1.14 in preparation of focal switch to 1.14. -- Didier Roche Wed, 08 Apr 2020 14:42:21 +0200 ** Changed in: zsys (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1868523 Title: "ERROR couldn't save system state: Current machine isn't Zsys, nothing to create" on non zsys system shouldn’t be visible Status in zsys package in Ubuntu: Fix Released Bug description: Hi, when I try to update the system I get this error even if the operations seem to complete. Hello. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1868523/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870052] Re: warning when mountpoint source is set to default
This bug was fixed in the package zsys - 0.4.3 --- zsys (0.4.3) focal; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Fix GC collection of failed revert or incomplete boots and add tests for them (LP: #1870057, #1870054) * Account filesystem datasets in GC bucket policy budget, as it was leading to under budget results once cleaned up. * Fix warning when mounting source is set to default (LP: #1870052) * Fix some issues in go-libzfs: - it was not assigning the correct dataset type, leading to a segfault if the user has a zfs volume in a pool. - Perf enhancements by only loading our needed properties to reduce the amount of C performed calls. * Enhance apt hook: - Only display output and errors if running on ZFS systems (LP: #1868523, #1870304). - Suppress the 20 minutes grace period and only prevent multiple snapshots when unattended-upgrades is running. * Transition from 19.10: change the userdata user properties on first boot for machines installed from 19.10 without zsys installed. * Add apport hook. * Fix various mispells, simplify some code and remove some ineffective assignements. * Fix error message typos. * Fix generator check on CI, update bug template and update CI to use Go 1.14 in preparation of focal switch to 1.14. -- Didier Roche Wed, 08 Apr 2020 14:42:21 +0200 ** Changed in: zsys (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1870052 Title: warning when mountpoint source is set to default Status in zsys package in Ubuntu: Fix Released Status in zsys source package in Focal: Fix Released Bug description: This is a valid source that we should consider "inherit". Example in log: https://github.com/ubuntu/zsys/issues/62 and https://gist.github.com/nirvdrum/67b9e496b215276538cbcf7bce6d3a4b. The bet is that it’s the case when the pool itself doesn’t have any mountpoint set. (and so the root datasets and all children have default) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1870052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870054] Re: warning issues for swap dataset mounpoint source property being ""
This bug was fixed in the package zsys - 0.4.3 --- zsys (0.4.3) focal; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Fix GC collection of failed revert or incomplete boots and add tests for them (LP: #1870057, #1870054) * Account filesystem datasets in GC bucket policy budget, as it was leading to under budget results once cleaned up. * Fix warning when mounting source is set to default (LP: #1870052) * Fix some issues in go-libzfs: - it was not assigning the correct dataset type, leading to a segfault if the user has a zfs volume in a pool. - Perf enhancements by only loading our needed properties to reduce the amount of C performed calls. * Enhance apt hook: - Only display output and errors if running on ZFS systems (LP: #1868523, #1870304). - Suppress the 20 minutes grace period and only prevent multiple snapshots when unattended-upgrades is running. * Transition from 19.10: change the userdata user properties on first boot for machines installed from 19.10 without zsys installed. * Add apport hook. * Fix various mispells, simplify some code and remove some ineffective assignements. * Fix error message typos. * Fix generator check on CI, update bug template and update CI to use Go 1.14 in preparation of focal switch to 1.14. -- Didier Roche Wed, 08 Apr 2020 14:42:21 +0200 ** Changed in: zsys (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1870054 Title: warning issues for swap dataset mounpoint source property being "" Status in zsys package in Ubuntu: Fix Released Bug description: Similar to https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1870052, the source can be "" for canmount. It seems to happen on swap dataset. We should evaluates what we consider it (maybe inherited to avoid setting it) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1870054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862566] Re: Corrupt sound played
Thanks for responding, Daniel. I missed your response. Unfortunately the issue is rare enough that I can't rely on reproducing it. -- 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/1862566 Title: Corrupt sound played Status in pulseaudio package in Ubuntu: Expired Bug description: Every once in a while, I get sort of static-y sound with a degree of echo. This affects all sounds - within browser, using `play` from the terminal, etc. I can solve it by restarting pulseaudio. However, when I do that, I no longer get the terminal beep. Ubuntu 18.04 It's not common, and I can't find anything wrong in the system log. To restart, I killed the process: /usr/bin/pulseaudio --start --log-target=syslog It restarts itself, and audio generally seems to be working now. However, I now see in the system log things like: Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [9666:9666:0209/220538.227104:ERROR:pulse_util.cc(300)] pa_operation is nullptr. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [9666:9666:0209/220538.227183:ERROR:pulse_util.cc(300)] pa_operation is nullptr. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [8767:1:0209/220538.229919:ERROR:webrtc_sdp.cc(402)] Failed to parse: "a=msid: ". Reason: Missing track ID in msid attribute. Feb 9 22:05:38 cerberus update-notifier.desktop[4802]: [8767:1:0209/220538.243052:ERROR:rtc_peer_connection_handler.cc(2446)] Failed to create native session description. Type: "offer" SDP: "v=0\r\no=- 4839823990544483155 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 0\r\na=msid-semantic: WMS\r\nm=application 9 UDP/TLS/RTP/SAVPF 119\r\nc=IN IP4 0.0.0.0\r\nb=AS:30\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=ice-ufrag:7Ejs\r\na=ice-pwd:938XM9CAOZEbY2uhDpuFrizo\r\na=ice-options:trickle\r\na=fingerprint:sha-256 23:5D:00:AF:7B:28:BA:7D:02:92:4E:00:66:5F:B3:C1:C4:F2:BD:66:2B:10:03:74:93:B5:F1:9E:61:45:A3:15\r\na=setup:actpass\r\na=mid:0\r\na=sendrecv\r\na=msid: \r\na=rtcp-mux\r\na=rtpmap:119 google-data/9\r\na=ssrc:4203958806 cname:1yXiouHPsVbMJDst\r\na=ssrc:4203958806 msid:- \r\na=ssrc:4203958806 mslabel:-\r\na=ssrc:4203958806 label:\r\n" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18 Uname: Linux 4.15.0-87-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 22:02:47 2020 InstallationDate: Installed on 2016-05-30 (1350 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-09-17 (511 days ago) dmi.bios.date: 01/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X10DAI dmi.board.vendor: Supermicro dmi.board.version: 1.01 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.:bvr1.0c:bd01/29/2015:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: SMC X10 dmi.product.name: X10DAi dmi.product.version: 123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1862566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870304] Re: Do not run update-grub in live session
This bug was fixed in the package zsys - 0.4.3 --- zsys (0.4.3) focal; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Fix GC collection of failed revert or incomplete boots and add tests for them (LP: #1870057, #1870054) * Account filesystem datasets in GC bucket policy budget, as it was leading to under budget results once cleaned up. * Fix warning when mounting source is set to default (LP: #1870052) * Fix some issues in go-libzfs: - it was not assigning the correct dataset type, leading to a segfault if the user has a zfs volume in a pool. - Perf enhancements by only loading our needed properties to reduce the amount of C performed calls. * Enhance apt hook: - Only display output and errors if running on ZFS systems (LP: #1868523, #1870304). - Suppress the 20 minutes grace period and only prevent multiple snapshots when unattended-upgrades is running. * Transition from 19.10: change the userdata user properties on first boot for machines installed from 19.10 without zsys installed. * Add apport hook. * Fix various mispells, simplify some code and remove some ineffective assignements. * Fix error message typos. * Fix generator check on CI, update bug template and update CI to use Go 1.14 in preparation of focal switch to 1.14. -- Didier Roche Wed, 08 Apr 2020 14:42:21 +0200 ** Changed in: zsys (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1870304 Title: Do not run update-grub in live session Status in zsys package in Ubuntu: Fix Released Bug description: update-grub cannot run on a live session. When a user installs a package in a live session, installation is successful but it ends with the following message: [...] Refreshing boot menu INFO Updating GRUB menu ERROR "update-grub" returned an error: exit status 1 We should detect the type of session and not run update-grub if it is a live session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 2 11:15:07 2020 InstallationDate: Installed on 2014-07-15 (2088 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) SourcePackage: zsys UpgradeStatus: Upgraded to focal on 2018-03-24 (739 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1870304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872053] Re: Local mail is never checked
Anyway my workaround... does not really work. It only works if I receive a new mail while gnome-terminal is running : in this case I will have "You have new mail" at next command line prompt. If I receive new mail while gnome-terminal is not running, THEN I launch gnome-terminal : no notification. But you are right, I should move to askubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround : Put export MAIL=/var/mail/$USER in ~/.bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872235] [NEW] package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127
Public bug reported: When doing a distro-upgrade from Ubuntu 16.04 to 18.04 shared-mime-info broke the whole process throwing errors about libicu60, which was installed as new in the upgrade process. While the system was broken, I forced a reinstall of libicu60 (apt install --reinstall libicu60) which then allowed shared-mime-info to be installable. As this interrupted the distro upgrade process, I have rolled back to a backup before the upgrade took place, so this system is not in the same state as when the issue happened. I am not able to provide further debug assistance here. I've performed many upgrades from 16.04 to 18.04 and have only seen this issue happen once so far. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shared-mime-info 1.9-2 ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214 Uname: Linux 4.4.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sat Apr 11 13:33:07 2020 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2016-03-14 (1489 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: shared-mime-info Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2020-04-11 (0 days ago) ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1872235 Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127 Status in shared-mime-info package in Ubuntu: New Bug description: When doing a distro-upgrade from Ubuntu 16.04 to 18.04 shared-mime- info broke the whole process throwing errors about libicu60, which was installed as new in the upgrade process. While the system was broken, I forced a reinstall of libicu60 (apt install --reinstall libicu60) which then allowed shared-mime-info to be installable. As this interrupted the distro upgrade process, I have rolled back to a backup before the upgrade took place, so this system is not in the same state as when the issue happened. I am not able to provide further debug assistance here. I've performed many upgrades from 16.04 to 18.04 and have only seen this issue happen once so far. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shared-mime-info 1.9-2 ProcVersionSignature: Ubuntu 4.4.0-177.207-generic 4.4.214 Uname: Linux 4.4.0-177-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sat Apr 11 13:33:07 2020 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2016-03-14 (1489 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12 SourcePackage: shared-mime-info Title: package shared-mime-info 1.9-2 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to bionic on 2020-04-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1872235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
** Changed in: libxml2 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in libxml2:
New
Status in libxml2 package in Ubuntu:
Fix Committed
Status in ubuntu-docs package in Ubuntu:
Fix Released
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/libxml2/+bug/1869814/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871787] Re: Screen sharing can not be enabled from the Gnome Control Center
I agree with @seb128, this is probably a duplicate of 1871351. -- 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/1871787 Title: Screen sharing can not be enabled from the Gnome Control Center Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Ubuntu Version: Ubuntu Focal Fossa Package version: 1:3.36.1-1ubuntu4 Expected: Using Screen sharing as expected and often used before Result: Screen sharing is disabled and can't be reenabled I have checked the system logs and found this entry: gnome-control-c[223776]: couldn't list networks: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid service name 'vino-server' Then I have tried to reinstall the vino package in case that something broke in the update yesterday. This did not help so I tried executing the binary manually and this worked: /usr/lib/vino/vino-server 09/04/2020 10:16:55 Autoprobing TCP port in (all) network interface 09/04/2020 10:16:55 Listening IPv6://[::]:5900 09/04/2020 10:16:55 Listening IPv4://0.0.0.0:5900 09/04/2020 10:16:55 Autoprobing selected port 5900 09/04/2020 10:16:55 Advertising security type: 'TLS' (18) ... (shortened) The problem might be something related to DBus but I'm not shure. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 9 10:09:05 2020 InstallationDate: Installed on 2017-11-18 (872 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-04-03 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872230] [NEW] With any US international layout left Ctrl key does not work
Public bug reported: I am using 20.04 Focal. I am using a US international keyboard layout with dead keys, so that I can enter text in many different languages. After I had rebooted my system today and so loaded the newest GNOME Shell, the left Ctrl key stopped working in the terminal windows and also in emacs, while the right Ctrl still works. To get the left Ctrl working again I have to switch to a plain US English keyboard layout, without dead keys. I have also tried the different alternatives of US International keyboard layouts, each of them seems to work as intended but the left Ctrl key is not working. Only with plain US English layout I get the left Ctrl working. ** Affects: gnome-shell (Ubuntu) Importance: Critical Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872230 Title: With any US international layout left Ctrl key does not work Status in gnome-shell package in Ubuntu: New Bug description: I am using 20.04 Focal. I am using a US international keyboard layout with dead keys, so that I can enter text in many different languages. After I had rebooted my system today and so loaded the newest GNOME Shell, the left Ctrl key stopped working in the terminal windows and also in emacs, while the right Ctrl still works. To get the left Ctrl working again I have to switch to a plain US English keyboard layout, without dead keys. I have also tried the different alternatives of US International keyboard layouts, each of them seems to work as intended but the left Ctrl key is not working. Only with plain US English layout I get the left Ctrl working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872192] Re: xserver-xorg-video-intel causes screen flickering in plasma on XPS 15 7590
You are so right, my apologies. This bug report can be discarded. In my efforts to get everything working on a new installation of Kubuntu over the past few days, I unknowingly enabled the Intel driver for XOrg. Unknowingly because: I assumed I was already using it. I put in a config snippet in /etc/X11/xorg.conf.d/20-intel.conf in a (failed) attempt to fix the screen brightness controls. This specifically links the PCI address and the intel drivers. I now removed that file, re-installed xserver-xorg-video-intel package and no flickering. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1872192 Title: xserver-xorg-video-intel causes screen flickering in plasma on XPS 15 7590 Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: I have been experiencing screen flickering related to the compositor in KDE / Plasma on Ubuntu 19.10 on my Dell XPS 15 7590 laptop. I found the same problem + a solution here: https://www.reddit.com/r/kde/comments/f7itw4/plasma_flickering_neonkubuntu/ It turns out that even though I do have Intel chip (IGP on Core i7-9775H) using the Intel driver i915, the package xserver-xorg-video- intel doesn't seem to be required and does cause screen flickering. Removing this package as suggested on reddit fixes the flickering issue for me and so far I didn't seen any negative side effects - all 3D rendering still works. Either xorg-video-intel package should be solved to not cause flickering (and have effects where it is not needed) or it shouldn't be installed by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1872192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872222] [NEW] [WH-CH700N, playback] fails after a while
Public bug reported: Whether I'm watching something, or doing something else whilst listening to playback, the playback stops and starts intermittently. Only happens on Bluetooth, not on Aux. CPU/RAM usage not high when issue occurs. As well as this, my bluetooth driver is not supported out of the box, so had to download 3rd party firmware file. Firmware file from here: https://github.com/winterheart/broadcom-bt-firmware Was the only solution that worked, possibly defective? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1395 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 19:18:26 2020 InstallationDate: Installed on 2020-04-10 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: WH-CH700N Symptom_PulseAudioLog: Apr 11 18:52:45 tom-Laptop dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=122 pid=820 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 18:52:45 tom-Laptop dbus-daemon[641]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=122 pid=820 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 18:56:08 tom-Laptop systemd[803]: pulseaudio.service: Succeeded. Apr 11 18:56:18 tom-Laptop systemd[803]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [WH-CH700N, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name dmi.board.vendor: Type2 - Board Manufacturer dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.50:bd10/08/2014:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTUE-04L00VEN:rvnType2-BoardManufacturer:rnType2-BoardProductName:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.sku: INVALID dmi.product.version: PSKTUE-04L00VEN dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/187 Title: [WH-CH700N, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: Whether I'm watching something, or doing something else whilst listening to playback, the playback stops and starts intermittently. Only happens on Bluetooth, not on Aux. CPU/RAM usage not high when issue occurs. As well as this, my bluetooth driver is not supported out of the box, so had to download 3rd party firmware file. Firmware file from here: https://github.com/winterheart/broadcom-bt-firmware Was the only solution that worked, possibly defective? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1395 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 19:18:26 2020 InstallationDate: Installed on 2020-04-10 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: WH-CH700N Symptom_PulseAudioLog: Apr 11 18:52:45 tom-Laptop dbus-daemon[641]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=122 pid=820 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 18:52:45 tom-Laptop dbus-daemon[641]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=122 pid=820 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 18:56:08 tom-Laptop systemd[803]: pulseaudio.service: Succeeded. Apr 11 18:56:18 tom-Laptop systemd[803]:
[Desktop-packages] [Bug 1870975] Re: No audio devices appear except "Dummy Output" when I close my laptop lid while audio is playing and then open it back up.
I apologize; I meant pavucontrol said it was a dummy output as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1870975 Title: No audio devices appear except "Dummy Output" when I close my laptop lid while audio is playing and then open it back up. Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When I closed my laptop lid while sound was playing in Audacity and then opened the lid back up, the device woke up from sleep. However, my headphones were plugged in at the time, and Ubuntu acted as if the audio resumed. However, I was not hearing audio. So I went to the Audio section of Settings and found there was only one sound device: Dummy Device, instead of seeing the speakers built into the laptop and the headphones. Description: Ubuntu 18.04.4 LTS Release: 18.04 I am forced to reboot my machine as a workaround. gnome-control-center: Installed: 1:3.28.2-0ubuntu0.18.04.6 Candidate: 1:3.28.2-0ubuntu0.18.04.6 Version table: *** 1:3.28.2-0ubuntu0.18.04.6 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.28.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 ProcVersionSignature: Ubuntu 5.3.0-45.37~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 Date: Sun Apr 5 15:00:42 2020 InstallationDate: Installed on 2020-04-04 (1 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-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/1870975/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872221] [NEW] Updates installed snap-store snap and uninstalled ubuntu-software
Public bug reported: snap store app is also see thru (100% transparent) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Sat Apr 11 14:29:33 2020 InstallationDate: Installed on 2020-02-05 (66 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1872221 Title: Updates installed snap-store snap and uninstalled ubuntu-software Status in gnome-software package in Ubuntu: New Bug description: snap store app is also see thru (100% transparent) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Sat Apr 11 14:29:33 2020 InstallationDate: Installed on 2020-02-05 (66 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200204) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1872221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872224] [NEW] [Satellite L300, Realtek ALC268, Mic, Internal] Sound is distorted
Public bug reported: Hi My internal mic does not work properly ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: petardemirev 1217 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 21:28:21 2020 InstallationDate: Installed on 2020-02-16 (55 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed Symptom_Card: Вграден звук - HDA Intel Symptom_Jack: Mic, Internal Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [Satellite L300, Realtek ALC268, Mic, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd12/09/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLBGE-00T009G3:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite L300 dmi.product.sku: Montevina_Fab dmi.product.version: PSLBGE-00T009G3 dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1872224 Title: [Satellite L300, Realtek ALC268, Mic, Internal] Sound is distorted Status in alsa-driver package in Ubuntu: New Bug description: Hi My internal mic does not work properly ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: petardemirev 1217 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 21:28:21 2020 InstallationDate: Installed on 2020-02-16 (55 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel failed Symptom_Card: Вграден звук - HDA Intel Symptom_Jack: Mic, Internal Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [Satellite L300, Realtek ALC268, Mic, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd12/09/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLBGE-00T009G3:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Intel_Mobile dmi.product.name: Satellite L300 dmi.product.sku: Montevina_Fab dmi.product.version: PSLBGE-00T009G3 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1872224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872071] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1872071 Title: ibus-x11 crashed with SIGSEGV in __GI___poll() Status in ibus package in Ubuntu: Confirmed Bug description: This happened at start up after software updater requested a restart.I attached unattended-upgrades.log unattended-upgrades-dpkg.log dpkg.log to show what packages were installed before the restart. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 07:16:32 2020 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-03-14 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f6b2b2919f6 <__run_exit_handlers+198>: mov 0x10(%rax),%rdx PC (0x7f6b2b2919f6) ok source "0x10(%rax)" (0x1042f359537650) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: __GI___poll (fds=0x7f6af80067e0, nfds=3, timeout=1766) at ../sysdeps/unix/sysv/linux/poll.c:29 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ibus_main () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () Title: ibus-x11 crashed with SIGSEGV in __GI___poll() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872217] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()
*** This bug is a duplicate of bug 1872071 *** https://bugs.launchpad.net/bugs/1872071 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1872071, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872217/+attachment/5351993/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1872217/+attachment/5351995/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1872217/+attachment/5351998/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1872217/+attachment/5351999/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1872217/+attachment/5352000/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872217/+attachment/5352001/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872217/+attachment/5352002/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1872071 ibus-x11 crashed with SIGSEGV in __GI___poll() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1872217 Title: ibus-x11 crashed with SIGSEGV in __GI___poll() Status in ibus package in Ubuntu: New Bug description: Problema constantes de Ibus ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Apr 11 14:10:03 2020 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/libexec/ibus-x11 --kill-daemon ProcEnviron: LANG=es_VE.UTF-8 LANGUAGE=es_VE:es PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fc97abc69f6 <__run_exit_handlers+198>: mov 0x10(%rax),%rdx PC (0x7fc97abc69f6) ok source "0x10(%rax)" (0xb143e205ad8c0) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: __GI___poll (fds=0x55f25e1ac530, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ibus_main () from /lib/x86_64-linux-gnu/libibus-1.0.so.5 ?? () Title: ibus-x11 crashed with SIGSEGV in __GI___poll() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1872217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1860930] Re: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio
I haven't had this problem for some time now. Maybe there was an update that fixed it? However sometimes the sound volume controller in the top right corner is no associated with sound device being used. I mean when I change the volume or mute it nothing happens because it controls some other device not the one being used. -- 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/1860930 Title: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I have an Asus Zephyrus S GX531GX laptop and a pair of Asus Delta USB headphones. When the headphones are plugged in during boot the internal speakers won't work. There is only crackling sound coming from them. It doesn't help in I unplug the headphones. There is no problem if they are not plugged in during boot. I'm using Ubuntu 19.10. Please let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 26 19:26:35 2020 InstallationDate: Installed on 2019-12-19 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX531GXR.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX531GXR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX531GXR.304:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnZephyrusSGX531GXR_GX531GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX531GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus S dmi.product.name: Zephyrus S GX531GXR_GX531GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855938] Re: [nvidia] Screen freezes and only mouse moves
@vanvugt: I haven't described a crash in Chromium. But I have switched away from Chromium, the frequency of Gnome Shell freezes it induces being one of the reasons. Attached is a journal from a freeze that happened today, with Firefox and VirtualBox open (and some filebrowser/terminal windows). ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855938/+attachment/5351978/+files/prevboot.txt -- 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/1855938 Title: [nvidia] Screen freezes and only mouse moves Status in gnome-shell package in Ubuntu: Incomplete Bug description: The screen freezes but the mouse can be moved. SSH access works. This is on Legion Y545, Ubuntu 19.10 Nvidia Geforce 1660Ti Intel 9750h Symptoms: This only happens when: Nvidia-Prime is selected as "on-demand" And maybe most likely after the laptop comes out of sleep. xserver-xorg-video-intel is the latest :: 2:2.99.917+git20190815-1 If I choose prime-select "nvidia", this never happens. Makes me believe this has to do with intel video drivers. Error trace: GpuWatchdog[22171]: segfault at 0 ip 56163556379d sp 7fdeb6dd8480 error 6 in chrome[561631628000+717] Dec 10 14:43:57 Legion-Y545 kernel: [27680.533760] Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 29 61 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 11 6a a4 03 01 80 7d 8f 00 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Dec 10 15:01:38 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffc] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU116M [GeForce GTX 1660 Mobile] [17aa:3ffc] InstallationDate: Installed on 2019-10-23 (48 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 048d:c100 Integrated Technology Express, Inc. ITE Device(8910) Bus 001 Device 002: ID 13d3:56a6 IMC Networks Integrated Camera Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81Q6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=8155cfb7-305e-41c0-9d80-fdf15d29e196 ro acpi=force SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y545 dmi.modalias: dmi:bvnLENOVO:bvrBHCN33WW:bd10/10/2019:svnLENOVO:pn81Q6:pvrLegionY545:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545: dmi.product.family: Legion Y545 dmi.product.name: 81Q6 dmi.product.sku: LENOVO_MT_81Q6_BU_idea_FM_Legion Y545 dmi.product.version: Legion Y545 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Desktop-packages] [Bug 1872192] Re: xserver-xorg-video-intel causes screen flickering in plasma on XPS 15 7590
It doesn't matter if it's installed by default, you need to specifically configure X to use it. The default is modesetting_drv.so. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1872192 Title: xserver-xorg-video-intel causes screen flickering in plasma on XPS 15 7590 Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: I have been experiencing screen flickering related to the compositor in KDE / Plasma on Ubuntu 19.10 on my Dell XPS 15 7590 laptop. I found the same problem + a solution here: https://www.reddit.com/r/kde/comments/f7itw4/plasma_flickering_neonkubuntu/ It turns out that even though I do have Intel chip (IGP on Core i7-9775H) using the Intel driver i915, the package xserver-xorg-video- intel doesn't seem to be required and does cause screen flickering. Removing this package as suggested on reddit fixes the flickering issue for me and so far I didn't seen any negative side effects - all 3D rendering still works. Either xorg-video-intel package should be solved to not cause flickering (and have effects where it is not needed) or it shouldn't be installed by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1872192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution
sync'd. please close this bug once libxml2 has been accepted
https://launchpad.net/ubuntu/focal/+queue?queue_state=1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/1869814
Title:
ubuntu-docs build failure - possible solution
Status in libxml2:
New
Status in libxml2 package in Ubuntu:
In Progress
Status in ubuntu-docs package in Ubuntu:
Fix Released
Bug description:
ubuntu-docs failed to build during the second Focal Fossa test
rebuild:
https://launchpad.net/ubuntu/+archive/test-
rebuild-20200327-focal/+build/18982738
It was itstool which failed to generate the localized zh_CN pages. If
dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
excluding the Chinese pages is apparently not an acceptable solution.
The itstool package in focal {build-,}depends on python3. I built
itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
built fine without modifications:
https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages
So the root cause seems to lie neither in ubuntu-docs nor itstool. I
would suspect that python3-libxml2 is buggy, but since itstool was
built against python2 in eoan, it's hard to tell if it's a regression.
Would building itstool against python2 be an acceptable workaround in
focal?
To manage notifications about this bug go to:
https://bugs.launchpad.net/libxml2/+bug/1869814/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872208] Re: gnome-control-center crashed with SIGSEGV in g_type_create_instance()
*** This bug is a duplicate of bug 1870737 *** https://bugs.launchpad.net/bugs/1870737 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1870737, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1872208/+attachment/5351938/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1872208/+attachment/5351940/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1872208/+attachment/5351944/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1872208/+attachment/5351945/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1872208/+attachment/5351946/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1872208/+attachment/5351947/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1872208/+attachment/5351948/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1870737 gnome-control-center crashed with SIGSEGV in get_renderer_from_helper() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1872208 Title: gnome-control-center crashed with SIGSEGV in g_type_create_instance() Status in gnome-control-center package in Ubuntu: New Bug description: Was trying to open Settings and it crashed. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 18:03:51 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7f5a3fbb6517 <__strlen_avx2+71>: vpcmpeqb (%rdi),%ymm0,%ymm1 PC (0x7f5a3fbb6517) ok source "(%rdi)" (0x0020) not located in a known VMA region (needed readable region)! destination "%ymm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () ?? () g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in g_type_create_instance() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872208/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872198] Re: perte pave numerique
** 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/1872198 Title: perte pave numerique Status in xorg package in Ubuntu: New Bug description: Hello I lost the use of the numeric keypad while it works in windows. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:17:54 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-46-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-47-generic, x86_64: installed ndiswrapper, 1.60, 5.3.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227c] InstallationDate: Installed on 2020-03-23 (18 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC MonitorsUser.xml: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic root=UUID=e42364f6-7faf-4750-be1d-6e44dd2b71f7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227C dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.57:bd11/09/2018:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227C:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.sku: J2U02EA#ABF dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872198] [NEW] perte pave numerique
You have been subscribed to a public bug: Hello I lost the use of the numeric keypad while it works in windows. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:17:54 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-46-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-47-generic, x86_64: installed ndiswrapper, 1.60, 5.3.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227c] InstallationDate: Installed on 2020-03-23 (18 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC MonitorsUser.xml: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic root=UUID=e42364f6-7faf-4750-be1d-6e44dd2b71f7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227C dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.57:bd11/09/2018:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227C:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.sku: J2U02EA#ABF dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- perte pave numerique https://bugs.launchpad.net/bugs/1872198 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 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
Same problem with Samsung Galaxy Book Flex 930QCG. The Samsung Galaxy Chromebook and Galaxy Book Flex look very similar, the sound chip should be the same, the Chromebook is open source and also uses the Linux kernel, can we refer to the Chromebook code? -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color
[Desktop-packages] [Bug 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298
Same problem with Samsung Galaxy Book Flex 930QCG. The Samsung Galaxy Chromebook and Galaxy Book Flex look very similar, the sound chip should be the same, the Chromebook is open source and also uses the Linux kernel, can we refer to the Chromebook code? -- 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/1834566 Title: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Unable to get system speakers working running 19.04. At max volume, sound is barely perceptible through headphones. Pavucontrol shows sounds is present, but no amount of adjustments makes a difference. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 3355 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 28 00:44:13 2019 InstallationDate: Installed on 2019-06-05 (22 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AHK.029.190425.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP930MBE-K04US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: Notebook 9 Series dmi.product.name: 930MBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK dmi.product.version: P02AHK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1085976] Re: Documentation has "FIXME" items that are unfixed
** Changed in: gtk+3.0 (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1085976 Title: Documentation has "FIXME" items that are unfixed Status in GTK+: Expired Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk+3.0 package in Debian: Fix Released Bug description: The Ubuntu package libgtk-3-doc supplies the items of interest... In the directory /usr/share/doc/libgtk-3-doc/gtk3 there are 3 files that contain FIXME content In that directory: # grep FIXME * GtkApplication.html:FIXME: MISSING XINCLUDE CONTENT GtkBuilder.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html: FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT # I am just starting with GTK+ and Glade, so having this instead of the first code sample in the gtk-getting-started page is a show-stopper. I suggest it's as urgent as documentation bugs get. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgtk-3-doc 3.4.2-0ubuntu0.5 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 Date: Mon Dec 3 05:59:17 2012 Dependencies: InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True PackageArchitecture: all SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1085976/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872201] [NEW] Gnome 3 dock "restarts" every 35 (or so) seconds. Causing massive IO overhead (text boxes pause, game fps drops).
Public bug reported: Added some gnome extensions, but this was always present. Maybe the multi monitor setup is at fault? Attached output is from running 'sudo strace -p' on gnome-shell. The whole FUTEX part in the middle is only observable during one of these "stutters". The parts before and after is just to show what "normally" is going on. I have no idea what any of this means. I hope this is somewhat useful. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.3-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 15:48:33 2020 InstallationDate: Installed on 2020-03-22 (20 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Output from strace during a "stutter"." https://bugs.launchpad.net/bugs/1872201/+attachment/5351910/+files/strace_gnome-shell.txt -- 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/1872201 Title: Gnome 3 dock "restarts" every 35 (or so) seconds. Causing massive IO overhead (text boxes pause, game fps drops). Status in mutter package in Ubuntu: New Bug description: Added some gnome extensions, but this was always present. Maybe the multi monitor setup is at fault? Attached output is from running 'sudo strace -p' on gnome-shell. The whole FUTEX part in the middle is only observable during one of these "stutters". The parts before and after is just to show what "normally" is going on. I have no idea what any of this means. I hope this is somewhat useful. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.3-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 15:48:33 2020 InstallationDate: Installed on 2020-03-22 (20 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1872201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871997] Re: The primary display will cause black screen when external 4K monitor is configured to flipped
** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871997/+attachment/5351890/+files/journal.log -- 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/1871997 Title: The primary display will cause black screen when external 4K monitor is configured to flipped Status in xorg package in Ubuntu: Incomplete Bug description: The primary (built-in) display will cause black screen when external 4K monitor is configured to flipped Steps to reproduce: 1. plug 4K monitor via HDMI 2. open gnome-control-center 3. select Displays -> Orientation -> Landscape (flipped) 4. apply 5. black screen on built-in displays The primary display can be recovered if HDMI cable is re-plugged again. Machine: Dell XPS 13 9380 (Intel Coffee Lake) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:24:13 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2020-04-07 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200405) MachineType: Dell Inc. XPS 13 9380 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-21-generic root=UUID=60712c21-4620-4018-821e-afb9a77f9ec8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.10.2 dmi.board.name: 0SSY11 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.10.2:bd01/15/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0SSY11:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1871997/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867462] Re: Desktop-icons extension runs, shows icons, even when disabled
** Summary changed: - Desktop icons extension does not work properly + Desktop-icons extension runs, shows icons, even when disabled ** Changed in: gnome-control-center (Ubuntu) Status: Invalid => Confirmed -- 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/1867462 Title: Desktop-icons extension runs, shows icons, even when disabled Status in gnome-control-center package in Ubuntu: Confirmed Bug description: First, I am unable to find any way of disabling/hiding desktop icons in Gnome settings. Is this intended behavior? Second, when using Gnome tweaks, there is currently no way of disabling/hiding desktop icons via the extension, clicking the settings button for it renders no result and disabling it will not hide desktop icons. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 20:23:41 2020 InstallationDate: Installed on 2020-03-06 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) 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/1867462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system
My privileges in custom group is in att screenshot I think I got the same bug years ago, and checked about this on a MacBookPro 13" 2011, and the same appeared about the groups, but I had no login problems!? Same usb-stick with (maybe an newer zsynk? still within the same day 20.04) Now I know why my wifi was buggy on the Mac, after screen was black. I'll check on my dell xps m1530 and check about groups/privileges. That one is more like clean install. ** Attachment added: "privileges" https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1240336/+attachment/5351889/+files/Screenshot%20from%202020-04-11%2014-51-59.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: After release upgrade, the user loses permissions for several basic actions in the system Status in gdm package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Status in lxdm package in Ubuntu: Triaged Status in policykit-desktop-privileges package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system
I experienced this 10. april and made a bugreport about login, #1872104. I lost my adm privileges and "was put" to a custom group, att screenshot ** Attachment added: "custom group" https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1240336/+attachment/5351888/+files/Screenshot%20from%202020-04-11%2014-53-05.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-desktop-privileges in Ubuntu. https://bugs.launchpad.net/bugs/1240336 Title: After release upgrade, the user loses permissions for several basic actions in the system Status in gdm package in Ubuntu: Triaged Status in lightdm package in Ubuntu: Triaged Status in lxdm package in Ubuntu: Triaged Status in policykit-desktop-privileges package in Ubuntu: Triaged Bug description: HOW TO REPRODUCE: - Upgrade Ubuntu to the next release. RESULT: - The user looses permissions for several basic actions in the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: policykit-desktop-privileges 0.16 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:20:55 2013 InstallationDate: Installed on 2013-10-09 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: policykit-desktop-privileges UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1240336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872192] [NEW] xserver-xorg-video-intel causes screen flickering in plasma on XPS 15 7590
Public bug reported: I have been experiencing screen flickering related to the compositor in KDE / Plasma on Ubuntu 19.10 on my Dell XPS 15 7590 laptop. I found the same problem + a solution here: https://www.reddit.com/r/kde/comments/f7itw4/plasma_flickering_neonkubuntu/ It turns out that even though I do have Intel chip (IGP on Core i7-9775H) using the Intel driver i915, the package xserver-xorg-video- intel doesn't seem to be required and does cause screen flickering. Removing this package as suggested on reddit fixes the flickering issue for me and so far I didn't seen any negative side effects - all 3D rendering still works. Either xorg-video-intel package should be solved to not cause flickering (and have effects where it is not needed) or it shouldn't be installed by default. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1872192 Title: xserver-xorg-video-intel causes screen flickering in plasma on XPS 15 7590 Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: I have been experiencing screen flickering related to the compositor in KDE / Plasma on Ubuntu 19.10 on my Dell XPS 15 7590 laptop. I found the same problem + a solution here: https://www.reddit.com/r/kde/comments/f7itw4/plasma_flickering_neonkubuntu/ It turns out that even though I do have Intel chip (IGP on Core i7-9775H) using the Intel driver i915, the package xserver-xorg-video- intel doesn't seem to be required and does cause screen flickering. Removing this package as suggested on reddit fixes the flickering issue for me and so far I didn't seen any negative side effects - all 3D rendering still works. Either xorg-video-intel package should be solved to not cause flickering (and have effects where it is not needed) or it shouldn't be installed by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1872192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819298] Re: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-commo
Affects Ubuntu 19.10 too. -- 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/1819298 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.116-0ubuntu0.18.10.1 Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: I tried to apply this driver and it provoked the bug ProblemType: Package DistroRelease: Ubuntu 18.10 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Sun Mar 10 01:46:53 2019 DuplicateSignature: package:nvidia-340:(not installed) Unpacking nvidia-340 (340.107-0ubuntu2) ... dpkg: error processing archive /var/cache/apt/archives/nvidia-340_340.107-0ubuntu2_amd64.deb (--unpack): trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.116-0ubuntu0.18.10.1 ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.116-0ubuntu0.18.10.1 InstallationDate: Installed on 2018-07-12 (240 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-kernel-common-390 390.116-0ubuntu0.18.10.1 UpgradeStatus: Upgraded to cosmic on 2019-03-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1819298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871358] Re: Dock shows on all displays even when you don't want it to (because all displays are the same model of monitor)
*** This bug is a duplicate of bug 1866088 *** https://bugs.launchpad.net/bugs/1866088 @Sebastien I tired to go a step further. I cloned the git repo for the gnome-shell-extension-ubuntu-dock. I found the line where the combobox listener triggers the change for the active monitor selection. I added the update to set the "multi-monitor" to "false" when the monitor selection index is "0". However I've have never done any development work with Ubuntu or Gnome Shell before so after performing a "make" and "make install" I have no idea how to install the extension update to try it out. So I will just leave it to the Ubuntu team. I'll have to see if I can find tutorials on gnome shell extension development for the future. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1871358 Title: Dock shows on all displays even when you don't want it to (because all displays are the same model of monitor) Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: In The Ubuntu Settings > Appearance there is a Dock option to "Show On" specific monitor. If there are multiple monitors and they are of the same brand/model number, the setting gets confused and always defaults to "All displays". > lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 GNOME 3.36.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1871358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1009766] Re: Clipboard not working in RemoteApps
Should be fixed in FreeRDP 2.0: https://github.com/FreeRDP/FreeRDP/pull/3934 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1009766 Title: Clipboard not working in RemoteApps Status in freerdp: New Status in remmina package in Ubuntu: Confirmed Bug description: I was excited today when I saw a Remmina update coming in. I checked the changelog and noticed it was a fix for clipboard support. But sadly the fix doesn't work when using remoteApps ... EDIT1: I think freerdp is the one that has the bug, here is the command I use: xfreerdp -z -a 32 -x l -g workarea --rfx --no-tls --disable-menu- animations --disable-wallpaper --fonts --gdi hw --app -u "$REMOTE_USER" -p "$REMOTE_PASS" --plugin rdpdr --data disk:home:"$HOME" disk:vfsroot:/ -- --plugin rail.so --data "$REMOTE_COMMAND":"$REMOTE_WORKING_DIR":"$REMOTE_COMMAND_ARGS" -- "$REMOTE_HOST" ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: remmina 1.0.0-1ubuntu6.1 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Thu Jun 7 08:55:55 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120316) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/freerdp/+bug/1009766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I'm HP Spectre x360 Linux amanah 5.3.0-46-generic #38~18.04.1-Ubuntu SMP Tue Mar 31 04:17:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [*] Laptop speakers work [ ] HDMI output does not work [ ] Internal microphone does not work [*] External microphone works -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870184] Re: Snap store not showing ubuntu repository apt apps inthe store
I'm having the same issue. I downloaded and installed the beta yesterday. When I opened the Snap Store to install Gimp, the apt repo version was listed... albeit concealed behind a blank field: https://i.imgur.com/eZAVN1x.png See the distribution channel pop-up in the top-right? The first two lines are snaps. The third, empty line, actually lead to the apt repo version. How could I know? I refreshed my snaps to update the Store, and now even the blank line is gone: https://i.imgur.com/nVEMMLg.png I understand that Canonical has its reasons to push snaps, but at that point that's confusing, in particular to new users. For example, a new user knows that Firefox is installed... but it's not listed as such in the Store, because the apt version isn't taken into account. That new user may then install Firefox twice by mistake. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1870184 Title: Snap store not showing ubuntu repository apt apps inthe store Status in snap-store: Confirmed Status in gnome-desktop package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: Invalid Bug description: OS : Ubuntu 20.04 (20200401) Problem : repository (apt) apps are not showing Problem Simulation: Install ubuntu 20.04 current daily build > open Snap Store> Search gnome tweak (or anyother apt apps) > no results Expected Solution: The Snap store should show repository apps or the gnome software should have installed by default. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1870184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872180] [NEW] Network printer does not print: cups-browsed
Public bug reported: On a new installed Ubuntu 20.04 daily, network printer is found but when file sent to print, job is blocked on print queue. Looking at the setting of the printer found message that maybe cups-browsed is not running. And, so found workaround to start it and prints finished successfully. I don't know if there is a way to make it automatic and handled transparently for Ubuntu user? Printer model HP DeskJet 3700 Thank you, Igor ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.27.3-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 12:13:22 2020 InstallationDate: Installed on 2020-04-01 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lpstat: device for HP_DeskJet_3700_series_6DEB51_: implicitclass://HP_DeskJet_3700_series_6DEB51_/ MachineType: LENOVO 20QTCTO1WW Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_DeskJet_3700_series_6DEB51_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_DeskJet_3700_series_6DEB51_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 SourcePackage: cups-filters UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1872180 Title: Network printer does not print: cups-browsed Status in cups-filters package in Ubuntu: New Bug description: On a new installed Ubuntu 20.04 daily, network printer is found but when file sent to print, job is blocked on print queue. Looking at the setting of the printer found message that maybe cups-browsed is not running. And, so found workaround to start it and prints finished successfully. I don't know if there is a way to make it automatic and handled transparently for Ubuntu user? Printer model HP DeskJet 3700 Thank you, Igor ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.27.3-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 12:13:22 2020 InstallationDate: Installed on 2020-04-01 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lpstat: device for HP_DeskJet_3700_series_6DEB51_: implicitclass://HP_DeskJet_3700_series_6DEB51_/ MachineType: LENOVO 20QTCTO1WW Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_DeskJet_3700_series_6DEB51_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_DeskJet_3700_series_6DEB51_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=f0159a4a-cd4b-48f7-8119-f697cb539ce5 ro quiet splash vt.handoff=7 SourcePackage: cups-filters UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1872180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Attachment added: "journalctl -b-1 > journal.txt" https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5351782/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 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.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872177] Re: Launcher animation initially does NOT work (20.04-X Server)
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/1872177 Title: Launcher animation initially does NOT work (20.04-X Server) Status in gnome-shell package in Ubuntu: Confirmed Bug description: OBSERVED: - Hit Super-A, Launcher Icons appear WITHOUT animation - Hit Super-A, Launcher Icons disappear with animation - Hit Super-A, Launcher Icons appear with animation - Hit Super-A, Launcher Icons disappear with animation - Hit Super (without A), User is taken back to desktop - Hit Super-A, Launcher Icons appear WITHOUT animation EXPECTED: Launcher icons flagged with should appear WITH animation but they do not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 10:49:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872176] [NEW] [MS-7B38, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] fails after a while
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 When I'm using certain applications, mostly games, the sound starts breaking randomly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rohan 2393 F pulseaudio /dev/snd/pcmC0D7p: rohan 2393 F...m pulseaudio /dev/snd/controlC1: rohan 2393 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 14:17:58 2020 InstallationDate: Installed on 2018-04-19 (722 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_PulseAudioLog: Apr 11 14:04:57 rohan-work dbus-daemon[884]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=126 pid=1920 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 14:04:58 rohan-work dbus-daemon[884]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=126 pid=1920 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 14:05:05 rohan-work systemd[1913]: pulseaudio.service: Succeeded. Apr 11 14:05:15 rohan-work systemd[1913]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [MS-7B38, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] fails after a while UpgradeStatus: Upgraded to focal on 2020-04-02 (8 days ago) dmi.bios.date: 12/02/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.GR dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M PRO-VD PLUS (MS-7B38) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.GR:bd12/02/2019:svnMicro-StarInternationalCo.,Ltd:pnMS-7B38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MPRO-VDPLUS(MS-7B38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B38 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1872176 Title: [MS-7B38, Nvidia GPU 51 HDMI/DP, Digital Out, HDMI] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 When I'm using certain applications, mostly games, the sound starts breaking randomly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rohan 2393 F pulseaudio /dev/snd/pcmC0D7p: rohan 2393 F...m pulseaudio /dev/snd/controlC1: rohan 2393 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 14:17:58 2020 InstallationDate: Installed on 2018-04-19 (722 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: GK208 HDMI/DP Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_PulseAudioLog: Apr 11 14:04:57 rohan-work dbus-daemon[884]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=126 pid=1920 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 14:04:58 rohan-work dbus-daemon[884]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.37' (uid=126 pid=1920 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Apr 11 14:05:05
[Desktop-packages] [Bug 1871913] Re: super key does not work with secondary keyboard layout
Hotkey not working also with russian layout (ubuntu 20.04 with all updates on today) -- 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/1871913 Title: super key does not work with secondary keyboard layout Status in gnome-shell package in Ubuntu: Confirmed Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872177] [NEW] Launcher animation initially does NOT work (20.04-X Server)
Public bug reported: OBSERVED: - Hit Super-A, Launcher Icons appear WITHOUT animation - Hit Super-A, Launcher Icons disappear with animation - Hit Super-A, Launcher Icons appear with animation - Hit Super-A, Launcher Icons disappear with animation - Hit Super (without A), User is taken back to desktop - Hit Super-A, Launcher Icons appear WITHOUT animation EXPECTED: Launcher icons flagged with should appear WITH animation but they do not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 10:49:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872177 Title: Launcher animation initially does NOT work (20.04-X Server) Status in gnome-shell package in Ubuntu: New Bug description: OBSERVED: - Hit Super-A, Launcher Icons appear WITHOUT animation - Hit Super-A, Launcher Icons disappear with animation - Hit Super-A, Launcher Icons appear with animation - Hit Super-A, Launcher Icons disappear with animation - Hit Super (without A), User is taken back to desktop - Hit Super-A, Launcher Icons appear WITHOUT animation EXPECTED: Launcher icons flagged with should appear WITH animation but they do not. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 10:49:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872177/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Attachment added: "journalctl -b0 > journal.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5351769/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 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.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected
** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1872159 Title: booting with splash hangs when external monitors are connected Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 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.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872164] Re: qhd (joined) via hdmi 1.4 not working
** 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/1872164 Title: qhd (joined) via hdmi 1.4 not working Status in xorg package in Ubuntu: New Bug description: bought a shiny new QHD screen and connected via hdmi it works in single screen mode and in mirror setup but joining/extending does not. it just stays black. don't know how to troubleshoot besides journal model is Philips 272B8Q resolution 2560 x 1440 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Apr 11 08:18:36 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.3.0-45-generic, x86_64: installed nvidia, 435.21, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0819] Subsystem: Dell GM108M [GeForce MX130] [1028:0819] InstallationDate: Installed on 2020-03-30 (11 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Latitude 5591 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=68c5a16c-e29b-4e94-b10c-a14954bc07f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0DVVG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872159] Re: booting with splash hangs when external monitors are connected
** 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/1872159 Title: booting with splash hangs when external monitors are connected Status in plymouth package in Ubuntu: New Status in xorg package in Ubuntu: New Bug description: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 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.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872164] [NEW] qhd (joined) via hdmi 1.4 not working
You have been subscribed to a public bug: bought a shiny new QHD screen and connected via hdmi it works in single screen mode and in mirror setup but joining/extending does not. it just stays black. don't know how to troubleshoot besides journal model is Philips 272B8Q resolution 2560 x 1440 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: GNOME Date: Sat Apr 11 08:18:36 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-42-generic, x86_64: installed nvidia, 435.21, 5.3.0-45-generic, x86_64: installed nvidia, 435.21, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0819] Subsystem: Dell GM108M [GeForce MX130] [1028:0819] InstallationDate: Installed on 2020-03-30 (11 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Latitude 5591 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=68c5a16c-e29b-4e94-b10c-a14954bc07f3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0DVVG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan performance ubuntu -- qhd (joined) via hdmi 1.4 not working https://bugs.launchpad.net/bugs/1872164 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 1872159] [NEW] booting with splash hangs when external monitors are connected
You have been subscribed to a public bug: I think this is a problem with the splash boot loader. I have installed 20.04 to this laptop. Clean install, not an upgrade. When booting from the install, the greeter screen is never reached if external monitors are connected at startup. I get the spinning ubuntu logo, and nothing more. I can not change to virtual terminals. In recovery mood, I can log in. I am used to having such problems with Nvidia graphics is involved, but this is not the case on this laptop. It has been happily running 18.04. External displays are recognised if they are connected after login. Also, when I edit /etc/default/grub so that it reads GRUB_CMDLINE_LINUX_DEFAULT="" (that is, splash disabled) it works fine with two external monitors attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 13:58:19 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-21-generic, x86_64: installed tp_smapi, 0.43, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:225d] InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 20L5S00F00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=/dev/mapper/myvg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET56W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L5S00F00 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.modalias: dmi:bvnLENOVO:bvrN24ET56W(1.31):bd02/19/2020:svnLENOVO:pn20L5S00F00:pvrThinkPadT480:rvnLENOVO:rn20L5S00F00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L5S00F00 dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- booting with splash hangs when external monitors are connected https://bugs.launchpad.net/bugs/1872159 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 1872101] Re: Can't start VNC server from Sharing window in Gnome
*** This bug is a duplicate of bug 1871787 *** https://bugs.launchpad.net/bugs/1871787 ** This bug has been marked a duplicate of bug 1871787 Screen sharing can not be enabled from the Gnome Control Center -- 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/1872101 Title: Can't start VNC server from Sharing window in Gnome Status in gnome-control-center package in Ubuntu: New Bug description: After upgrading to Focal, I'm (mostly) unable to start screen sharing from the Sharing window in Settings. Unfortunately it's "mostly", as I managed to do it a couple of times, unfortunately usually it's not possible. The toggle in the title bar of the window is inactive and doesn't flip. I can start all the other shares no problem (files, multimedia, ssh). Manually starting /usr/lib/vino/vino-server works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Apr 10 17:21:30 2020 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-12 (911 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171011) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-26 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1872101/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872162] [NEW] crash report fail to submit
Public bug reported: Since 2020-03-19, firefox crashed about 17 times (it did not crash 1,5 years before). Though, all crash reports failed to submit. My firefox crash report submit.log reads: [Mo 17 Dez 2018 00:14:42 CET] Crash report submitted successfully [Do 19 Mär 2020 00:06:24 CET] Crash report submission failed: Couldn't connect to server [Sa 21 Mär 2020 15:14:19 CET] Crash report submission failed: Couldn't connect to server [Di 24 Mär 2020 23:22:51 CET] Crash report submission failed: Couldn't connect to server [Mi 25 Mär 2020 14:22:41 CET] Crash report submission failed: Couldn't connect to server [Do 26 Mär 2020 17:40:46 CET] Crash report submission failed: Couldn't connect to server [Sa 28 Mär 2020 10:59:32 CET] Crash report submission failed: Couldn't connect to server [Mo 30 Mär 2020 01:03:56 CEST] Crash report submission failed: Couldn't connect to server [Mi 01 Apr 2020 16:01:11 CEST] Crash report submission failed: Couldn't connect to server [Do 02 Apr 2020 20:39:29 CEST] Crash report submission failed: Couldn't connect to server [Fr 03 Apr 2020 21:07:53 CEST] Crash report submission failed: Couldn't connect to server [So 05 Apr 2020 22:38:08 CEST] Crash report submission failed: Couldn't connect to server [Di 07 Apr 2020 21:40:43 CEST] Crash report submission failed: Couldn't connect to server [Mi 08 Apr 2020 13:05:39 CEST] Crash report submission failed: Couldn't connect to server [Mi 08 Apr 2020 20:16:28 CEST] Crash report submission failed: Couldn't connect to server [Mi 08 Apr 2020 22:27:58 CEST] Crash report submission failed: Couldn't connect to server [Do 09 Apr 2020 23:36:31 CEST] Crash report submission failed: Couldn't connect to server [Fr 10 Apr 2020 20:07:48 CEST] Crash report submission failed: Couldn't connect to server ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1872162 Title: crash report fail to submit Status in firefox package in Ubuntu: New Bug description: Since 2020-03-19, firefox crashed about 17 times (it did not crash 1,5 years before). Though, all crash reports failed to submit. My firefox crash report submit.log reads: [Mo 17 Dez 2018 00:14:42 CET] Crash report submitted successfully [Do 19 Mär 2020 00:06:24 CET] Crash report submission failed: Couldn't connect to server [Sa 21 Mär 2020 15:14:19 CET] Crash report submission failed: Couldn't connect to server [Di 24 Mär 2020 23:22:51 CET] Crash report submission failed: Couldn't connect to server [Mi 25 Mär 2020 14:22:41 CET] Crash report submission failed: Couldn't connect to server [Do 26 Mär 2020 17:40:46 CET] Crash report submission failed: Couldn't connect to server [Sa 28 Mär 2020 10:59:32 CET] Crash report submission failed: Couldn't connect to server [Mo 30 Mär 2020 01:03:56 CEST] Crash report submission failed: Couldn't connect to server [Mi 01 Apr 2020 16:01:11 CEST] Crash report submission failed: Couldn't connect to server [Do 02 Apr 2020 20:39:29 CEST] Crash report submission failed: Couldn't connect to server [Fr 03 Apr 2020 21:07:53 CEST] Crash report submission failed: Couldn't connect to server [So 05 Apr 2020 22:38:08 CEST] Crash report submission failed: Couldn't connect to server [Di 07 Apr 2020 21:40:43 CEST] Crash report submission failed: Couldn't connect to server [Mi 08 Apr 2020 13:05:39 CEST] Crash report submission failed: Couldn't connect to server [Mi 08 Apr 2020 20:16:28 CEST] Crash report submission failed: Couldn't connect to server [Mi 08 Apr 2020 22:27:58 CEST] Crash report submission failed: Couldn't connect to server [Do 09 Apr 2020 23:36:31 CEST] Crash report submission failed: Couldn't connect to server [Fr 10 Apr 2020 20:07:48 CEST] Crash report submission failed: Couldn't connect to server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872162/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
