[Desktop-packages] [Bug 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch
Still waiting to hear if 'jammy' will be getting this fix. Certainly not in 'proposed-updates'. -- 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/1970800 Title: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: If you click a calendar date in the bottom row of the top panel calendar, the backdrop shrinks and the dates overflow out of the backdrop boundaries. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .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 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 16:25:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD Graphics] [1462:129c] Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 1650 Mobile / Max-Q] [1462:129c] InstallationDate: Installed on 2022-04-22 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2019 dmi.bios.release: 1.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16S3IMS.108 dmi.board.asset.tag: Default string dmi.board.name: MS-16S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1: dmi.product.family: Prestige dmi.product.name: Prestige 15 A10SC dmi.product.sku: 16S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 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:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1019738] Re: FileZilla regularly freezes while downloading to an SMB share
Fixed in newer versions. An old issue. ** Changed in: filezilla Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1019738 Title: FileZilla regularly freezes while downloading to an SMB share Status in FileZilla: Fix Released Status in filezilla package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: Invalid Bug description: Hello, When transferring files from an FTP server (TLS or not) to an SMB share, Filezilla keeps freezing which leads down to very much slower transfers ... Looking at resources usage, the gvfs-smb process works hard (60% cpu usage on my I7) I don't have such an issue or any slowdown when using other apps over the same SMB shares. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: filezilla 3.5.3-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sun Jul 1 19:06:31 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: filezilla UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-02-23 (395 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Package: gvfs PackageArchitecture: amd64 ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-19-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-03-25 (0 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/filezilla/+bug/1019738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1019738] Re: FileZilla regularly freezes while downloading to an SMB share
I have tested this and because of age will mark it as fixed. Test machine(s): * Remote in London. * Ubuntu 22.04 laptop running filezilla. * Debian unstable VM server running samba. Connecting to remote and downloading files to samba server at: /run/user/1000/gvfs/ All was well and no speed issues. ** Changed in: filezilla Assignee: (unassigned) => Phil Wyett (kathenas) ** Changed in: filezilla (Ubuntu) Assignee: (unassigned) => Phil Wyett (kathenas) ** Changed in: gvfs (Ubuntu) Assignee: (unassigned) => Phil Wyett (kathenas) ** Changed in: gvfs (Ubuntu) Status: New => Invalid ** Changed in: filezilla (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1019738 Title: FileZilla regularly freezes while downloading to an SMB share Status in FileZilla: Fix Released Status in filezilla package in Ubuntu: Fix Released Status in gvfs package in Ubuntu: Invalid Bug description: Hello, When transferring files from an FTP server (TLS or not) to an SMB share, Filezilla keeps freezing which leads down to very much slower transfers ... Looking at resources usage, the gvfs-smb process works hard (60% cpu usage on my I7) I don't have such an issue or any slowdown when using other apps over the same SMB shares. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: filezilla 3.5.3-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sun Jul 1 19:06:31 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: filezilla UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-02-23 (395 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Package: gvfs PackageArchitecture: amd64 ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-19-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-03-25 (0 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/filezilla/+bug/1019738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1019738] Re: FileZilla regularly freezes while downloading to an SMB share
Is this issue still present or a concern? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1019738 Title: FileZilla regularly freezes while downloading to an SMB share Status in FileZilla: New Status in filezilla package in Ubuntu: New Status in gvfs package in Ubuntu: New Bug description: Hello, When transferring files from an FTP server (TLS or not) to an SMB share, Filezilla keeps freezing which leads down to very much slower transfers ... Looking at resources usage, the gvfs-smb process works hard (60% cpu usage on my I7) I don't have such an issue or any slowdown when using other apps over the same SMB shares. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: filezilla 3.5.3-1ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sun Jul 1 19:06:31 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: filezilla UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 14.04 EcryptfsInUse: Yes InstallationDate: Installed on 2013-02-23 (395 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) Package: gvfs PackageArchitecture: amd64 ProcEnviron: LANGUAGE=fr_FR TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Tags: trusty Uname: Linux 3.13.0-19-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-03-25 (0 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/filezilla/+bug/1019738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2044420] Re: gtkpod segfaults when attempting to display songs
This is likely to see little attention for the following reasons: * Not maintained/No viable upstream. * Remove Request (RM) is active in Debian. [1] This package is likely to be soon removed and I would advise looking for an alternative to it. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018855 ** Bug watch added: Debian Bug tracker #1018855 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018855 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2044420 Title: gtkpod segfaults when attempting to display songs Status in glib2.0 package in Ubuntu: New Status in gtkpod package in Ubuntu: New Status in glib2.0 source package in Mantic: New Status in gtkpod source package in Mantic: New Status in glib2.0 source package in Noble: New Status in gtkpod source package in Noble: New Bug description: Open gtkpod, and select your ipod from the list. If it has more than one screenfull of songs to display in the list, gtkpod will immediately segfault. I haven't found a workaround yet. Broken on Mantic, works on Lunar. Thread 1 "gtkpod" received signal SIGSEGV, Segmentation fault. __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 <_nl_global_locale>) at ../string/strxfrm_l.c:685 685 ../string/strxfrm_l.c: No such file or directory. (gdb) bt #0 __GI___wcsxfrm_l (dest=0x0, src=0x0, n=0, l=0x76fff5a0 <_nl_global_locale>) at ../string/strxfrm_l.c:685 #1 0x770c5a5e in g_utf8_collate_key () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x77f852ec in fuzzy_skip_prefix () at /lib/x86_64-linux-gnu/libgtkpod.so.1 #3 0x7fffa80980ca in ??? () at /usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so #4 0x7fffa80997fd in normal_sort_tab_page_add_track () at /usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so #5 0x7fffa8099526 in normal_sort_tab_page_add_track () at /usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so #6 0x7fffa809f196 in sorttab_display_select_playlist_cb () at /usr/lib/x86_64-linux-gnu/gtkpod/libsorttab_display.so #7 0x7718d130 in g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x771ba4ac in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x771ab9b1 in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x771abbd6 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x771abc93 in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #12 0x77f67e4b in gtkpod_set_current_playlist () at /lib/x86_64-linux-gnu/libgtkpod.so.1 #13 0x7fffa807cce0 in ??? () at /usr/lib/x86_64-linux-gnu/gtkpod/libplaylist_display.so #14 0x7708ba11 in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x770e746f in ??? () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7708c46f in g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x777f61ed in gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #18 0xea1f in main () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2044420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043609] Re: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK.
Time zones would be London. I used the first working AMD64 daily live ISO of yesterday 20231115.1 that I assume defaults to the new flutter based GUI installer. -- 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/2043609 Title: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. Status in gnome-control-center package in Ubuntu: Incomplete Bug description: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:45.0-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 18:17:48 2023 InstallationDate: Installed on 2023-11-15 (0 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231115.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= 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/2043609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043609] Re: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK.
Thanks I will report differently. An English->English UK install should be setting UK language and numerical etc. not United States. -- 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/2043609 Title: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. Status in gnome-control-center package in Ubuntu: Invalid Bug description: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:45.0-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 18:17:48 2023 InstallationDate: Installed on 2023-11-15 (0 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231115.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= 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/2043609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043609] Re: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK.
Shows as United States in 'Language Support'. See screenshot. ** Attachment added: "Issue in Language Support." https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2043609/+attachment/5719809/+files/Screenshot%20from%202023-11-15%2018-30-02.png -- 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/2043609 Title: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. Status in gnome-control-center package in Ubuntu: New Bug description: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:45.0-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 18:17:48 2023 InstallationDate: Installed on 2023-11-15 (0 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231115.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= 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/2043609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043609] [NEW] 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK.
Public bug reported: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:45.0-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 18:17:48 2023 InstallationDate: Installed on 2023-11-15 (0 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231115.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "Issue at hand." https://bugs.launchpad.net/bugs/2043609/+attachment/5719806/+files/Screenshot%20from%202023-11-15%2018-17-22.png -- 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/2043609 Title: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. Status in gnome-control-center package in Ubuntu: New Bug description: 24.04 install (UK keyboard) is showing United States in 'Your Account' section of control center when keyboard is UK. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:45.0-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 18:17:48 2023 InstallationDate: Installed on 2023-11-15 (0 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231115.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= 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/2043609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2043604] [NEW] Sidebar is not mnaually expandable to make directory names visiible.
Public bug reported: Sidebar is not manually expandable to make directory names visible. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 17:46:14 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2023-11-15 (0 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231115.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble wayland-session ** Attachment added: "Screenshot of issue." https://bugs.launchpad.net/bugs/2043604/+attachment/5719800/+files/Screenshot%20from%202023-11-15%2017-49-32.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2043604 Title: Sidebar is not mnaually expandable to make directory names visiible. Status in nautilus package in Ubuntu: New Bug description: Sidebar is not manually expandable to make directory names visible. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45~rc-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Wed Nov 15 17:46:14 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2023-11-15 (0 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231115.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2043604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch
This is a minor fix, can we have it backported to jammy? -- 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/1970800 Title: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Bug description: If you click a calendar date in the bottom row of the top panel calendar, the backdrop shrinks and the dates overflow out of the backdrop boundaries. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .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 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 28 16:25:17 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD Graphics] [1462:129c] Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 1650 Mobile / Max-Q] [1462:129c] InstallationDate: Installed on 2022-04-22 (6 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2019 dmi.bios.release: 1.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16S3IMS.108 dmi.board.asset.tag: Default string dmi.board.name: MS-16S3 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1: dmi.product.family: Prestige dmi.product.name: Prestige 15 A10SC dmi.product.sku: 16S3.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 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:21.1.3-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-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970800/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040077] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/2040077/+attachment/5712238/+files/monitors.xml.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/2040077 Title: Drop-down calendar not drawn correctly when clicking into next month. Status in gnome-shell package in Ubuntu: New Bug description: Drop-down calendar not drawn correctly when clicking into next month. See attached video of issue. === INFO === Ubuntu 22.04 - Up to date. Gnome desktop. Using Wayland. Intel Core i5-8265U. Mesa Intel® UHD Graphics 620 (WHL GT2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-01 (113 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Package: gnome-shell 42.9-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 RelatedPackageVersions: mutter-common 42.9-0ubuntu5 Tags: wayland-session jammy Uname: Linux 6.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040077] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2040077/+attachment/5712236/+files/ProcEnviron.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/2040077 Title: Drop-down calendar not drawn correctly when clicking into next month. Status in gnome-shell package in Ubuntu: New Bug description: Drop-down calendar not drawn correctly when clicking into next month. See attached video of issue. === INFO === Ubuntu 22.04 - Up to date. Gnome desktop. Using Wayland. Intel Core i5-8265U. Mesa Intel® UHD Graphics 620 (WHL GT2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-01 (113 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Package: gnome-shell 42.9-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 RelatedPackageVersions: mutter-common 42.9-0ubuntu5 Tags: wayland-session jammy Uname: Linux 6.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040077] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/2040077/+attachment/5712237/+files/ShellJournal.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/2040077 Title: Drop-down calendar not drawn correctly when clicking into next month. Status in gnome-shell package in Ubuntu: New Bug description: Drop-down calendar not drawn correctly when clicking into next month. See attached video of issue. === INFO === Ubuntu 22.04 - Up to date. Gnome desktop. Using Wayland. Intel Core i5-8265U. Mesa Intel® UHD Graphics 620 (WHL GT2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-01 (113 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Package: gnome-shell 42.9-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 RelatedPackageVersions: mutter-common 42.9-0ubuntu5 Tags: wayland-session jammy Uname: Linux 6.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040077] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2040077/+attachment/5712235/+files/ProcCpuinfoMinimal.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/2040077 Title: Drop-down calendar not drawn correctly when clicking into next month. Status in gnome-shell package in Ubuntu: New Bug description: Drop-down calendar not drawn correctly when clicking into next month. See attached video of issue. === INFO === Ubuntu 22.04 - Up to date. Gnome desktop. Using Wayland. Intel Core i5-8265U. Mesa Intel® UHD Graphics 620 (WHL GT2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-01 (113 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Package: gnome-shell 42.9-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 RelatedPackageVersions: mutter-common 42.9-0ubuntu5 Tags: wayland-session jammy Uname: Linux 6.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040077] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/2040077/+attachment/5712234/+files/GsettingsChanges.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/2040077 Title: Drop-down calendar not drawn correctly when clicking into next month. Status in gnome-shell package in Ubuntu: New Bug description: Drop-down calendar not drawn correctly when clicking into next month. See attached video of issue. === INFO === Ubuntu 22.04 - Up to date. Gnome desktop. Using Wayland. Intel Core i5-8265U. Mesa Intel® UHD Graphics 620 (WHL GT2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-01 (113 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Package: gnome-shell 42.9-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 RelatedPackageVersions: mutter-common 42.9-0ubuntu5 Tags: wayland-session jammy Uname: Linux 6.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040077] Re: Drop-down calendar not drawn correctly when clicking into next month.
apport information ** Tags added: apport-collected wayland-session ** Description changed: Drop-down calendar not drawn correctly when clicking into next month. See attached video of issue. === INFO === Ubuntu 22.04 - Up to date. Gnome desktop. Using Wayland. Intel Core i5-8265U. Mesa Intel® UHD Graphics 620 (WHL GT2). + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2023-07-01 (113 days ago) + InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) + Package: gnome-shell 42.9-0ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 + RelatedPackageVersions: mutter-common 42.9-0ubuntu5 + Tags: wayland-session jammy + Uname: Linux 6.2.0-35-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/2040077/+attachment/5712233/+files/Dependencies.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/2040077 Title: Drop-down calendar not drawn correctly when clicking into next month. Status in gnome-shell package in Ubuntu: New Bug description: Drop-down calendar not drawn correctly when clicking into next month. See attached video of issue. === INFO === Ubuntu 22.04 - Up to date. Gnome desktop. Using Wayland. Intel Core i5-8265U. Mesa Intel® UHD Graphics 620 (WHL GT2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-07-01 (113 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Package: gnome-shell 42.9-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16 RelatedPackageVersions: mutter-common 42.9-0ubuntu5 Tags: wayland-session jammy Uname: Linux 6.2.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2040077] [NEW] Drop-down calendar not drawn correctly when clicking into next month.
Public bug reported: Drop-down calendar not drawn correctly when clicking into next month. See attached video of issue. === INFO === Ubuntu 22.04 - Up to date. Gnome desktop. Using Wayland. Intel Core i5-8265U. Mesa Intel® UHD Graphics 620 (WHL GT2). ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: jammy ** Attachment added: "Calendar draw issue." https://bugs.launchpad.net/bugs/2040077/+attachment/5712118/+files/Screencast%20from%2021-10-23%2023%3A05%3A58.webm -- 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/2040077 Title: Drop-down calendar not drawn correctly when clicking into next month. Status in gnome-shell package in Ubuntu: New Bug description: Drop-down calendar not drawn correctly when clicking into next month. See attached video of issue. === INFO === Ubuntu 22.04 - Up to date. Gnome desktop. Using Wayland. Intel Core i5-8265U. Mesa Intel® UHD Graphics 620 (WHL GT2). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040077/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2037907] Re: No package 'nss' found
You are trying to build an upstream release tarball, this is not supported. You can have many other non distro supplied packages installed. How can anyone tell, thus unsupported. When reporting bugs on Ubuntu, be sure to specify the version you are working on. Be verbose but concise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/2037907 Title: No package 'nss' found Status in poppler package in Ubuntu: Invalid Bug description: Have installed poppler on several systems, but experience issues in some cases. All the dependencies should be installed! Distro: Debian Bullseye 11 # apt-get install libopenjp2-7-dev libfreetype6-dev libfontconfig1-dev libjpeg-dev libtiff5-dev # cd /var/bin && wget https://poppler.freedesktop.org/poppler-23.09.0.tar.xz && tar -xvf poppler-23.09.0.tar.xz # cd poppler-23.09.0 && mkdir build && cd build # cmake .. CMake Warning at CMakeLists.txt:95 (message): No test data found in $testdatadir. You will not be able to run 'make test' successfully. The test data is not included in the source packages and is also not part of the main git repository. Instead, you can checkout the test data from its own git repository with: git clone git://git.freedesktop.org/git/poppler/test You should checkout the test data as a sibling of your poppler source folder or specify the location of your checkout with -DTESTDATADIR=/path/to/checkoutdir/test. -- Checking for module 'nss>=3.49' -- No package 'nss' found -- Could NOT find NSS3 (missing: NSS3_LIBRARIES NSS3_CFLAGS) CMake Warning at cmake/modules/MacroOptionalFindPackage.cmake:32 (find_package): By not providing "FindGpgmepp.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Gpgmepp", but CMake did not find one. Could not find a package configuration file provided by "Gpgmepp" (requested version 1.19) with any of the following names: GpgmeppConfig.cmake gpgmepp-config.cmake Add the installation prefix of "Gpgmepp" to CMAKE_PREFIX_PATH or set "Gpgmepp_DIR" to a directory containing one of the above files. If "Gpgmepp" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:158 (macro_optional_find_package) CMake Warning at CMakeLists.txt:198 (find_package): By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Core", but CMake did not find one. Could not find a package configuration file provided by "Qt5Core" (requested version 5.12) with any of the following names: Qt5CoreConfig.cmake qt5core-config.cmake Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set "Qt5Core_DIR" to a directory containing one of the above files. If "Qt5Core" provides a separate development package or SDK, be sure it has been installed. CMake Warning at CMakeLists.txt:199 (find_package): By not providing "FindQt5Gui.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Gui", but CMake did not find one. Could not find a package configuration file provided by "Qt5Gui" with any of the following names: Qt5GuiConfig.cmake qt5gui-config.cmake Add the installation prefix of "Qt5Gui" to CMAKE_PREFIX_PATH or set "Qt5Gui_DIR" to a directory containing one of the above files. If "Qt5Gui" provides a separate development package or SDK, be sure it has been installed. CMake Warning at CMakeLists.txt:200 (find_package): By not providing "FindQt5Xml.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Xml", but CMake did not find one. Could not find a package configuration file provided by "Qt5Xml" with any of the following names: Qt5XmlConfig.cmake qt5xml-config.cmake Add the installation prefix of "Qt5Xml" to CMAKE_PREFIX_PATH or set "Qt5Xml_DIR" to a directory containing one of the above files. If "Qt5Xml" provides a separate development package or SDK, be sure it has been installed. CMake Warning at CMakeLists.txt:201 (find_package): By not providing "FindQt5Widgets.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Widgets", but CMake did not find one. Could not find a package configuration file provided by "Qt5Widgets" with any of the following names: Qt5WidgetsConfig.cmake qt5widgets-config.cmake Add the installation prefix of "Qt5Widgets" to CMAKE_PREFIX_PATH or set "Qt5Widgets_DIR" to a
[Desktop-packages] [Bug 2037907] Re: No package 'nss' found
You state distro as Debian 11 (bullseye), so you need to be making bug reports on the Debian bug tracker. https://www.debian.org/Bugs/ Note: You are trying to build out of distro upstream packages that are not supported by Debian. This is not supported. ** Changed in: poppler (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/2037907 Title: No package 'nss' found Status in poppler package in Ubuntu: Invalid Bug description: Have installed poppler on several systems, but experience issues in some cases. All the dependencies should be installed! Distro: Debian Bullseye 11 # apt-get install libopenjp2-7-dev libfreetype6-dev libfontconfig1-dev libjpeg-dev libtiff5-dev # cd /var/bin && wget https://poppler.freedesktop.org/poppler-23.09.0.tar.xz && tar -xvf poppler-23.09.0.tar.xz # cd poppler-23.09.0 && mkdir build && cd build # cmake .. CMake Warning at CMakeLists.txt:95 (message): No test data found in $testdatadir. You will not be able to run 'make test' successfully. The test data is not included in the source packages and is also not part of the main git repository. Instead, you can checkout the test data from its own git repository with: git clone git://git.freedesktop.org/git/poppler/test You should checkout the test data as a sibling of your poppler source folder or specify the location of your checkout with -DTESTDATADIR=/path/to/checkoutdir/test. -- Checking for module 'nss>=3.49' -- No package 'nss' found -- Could NOT find NSS3 (missing: NSS3_LIBRARIES NSS3_CFLAGS) CMake Warning at cmake/modules/MacroOptionalFindPackage.cmake:32 (find_package): By not providing "FindGpgmepp.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Gpgmepp", but CMake did not find one. Could not find a package configuration file provided by "Gpgmepp" (requested version 1.19) with any of the following names: GpgmeppConfig.cmake gpgmepp-config.cmake Add the installation prefix of "Gpgmepp" to CMAKE_PREFIX_PATH or set "Gpgmepp_DIR" to a directory containing one of the above files. If "Gpgmepp" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:158 (macro_optional_find_package) CMake Warning at CMakeLists.txt:198 (find_package): By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Core", but CMake did not find one. Could not find a package configuration file provided by "Qt5Core" (requested version 5.12) with any of the following names: Qt5CoreConfig.cmake qt5core-config.cmake Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set "Qt5Core_DIR" to a directory containing one of the above files. If "Qt5Core" provides a separate development package or SDK, be sure it has been installed. CMake Warning at CMakeLists.txt:199 (find_package): By not providing "FindQt5Gui.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Gui", but CMake did not find one. Could not find a package configuration file provided by "Qt5Gui" with any of the following names: Qt5GuiConfig.cmake qt5gui-config.cmake Add the installation prefix of "Qt5Gui" to CMAKE_PREFIX_PATH or set "Qt5Gui_DIR" to a directory containing one of the above files. If "Qt5Gui" provides a separate development package or SDK, be sure it has been installed. CMake Warning at CMakeLists.txt:200 (find_package): By not providing "FindQt5Xml.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Xml", but CMake did not find one. Could not find a package configuration file provided by "Qt5Xml" with any of the following names: Qt5XmlConfig.cmake qt5xml-config.cmake Add the installation prefix of "Qt5Xml" to CMAKE_PREFIX_PATH or set "Qt5Xml_DIR" to a directory containing one of the above files. If "Qt5Xml" provides a separate development package or SDK, be sure it has been installed. CMake Warning at CMakeLists.txt:201 (find_package): By not providing "FindQt5Widgets.cmake" in CMAKE_MODULE_PATH this project has asked CMake to find a package configuration file provided by "Qt5Widgets", but CMake did not find one. Could not find a package configuration file provided by "Qt5Widgets" with any of the following names: Qt5WidgetsConfig.cmake qt5widgets-config.cmake Add the installation prefix of "Qt5Widgets" to CMAKE_PREFIX_PATH
[Desktop-packages] [Bug 2036298] Re: jammy: nautilus sidebar will not accept left mouse click actions in sidebar.
** Summary changed: - jammy: nautilus sidebat will not accept left mouse click actions in sidebar. + jammy: nautilus sidebar will not accept left mouse click actions in sidebar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2036298 Title: jammy: nautilus sidebar will not accept left mouse click actions in sidebar. Status in nautilus package in Ubuntu: New Bug description: jammy: nautilus sidebar will not accept left mouse click actions after long uptime. Happens on occasion during normal use. DE is running on wayland. See attached video for visual of issue. Disabling and re-enabling the sidebar does nothing. Nautilus needs to be shutdown and restarted to return to normal operation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2036298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2036298] [NEW] jammy: nautilus sidebat will not accept left mouse click actions in sidebar.
Public bug reported: jammy: nautilus sidebar will not accept left mouse click actions after long uptime. Happens on occasion during normal use. DE is running on wayland. See attached video for visual of issue. Disabling and re-enabling the sidebar does nothing. Nautilus needs to be shutdown and restarted to return to normal operation. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Visual of issue" https://bugs.launchpad.net/bugs/2036298/+attachment/5701397/+files/Screencast%20from%2016-09-23%2003%3A44%3A18.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2036298 Title: jammy: nautilus sidebat will not accept left mouse click actions in sidebar. Status in nautilus package in Ubuntu: New Bug description: jammy: nautilus sidebar will not accept left mouse click actions after long uptime. Happens on occasion during normal use. DE is running on wayland. See attached video for visual of issue. Disabling and re-enabling the sidebar does nothing. Nautilus needs to be shutdown and restarted to return to normal operation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2036298/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025531] Re: file-roller crashed with signal 5 in g_object_new_valist()
Triggered for me in 23.10 during routine system updates. Problem on two 23.10 VMs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/2025531 Title: file-roller crashed with signal 5 in g_object_new_valist() Status in file-roller package in Ubuntu: Incomplete Bug description: While edubuntu-mantic parallel installing kubuntu kde-desktop ubuntucinnamon-desktop: E: /tmp/apt-dpkg-install-iBrOhl/518-kubuntu-settings- desktop_1%3a23.04.5_all.deb: »/etc/skel/.face« tried to override because of desktop-base 12.0.6ubuntu1 ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: file-roller 43.0-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 1 14:35:45 2023 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2023-07-01 (0 days ago) InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230629) ProcCmdline: /usr/bin/file-roller --service ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 5 SourcePackage: file-roller StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () 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 g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: file-roller crashed with signal 5 in g_object_new_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: My solution in synaptic was: uninstall kubuntu-desktop and kubuntu-settings-desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/2025531/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2035143] [NEW] Jammy: 'Appearance' icon not fully visible when not highlighted.
Public bug reported: Jammy: 'Appearance' icon not fully visible when not highlighted. See attached video for visual of issue. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "visual of issue" https://bugs.launchpad.net/bugs/2035143/+attachment/5700042/+files/Screencast%20from%2011-09-23%2021%3A12%3A26.webm -- 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/2035143 Title: Jammy: 'Appearance' icon not fully visible when not highlighted. Status in gnome-control-center package in Ubuntu: New Bug description: Jammy: 'Appearance' icon not fully visible when not highlighted. See attached video for visual of issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2035143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2033658] [NEW] Mantic: 'Ubuntu Desktop' section has no titlebar.
Public bug reported: Mantic: 'Ubuntu Desktop' section has no titlebar. Also no 'minimize', 'maximize' or 'close' icons. See attached screenshot. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Ubuntu Desktop section, no titlebar." https://bugs.launchpad.net/bugs/2033658/+attachment/5696830/+files/Screenshot%20from%202023-08-31%2014-52-51.png -- 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/2033658 Title: Mantic: 'Ubuntu Desktop' section has no titlebar. Status in gnome-control-center package in Ubuntu: New Bug description: Mantic: 'Ubuntu Desktop' section has no titlebar. Also no 'minimize', 'maximize' or 'close' icons. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2033658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2028525] [NEW] Evolution mail received section indicator icon hard to see under dark.
Public bug reported: Evolution mail received section indicator icon hard to see under dark. See series of attached screenshots. Under dark, the hard to see grey circle icon could maybe replaced with an easier to see green or similar coloured icon for visibility. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Attachment added: "screenshot_01.png" https://bugs.launchpad.net/bugs/2028525/+attachment/5688038/+files/screenshot_01.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/2028525 Title: Evolution mail received section indicator icon hard to see under dark. Status in yaru-theme package in Ubuntu: New Bug description: Evolution mail received section indicator icon hard to see under dark. See series of attached screenshots. Under dark, the hard to see grey circle icon could maybe replaced with an easier to see green or similar coloured icon for visibility. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2028525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017677] Re: Unable to drag window by title bar
*** This bug is a duplicate of bug 2013216 *** https://bugs.launchpad.net/bugs/2013216 ** This bug has been marked a duplicate of bug 2013216 Single click on title bar does not transfer focus to target window (server side decorations in Xorg sessions) -- 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/2017677 Title: Unable to drag window by title bar Status in xorg package in Ubuntu: New Bug description: >lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 Intermittent - more often than not this works fine. However, sometimes unable to move window by left-click & drag on the title bar. Not sure what exact conditions are, maybe when alt-tabbing to a different window or when moving onto a different monitor. Upgraded to 23.04 late yesterday and it's happened about 4 times so far today.When it doesn't work - the dragged window just stays still, but relocating the mouse to lower on the window (say the menu bar) resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 25 15:48:44 2023 DistUpgraded: 2023-04-24 20:50:34,905 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:1413] InstallationDate: Installed on 2021-12-13 (498 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Entroware Apollo ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=943b6cc2-9015-4dda-8079-67ac161950f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-24 (0 days ago) dmi.bios.date: 03/26/2018 dmi.bios.release: 5.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02E dmi.board.asset.tag: Tag 12345 dmi.board.name: Apollo dmi.board.vendor: Entroware dmi.board.version: EL02R5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Entroware dmi.chassis.version: N/A dmi.ec.firmware.release: 5.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02E:bd03/26/2018:br5.2:efr5.2:svnEntroware:pnApollo:pvrEL02R5:rvnEntroware:rnApollo:rvrEL02R5:cvnEntroware:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Apollo dmi.product.sku: Not Applicable dmi.product.version: EL02R5 dmi.sys.vendor: Entroware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2017677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017677] Re: Unable to drag window by title bar
This bug doesn't just affect window movement (dragging), it also fails to properly select the window, so that it doesn't become the foreground window -- 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/2017677 Title: Unable to drag window by title bar Status in xorg package in Ubuntu: New Bug description: >lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 Intermittent - more often than not this works fine. However, sometimes unable to move window by left-click & drag on the title bar. Not sure what exact conditions are, maybe when alt-tabbing to a different window or when moving onto a different monitor. Upgraded to 23.04 late yesterday and it's happened about 4 times so far today.When it doesn't work - the dragged window just stays still, but relocating the mouse to lower on the window (say the menu bar) resolves the problem. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 25 15:48:44 2023 DistUpgraded: 2023-04-24 20:50:34,905 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer UHD Graphics 620 [1558:1413] InstallationDate: Installed on 2021-12-13 (498 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 04f2:b649 Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Entroware Apollo ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=943b6cc2-9015-4dda-8079-67ac161950f9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-24 (0 days ago) dmi.bios.date: 03/26/2018 dmi.bios.release: 5.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02E dmi.board.asset.tag: Tag 12345 dmi.board.name: Apollo dmi.board.vendor: Entroware dmi.board.version: EL02R5 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Entroware dmi.chassis.version: N/A dmi.ec.firmware.release: 5.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02E:bd03/26/2018:br5.2:efr5.2:svnEntroware:pnApollo:pvrEL02R5:rvnEntroware:rnApollo:rvrEL02R5:cvnEntroware:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: Apollo dmi.product.sku: Not Applicable dmi.product.version: EL02R5 dmi.sys.vendor: Entroware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2017677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987291] [NEW] Statistics are not always updated
Public bug reported: Using Bristol as an example, if the "Close" option is selected in the "Congratulations" dialog at the end of a win, or if the "Close" option is selected in the "There are no more moves" at the end of a loss, the statistics in ~/.config/gnome-games/aisleriot are left unchanged. In previous versions, if the game window was closed with a game in progress, the statistics would be updated with a loss. In this version, the statistics are unchanged. Source package: aisleriot (1:3.22.22-1) Release: jammy (22.04LTS) ** Affects: aisleriot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to aisleriot in Ubuntu. https://bugs.launchpad.net/bugs/1987291 Title: Statistics are not always updated Status in aisleriot package in Ubuntu: New Bug description: Using Bristol as an example, if the "Close" option is selected in the "Congratulations" dialog at the end of a win, or if the "Close" option is selected in the "There are no more moves" at the end of a loss, the statistics in ~/.config/gnome-games/aisleriot are left unchanged. In previous versions, if the game window was closed with a game in progress, the statistics would be updated with a loss. In this version, the statistics are unchanged. Source package: aisleriot (1:3.22.22-1) Release: jammy (22.04LTS) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aisleriot/+bug/1987291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976554] Re: Screen auto rotates randomly after suspend
I detected the screen is also rotating after suspend if you *lock* screen rotation. This is even more annoying, cause the screen rotations does not revert into its current position. Machine is a X1 Yoga 5th Gen -- 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/1976554 Title: [Lenovo X1 Yoga 5th Gen] Screen auto rotates randomly after suspend Status in mutter package in Ubuntu: New Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-30 (707 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: mutter 42.0-3ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-22 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976554] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1976554/+attachment/5595558/+files/ProcCpuinfoMinimal.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/1976554 Title: Screen auto rotates randomly after suspend Status in mutter package in Ubuntu: Incomplete Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-30 (707 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: mutter 42.0-3ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-22 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976554] Re: Screen auto rotates randomly after suspend
apport information ** Tags added: apport-collected ** Description changed: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2020-06-30 (707 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: mutter 42.0-3ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/usr/bin/zsh + ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 + Tags: jammy + Uname: Linux 5.15.0-33-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-22 (46 days ago) + UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1976554/+attachment/5595557/+files/Dependencies.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/1976554 Title: Screen auto rotates randomly after suspend Status in mutter package in Ubuntu: Incomplete Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-06-30 (707 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: mutter 42.0-3ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-22 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976554] [NEW] Screen auto rotates randomly after suspend
Public bug reported: Description:Ubuntu 22.04 LTS Release:22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1976554 Title: Screen auto rotates randomly after suspend Status in mutter package in Ubuntu: New Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 iio-sensor-proxy: 3.3-0ubuntu6 mutter: 42.0-3ubuntu2 Since update to Ubuntu 22.04: If i leave screen rotation in GNOME enabled and come back form suspend mode (open/close Laptop) the screen is rotated wrong. Mostly 90 degrees left from normal view axis. Expected behaviour: The screen should not rotate until logged in again or there should be a delay before choosing an new rotation whilst laptop is opened. Same problem seems to be present in older iio-sensor-proxy versions. Mabye affected to Mutter and or iio-sensor-proxy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957103] Re: Evince 41.3 large pdf can't be viewed at 100%
Errata: 4/ Try to view it at 100%, it won't on my external HDMI screen limited to 43.5% -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1957103 Title: Evince 41.3 large pdf can't be viewed at 100% Status in evince package in Ubuntu: New Bug description: OS: Manjaro XFCE 21.2.1 (latest) Evince 41.3 REPRODUCE: 1/ In a browser open https://www.sncf-reseau.com/fr/carte/carte-reseau-ferre-en-france 2/ Download & save 7Mb pdf "Télécharger la carte du réseau ferré en France (PDF - 7 Mo)" which URL is: https://www.sncf-reseau.com/sites/default/files/2020-06/CARTE%20RFN%202020_WEB_0.pdf 3/ Open this pdf with Evince 4/ Try to view it at 100M, it won't on my external HDMI screen limited to 43.5% Thanks for fixing it. inxi -F System: Host: xf-512 Kernel: 5.15.12-1-MANJARO x86_64 bits: 64 Desktop: Xfce 4.16.0 Distro: Manjaro Linux Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel Device-2: Chicony TOSHIBA Web Camera - HD type: USB driver: uvcvideo Display: x11 server: X.Org 1.21.1.2 driver: loaded: modesetting resolution: 1920x1080~60Hz Message: Unable to show advanced data. Required tool glxinfo missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1957103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957103] [NEW] Evince 41.3 large pdf can't be viewed at 100%
Public bug reported: OS: Manjaro XFCE 21.2.1 (latest) Evince 41.3 REPRODUCE: 1/ In a browser open https://www.sncf-reseau.com/fr/carte/carte-reseau-ferre-en-france 2/ Download & save 7Mb pdf "Télécharger la carte du réseau ferré en France (PDF - 7 Mo)" which URL is: https://www.sncf-reseau.com/sites/default/files/2020-06/CARTE%20RFN%202020_WEB_0.pdf 3/ Open this pdf with Evince 4/ Try to view it at 100M, it won't on my external HDMI screen limited to 43.5% Thanks for fixing it. inxi -F System: Host: xf-512 Kernel: 5.15.12-1-MANJARO x86_64 bits: 64 Desktop: Xfce 4.16.0 Distro: Manjaro Linux Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel Device-2: Chicony TOSHIBA Web Camera - HD type: USB driver: uvcvideo Display: x11 server: X.Org 1.21.1.2 driver: loaded: modesetting resolution: 1920x1080~60Hz Message: Unable to show advanced data. Required tool glxinfo missing. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1957103 Title: Evince 41.3 large pdf can't be viewed at 100% Status in evince package in Ubuntu: New Bug description: OS: Manjaro XFCE 21.2.1 (latest) Evince 41.3 REPRODUCE: 1/ In a browser open https://www.sncf-reseau.com/fr/carte/carte-reseau-ferre-en-france 2/ Download & save 7Mb pdf "Télécharger la carte du réseau ferré en France (PDF - 7 Mo)" which URL is: https://www.sncf-reseau.com/sites/default/files/2020-06/CARTE%20RFN%202020_WEB_0.pdf 3/ Open this pdf with Evince 4/ Try to view it at 100M, it won't on my external HDMI screen limited to 43.5% Thanks for fixing it. inxi -F System: Host: xf-512 Kernel: 5.15.12-1-MANJARO x86_64 bits: 64 Desktop: Xfce 4.16.0 Distro: Manjaro Linux Graphics: Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics driver: i915 v: kernel Device-2: Chicony TOSHIBA Web Camera - HD type: USB driver: uvcvideo Display: x11 server: X.Org 1.21.1.2 driver: loaded: modesetting resolution: 1920x1080~60Hz Message: Unable to show advanced data. Required tool glxinfo missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1957103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904789] Re: [snap] Cannot confirm security exception for invalid certificate
Same here, cannot use the snap version because of this :/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1904789 Title: [snap] Cannot confirm security exception for invalid certificate Status in thunderbird package in Ubuntu: Confirmed Bug description: Note: This bug is specific to the Snap version of Thunderbird, I can't reproduce it with the Ubuntu-packaged version for example (which I have installed on Ubuntu, used for multiple years and stopped using recently to get the more recent versions of TB available with Snap). When a certificate problem arrises with a server from which Thunderbird tries to retrieve emails, the "Add Security Exception" window gives you the option to "Confirm Security Exception" (meaning that Thunderbird will overlook the invalid certificate). The problem is that nothing happens when I click the "Confirm Security Exception" button. I've tried the usual workarounds, including removing the email account and adding it again, to no avail. The peculiar thing here is that I have had certificate problems before, when using a non-snap version of Thunderbird, and clicking the "Confirm Security Exception" button has always worked. Not with the Snap version it seems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1904789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
I'm seeing the same thing after the recent update to Thunderbird 78.11. Ubuntu 21.04 on Wayland. x11 is ok. In my case it appears to be related to the Reminder dialogue opening. Some more details: Start Thunderbird and make sure the Reminder dialogue does not open (eg by snoozing any reminders in a previous session). Open a few emails in new windows - everything works as normal. Now set a calendar entry for a few minutes and wait for the reminder dialogue to pop up. Icon on dock shows indicator showing two open window Open an email in a new window Icon on dock shows indicator showing three open windows Close email Icon on dock still shows indicator showing three open windows Icon on dock is now unresponsive to left click. Right-click shows the menu listing all the windows you have opened, but is unresponsive and stays on the screen. It goes if you press "Super" twice. Then switch to Thunderbird using Alt-tab Repeat until more than 4 windows have been opened - icon show the maximum 4 indicators. Close Thunderbird using Quit from the menu (ps shows no running Thunderbird processes) Dock still shows icon with 4 indicators Left or right click no longer does anything. A middle-click starts a new instance of Thunderbird. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" do not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1932328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925056] [NEW] Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel 5.6.0-1048-oem
Public bug reported: Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts to hang and finally freezes when I want to connect to my AV-receiver over bluetooth. There is something funky going on in the kernel, hence I attached the dmesg kernel messages since system boot. All consecutive versions > 5.6.0-1048-oem show the same behaviour, hence I'm still booting 5.6.0-1047-oem currently. I tried the 5.4 kernel series and the latest one (5.4.0-72-generic) was also working fine. The only HW change I did to my Dell XPS 13 9380 was changing my SSD to a bigger Samsung SSD 970 EVO Plus 1TB, everything is as I ordered it. I read about bluetooth vulnerability fixes in exactly the version where the problem started here: https://ubuntu.com/security/notices/USN-4752-1 Maybe that has something to do with the issue? Can somebody reproduce this issue? lsb_release -rd ``` Description:Ubuntu 20.04.2 LTS Release:20.04 ``` ** Affects: linux-meta-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Tags: 9380 bluetooth crash dell xps ** Attachment added: "dmesg output" https://bugs.launchpad.net/bugs/1925056/+attachment/5489843/+files/bluetooth_crash_dmesg.txt ** Package changed: gnome-shell (Ubuntu) => linux-meta-oem-5.6 (Ubuntu) -- 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/1925056 Title: Dell XPS 13 9380 - System hangs when connecting bluetooth since kernel 5.6.0-1048-oem Status in linux-meta-oem-5.6 package in Ubuntu: New Bug description: Since the kernel upgrade to 5.6.0-1048-oem my Dell XPS 13 9380 starts to hang and finally freezes when I want to connect to my AV-receiver over bluetooth. There is something funky going on in the kernel, hence I attached the dmesg kernel messages since system boot. All consecutive versions > 5.6.0-1048-oem show the same behaviour, hence I'm still booting 5.6.0-1047-oem currently. I tried the 5.4 kernel series and the latest one (5.4.0-72-generic) was also working fine. The only HW change I did to my Dell XPS 13 9380 was changing my SSD to a bigger Samsung SSD 970 EVO Plus 1TB, everything is as I ordered it. I read about bluetooth vulnerability fixes in exactly the version where the problem started here: https://ubuntu.com/security/notices/USN-4752-1 Maybe that has something to do with the issue? Can somebody reproduce this issue? lsb_release -rd ``` Description: Ubuntu 20.04.2 LTS Release: 20.04 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-5.6/+bug/1925056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824282] Re: Add a mode that load nvidia.ko only so that we display on intel and do cuda deep learning in NV GPU
The commit referenced here is super useful: https://code.launchpad.net/~ycheng-twn/junk/+git/nvidia- prime/+ref/ubuntu/devel However, what made it into Focal is super different - it uses nvidia to drive the display but enables power management via a udev rule. That is *also* useful, but it's not the same at all. It would be useful to get the feature that was implemented here actually released. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1824282 Title: Add a mode that load nvidia.ko only so that we display on intel and do cuda deep learning in NV GPU Status in nvidia-prime package in Ubuntu: Fix Released Bug description: Per current NV and intel GPU driver, if we load nvidia.ko only, we can do display on intel GPU and leave the NV to deep learning for a graphic workstation. I proposed to add a mode might call "intel+nv_cuda" for this mode. Test procedure: 1. install the new package on a platform with both intel and NV graphic card. 2. $ sudo prime-select intel+nv_cuda; sudo reboot 3. $ nvidia-smi # it will show the nvidia GPU status and we will found that no GUI process use any NV GPU memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1824282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
I can also confirm that after installing libmutter-7-0 from groovy- proposed, 3 snaps that wouldn't run before now run (chromium, keepassxc, vlc). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: In Progress Status in mutter package in Ubuntu: In Progress Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Committed Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: In Progress Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
@Daniel, is it possible to add a repo for this fix early ahead of coming down in the release repos? On the release repos I have the latest version. mutter is already the newest version (3.36.4-0ubuntu0.20.04.2). Cheers for any advice -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Triaged Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1890843] Re: Freeze
Hi Daniel, Just for your information I installed the Nvidia version 440 driver $ sudo nvidia-smi Mon Aug 10 14:02:14 2020 +-+ | NVIDIA-SMI 440.100 Driver Version: 440.100 CUDA Version: 10.2 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce GTX 950 Off | :82:00.0 On | N/A | | 11% 64CP030W / 110W | 1220MiB / 2000MiB | 8% Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0 10459 G /usr/lib/xorg/Xorg 71MiB | |0 10959 G /usr/bin/gnome-shell 47MiB | |0 13605 G /usr/lib/xorg/Xorg 771MiB | |0 13727 G /usr/bin/gnome-shell 193MiB | |0 15399 G ...CAA= --shared-files 63MiB | +-+ So far things booted up fine. Since this was an intermittent (albeit often) issue, it will take a few days of my use to fully evaluate. I'll keep you posted. Thanks, Phil On Sun, Aug 9, 2020 at 11:03 PM phil marsh wrote: > Will do and thanks again for your help! > > On Sun, Aug 9, 2020, 10:45 PM Daniel van Vugt <1890...@bugs.launchpad.net> > wrote: > >> Yes please do try Nvidia driver 440. And certainly don't upgrade the >> whole OS unless you can afford the time and risk. >> >> If the problem persists then please run the commands in comment #4. And >> come to think of it, please also check /var/crash for any crash files. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1890843 >> >> Title: >> Freeze >> >> Status in gnome-shell package in Ubuntu: >> Incomplete >> >> Bug description: >> I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug: >> 1. double left mouse click on launcher icon on left toolbar (usually >> happens with Chromium Browser icon) >> 2. Desired result: Drop down menu appears with options to open Chromium >> browser >> 3. Actual result when bug appears: Drop down menu appears then whole >> desktop freezes. No further mouseclicks on display work. Dropdown menu >> remains frozen on display. >> 4. Current workaround: >> When bug appears, the desktop can be unfrozen via cntl-alt-del keys >> but the drop-down menu remains frozen in place. Next, the frozen drop-down >> menu can now be closed by clicking on the "Activities" menu on the >> upper-left corner of the desktop and then clicking on the icon with the >> frozen drop-down menu. These actions close the frozen drop-down menu and >> restore normal operation of the Gnome III for a while until the bug pops up >> again. This bug has become especially common now rendering the desktop >> almost unusable and I'm thinking of replacing Gnome III due to this. >> Thanks, Phil >> >> ProblemType: Bug >> DistroRelease: Ubuntu 18.04 >> Package: xorg 1:7.7+19ubuntu7.1 >> ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 >> Uname: Linux 4.15.0-112-generic x86_64 >> NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair >> nvidia_modeset nvidia >> .proc.driver.nvidia.gpus..82.00.0: Error: [Errno 21] Is a >> directory: '/proc/driver/nvidia/gpus/:82:00.0' >> .proc.driver.nvidia.registry: Binary: "" >> .proc.driver.nvidia.version: >>NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 >> 01:01:53 PDT 2020 >>GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) >> ApportVersion: 2.20.9-0ubuntu7.16 >> Architecture: amd64 >> BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' >> CompizPlugins: No value set for >> `/apps/compiz-1/general/screen0/options/active_plugins' >> CompositorRunning: None >> CurrentDesktop: ubuntu:GNOME >> Date: Fri Aug 7 12:37:36 2020 >> DistUpgraded: Fresh install >> DistroCodename: bionic >> DistroVariant: ubuntu >&
Re: [Desktop-packages] [Bug 1890843] Re: Freeze
Will do and thanks again for your help! On Sun, Aug 9, 2020, 10:45 PM Daniel van Vugt <1890...@bugs.launchpad.net> wrote: > Yes please do try Nvidia driver 440. And certainly don't upgrade the > whole OS unless you can afford the time and risk. > > If the problem persists then please run the commands in comment #4. And > come to think of it, please also check /var/crash for any crash files. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1890843 > > Title: > Freeze > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug: > 1. double left mouse click on launcher icon on left toolbar (usually > happens with Chromium Browser icon) > 2. Desired result: Drop down menu appears with options to open Chromium > browser > 3. Actual result when bug appears: Drop down menu appears then whole > desktop freezes. No further mouseclicks on display work. Dropdown menu > remains frozen on display. > 4. Current workaround: > When bug appears, the desktop can be unfrozen via cntl-alt-del keys but > the drop-down menu remains frozen in place. Next, the frozen drop-down menu > can now be closed by clicking on the "Activities" menu on the upper-left > corner of the desktop and then clicking on the icon with the frozen > drop-down menu. These actions close the frozen drop-down menu and restore > normal operation of the Gnome III for a while until the bug pops up again. > This bug has become especially common now rendering the desktop almost > unusable and I'm thinking of replacing Gnome III due to this. > Thanks, Phil > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 > Uname: Linux 4.15.0-112-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > nvidia_modeset nvidia > .proc.driver.nvidia.gpus..82.00.0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/gpus/:82:00.0' > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 > 01:01:53 PDT 2020 >GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) > ApportVersion: 2.20.9-0ubuntu7.16 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Aug 7 12:37:36 2020 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GpuHangFrequency: Several times a week > GpuHangReproducibility: Seems to happen randomly > GpuHangStarted: Immediately after installing this version of Ubuntu > GraphicsCard: >NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2951] > InstallationDate: Installed on 2018-06-01 (798 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > MachineType: Supermicro X9DR3-F > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic > root=UUID=89151cf5-98dc-43fa-9046-917fe8211331 ro quiet splash vt.handoff=1 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/31/2013 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 3.0a > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: X9DR3-F > dmi.board.vendor: Supermicro > dmi.board.version: 0123456789 > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Supermicro > dmi.chassis.version: 0123456789 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd07/31/2013:svnSupermicro:pnX9DR3-F:pvr0123456789:rvnSupermicro:rnX9DR3-F:rvr0123456789:cvnSupermicro:ct3:cvr0123456789: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: X9DR3-F > dmi.product.version: 0123456789 > dmi.sys.vendor: Supermicro > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.101-2~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0u
Re: [Desktop-packages] [Bug 1890843] Re: Freeze
Hi Daniel, Thanks so much for your email and for your efforts looking into this for me! The idea of upgrading to 20.04 is well-taken but involves substantial effort to bring up my servers. Therefore, I will first try upgrading my Nvidia to say libnvidia-cfg1-440 and libnvidia-common-440 etc because these are the latest Nvidia packages as listed in my Synaptic app on Ubuntu 18.04? Does that make sense? I will back up my OS prior as I alway maintain a nightly backup of my OS via ZFS snapshots. Thanks again and best, Phil On Sun, Aug 9, 2020 at 7:40 PM Daniel van Vugt <1890...@bugs.launchpad.net> wrote: > We also recommend upgrading to Ubuntu 20.04 if you can. It seems to have > fewer issues than 18.04 still does. Although we do try to provide fixes > for both, some fixes will go under the radar and only appear in newer > versions. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1890843 > > Title: > Freeze > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug: > 1. double left mouse click on launcher icon on left toolbar (usually > happens with Chromium Browser icon) > 2. Desired result: Drop down menu appears with options to open Chromium > browser > 3. Actual result when bug appears: Drop down menu appears then whole > desktop freezes. No further mouseclicks on display work. Dropdown menu > remains frozen on display. > 4. Current workaround: > When bug appears, the desktop can be unfrozen via cntl-alt-del keys but > the drop-down menu remains frozen in place. Next, the frozen drop-down menu > can now be closed by clicking on the "Activities" menu on the upper-left > corner of the desktop and then clicking on the icon with the frozen > drop-down menu. These actions close the frozen drop-down menu and restore > normal operation of the Gnome III for a while until the bug pops up again. > This bug has become especially common now rendering the desktop almost > unusable and I'm thinking of replacing Gnome III due to this. > Thanks, Phil > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 > Uname: Linux 4.15.0-112-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > nvidia_modeset nvidia > .proc.driver.nvidia.gpus..82.00.0: Error: [Errno 21] Is a directory: > '/proc/driver/nvidia/gpus/:82:00.0' > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 > 01:01:53 PDT 2020 >GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) > ApportVersion: 2.20.9-0ubuntu7.16 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Fri Aug 7 12:37:36 2020 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GpuHangFrequency: Several times a week > GpuHangReproducibility: Seems to happen randomly > GpuHangStarted: Immediately after installing this version of Ubuntu > GraphicsCard: >NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2951] > InstallationDate: Installed on 2018-06-01 (798 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > MachineType: Supermicro X9DR3-F > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic > root=UUID=89151cf5-98dc-43fa-9046-917fe8211331 ro quiet splash vt.handoff=1 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/31/2013 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 3.0a > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: X9DR3-F > dmi.board.vendor: Supermicro > dmi.board.version: 0123456789 > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Supermicro > dmi.chassis.version: 0123456789 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd07/31/2013:svnSupermicro:pnX9DR3-F:pvr0123
[Desktop-packages] [Bug 1890843] [NEW] Xorg freeze
Public bug reported: I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug: 1. double left mouse click on launcher icon on left toolbar (usually happens with Chromium Browser icon) 2. Desired result: Drop down menu appears with options to open Chromium browser 3. Actual result when bug appears: Drop down menu appears then whole desktop freezes. No further mouseclicks on display work. Dropdown menu remains frozen on display. 4. Current workaround: When bug appears, the desktop can be unfrozen via cntl-alt-del keys but the drop-down menu remains frozen in place. Next, the frozen drop-down menu can now be closed by clicking on the "Activities" menu on the upper-left corner of the desktop and then clicking on the icon with the frozen drop-down menu. These actions close the frozen drop-down menu and restore normal operation of the Gnome III for a while until the bug pops up again. This bug has become especially common now rendering the desktop almost unusable and I'm thinking of replacing Gnome III due to this. Thanks, Phil ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..82.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:82:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Aug 7 12:37:36 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 950] [10de:1402] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GM206 [GeForce GTX 950] [3842:2951] InstallationDate: Installed on 2018-06-01 (798 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Supermicro X9DR3-F ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=89151cf5-98dc-43fa-9046-917fe8211331 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0a dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DR3-F dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0a:bd07/31/2013:svnSupermicro:pnX9DR3-F:pvr0123456789:rvnSupermicro:rnX9DR3-F:rvr0123456789:cvnSupermicro:ct3:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: X9DR3-F dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1890843 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I am running Ubuntu 18.04 64 bit with Gnome III. Action to see bug: 1. double left mouse click on launcher icon on left toolbar (usually happens with Chromium Browser icon) 2. Desired result: Drop down menu appears with options to open Chromium browser 3. Actual result when bug appears: Drop down menu appears then whole desktop freezes. No further mouseclicks on display work. Dropdown menu r
[Desktop-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
Found in a post on Reddit, a workaround that worked for me via GUI. Even though this is still a bug I wanted to help this workaround get more exposure. ``` Just installed 20.04. Same issue. But i have a workaround that doesn't involve manual settings with xrandr. If i set them so that all monitors align at the bottom, it works as expected. This makes for a bit of wonky cursor movement screen-to- screen, but it's usable for now until it gets fixed. Something about the nvdidia driver seems to not be able to map the position to any other configuration. It does not work if for me if I align them all at the top, only with them all aligned at the bottom. Source: https://www.reddit.com/r/pop_os/comments/g7pwq8/multimonitor_screen_rotation_not_working_in_2004/ ``` -- 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/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Invalid Status in mutter source package in Focal: In Progress Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 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.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A
[Desktop-packages] [Bug 1879751] Re: ALSA sees my intel soundcards but pulseaudio does not. Error is : "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1
Thank you, but didn't help. "debuild" and plain old make failed: ... CCLD alsa-mixer-path-test /usr/bin/ld: ./.libs/libalsa-util.so: undefined reference to `snd_use_case_parse_ctl_elem_id' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:6955: alsa-mixer-path-test] Error 1 make[3]: Leaving directory '/root/DEV/pulseaudio-13.99.1/src' make[2]: *** [Makefile:5401: all] Error 2 make[2]: Leaving directory '/root/DEV/pulseaudio-13.99.1/src' make[1]: *** [Makefile:833: all-recursive] Error 1 make[1]: Leaving directory '/root/DEV/pulseaudio-13.99.1' make: *** [Makefile:648: all] Error 2 # ~/DEV/pulseaudio-13.99.1# dpkg -l | grep libasound ii libasound2:amd64 1.2.2-2.1 amd64shared library for ALSA applications ii libasound2:i3861.2.2-2.1 i386 shared library for ALSA applications ii libasound2-data1.2.2-2.1 all Configuration files and profiles for ALSA drivers ii libasound2-dev:amd64 1.2.2-2.1 amd64shared library for ALSA applications -- development files ii libasound2-plugins:amd64 1.2.2-1ubuntu1 amd64ALSA library additional plugins rc libasound2-plugins:i3861.2.2-1ubuntu1 i386 ALSA library additional plugins -- 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/1879751 Title: ALSA sees my intel soundcards but pulseaudio does not. Error is : "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa- card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9" Status in pulseaudio package in Ubuntu: Incomplete Bug description: ALSA sees my intel soundcards but pulseaudio does not. 'pavucontrol' sees only a "Dummy" device. #journalctl|grep pulse' gives "pulseaudio[18489]: Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9" Making pulseaudio from source fixes the problem/ (Linux CF-C2CQAZXCM 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux 20.04) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 20 12:48:07 2020 InstallationDate: Installed on 2015-04-29 (1848 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-05 (15 days ago) dmi.bios.date: 09/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.00L21 dmi.board.asset.tag: No Asset Tag dmi.board.name: CFC2-2 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.00L21:bd09/12/2018:svnPanasonicCorporation:pnCF-C2CQAZXCM:pvr002:rvnPanasonicCorporation:rnCFC2-2:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CFC2-2 dmi.product.name: CF-C2CQAZXCM dmi.product.sku: CF-C2CQAZXCM dmi.product.version: 002 dmi.sys.vendor: Panasonic Corporation mtime.conffile..etc.init.d.apport: 2020-02-26T22:18:45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879751] Re: ALSA sees my intel soundcards but pulseaudio does not. Error is : "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1
I purged and installed jackd1 I never had but then installed jackd I never had but then installed timidity Rebooted and still only the dummy device and #journalctl |grep pulseaudio Failed to open module "module-alsa-card". May 21 13:47:15 CF-C2CQAZXCM pulseaudio[3849]: Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9 alsamixer sees the cards __END__ -- 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/1879751 Title: ALSA sees my intel soundcards but pulseaudio does not. Error is : "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa- card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9" Status in pulseaudio package in Ubuntu: Incomplete Bug description: ALSA sees my intel soundcards but pulseaudio does not. 'pavucontrol' sees only a "Dummy" device. #journalctl|grep pulse' gives "pulseaudio[18489]: Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9" Making pulseaudio from source fixes the problem/ (Linux CF-C2CQAZXCM 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux 20.04) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 20 12:48:07 2020 InstallationDate: Installed on 2015-04-29 (1848 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-05 (15 days ago) dmi.bios.date: 09/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.00L21 dmi.board.asset.tag: No Asset Tag dmi.board.name: CFC2-2 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.00L21:bd09/12/2018:svnPanasonicCorporation:pnCF-C2CQAZXCM:pvr002:rvnPanasonicCorporation:rnCFC2-2:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CFC2-2 dmi.product.name: CF-C2CQAZXCM dmi.product.sku: CF-C2CQAZXCM dmi.product.version: 002 dmi.sys.vendor: Panasonic Corporation mtime.conffile..etc.init.d.apport: 2020-02-26T22:18:45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1879751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1879751] [NEW] ALSA sees my intel soundcards but pulseaudio does not. Error is : "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99
Public bug reported: ALSA sees my intel soundcards but pulseaudio does not. 'pavucontrol' sees only a "Dummy" device. #journalctl|grep pulse' gives "pulseaudio[18489]: Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9" Making pulseaudio from source fixes the problem/ (Linux CF-C2CQAZXCM 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux 20.04) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 20 12:48:07 2020 InstallationDate: Installed on 2015-04-29 (1848 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/tcsh SourcePackage: pulseaudio UpgradeStatus: Upgraded to focal on 2020-05-05 (15 days ago) dmi.bios.date: 09/12/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.00L21 dmi.board.asset.tag: No Asset Tag dmi.board.name: CFC2-2 dmi.board.vendor: Panasonic Corporation dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Panasonic Corporation dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.00L21:bd09/12/2018:svnPanasonicCorporation:pnCF-C2CQAZXCM:pvr002:rvnPanasonicCorporation:rnCFC2-2:rvr1:cvnPanasonicCorporation:ct10:cvr001: dmi.product.family: CFC2-2 dmi.product.name: CF-C2CQAZXCM dmi.product.sku: CF-C2CQAZXCM dmi.product.version: 002 dmi.sys.vendor: Panasonic Corporation mtime.conffile..etc.init.d.apport: 2020-02-26T22:18:45 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - ALSA sees my intel soundcards but pulseaudio does not. 'journalctl|grep pulse' gives "pulseaudio[18489]: Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9" Making pulseaudio from source fixes the problem/ + ALSA sees my intel soundcards but pulseaudio does not. Error is : "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9" -- 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/1879751 Title: ALSA sees my intel soundcards but pulseaudio does not. Error is : "Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa- card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9" Status in pulseaudio package in Ubuntu: New Bug description: ALSA sees my intel soundcards but pulseaudio does not. 'pavucontrol' sees only a "Dummy" device. #journalctl|grep pulse' gives "pulseaudio[18489]: Failed to open module /usr/lib/pulse-13.99.1/modules/module-alsa-card.so: /usr/lib/pulse-13.99.1/modules/libalsa-util.so: undefined symbol: snd_use_case_parse_ctl_elem_id, version ALSA_0.9" Making pulseaudio from source fixes the problem/ (Linux CF-C2CQAZXCM 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux 20.04) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: GNOME-Flashback:GNOME Date: Wed May 20 12:48:07 2020 InstallationDate: Installed on 2015-04-29 (1848 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) ProcEnviron:
Re: [Desktop-packages] [Bug 1868782] Re: PCI/internal sound card not detected "dummy output"
*** This bug is a duplicate of bug 1864061 *** https://bugs.launchpad.net/bugs/1864061 Thank you Hui Wang for your help. >Please add "options snd-hda-intel dmic_detect=0" in the /etc/modprobe.d/alsa-base.conf, then the legacy hda driver will work as before. I can confirm, this solved both the sound problem as well as suspend problem. Peace, Phil On 3/24/20 6:52 PM, Hui Wang wrote: > *** This bug is a duplicate of bug 1864061 *** > https://bugs.launchpad.net/bugs/1864061 > > Please try 5.3.0-43 kernel. > > > ** This bug has been marked a duplicate of bug 1864061 > PCI/internal sound card not detected -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1868782 Title: PCI/internal sound card not detected "dummy output" Status in alsa-driver package in Ubuntu: New Bug description: On 22 March, 2020 I ran the latest update as requested by the computer. After rebooting, as requested, I no longer have sound & the only sound output is "Dummy Output". No sound card is detected but i have a Multimedia Audio Controller Intel Corp Device 9dc8(rev30) installed. After running Ubuntu-bug in terminal I get: ProblemType: Bug DistroRelease: Ubuntu 18.04.4 Package: alsa-base 1.0.25+dfsg-Oubuntu5 Apport Version: 2.20.9-Obuntu7.12 Manufacturer: Acer Product Name: Swift SF314-56 Product Version: V1.10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 11:25:53 2020 InstallationDate: Installed on 2019-09-18 (188 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd02/22/2019:svnAcer:pnSwiftSF314-56:pvrV1.10:rvnWL:rnStrongbow_WL:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868782] [NEW] PCI/internal sound card not detected "dummy output"
Public bug reported: On 22 March, 2020 I ran the latest update as requested by the computer. After rebooting, as requested, I no longer have sound & the only sound output is "Dummy Output". No sound card is detected but i have a Multimedia Audio Controller Intel Corp Device 9dc8(rev30) installed. After running Ubuntu-bug in terminal I get: ProblemType: Bug DistroRelease: Ubuntu 18.04.4 Package: alsa-base 1.0.25+dfsg-Oubuntu5 Apport Version: 2.20.9-Obuntu7.12 Manufacturer: Acer Product Name: Swift SF314-56 Product Version: V1.10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 11:25:53 2020 InstallationDate: Installed on 2019-09-18 (188 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd02/22/2019:svnAcer:pnSwiftSF314-56:pvrV1.10:rvnWL:rnStrongbow_WL:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer ** 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/1868782 Title: PCI/internal sound card not detected "dummy output" Status in alsa-driver package in Ubuntu: New Bug description: On 22 March, 2020 I ran the latest update as requested by the computer. After rebooting, as requested, I no longer have sound & the only sound output is "Dummy Output". No sound card is detected but i have a Multimedia Audio Controller Intel Corp Device 9dc8(rev30) installed. After running Ubuntu-bug in terminal I get: ProblemType: Bug DistroRelease: Ubuntu 18.04.4 Package: alsa-base 1.0.25+dfsg-Oubuntu5 Apport Version: 2.20.9-Obuntu7.12 Manufacturer: Acer Product Name: Swift SF314-56 Product Version: V1.10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Mar 24 11:25:53 2020 InstallationDate: Installed on 2019-09-18 (188 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.name: Strongbow_WL dmi.board.vendor: WL dmi.board.version: V1.10 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd02/22/2019:svnAcer:pnSwiftSF314-56:pvrV1.10:rvnWL:rnStrongbow_WL:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-56 dmi.product.sku: dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1753509] Re: avahi-daemon adds/installs every printer on network
Thank you for the step by step procedure jrgsampaio. I just followed it with the trivial modification to edit cupsd.conf instead of cups.conf. Unfortunately, I can't test it until I next travel to a conference with discoverable printers on the network, so I have no idea if it worked yet. I definitely wish this were easier. It would make sense to have an explicit "find printers" capability, followed by a checkbox list to confirm which ones you actually want to add. Having them automatically appear in your list (and stay there, long after you have disconnected from the network where those printers existed!) is not helpful at all, and in fact makes it too easy to send jobs to the wrong printer, which can be be a very serious problem if you have sensitive material in your printout. -- 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/1753509 Title: avahi-daemon adds/installs every printer on network Status in cups-filters package in Ubuntu: Expired Bug description: When connected to a network, avahi-daemon adds & installs all printer on a network without being prompted. This is not desired behaviour. Discovery of the printers is good, but not automatic installation & addition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 5 09:29:05 2018 InstallationDate: Installed on 2017-09-29 (157 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1753509/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Following up on my previous comment, after removing Chrome Remote Desktop three weeks ago I have not had any crashes on login. That old program (which Chrome didn't register as being installed, but was running in the background) seems to be the source of the issue for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: I've had this happen a couple of times now since upgrading to 18.04: soon (perhaps within a minute) after logging in, Gnome session ends abruptly and I'm thrown back to the login screen. IIRC, in both instances this occurred on the first login after boot, so it does not reoccur on the subsequent re-login, and not on every login (very rarely in fact), and for now I have no better steps to reproduce this other than "boot, log in". Bug #1663839 (reported against 17.04) seems similar, as does bug #1731428 (reported against 17.10). journalctl output during the issue: Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 16 17:07:14 2018 InstallationDate: Installed on 2016-10-13 (550 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1728012] Update Released
Just wanted you to know the scan function on my OfficeEdge Pro5500 is working again! I installed the following driver from Lexmark Support (Australia). lexmark_network-scan-linux-glibc2_04082019_x86_64.deb Regards On Mon, Jul 22, 2019 at 4:31 PM Manuel wrote: > Worked for me... > ~$ uname -a > Linux hades 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 > x86_64 x86_64 x86_64 GNU/Linux > ~$ lsb_release -a > LSB Version: > core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch > Distributor ID: Ubuntu > Description: Ubuntu 18.04.2 LTS > Release: 18.04 > Codename: bionic > > Manuel SCHULTE > *Managing Director, Olympus Consulting sprl* > *gsm :* +32(0)498 881 718 > *mail :* manuel.schu...@olympusconsulting.eu > *web :* http://www.olympusconsulting.eu/ > > > Le dim. 21 juil. 2019 à 23:35, Phil a écrit : > > > Hi Lukasz, > > > > I am an Ubuntu user but *not* a technician so please bear with me. Your > > e-mail says "The verification of the Stable Release Update for > > sane-backends has > > completed successfully and the package has now been released to > -updates." > > Do you know what release will contain the fix and when the release will > > occur? > > (I updated my system a couple of minutes ago and the scanner is still not > > working.) Should I have checkmarked Pre-released updates Bionic-proposed > > in the Developer Options tab of the update settings - see picture? (The > > release I'm using is 18.04.02) Thanks! > > > > > > [image: image.png] > > > > > > > > On Thu, Jul 18, 2019 at 3:26 AM Łukasz Zemczak < > 1728...@bugs.launchpad.net > > > > > wrote: > > > > > The verification of the Stable Release Update for sane-backends has > > > completed successfully and the package has now been released to > > > -updates. Subsequently, the Ubuntu Stable Release Updates Team is > being > > > unsubscribed and will not receive messages about this bug report. In > > > the event that you encounter a regression using the package from > > > -updates please report a new bug using ubuntu-bug and tag the bug > report > > > regression-update so we can easily find any regressions. > > > > > > -- > > > You received this bug notification because you are subscribed to a > > > duplicate bug report (1822360). > > > https://bugs.launchpad.net/bugs/1728012 > > > > > > Title: > > > Many 3rd party scanner drivers are broken by a sane change > > > > > > Status in sane-backends package in Ubuntu: > > > Fix Released > > > Status in sane-backends source package in Bionic: > > > Fix Released > > > Status in sane-backends package in Debian: > > > Fix Released > > > > > > Bug description: > > > To the sponsor: Please upload to bionic using the attached sane- > > > backends_lp1728012_bionic.debdiff. > > > > > > [Impact] > > > > > >* Starting with Ubuntu 17.10, Ubuntu changed the directory where > sane > > > dll looks for third party drivers. This configuration effectively > > > broke backward compatibility for all existing third-party drivers. > > > > > >* A large swath of these third party drivers (most of them) are no > > > longer supported by the OEM, so maintaining compatibility is > > > important. > > > > > >* No open source replacement drivers are currently available, nor > > > does the community have the resources to easily replace them. > > > > > >* This bug represents a substantial portion of the scanners in use. > > > > > > Scanners known to be affected include, but are not limited to: > > > > > >- Brother Scanners (all Brother scanners before brscan4) > > > - DCP-145C > > > - DCP-163C > > > - DCP-165C > > > - DCP-167C > > > - DCP-185C > > > - DCP-195C > > > - DCP-197C > > > - DCP-365CN > > > - DCP-373CW > > > - DCP-375CW > > > - DCP-377CW > > > - DCP-383C > > > - DCP-385C > > > - DCP-387C > > > - DCP-395CN > > > - DCP-585CW > > > - DCP-6690CW > > > - DCP-7030 > > > - DCP-7040 > > > - DCP-7045N > > > - DCP-8070D > > > - DCP-8080DN > > > - DCP-8085DN > > > - DCP-9010CN > > > - DCP-9040CN > > >
[Desktop-packages] [Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Very similar issue to the other reports. I see this every few days when I login. Typically I go to Nautilus, mount an encrypted FUSE drive, open Chrome, then randomly the session just dies. Interesting, my dual monitors are reversed so the order of them is wrong (left is on the right, and vice versa). Restarting seems fine. OS: Ubuntu 18.04.03 Kernel: Linux 4.4.0-148-generic x86_64 Ubuntu Processor: Intel® Core™ i7-2600 CPU @ 3.40GHz × 8 Graphics: GeForce GTX 1060 6GB/PCIe/SSE2 GNOME: 3.28.2 I also have the Chrome Remote Desktop installed. I'll try removing it. Relevant syslog attached for reference. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+attachment/5317862/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: I've had this happen a couple of times now since upgrading to 18.04: soon (perhaps within a minute) after logging in, Gnome session ends abruptly and I'm thrown back to the login screen. IIRC, in both instances this occurred on the first login after boot, so it does not reoccur on the subsequent re-login, and not on every login (very rarely in fact), and for now I have no better steps to reproduce this other than "boot, log in". Bug #1663839 (reported against 17.04) seems similar, as does bug #1731428 (reported against 17.10). journalctl output during the issue: Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 16 17:07:14 2018 InstallationDate: Installed on 2016-10-13 (550 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850088] Re: permission denied when opening a mounted folder in save file dialog
Another fairly simple path to hit this issue is when I mount a drive
from the File Browser. It gets mounted automatically under
/media/$USER/ and isn't accessible in the Snap by default.
I guess installing the snap with --classic would resolve it?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1850088
Title:
permission denied when opening a mounted folder in save file dialog
Status in chromium-browser package in Ubuntu:
Incomplete
Bug description:
After upgrading to Ubuntu 19.10, when I tried to open a file into a
sshfs-mounted folder inside my home folder, it says permission denied.
This didn't happen at Ubuntu 19.04.
Steps to reproduce:
1. Use sshfs to mount a sftp folder on an empty folder inside my home drive
(e.g. ~/.server)
2. Create a soft link in the home folder to a folder inside the mounted sftp
file system (e.g. ~/server > .server/home/michael )
3. Open chromium
4. Download a file
5. Enter that folder in the file dialog
Expected result:
I can enter the folder
Actual result:
It says permission denied
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
DRM.card1-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card1-VGA-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wBBDGbAJEYAAA8WAQNuMx14LspFpFZLnCUSUFS9SwDRwLMAlQCBgJUPAQEBAQEBAjqAGHE4LUBYLEUA/R4RAAAe/wBVSEIxMjE1MDE3OTU2/ABQaGlsaXBzIDIzNENM/QA4TB5TEQAKICAgICAgAHs=
modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1024x768
1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400
Date: Mon Oct 28 10:14:27 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/vg0-root ext4 230G 190G 29G 87% /
tmpfstmpfs 7.8G 165M 7.6G 3% /dev/shm
/dev/mapper/vg0-root ext4 230G 190G 29G 87% /
InstallationDate: Installed on 2016-10-03 (1119 days ago)
InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=/dev/mapper/vg0-root ro quiet splash resume=/dev/vg0/swap vt.handoff=7
Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.70
(edb9c9f3de0247fd912a77b7f6cae7447f6d3ad5-refs/branch-heads/3904@{#800})
Snap.ChromiumVersion: Chromium 78.0.3904.70 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to eoan on 2019-10-25 (2 days ago)
dmi.bios.date: 08/13/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2105
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2105:bd08/13/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-E:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850088/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840268] [NEW] Bluetooth headphones and wifi video streaming causes buffering
Public bug reported: When using headphones via bluetooth and streaming a youtube video in Chrome, unacceptable buffering occurs. Switch off bluetooth and the video streams as expected. Switch on bluetooth and video buffers. I tried this several times with consistent results. Hardware: DELL Inspiron N5110 processor: Intel® Core™ i3-2350M CPU @ 2.30GHz × 4 64 bit. O.S. Ubuntu 18.04.3 Headphones: mixcder ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ftf1575 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 15 14:56:36 2019 InstallationDate: Installed on 2019-03-11 (156 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 034W60 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/30/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn034W60:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** 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/1840268 Title: Bluetooth headphones and wifi video streaming causes buffering Status in alsa-driver package in Ubuntu: New Bug description: When using headphones via bluetooth and streaming a youtube video in Chrome, unacceptable buffering occurs. Switch off bluetooth and the video streams as expected. Switch on bluetooth and video buffers. I tried this several times with consistent results. Hardware: DELL Inspiron N5110 processor: Intel® Core™ i3-2350M CPU @ 2.30GHz × 4 64 bit. O.S. Ubuntu 18.04.3 Headphones: mixcder ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ftf1575 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Aug 15 14:56:36 2019 InstallationDate: Installed on 2019-03-11 (156 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 034W60 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/30/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn034W60:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1728012] Update Released
Hi Lukasz, I am an Ubuntu user but *not* a technician so please bear with me. Your e-mail says "The verification of the Stable Release Update for sane-backends has completed successfully and the package has now been released to -updates." Do you know what release will contain the fix and when the release will occur? (I updated my system a couple of minutes ago and the scanner is still not working.) Should I have checkmarked Pre-released updates Bionic-proposed in the Developer Options tab of the update settings - see picture? (The release I'm using is 18.04.02) Thanks! [image: image.png] On Thu, Jul 18, 2019 at 3:26 AM Łukasz Zemczak <1728...@bugs.launchpad.net> wrote: > The verification of the Stable Release Update for sane-backends has > completed successfully and the package has now been released to > -updates. Subsequently, the Ubuntu Stable Release Updates Team is being > unsubscribed and will not receive messages about this bug report. In > the event that you encounter a regression using the package from > -updates please report a new bug using ubuntu-bug and tag the bug report > regression-update so we can easily find any regressions. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1822360). > https://bugs.launchpad.net/bugs/1728012 > > Title: > Many 3rd party scanner drivers are broken by a sane change > > Status in sane-backends package in Ubuntu: > Fix Released > Status in sane-backends source package in Bionic: > Fix Released > Status in sane-backends package in Debian: > Fix Released > > Bug description: > To the sponsor: Please upload to bionic using the attached sane- > backends_lp1728012_bionic.debdiff. > > [Impact] > >* Starting with Ubuntu 17.10, Ubuntu changed the directory where sane > dll looks for third party drivers. This configuration effectively > broke backward compatibility for all existing third-party drivers. > >* A large swath of these third party drivers (most of them) are no > longer supported by the OEM, so maintaining compatibility is > important. > >* No open source replacement drivers are currently available, nor > does the community have the resources to easily replace them. > >* This bug represents a substantial portion of the scanners in use. > > Scanners known to be affected include, but are not limited to: > >- Brother Scanners (all Brother scanners before brscan4) > - DCP-145C > - DCP-163C > - DCP-165C > - DCP-167C > - DCP-185C > - DCP-195C > - DCP-197C > - DCP-365CN > - DCP-373CW > - DCP-375CW > - DCP-377CW > - DCP-383C > - DCP-385C > - DCP-387C > - DCP-395CN > - DCP-585CW > - DCP-6690CW > - DCP-7030 > - DCP-7040 > - DCP-7045N > - DCP-8070D > - DCP-8080DN > - DCP-8085DN > - DCP-9010CN > - DCP-9040CN > - DCP-9042CDN > - DCP-9045CDN > - DCP-J125 > - DCP-J315W > - DCP-J515W > - DCP-J715W > - MFC-250C > - MFC-255CW > - MFC-257CW > - MFC-290C > - MFC-295CN > - MFC-297C > - MFC-490CW > - MFC-495CW > - MFC-5490CN > - MFC-5890CN > - MFC-5895CW > - MFC-6490CW > - MFC-6890CDW > - MFC-7320 > - MFC-7340 > - MFC-7345N > - MFC-7440N > - MFC-7450 > - MFC-7840N > - MFC-7840W > - MFC-790CW > - MFC-795CW > - MFC-8370DN > - MFC-8380DN > - MFC-8480DN > - MFC-8510DN > - MFC-8680DN > - MFC-8880DN > - MFC-8890DW > - MFC-9010CN > - MFC-9120CN > - MFC-9320CW > - MFC-9440CN > - MFC-9450CDN > - MFC-9840CDW > - MFC-990CW > - MFC-J220 > - MFC-J265W > - MFC-J270W > - MFC-J410 > - MFC-J410W > - MFC-J415W > - MFC-J615W > - MFC-J630W > >- Dell MFP Laser Printer 1135n > >- Epson Scanners > - All scanners supported by the libsane-epk driver > - All scanners supported by the iscan driver > - Epson Perfection V10 > - Epson Perfection V1000 > - Epson WorkForce GT-1500 > - Epson Perfection V33 > >- Samsung M2070 > >- Xerox Workcentre 3225 > >* This was working in the 17.04 release. 18.04 is an LTS release, so > backporting is warranted for the 18.04 release. > > [Test Case] > >* Following the standard installation procedures for any of the > affected scanner drivers results in the driver files being installed > to /usr/lib/sane/, and sane looking for them in /usr/lib/x86_64-linux- > gnu/sane. When xsane is run, the scanner is not found. > > * Install the libsane1, libsane-common and sane-utils packages from > bionic-proposed and confirm that it now finds drivers in > /usr/lib/sane. > > [Regression Potential] > >* The proposed change is based on an upstream commit, and the patch > is functional and stable in both 19.04 and 19.10. Low regression risk. > > [Other Info] >* Third party sane drivers in previous version of
[Desktop-packages] [Bug 1822360] Re: Scan does not work with Lexmark OfficeEdge Pro 5500
*** This bug is a duplicate of bug 1728012 *** https://bugs.launchpad.net/bugs/1728012 Updated software - scanner still does not work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1822360 Title: Scan does not work with Lexmark OfficeEdge Pro 5500 Status in sane-backends package in Ubuntu: New Bug description: ~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 Printer portion works fine. Simple scane and XSANE do not detect scanner. Scanner worked in release 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1822360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
On 25/4/19 8:31 am, Troels Petersen wrote: > I also reverted to Linux kernel 4.18.0-13-generic (The one that ships > with Ubuntu 18.10) after upgrading to 19.04. > > System: HP Spectre 13 v000nf, 8 GB Memory, Dual core Intel i5-6200U CPU > @ 2.30 GHz, Intel HD Graphics 520 (Skylake GT2) > > When running 'sudo apt upgrade' it complains about a missing dkms.conf > file: > > Setting up linux-headers-5.0.0-13-generic (5.0.0-13.14) ... > /etc/kernel/header_postinst.d/dkms: > Error! Could not locate dkms.conf file. > File: /var/lib/dkms/igfxdcd/1.1.11/source/dkms.conf does not exist. > run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4 > dpkg: error processing package linux-headers-5.0.0-13-generic (--configure): > installed linux-headers-5.0.0-13-generic package post-installation script > subprocess returned error exit status 1 > dpkg: dependency problems prevent configuration of linux-headers-generic: > linux-headers-generic depends on linux-headers-5.0.0-13-generic; however: >Package linux-headers-5.0.0-13-generic is not configured yet. > > dpkg: error processing package linux-headers-generic (--configure): > dependency problems - leaving unconfigured > Setting up linux-image-5.0.0-13-generic (5.0.0-13.14) ... > No apport report written because the error message indicates its a followup > error from a previous failure. > dpkg: dependency problems prevent configuration of linux-generic: > linux-generic depends on linux-headers-generic (= 5.0.0.13.14); however: >Package linux-headers-generic is not configured yet. > > dpkg: error processing package linux-generic (--configure): > dependency problems - leaving unconfigured > No apport report written because the error message indicates its a followup > error from a previous failure. > Processing triggers for linux-image-5.0.0-13-generic (5.0.0-13.14) ... > /etc/kernel/postinst.d/dkms: > Error! Could not locate dkms.conf file. > File: /var/lib/dkms/igfxdcd/1.1.11/source/dkms.conf does not exist. > run-parts: /etc/kernel/postinst.d/dkms exited with return code 4 > dpkg: error processing package linux-image-5.0.0-13-generic (--configure): > installed linux-image-5.0.0-13-generic package post-installation script > subprocess returned error exit status 1 > No apport report written because MaxReports is reached already >Errors were > encountered while processing: > linux-headers-5.0.0-13-generic > linux-headers-generic > linux-generic > linux-image-5.0.0-13-generic > E: Sub-process /usr/bin/dpkg returned an error code (1) > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0
[Desktop-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
System: Dell Studio XPS 8300 64bit. memory: 7.8 GiB. CPU: Intel® Core™ i7-2600 CPU @ 3.40GHz × 8. Graphics AMD® Juniper. Upgrading from perfectly good 18.10. Before this bug appeared another error message had stated /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory. Grub indicated the presence of 5.0.0.13.14 but login failed. I can log in with the previous kernel but it's very slow. Using Gimp 2.10.10 I'm experiencing odd behavior in tools, followed by hanging, before totally freezing the computer. After giving it 90 minutes It was still unusable, Control alt delete didn't work.The system required a hard reboot, losing hours of work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824072] [NEW] Intel 710 series INC can't receive any packet on 18.04 & 18.10 Ubuntu-arm64-server
Public bug reported: ## PCI info for the NIC XXV710DA2BLK pci@:8e:00.1 enp142s0f1 networkEthernet Controller XL710 for 40GbE QSFP+ ## link detected & promisc mode turned on $ ip link list enp142s0f1 3: enp142s0f1: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 3c:fd:fe:bb:cf:61 brd ff:ff:ff:ff:ff:ff $ sudo ethtool enp142s0f1 Settings for enp142s0f1: Supported ports: [ FIBRE ] Supported link modes: 4baseCR4/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 4baseCR4/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 4Mb/s Duplex: Full Port: Direct Attach Copper PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: d Wake-on: d Current message level: 0x0007 (7) drv probe link Link detected: yes $ sudo ethtool -i enp142s0f1 driver: i40e version: 2.8.10-k firmware-version: 6.01 0x800035da 1.1747.0 expansion-rom-version: bus-info: :8e:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ## Kernel info 5.1-rc3+ commit 5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539 ## Packet generated by IXIA ## XDP & tcpdump can't capture any packet. $ sudo ./samples/bpf/xdp1 -N enp142s0f1 $ sudo tcpdump -i enp142s0f1 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on enp142s0f1, link-type EN10MB (Ethernet), capture size 262144 bytes 15:08:50.176524 IP6 net-arm-thunderx2-03 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 15:08:50.588515 IP6 net-arm-thunderx2-03 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 = Ubuntu 16.04.5 LTS with Kernel 4.15.0-43-generic + Intel 710 NIC (The same NIC XXV710DA2BLK): tcpdump worked as expected. $ sudo ethtool -i enp138s0f0 driver: i40e version: 2.7.29 firmware-version: 6.80 0x80003d05 1.2007.0 expansion-rom-version: bus-info: :8a:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ** Affects: mutter (Ubuntu) Importance: Undecided Status: New -- 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/1824072 Title: Intel 710 series INC can't receive any packet on 18.04 & 18.10 Ubuntu-arm64-server Status in mutter package in Ubuntu: New Bug description: ## PCI info for the NIC XXV710DA2BLK pci@:8e:00.1 enp142s0f1 networkEthernet Controller XL710 for 40GbE QSFP+ ## link detected & promisc mode turned on $ ip link list enp142s0f1 3: enp142s0f1: mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000 link/ether 3c:fd:fe:bb:cf:61 brd ff:ff:ff:ff:ff:ff $ sudo ethtool enp142s0f1 Settings for enp142s0f1: Supported ports: [ FIBRE ] Supported link modes: 4baseCR4/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 4baseCR4/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 4Mb/s Duplex: Full Port: Direct Attach Copper PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: d Wake-on: d Current message level: 0x0007 (7) drv probe link Link detected: yes $ sudo ethtool -i enp142s0f1 driver: i40e version: 2.8.10-k firmware-version: 6.01 0x800035da 1.1747.0 expansion-rom-version: bus-info: :8e:00.1 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ## Kernel info 5.1-rc3+ commit 5e7a8ca319268a70a6c7c3c1fde5bea38e1e5539 ## Packet generated by IXIA ## XDP & tcpdump can't capture any packet. $ sudo ./samples/bpf/xdp1 -N enp142s0f1 $ sudo tcpdump -i enp142s0f1 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on enp142s0f1, link-type EN10MB (Ethernet), capture size 262144 bytes 15:08:50.176524 IP6 net-arm-thunderx2-03 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28 15:08:50.588515 IP6 net-arm-thunderx2-03 > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
[Desktop-packages] [Bug 1822360] [NEW] Scan does not work with Lexmark OfficeEdge Pro 5500
Public bug reported: ~$ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 Printer portion works fine. Simple scane and XSANE do not detect scanner. Scanner worked in release 14.04 ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1822360 Title: Scan does not work with Lexmark OfficeEdge Pro 5500 Status in sane-backends package in Ubuntu: New Bug description: ~$ lsb_release -rd Description: Ubuntu 18.04.2 LTS Release: 18.04 Printer portion works fine. Simple scane and XSANE do not detect scanner. Scanner worked in release 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1822360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1757091] Re: systemctl enable lightdm
I confirm this bug for 18.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1757091 Title: systemctl enable lightdm Status in lightdm package in Ubuntu: Confirmed Bug description: Synchronizing state of lightdm.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable lightdm The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lightdm 1.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Tue Mar 20 11:44:46 2018 InstallationDate: Installed on 2018-01-22 (57 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1757091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1587614] Re: Open with - duplicate entries
This is from 2 years ago and I already gave up on this, please close if it's still open. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1587614 Title: Open with - duplicate entries Status in nautilus package in Ubuntu: Incomplete Bug description: 1. Installed Ubuntu 16.04 2. Followed this guide to try out Xubuntu (except for step 3, because I wanted to keep Unity in case. 3. Ended up going back to Unity via other steps I don't remember (using terminal to edit lightdm, etc) 4. Open with now has duplicate entries Based on question 61397, I can use this as a workaround but I'd appreciate the devs can look into how this can be prevented in future. Thanks Phil To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1587614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1810770] [NEW] package libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should rein
Public bug reported: found during upgdate ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Jan 7 10:54:57 2019 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-08-20 (139 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: freerdp2 Title: package libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: freerdp2 (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 freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1810770 Title: package libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in freerdp2 package in Ubuntu: New Bug description: found during upgdate ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Jan 7 10:54:57 2019 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-08-20 (139 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: freerdp2 Title: package libfreerdp2-2:amd64 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1810770/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1739468] Re: Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered
I see this when I try to install Microstack snap on Bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1739468 Title: Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in indicator-multiload package in Ubuntu: Confirmed Bug description: The following message is continuously logged to /var/log/syslog (every few seconds): Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] Attempting to re-register :1.51/org/ayatana/NotificationItem/multiload; resetting instead Dec 20 10:29:26 lxjima gnome-shell[13730]: [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered It's hard to find anything in syslog because thousands of these messages intermingle with everything else ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 20 10:28:49 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-13 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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-extension-appindicator/+bug/1739468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796434] Re: USB storage device does not finish ejecting
@Steve OK, sorry for the incorrect tag. I was just following the instruction to tag it as 'regression-update' in message #26 of bug report #1762595. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1796434 Title: USB storage device does not finish ejecting Status in gvfs package in Ubuntu: New Bug description: Regresssion of bug #1762595. I have installed Ubuntu 18.04.1 in the past week, and have encountered this problem repeatedly. I found it reported as fixed in gvfs 1.36.1-0ubuntu1.1, but it clearly isn't, because that's the version of gvfs that I currently have installed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 01:18:02 2018 InstallationDate: Installed on 2018-09-26 (9 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1796434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796434] Re: USB storage device does not finish ejecting
To add more information to my previous report, I've recently installed Ubuntu 18.04.1 on two machines, one of which is pretty old, and the other is about a year and a half old. I now have a USB storage device that causes this problem to happen every single time I plug it into my older machine. It's a Verbatim 32GB flash stick. It doesn't cause the problem on my newer machine. The logs attached to my report are from the older machine. lsusb reports the vendor and device IDs of the memory stick as 18a5:0302. The stick containsh an exFAT filesystem, and it has a number of large files on it (a few partition image backups made with Clonezilla). It didn't exhibit the problem when it was blank. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1796434 Title: USB storage device does not finish ejecting Status in gvfs package in Ubuntu: New Bug description: Regresssion of bug #1762595. I have installed Ubuntu 18.04.1 in the past week, and have encountered this problem repeatedly. I found it reported as fixed in gvfs 1.36.1-0ubuntu1.1, but it clearly isn't, because that's the version of gvfs that I currently have installed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 01:18:02 2018 InstallationDate: Installed on 2018-09-26 (9 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1796434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796434] [NEW] USB storage device does not finish ejecting
Public bug reported: Regresssion of bug #1762595. I have installed Ubuntu 18.04.1 in the past week, and have encountered this problem repeatedly. I found it reported as fixed in gvfs 1.36.1-0ubuntu1.1, but it clearly isn't, because that's the version of gvfs that I currently have installed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 01:18:02 2018 InstallationDate: Installed on 2018-09-26 (9 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic regression-update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1796434 Title: USB storage device does not finish ejecting Status in gvfs package in Ubuntu: New Bug description: Regresssion of bug #1762595. I have installed Ubuntu 18.04.1 in the past week, and have encountered this problem repeatedly. I found it reported as fixed in gvfs 1.36.1-0ubuntu1.1, but it clearly isn't, because that's the version of gvfs that I currently have installed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 01:18:02 2018 InstallationDate: Installed on 2018-09-26 (9 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1796434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791353] [NEW] Expanders in Gio::Socket* docs don't expand
Public bug reported: In the GLIBMM documentation package, Gio::SocketConnection in particular and several other (perhaps all) Gio::Socket* classes, the expanders for showing inherited types and functions do not in fact expand, nor do the expander icons rotate, suggesting that they are somehow disabled. 18.04.1 libglibmm-2.4-docs-1v5 2.56.0-1 ** Affects: glibmm2.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glibmm2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1791353 Title: Expanders in Gio::Socket* docs don't expand Status in glibmm2.4 package in Ubuntu: New Bug description: In the GLIBMM documentation package, Gio::SocketConnection in particular and several other (perhaps all) Gio::Socket* classes, the expanders for showing inherited types and functions do not in fact expand, nor do the expander icons rotate, suggesting that they are somehow disabled. 18.04.1 libglibmm-2.4-docs-1v5 2.56.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1791353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788005] [NEW] print-playing-formats %aa and %aA report wrong value
Public bug reported: These formats incorrectly supply the value of the track artist, instead of the album artist. To fix this in 3.4.2 (Ubuntu 18.04), edit remote/dbus/rb-client.c lines 301 and 308 to say "xesam:albumArtist" instead of "xesam:artist". In 3.3 (Ubuntu 16.04) the corresponding lines are 288 and 295. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1788005 Title: print-playing-formats %aa and %aA report wrong value Status in rhythmbox package in Ubuntu: New Bug description: These formats incorrectly supply the value of the track artist, instead of the album artist. To fix this in 3.4.2 (Ubuntu 18.04), edit remote/dbus/rb-client.c lines 301 and 308 to say "xesam:albumArtist" instead of "xesam:artist". In 3.3 (Ubuntu 16.04) the corresponding lines are 288 and 295. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1788005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762827] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from oth
I got this error message while attempting to install Wine from the Ubuntu 18.04 repository. The Wine install failed. Thanks, Phil -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1762827 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 Status in sane-backends package in Ubuntu: Confirmed Bug description: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Apr 11 01:29:46 2018 DuplicateSignature: package:libsane1:1.0.27-1~experimental2ubuntu2.1 Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-BVXsrr/2-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 InstallationDate: Installed on 2017-12-21 (109 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of package libsane1:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1762827/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740869] Re: is not respoding window is constantly showing when debugging a program in Eclipse
It appears that the dialog is system-wide modal. Is that really necessary? If so, it should also appear on top of *every* window stack in the system, not just the stack containing the offender. -- 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/1740869 Title: is not respoding window is constantly showing when debugging a program in Eclipse Status in mutter package in Ubuntu: Confirmed Bug description: Mentioned window about no responding program is showing and stealing focus when I try to debug a Java program in Eclipse. When I click on Wait, it disappears for a moment and opens again. This renders Ubuntu 17.10 with Gnome 3 nearly useless for program debugging. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mutter 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 2 14:22:56 2018 InstallationDate: Installed on 2017-12-04 (28 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) 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/1740869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748000] Re: Remove from the archive: this legacy driver is unmaintained upstream
My office is full of HP workstations with nvidia quadro cards which need this driver. Like other respondents, I will have to move to another distribution if the 304 driver is not available for Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1748000 Title: Remove from the archive: this legacy driver is unmaintained upstream Status in nvidia-graphics-drivers-304 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-304-updates package in Ubuntu: Fix Released Bug description: This driver branch is now dead upstream, so it should be removed from bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1748000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749273] Re: gnome-control-center crashed with SIGABRT in g_assertion_message() attempting to connect to hidden wi-fi ssid
*** This bug is a duplicate of bug 1720441 *** https://bugs.launchpad.net/bugs/1720441 Mouse-over the link in #2, tooltip says "Bug1720441 cannot be found" -- 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/1749273 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() attempting to connect to hidden wi-fi ssid Status in gnome-control-center package in Ubuntu: New Bug description: Was running on ethernet. Opened system settings, clicked on wi-fi menu, selected Connect to Hidden Network. After 10-15 seconds of displaying the menu with no discernible response, settings window disappeared. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 13 10:49:14 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-02-13 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180213) ProcCmdline: gnome-control-center --overview ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-control-center StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libnma.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libnma.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libnma.so.0 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1749273/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744471] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1744471/+attachment/5054690/+files/JournalErrors.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/1744471 Title: Dock erroneously shows generic icon with org.*.desktop file Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Launching an application which has a desktop filename of the form , the generic application icon appears in the dock. If the desktop filename is changed to the form , the icon that appears in the dock is the one specified in the desktop file. Ubuntu 17.10 / Wayland gnome-shell-extension-ubuntu-dock 0.7.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2015-07-17 (942 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful wayland-session third-party-packages Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-21 (115 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users vboxsf vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744471] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1744471/+attachment/5054691/+files/ProcCpuinfoMinimal.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/1744471 Title: Dock erroneously shows generic icon with org.*.desktop file Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Launching an application which has a desktop filename of the form , the generic application icon appears in the dock. If the desktop filename is changed to the form , the icon that appears in the dock is the one specified in the desktop file. Ubuntu 17.10 / Wayland gnome-shell-extension-ubuntu-dock 0.7.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2015-07-17 (942 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful wayland-session third-party-packages Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-21 (115 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users vboxsf vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744471] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1744471/+attachment/5054689/+files/GsettingsChanges.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/1744471 Title: Dock erroneously shows generic icon with org.*.desktop file Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Launching an application which has a desktop filename of the form , the generic application icon appears in the dock. If the desktop filename is changed to the form , the icon that appears in the dock is the one specified in the desktop file. Ubuntu 17.10 / Wayland gnome-shell-extension-ubuntu-dock 0.7.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2015-07-17 (942 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful wayland-session third-party-packages Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-21 (115 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users vboxsf vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744471] Re: Dock erroneously shows generic icon with org.*.desktop file
apport information ** Tags added: apport-collected artful third-party-packages wayland- session ** Description changed: Launching an application which has a desktop filename of the form , the generic application icon appears in the dock. If the desktop filename is changed to the form , the icon that appears in the dock is the one specified in the desktop file. Ubuntu 17.10 / Wayland gnome-shell-extension-ubuntu-dock 0.7.1 + --- + ApportVersion: 2.20.7-0ubuntu3.7 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 17.10 + InstallationDate: Installed on 2015-07-17 (942 days ago) + InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) + Package: gnome-shell-extension-ubuntu-dock + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 + Tags: artful wayland-session third-party-packages + Uname: Linux 4.13.0-32-generic x86_64 + UpgradeStatus: Upgraded to artful on 2017-10-21 (115 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users vboxsf vboxusers + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1744471/+attachment/5054688/+files/Dependencies.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/1744471 Title: Dock erroneously shows generic icon with org.*.desktop file Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Launching an application which has a desktop filename of the form , the generic application icon appears in the dock. If the desktop filename is changed to the form , the icon that appears in the dock is the one specified in the desktop file. Ubuntu 17.10 / Wayland gnome-shell-extension-ubuntu-dock 0.7.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2015-07-17 (942 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful wayland-session third-party-packages Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-21 (115 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users vboxsf vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1744471] Re: Dock erroneously shows generic icon with org.*.desktop file
@#2 - Yes, it's OK on 18.04 @#3 - done -- 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/1744471 Title: Dock erroneously shows generic icon with org.*.desktop file Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: Launching an application which has a desktop filename of the form , the generic application icon appears in the dock. If the desktop filename is changed to the form , the icon that appears in the dock is the one specified in the desktop file. Ubuntu 17.10 / Wayland gnome-shell-extension-ubuntu-dock 0.7.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2015-07-17 (942 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful wayland-session third-party-packages Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-21 (115 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare staff sudo users vboxsf vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1744471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745390] [NEW] Incorrect function prototype in documentation
Public bug reported: In the chapter on Gtk::TreeView, there are two instances of the string "void on_search_equal" that should read "bool on_search_equal". Ubuntu 17.10/Wayland libgtkmm-3.0 3.22.2-1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgtkmm-3.0-doc 3.22.2-1 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 25 06:23:19 2018 InstallationDate: Installed on 2015-07-17 (922 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtkmm3.0 UpgradeStatus: Upgraded to artful on 2017-10-21 (95 days ago) ** Affects: gtkmm3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtkmm3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1745390 Title: Incorrect function prototype in documentation Status in gtkmm3.0 package in Ubuntu: New Bug description: In the chapter on Gtk::TreeView, there are two instances of the string "void on_search_equal" that should read "bool on_search_equal". Ubuntu 17.10/Wayland libgtkmm-3.0 3.22.2-1 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgtkmm-3.0-doc 3.22.2-1 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 25 06:23:19 2018 InstallationDate: Installed on 2015-07-17 (922 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtkmm3.0 UpgradeStatus: Upgraded to artful on 2017-10-21 (95 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtkmm3.0/+bug/1745390/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
I got it to work, and it fixes my problem with the launcher resulting in an unknown file error on /usr/bin/compiz. Go to Software & Updates via command line ubuntu-software & and selecting it from a list of apt applications. Use Developer Options to enable xenial-proposed. Then run command line: sudo apt-get install libgl1-mesa-dri/xenial-proposed This installed it for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
This bug needs fixed for the following: 7.6 GiB Intel® Core™ i5 CPU M 480 @ 2.67GHz × 4 Intel® Ironlake Mobile 64-bit Sorry I didn't add a comment elsewhere; not enough "Reputation Points" GAH!~ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade
How about withdrawing the update that causes this until fixed? Or, publishing some kind of advisory that doesn't require searching many threads to find??? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Xenial: Confirmed Status in mesa source package in Artful: Confirmed Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735991] Re: QL-570 printer : the led flashes red and nothing happens
Another thought - can you also post the Brother part number of the labels you're using please? (then I can look that up and make sure your page size is right) It'll be on a label on the side of the plastic label roll cartridge. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ptouch-driver in Ubuntu. https://bugs.launchpad.net/bugs/1735991 Title: QL-570 printer : the led flashes red and nothing happens Status in ptouch-driver package in Ubuntu: New Bug description: The label printer Brother QL-570 refuses to print ... When I ask the printer to print, the led flashes red and nothing happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: printer-driver-ptouch 1.4.2-2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 13:46:56 2017 InstallationDate: Installed on 2017-12-03 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: ptouch-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735991] Re: QL-570 printer : the led flashes red and nothing happens
Clean Print Head doesn't apply to the QL driver. "cleaning" the heads requires either a cleaning card or a bit of manual work (can't remember if the 570 is like a Zebra printer; the instructions should be in the manual). The CUPS test page is geared up for page printers, not label printers. I haven't tried it with the Ptouch driver but I wouldn't be surprised if it had problems. As I said - you need to configure the label dimensions correctly in both the driver and the application. I've never tried Libreoffice, but gLabels works well. If you get the page size wrong (especially width), the printer may refuse to print on the labels. Can you post the settings you have set in the driver? Screenshots from CUPS (http://localhost:631 -> printers -> QL) would be useful, and I can see if you have anything set obviously wrong. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ptouch-driver in Ubuntu. https://bugs.launchpad.net/bugs/1735991 Title: QL-570 printer : the led flashes red and nothing happens Status in ptouch-driver package in Ubuntu: New Bug description: The label printer Brother QL-570 refuses to print ... When I ask the printer to print, the led flashes red and nothing happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: printer-driver-ptouch 1.4.2-2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 13:46:56 2017 InstallationDate: Installed on 2017-12-03 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: ptouch-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1735991] Re: QL-570 printer : the led flashes red and nothing happens
The most common issue which can cause this is setting the Page Size incorrectly in the driver. You'll get the red flashing light if the intended page size doesn't match the label. The other issue is swapping the X and Y dimensions - the X (as far as the printer is concerned) is across the printer; the Y axis is the direction the label feeds. Note that most of the Ptouch labels are longer (Y axis) than they are wide (X axis), but the dimensions on the label box are the other way around. This means you need to specify the paper size as it is on the physical label (i.e. longer than wide) then rotate the label (e.g. gLabels's "Rotated" option). What are you trying to print, and with which application? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ptouch-driver in Ubuntu. https://bugs.launchpad.net/bugs/1735991 Title: QL-570 printer : the led flashes red and nothing happens Status in ptouch-driver package in Ubuntu: New Bug description: The label printer Brother QL-570 refuses to print ... When I ask the printer to print, the led flashes red and nothing happens. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: printer-driver-ptouch 1.4.2-2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 3 13:46:56 2017 InstallationDate: Installed on 2017-12-03 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: ptouch-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ptouch-driver/+bug/1735991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726538] Re: Dual monitor configuration not saved across logout / login
further update - prior to 17.10, my logon routine was to boot up my laptop with the screen open, then as soonn as my 2 monitors picked up the screen image during the boot up process, I closed my laptop screen fully shut, and completed the rest of the boot up process, including entering my logon password on the montiors, with the left one showing as my default primary monitor. This worked every time. Since 17.10 this big 1726538 has occurred. I discovered today though that if I keep my laptop screen fully open throughout the boot up and logon process and type my logon password into the logon prompt on th laptop screen, then let the boot up process run fully, with the laptop screen open, when the boot up process ends the monitors are correct with the primary default monitor on the left and bug 1726538 does not occur. I close my laptop screen fully then and all is well. No issues. However if I close my laptop screen part way through the boot up process, before it is fully finished, the bug reappears and my montiors are switched round again. For me this is a decent work around fix, although I'm not sure it's working as designed so probably still valid to keep this bug open and investigate some more. -- 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/1726538 Title: Dual monitor configuration not saved across logout / login Status in gnome-shell package in Ubuntu: Confirmed Bug description: System76 Galaga UltraPro laptop. Two monitors, one plugged into the DisplayPort and one plugged into HDMI. I use the Displays settings page to tell the system which monitor is on the right and which is on the left, and tell it to make the left monitor the primary one. All is well. Then I log out and log back in. Now the two monitors are reversed -- i.e., it thinks that the monitor on the right is on the left and vice versa -- and the right monitor (which, remember, it thinks is on the left) is the primary one. In short, it forgets the configuration I told it to use immediately before logging out. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 14:55:09 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-19 (157 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725315] Re: evolution crashed with SIGSEGV in g_hash_table_lookup_node()
Thank you for this, José. My machines that were crashing had the evolution-indicator package installed, and the one that never crashed did not. Hopefully, removing that package solves the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1725315 Title: evolution crashed with SIGSEGV in g_hash_table_lookup_node() Status in evolution package in Ubuntu: Confirmed Bug description: Every few minutes, evolution exits the desktop. Sometimes it will only stay up for seconds, and sometimes it exits in the first second. Occasionally it stays up for ~20 minutes. When it is running, it seems to function normally. This machine was upgraded from 17.04 (where Evolution was stable) to 17.10 release. Apport crashdump analysis attached. Looking at /var/log/syslog after one of these crashes, I see the following entries: Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: /usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant Oct 20 09:50:00 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (254): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (287): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (300): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:52 es-lzz-det470s org.gnome.Shell.desktop[2287]: [Parent 8840] WARNING: pipe error (417): Connection reset by peer: file /build/firefox-9cfKiA/firefox-56.0+build6/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 353 Oct 20 09:50:57 es-lzz-det470s kernel: [88013.689438] evolution[1461]: segfault at 0 ip (null) sp 7ffee4f96718 error 14 in evolution[557e54c52000+7000] It is not clear that the first few syslog entries are related. Running evolution with debugging enabled: CAMEL_DEBUG=all evolution I see the following output when the crash occurs: ### message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 (john.mel...@esentire.com : Inbox) for expression:---(and (match-all (and (not (system-flag "deleted")) (not (system-flag "junk" (and (and (match-all (not (or (= (user-tag "label") "important") (user-flag "$Labelimportant") (user-flag "important" (match-all (not (or (= (user-tag "label") "work") (user-flag "$Labelwork") (user-flag "work" (match-all (not (or (= (user-tag "label") "personal") (user-flag "$Labelpersonal") (user-flag "personal" (match-all (not (or (= (user-tag "label") "todo") (user-flag "$Labeltodo") (user-flag "todo" (match-all (not (or (= (user-tag "label") "later") (user-flag "$Labellater") (user-flag "later")))--- message_list_regen_thread: got 1521 uids in folder 0x5615e38015f0 (john.mel...@esentire.com : Inbox) after tweak, hide_deleted:1, hide_junk:1 Segmentation fault (core dumped) Not sure if I can provide further information. This crash is highly- repeatable, happening hundreds of times/day. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: evolution 3.26.1-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 20 09:50:57 2017 Disassembly: => 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/bin/evolution InstallationDate: Installed on 2017-05-31 (142 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: evolution -c current ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: ?? () g_hash_table_lookup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gdk_x11_atom_to_xatom_for_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so org_gnome_mail_new_notify () from /usr/lib/evolution/plugins/liborg-freedesktop-evolution-indicator.so Title: evolution crashed with SIGSEGV in g_hash_table_lookup() UpgradeStatus: Upgraded to artful on
[Desktop-packages] [Bug 1726538] Re: Dual monitor configuration not saved across logout / login
been testing out some things with this - starting with both montitors correct, left monitor is primary, mouse moves across to right monitor ok. Then reboot/logoff and back on, monitors reversed and I have to manually change in settings / displays etc. before the reboot, after manually making the correct display settings - I see in: stat -c %y .config/monitors.xml a timestamp of 2017-11-08 17:11:55.624995543 +0100 after the reboot the displays are back in the wrong setting and timestamp in stat -c %y .config/monitors.xml = 11-08 17:41:21.223296912 +0100 -- 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/1726538 Title: Dual monitor configuration not saved across logout / login Status in gnome-shell package in Ubuntu: Confirmed Bug description: System76 Galaga UltraPro laptop. Two monitors, one plugged into the DisplayPort and one plugged into HDMI. I use the Displays settings page to tell the system which monitor is on the right and which is on the left, and tell it to make the left monitor the primary one. All is well. Then I log out and log back in. Now the two monitors are reversed -- i.e., it thinks that the monitor on the right is on the left and vice versa -- and the right monitor (which, remember, it thinks is on the left) is the primary one. In short, it forgets the configuration I told it to use immediately before logging out. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 23 14:55:09 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-19 (157 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-20 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1725116] Re: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed
occurred during upgrade from 17.04 to 17.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cracklib2 in Ubuntu. https://bugs.launchpad.net/bugs/1725116 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cracklib2 package in Ubuntu: Confirmed Bug description: Update to 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: cracklib-runtime 2.9.2-5build1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Thu Oct 19 21:36:09 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2012-04-02 (2026 days ago) InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: cracklib2 Title: package cracklib-runtime 2.9.2-5build1 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cracklib2/+bug/1725116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723884] Re: Copy of text from terminal window does not copy
The same happens if I use a PHPstorm instead of gedit in the above example. So it seems that other applications "take over" the copy-paste buffer and terminal is unable to write to it. -- 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/1723884 Title: Copy of text from terminal window does not copy Status in gnome-terminal package in Ubuntu: New Bug description: - do a default install of Ubuntu 17.10 - open a terminal window - select some text, click and select "Copy" - go to any other application and try to paste the text Expected: The text is pasted Actual: There is no text pasted Problem happens with all text selection/copy methods that I can find, e.g. laptop touchpad, external wireless mouse, shift-ctrl-C. Using a brand new Dell Inspiron 14 5000 series laptop. Text can be copied fine from other application windows (e.g. gedit) and then pasted into the terminal window. So it seems to be just the copy operation in the terminal window that does not work. Also, I can't believe this is really broken and not reported, because many many people would quickly notice this. I can't think what I can do wrong to have caused this problem. But yet here I am? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 14:10:48 2017 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2017-10-13 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1723884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723884] Re: Copy of text from terminal window does not copy
I can reproduce by: 1) Open text editor (gedit) 2) Select-copy some text from a terminal window - paste it anywhere (into the terminal or gedit), it works - good. 3) Type some text into gedit. Select-copy some of that text. Paste it to gedit or the terminal - works - good. 4) Select-copy some text from a terminal window. Try to paste it anywhere - the previous text copied in gedit is still in the copy-paste buffer - not good. Now close gedit - copy works again from a terminal window. So gedit (at least) seems to "take control of" or "lock" the copy-paste buffer. -- 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/1723884 Title: Copy of text from terminal window does not copy Status in gnome-terminal package in Ubuntu: New Bug description: - do a default install of Ubuntu 17.10 - open a terminal window - select some text, click and select "Copy" - go to any other application and try to paste the text Expected: The text is pasted Actual: There is no text pasted Problem happens with all text selection/copy methods that I can find, e.g. laptop touchpad, external wireless mouse, shift-ctrl-C. Using a brand new Dell Inspiron 14 5000 series laptop. Text can be copied fine from other application windows (e.g. gedit) and then pasted into the terminal window. So it seems to be just the copy operation in the terminal window that does not work. Also, I can't believe this is really broken and not reported, because many many people would quickly notice this. I can't think what I can do wrong to have caused this problem. But yet here I am? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 14:10:48 2017 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2017-10-13 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1723884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723884] Re: Copy of text from terminal window does not copy
After logout-login copy works again in the terminal. I will keep an "eye" on it and try to determine under what conditions the "Copy" stops working. -- 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/1723884 Title: Copy of text from terminal window does not copy Status in gnome-terminal package in Ubuntu: New Bug description: - do a default install of Ubuntu 17.10 - open a terminal window - select some text, click and select "Copy" - go to any other application and try to paste the text Expected: The text is pasted Actual: There is no text pasted Problem happens with all text selection/copy methods that I can find, e.g. laptop touchpad, external wireless mouse, shift-ctrl-C. Using a brand new Dell Inspiron 14 5000 series laptop. Text can be copied fine from other application windows (e.g. gedit) and then pasted into the terminal window. So it seems to be just the copy operation in the terminal window that does not work. Also, I can't believe this is really broken and not reported, because many many people would quickly notice this. I can't think what I can do wrong to have caused this problem. But yet here I am? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 14:10:48 2017 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2017-10-13 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1723884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1723884] [NEW] Copy of text from terminal window does not copy
Public bug reported: - do a default install of Ubuntu 17.10 - open a terminal window - select some text, click and select "Copy" - go to any other application and try to paste the text Expected: The text is pasted Actual: There is no text pasted Problem happens with all text selection/copy methods that I can find, e.g. laptop touchpad, external wireless mouse, shift-ctrl-C. Using a brand new Dell Inspiron 14 5000 series laptop. Text can be copied fine from other application windows (e.g. gedit) and then pasted into the terminal window. So it seems to be just the copy operation in the terminal window that does not work. Also, I can't believe this is really broken and not reported, because many many people would quickly notice this. I can't think what I can do wrong to have caused this problem. But yet here I am? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 14:10:48 2017 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2017-10-13 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages wayland-session -- 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/1723884 Title: Copy of text from terminal window does not copy Status in gnome-terminal package in Ubuntu: New Bug description: - do a default install of Ubuntu 17.10 - open a terminal window - select some text, click and select "Copy" - go to any other application and try to paste the text Expected: The text is pasted Actual: There is no text pasted Problem happens with all text selection/copy methods that I can find, e.g. laptop touchpad, external wireless mouse, shift-ctrl-C. Using a brand new Dell Inspiron 14 5000 series laptop. Text can be copied fine from other application windows (e.g. gedit) and then pasted into the terminal window. So it seems to be just the copy operation in the terminal window that does not work. Also, I can't believe this is really broken and not reported, because many many people would quickly notice this. I can't think what I can do wrong to have caused this problem. But yet here I am? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-terminal 3.24.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 16 14:10:48 2017 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2017-10-13 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1723884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696589] Re: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while
It's my lucky day. Pulseaudio has failed several times today. I see this in syslog for only one of the failures: $ grep -Ei "alsa|pulseaudio|usb" /var/log/syslog Jun 7 14:50:15 phord-x1 pulseaudio[9173]: CLI got EOF from user. Jun 7 14:50:15 phord-x1 pulseaudio[9173]: Freed 27 "UNIX socket client" Jun 7 14:50:15 phord-x1 pulseaudio[9173]: Created 28 "UNIX socket client" Jun 7 14:50:15 phord-x1 pulseaudio[9173]: CLI got EOF from user. Jun 7 14:50:15 phord-x1 pulseaudio[9173]: Freed 28 "UNIX socket client" Jun 7 14:50:32 phord-x1 pulseaudio[9173]: Created 29 "UNIX socket client" Jun 7 15:16:36 phord-x1 pulseaudio[9173]: Got POLLNVAL from ALSA Jun 7 15:16:36 phord-x1 pulseaudio[9173]: Could not recover from POLLERR|POLLNVAL|POLLHUP with snd_pcm_prepare(): No such device Jun 7 15:16:36 phord-x1 kernel: [26867.240852] usb 1-4.1.4: reset full-speed USB device number 18 using xhci_hcd After this I ran pulseaudio manually. An hour or so later it quit. Not much detail, though: $ time LANG=C pulseaudio - --log-time=1 > ~/pulseverbose.log 2>&1 [1]17630 killed LANG=C pulseaudio - --log-time=1 > ~/pulseverbose.log 2>&1 LANG=C pulseaudio - --log-time=1 > ~/pulseverbose.log 2>&1 32.48s user 29.58s system 1% cpu 1:08:45.80 total I've attached the log from that 2nd failure (PID=17630). I don't have the log from the first one because I had restarted it manually without logs earlier in the day. ** Attachment added: "pulseaudio log from another failure" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+attachment/4891739/+files/pulseverbose.log.gz -- 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/1696589 Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 16.10 The pulseaudio daemon dies occasionally. It's probably caused by audio output activity, but I can't be sure it always stops during playback because I can't always hear it (headphones plugged in but not on my head). It doesn't seem to die as much when I'm not playing audio, however. The included log collected by `ubuntu-bug audio` does not represent the bug. It does not occur frequently enough to capture it while creating this report. But I have capture logs of several crashes in the past. A month or so ago I added this to my /etc/pulse/client.conf: ; Added for debugging pulseaudio failures ; https://wiki.ubuntu.com/PulseAudio/Log ; Maybe related: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324 extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log --log-time=1 I have attached some of the logs up the point of failure to this report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: phord 9173 F...m pulseaudio /dev/snd/controlC1: phord 9173 F pulseaudio /dev/snd/pcmC0D0c: phord 9173 F...m pulseaudio /dev/snd/controlC0: phord 9173 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 7 14:48:59 2017 InstallationDate: Installed on 2017-02-17 (110 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: ThinkPad OneLink Plus Dock Audio - ThinkPad OneLink Plus Dock Audi Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FB005LUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB005LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB005LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FB005LUS dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696589] Re: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while
** Attachment added: "log up to point of failure, but I don't remember details of activity at the time" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+attachment/4891707/+files/pulseverbose.log.4.gz -- 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/1696589 Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 16.10 The pulseaudio daemon dies occasionally. It's probably caused by audio output activity, but I can't be sure it always stops during playback because I can't always hear it (headphones plugged in but not on my head). It doesn't seem to die as much when I'm not playing audio, however. The included log collected by `ubuntu-bug audio` does not represent the bug. It does not occur frequently enough to capture it while creating this report. But I have capture logs of several crashes in the past. A month or so ago I added this to my /etc/pulse/client.conf: ; Added for debugging pulseaudio failures ; https://wiki.ubuntu.com/PulseAudio/Log ; Maybe related: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324 extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log --log-time=1 I have attached some of the logs up the point of failure to this report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: phord 9173 F...m pulseaudio /dev/snd/controlC1: phord 9173 F pulseaudio /dev/snd/pcmC0D0c: phord 9173 F...m pulseaudio /dev/snd/controlC0: phord 9173 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 7 14:48:59 2017 InstallationDate: Installed on 2017-02-17 (110 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: ThinkPad OneLink Plus Dock Audio - ThinkPad OneLink Plus Dock Audi Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FB005LUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB005LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB005LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FB005LUS dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696589] Re: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while
Each time this failure occurs it is sufficient to run "pulseaudio --start" to get my devices back online, then restart the audio apps so they can find the device again. I normally use the external audio device (headphone jack) on a hot- plugged ThinkPad OneLink Plus dock. I have not seen pulseaudio fail when the laptop is not docked, but I don't listen to audio much in that mode. The failure does not seem to be coincident with plug/unplug actions. It seems to be tied to audio playback. -- 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/1696589 Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 16.10 The pulseaudio daemon dies occasionally. It's probably caused by audio output activity, but I can't be sure it always stops during playback because I can't always hear it (headphones plugged in but not on my head). It doesn't seem to die as much when I'm not playing audio, however. The included log collected by `ubuntu-bug audio` does not represent the bug. It does not occur frequently enough to capture it while creating this report. But I have capture logs of several crashes in the past. A month or so ago I added this to my /etc/pulse/client.conf: ; Added for debugging pulseaudio failures ; https://wiki.ubuntu.com/PulseAudio/Log ; Maybe related: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324 extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log --log-time=1 I have attached some of the logs up the point of failure to this report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: phord 9173 F...m pulseaudio /dev/snd/controlC1: phord 9173 F pulseaudio /dev/snd/pcmC0D0c: phord 9173 F...m pulseaudio /dev/snd/controlC0: phord 9173 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 7 14:48:59 2017 InstallationDate: Installed on 2017-02-17 (110 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: ThinkPad OneLink Plus Dock Audio - ThinkPad OneLink Plus Dock Audi Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FB005LUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB005LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB005LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FB005LUS dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696589] Re: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while
** Attachment added: "log up to point of failure, but I don't remember details of activity at the time" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+attachment/4891706/+files/pulseverbose.log.3.gz -- 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/1696589 Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: On Ubuntu 16.10 The pulseaudio daemon dies occasionally. It's probably caused by audio output activity, but I can't be sure it always stops during playback because I can't always hear it (headphones plugged in but not on my head). It doesn't seem to die as much when I'm not playing audio, however. The included log collected by `ubuntu-bug audio` does not represent the bug. It does not occur frequently enough to capture it while creating this report. But I have capture logs of several crashes in the past. A month or so ago I added this to my /etc/pulse/client.conf: ; Added for debugging pulseaudio failures ; https://wiki.ubuntu.com/PulseAudio/Log ; Maybe related: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324 extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log --log-time=1 I have attached some of the logs up the point of failure to this report. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: phord 9173 F...m pulseaudio /dev/snd/controlC1: phord 9173 F pulseaudio /dev/snd/pcmC0D0c: phord 9173 F...m pulseaudio /dev/snd/controlC0: phord 9173 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 7 14:48:59 2017 InstallationDate: Installed on 2017-02-17 (110 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: ThinkPad OneLink Plus Dock Audio - ThinkPad OneLink Plus Dock Audi Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET43W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FB005LUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB005LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB005LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FB005LUS dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
