[Desktop-packages] [Bug 1835024] Re: firefox fails to use the default profile from classic snaps
** Changed in: firefox (Ubuntu) Status: In Progress => Fix Committed ** Changed in: firefox (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1835024 Title: firefox fails to use the default profile from classic snaps Status in Mozilla Firefox: Fix Released Status in snapd: Invalid Status in firefox package in Ubuntu: Fix Committed Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874020] Re: Jack clients cannot use real-time scheduling with kernel 5.4.0-25-generic
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- 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/1874020 Title: Jack clients cannot use real-time scheduling with kernel 5.4.0-25-generic Status in lightdm package in Ubuntu: Confirmed Bug description: With kernels 5.4.0-24-generic and 5.4.0-25-generic Jack client applications can no longer use real-time scheduling. Kernel 5.4.0-23-generic works. For example starting guitarix or ardour produces the following logs on stderr: Cannot use real-time scheduling (RR/5)(1: Operation not permitted) JackClient::AcquireSelfRealTime error The following is a strace from an older (working) kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7fd5c307c000 mprotect(0x7fd5c307d000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7fd5c387b9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[47564], tls=0x7fd5c3 87c700, child_tidptr=0x7fd5c387c9d0) = 47564 sched_setscheduler(47564, SCHED_FIFO, [1]) = 0 Compare against an strace with an affected kernel: sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 sched_get_priority_min(SCHED_FIFO) = 1 sched_get_priority_max(SCHED_FIFO) = 99 mmap(NULL, 8392704, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_STACK, -1, 0) = 0x7f8d827ee000 mprotect(0x7f8d827ef000, 8388608, PROT_READ|PROT_WRITE) = 0 clone(child_stack=0x7f8d82fed9f0, flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CL ONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID, parent_tid=[21592], tls=0x7f8d82 fee700, child_tidptr=0x7f8d82fee9d0) = 21592 sched_setscheduler(21592, SCHED_FIFO, [1]) = -1 EPERM (Operation not permitted) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1874020/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899254] Re: Drag & Drop not working
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1899254 Title: Drag & Drop not working Status in nautilus package in Ubuntu: Expired Bug description: After the latest update, Nautilus file manager in 20.04 no longer offers file drag and drop. You cannot select or even move the file(s) to another Nautilus window. Right context window commands still function. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 07:54:14 2020 InstallationDate: Installed on 2020-07-28 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox 2020.03.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1899254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899116] Re: gnome-font-viewer crashed with SIGSEGV in font_infos_loaded()
[Expired for gnome-font-viewer (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-font-viewer (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1899116 Title: gnome-font-viewer crashed with SIGSEGV in font_infos_loaded() Status in gnome-font-viewer package in Ubuntu: Expired Bug description: Install late font family. After every one font install font installer window automatically closed. It`s normal? ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-font-viewer 3.34.0-2 ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13 Uname: Linux 5.8.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri Oct 9 04:26:13 2020 ExecutablePath: /usr/bin/gnome-font-viewer InstallationDate: Installed on 2020-10-08 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcCmdline: /usr/bin/gnome-font-viewer --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x56011a0005a3:mov0x8(%rax),%r8d PC (0x56011a0005a3) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%r8d" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-font-viewer StacktraceTop: ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-font-viewer crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1899116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899313] Re: GNOME Shell consumes a lot of memory - Groovy
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1899313 Title: GNOME Shell consumes a lot of memory - Groovy Status in gnome-shell package in Ubuntu: Expired Bug description: Since the update to Groovy, Shell consumption has increased drastically, in some cases more than 90% available is consumed, the only solution is to restart the interface. Captures: https://imgur.com/a/nPsXABh ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-21.22-generic 5.8.13 Uname: Linux 5.8.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu49 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 22:43:19 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-18 (84 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-07 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835024]
Hi, Phabricator show this bug has this tag : testing-exception-other (Please leave a comment explaining why). Removing check-in needed because of that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1835024 Title: firefox fails to use the default profile from classic snaps Status in Mozilla Firefox: Fix Released Status in snapd: Invalid Status in firefox package in Ubuntu: In Progress Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835024]
Pushed by stran...@redhat.com: https://hg.mozilla.org/integration/autoland/rev/51d1c7feaa42 Check for the actual snap name when detecting whether running as a snap. r=stransky -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1835024 Title: firefox fails to use the default profile from classic snaps Status in Mozilla Firefox: Fix Released Status in snapd: Invalid Status in firefox package in Ubuntu: In Progress Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835024]
https://hg.mozilla.org/mozilla-central/rev/51d1c7feaa42 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1835024 Title: firefox fails to use the default profile from classic snaps Status in Mozilla Firefox: Fix Released Status in snapd: Invalid Status in firefox package in Ubuntu: In Progress Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835024] Re: firefox fails to use the default profile from classic snaps
** Changed in: firefox Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1835024 Title: firefox fails to use the default profile from classic snaps Status in Mozilla Firefox: Fix Released Status in snapd: Invalid Status in firefox package in Ubuntu: In Progress Bug description: Hi, I've recently made a clean install of Ubuntu 19.10 (development release) and have noticed that whenever I try to open a link from one of the snap apps (being it Slack or Skype) the links although opened in the default browser are being opened in a separate session of the web browser. I am using Firefox and it is installed as a regular deb package (default). This is wrong and causes issues with history, sessions and settings not being shared between these windows. Now I have the default browser I use + a separate session for Slack and another one for Skype. Not to mention Firefox also acts just like another Slack/Skype window so dash displays these as two instances of the same app. To reproduce: * Install Ubuntu 19.10 (not sure if upgrade from 19.04 would lead to the same behaviour). * Confirm FFox is installed as a regular deb package. * Install I suppose almost any snap app, although I've only reproduced this with Slack and Skype and haven't tried to install other apps. System monitor also seems to be installed but when trying to open links from the about window - translators - individual names, it seems to do nothing. On the other hand Gnome calculator which is also installed as a snap package opens the link in the about dialog correctly = in my default browser session. ``` :~# which gnome-calculator /snap/bin/gnome-calculator ``` Thank you very much for looking into that. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1835024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I have followed this guide https://davidwpearson.wordpress.com/2020/01/10/lenovo-laptop-subwoofers-and-linux/#fix i don't think it did a thing for the subwoofer, but it manages to sound a bit nicer -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907870] [NEW] Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9
Public bug reported: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via HDMI, the screen is detected (i can see it in display settings) but the external monitor remains black. Seams like a bad frequency or resolution. I tried adding a new mode to xrandr with no luck. Also i tried different versions of kernels from 5.4 to 5.9. I am using Ubuntu 20.10 This is my lspci 0:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:12.0 Signal processing controller: Intel Corporation Comet Lake Thermal Subsytem 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:14.3 Network controller: Intel Corporation Wireless-AC 9462 00:14.5 SD Host controller: Intel Corporation Device 02f5 00:15.0 Serial bus controller [0c80]: Intel Corporation Serial IO I2C Host Controller 00:16.0 Communication controller: Intel Corporation Comet Lake Management Engine Interface 00:17.0 SATA controller: Intel Corporation Comet Lake SATA AHCI Controller 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Multimedia audio controller: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake SPI (flash) Controller 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) 02:00.0 Non-Volatile memory controller: Sandisk Corp Device 5009 (rev 01) inxi -Gx output: Graphics: Device-1: Intel UHD Graphics vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 Device-2: Lite-On HP HD Camera type: USB driver: uvcvideo bus ID: 1-2:2 Display: x11 server: X.Org 1.20.9 driver: modesetting unloaded: fbdev,vesa resolution: 1366x768~60Hz OpenGL: renderer: Mesa Intel UHD Graphics (CML GT2) v: 4.6 Mesa 20.2.1 direct render: Yes xrandr output (with hdmi cable connected to external monitor): Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384 eDP-1 connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 309mm x 173mm 1366x768 60.06*+ 40.04 1360x768 59.8059.96 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 50.0059.94 1920x1080i60.0050.0059.94 1600x1200 60.00 1680x1050 59.88 1280x1024 75.0260.02 1440x900 74.9859.90 1280x960 60.00 1280x800 59.91 1152x864 75.00 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 832x624 74.55 800x600 72.1975.0060.3256.25 720x576 50.00 720x480 60.0059.94 640x480 75.0072.8166.6760.0059.94 720x400 70.08 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1907870 Title: Secondary screen detected but black screen with Intel UHD graphics on kernel 5.9 Status in xorg package in Ubuntu: New Bug description: Hi! I have an HP ProBook 440 G7 with i7-10510U and INTEL UHD GRAPHICS. The problem: When i connect to my external monitor (a Samsung BX2250) via
[Desktop-packages] [Bug 1907865] [NEW] Xorg crash
Public bug reported: I can't reliably reproduce this crash, and I don't know, even approximately, what's causing it, or what I might be doing to possibly cause it. It just randomly crashes, and dumps me back to the login screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 11 15:35:06 2020 DistUpgraded: 2020-10-07 09:25:09,468 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06de] InstallationDate: Installed on 2016-12-06 (1466 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-10-07 (65 days ago) dmi.bios.date: 06/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.3 dmi.board.name: 0VHKV0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0VHKV0:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.product.sku: 06DE dmi.sys.vendor: Dell Inc. modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-12-09T15:53:03.120486 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri Aug 17 21:02:51 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1523 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash focal 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/1907865 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: I can't reliably reproduce this crash, and I don't know, even approximately, what's causing it, or what I might be doing to possibly cause it. It just randomly crashes, and dumps me back to the login screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 11 15:35:06 2020 DistUpgraded: 2020-10-07 09:25:09,468 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06de] InstallationDate: Installed on 2016-12-06 (1466 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5470 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-56-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to focal on 2020-10-07 (65 days ago) dmi.bios.date: 06/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.3 dmi.board.name: 0VHKV0 dmi.board.vendor: Dell Inc. dmi.board.version: A00
[Desktop-packages] [Bug 1826290] Re: geoclue mozilla location api key rate limited
Update: key has not worked for several days.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Triaged
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1804431] Re: No support for Georgian lari currency sign (U+20BE)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fonts-liberation (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation in Ubuntu. https://bugs.launchpad.net/bugs/1804431 Title: No support for Georgian lari currency sign (U+20BE) Status in fonts-liberation package in Ubuntu: Confirmed Bug description: I think title describes it well. I have attached screenshot of current state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-liberation/+bug/1804431/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897765] Re: gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw accounting") from meta_window_actor_thaw() from WindowManager::_sizeChangedWindow
had same issue with vscode
added Ernst ppa and updated (cheers for that mate)
all good
fix should be added asap imo
--
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/1897765
Title:
gnome-shell crashed with signal 5 in g_log("Error in freeze/thaw
accounting") from meta_window_actor_thaw() from
WindowManager::_sizeChangedWindow
Status in Mutter:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Committed
Status in gnome-shell package in Debian:
Unknown
Bug description:
https://errors.ubuntu.com/problem/2f47b25de323a59b617efbd8ce4b9bc7789848bd
https://errors.ubuntu.com/problem/fc9ef2077ed4ee125d73f018d3f8101a2beb0605
---
Launching terminator crashes gnome-shell, happens on two separate
machines.
ProblemType: Crash
DistroRelease: Ubuntu 20.10
Package: gnome-shell 3.38.0-1ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
Uname: Linux 5.8.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 29 18:05:57 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1600706451
InstallationDate: Installed on 2019-10-14 (350 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/tjaalton
ProcEnviron:
LANG=fi_FI.UTF-8
PATH=(custom, user)
SHELL=/bin/zsh
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? ()
g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_structured_array()
UpgradeStatus: Upgraded to groovy on 2020-09-29 (0 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1897765/+subscriptions
--
Mailing list: https://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 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded)
2020-12-09, tr, 08:26 Daniel van Vugt <1872...@bugs.launchpad.net> rašė: > It seems almost always, maybe always, to be Ubuntu 20.04 suffering from > this bug. There's only one report from 20.10 and that might not even be > the same bug. So it's possible the issue was fixed in 20.10... > > I've been trying on 20.04 again and still cannot reproduce this bug. If > anyone else can then please: > > 1. Reproduce the freeze. > > 2. Reboot. > > 3. Run: > >journalctl -b-1 > prevboot.txt > >and attach the resulting text file here. > > 4. Follow all of these steps to report any crashes in gnome-shell that > might have happened around the same time: > > https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment > > ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) >Status: Confirmed => Incomplete > > ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1889436). > https://bugs.launchpad.net/bugs/1872268 > > Title: > Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside > of app icon folders (when ubuntu-dock is loaded) > > Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: > Incomplete > Status in gnome-shell-extension-ubuntu-dock source package in Focal: > Incomplete > > Bug description: > Description: Ubuntu Focal Fossa (development branch) > Release: 20.04 > > Bug: Gnome shell while opening app drawer, clicking on an app folder > and clicking on the blank area freezes gnome shell and it makes the > session completely unusable and non recoverable. > > How to reproduce: 1- Click 9 dots on bottom corner of dash (the app > launcher button), wait for the app grid to show up. > > 2- Click on an app folder to open it. > 3- Click on the blank area outside of the opened folder dialog. > 4- Gnome shell gets freezes and never come back from this state, on both > wayland session and x11 session. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-shell 3.36.1-4ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 > Uname: Linux 5.4.0-21-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.20.11-0ubuntu26 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sun Apr 12 12:00:13 2020 > DisplayManager: gdm3 > InstallationDate: Installed on 2020-04-11 (0 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 > (20200329) > RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1872268/+subscriptions > ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1872268/+attachment/5442828/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1872268 Title: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Status in gnome-shell-extension-ubuntu-dock source package in Focal: Incomplete Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app drawer, clicking on an app folder and clicking on the blank area freezes gnome shell and it makes the session completely unusable and non recoverable. How to reproduce: 1- Click 9 dots on bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Click on an app folder to open it. 3- Click on the blank area outside of the opened folder dialog. 4- Gnome shell gets freezes and never come back from this state, on both wayland session and x11 session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:00:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1907844] [NEW] [SRU] Backport icon-changes from groovy to focal
Public bug reported: [Impact] * focal users will gain the addition and refinement of more mimetype- icons, scalable-icons, devices-icons that were previously not present * will make it consistent with the icons present in gtk-common-themes snap * Backporting them to focal would greatly increase the differentiation of the file types that are existent for the average user [Test Case] * open files and have a look at archive-based files (ex: gzip,7z), virtual-box based files, dart, docker files, some files use generic mimetype-icons and some scalable icons are not consistent and missing * install yaru from ubuntu/groovy branch and github and open files again to see the refinement to the already existing mimetype and inclusion of more mimetype-icons and scalable icons [Other-info] * will be followed with changes made to ubuntu/focal branch on github ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- 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/1907844 Title: [SRU] Backport icon-changes from groovy to focal Status in yaru-theme package in Ubuntu: New Bug description: [Impact] * focal users will gain the addition and refinement of more mimetype- icons, scalable-icons, devices-icons that were previously not present * will make it consistent with the icons present in gtk-common-themes snap * Backporting them to focal would greatly increase the differentiation of the file types that are existent for the average user [Test Case] * open files and have a look at archive-based files (ex: gzip,7z), virtual-box based files, dart, docker files, some files use generic mimetype-icons and some scalable icons are not consistent and missing * install yaru from ubuntu/groovy branch and github and open files again to see the refinement to the already existing mimetype and inclusion of more mimetype-icons and scalable icons [Other-info] * will be followed with changes made to ubuntu/focal branch on github To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1907844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532264] Re: fprintd allows unauthorized root access
This bug was fixed in the package fprintd - 1.90.7-1 --- fprintd (1.90.7-1) unstable; urgency=medium * New upstream release - Fix fprintd DBus configuration (Closes: #976990) - Change details of what requires authorization - Fix various race conditions in pam_fprintd - Permit interactive authorization from fprintd utilities - Do not allow deletion while another operation is ongoing - pam: Guard strdup calls against NULL pointers * debian/patches: - Refresh - Ignore NameOwnerChanged until fprintd is running -- Marco Trevisan (Treviño) Fri, 11 Dec 2020 00:03:27 +0100 ** Changed in: fprintd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1532264 Title: fprintd allows unauthorized root access Status in fprintd: Invalid Status in fprintd package in Ubuntu: Fix Released Bug description: For some reason, fprintd-enroll does not require any special authorization to run. This means that anyone coming across or stealing a machine with it installed and which is currently logged in and for which fingerprints are enabled for sudo authentication can elevate their access to superuser by simply running fprintd-enroll and scanning their own fingers. A subsequent sudo command will then give the new user access. Even if sudo access is not granted through fingerprints, a thief could get continued access to someone's account (for subsequent logging in) if they can enroll new fingerprints without re-authenticating as the original user. This seems a security threat. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: fprintd 0.6.0-1 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 8 11:35:02 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-12-18 (21 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: fprintd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fprintd/+bug/1532264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1888495] Re: fprintd-verify fails with an USB UPEK reader
This bug was fixed in the package fprintd - 1.90.7-1 --- fprintd (1.90.7-1) unstable; urgency=medium * New upstream release - Fix fprintd DBus configuration (Closes: #976990) - Change details of what requires authorization - Fix various race conditions in pam_fprintd - Permit interactive authorization from fprintd utilities - Do not allow deletion while another operation is ongoing - pam: Guard strdup calls against NULL pointers * debian/patches: - Refresh - Ignore NameOwnerChanged until fprintd is running -- Marco Trevisan (Treviño) Fri, 11 Dec 2020 00:03:27 +0100 ** Changed in: fprintd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1888495 Title: fprintd-verify fails with an USB UPEK reader Status in fprintd package in Ubuntu: Fix Released Status in libfprint package in Ubuntu: Triaged Bug description: [ Impact ] The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It was working fine with ubuntu 16.04 and 18.04. [ Test case ] With an UPEK fingerprint reader run: - fprintd-verify Verification should work properly [ Regression potential ] Fingers are not verified lsusb shows: 0483:2016 STMicroelectronics Fingerprint Reader user@xubuntu:~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error: transfer timed out user@xubuntu:~$ fprintd-list user found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 User user has no fingers enrolled for UPEK TouchStrip. This bug is probably the same as: https://bugzilla.redhat.com/show_bug.cgi?id=1832229 Related to bug #1881380 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1888495/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907832] [NEW] package yaru-theme-icon 20.04.8 failed to install/upgrade: unable to open '/usr/share/icons/Yaru/256x256@2x/emblems/emblem-danger.png.dpkg-new': Operation not pe
Public bug reported: Automatic bug report generated ProblemType: Package DistroRelease: Ubuntu 20.04 Package: yaru-theme-icon 20.04.8 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 11 10:08:54 2020 Dependencies: DuplicateSignature: package:yaru-theme-icon:20.04.8 Unpacking yaru-theme-icon (20.04.10.1) over (20.04.8) ... dpkg: error processing archive /tmp/apt-dpkg-install-q2lxQF/24-yaru-theme-icon_20.04.10.1_all.deb (--unpack): unable to open '/usr/share/icons/Yaru/256x256@2x/emblems/emblem-danger.png.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/icons/Yaru/256x256@2x/emblems/emblem-danger.png.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-10-18 (54 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: yaru-theme Title: package yaru-theme-icon 20.04.8 failed to install/upgrade: unable to open '/usr/share/icons/Yaru/256x256@2x/emblems/emblem-danger.png.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1907832 Title: package yaru-theme-icon 20.04.8 failed to install/upgrade: unable to open '/usr/share/icons/Yaru/256x256@2x/emblems/emblem-danger.png.dpkg- new': Operation not permitted Status in yaru-theme package in Ubuntu: New Bug description: Automatic bug report generated ProblemType: Package DistroRelease: Ubuntu 20.04 Package: yaru-theme-icon 20.04.8 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 11 10:08:54 2020 Dependencies: DuplicateSignature: package:yaru-theme-icon:20.04.8 Unpacking yaru-theme-icon (20.04.10.1) over (20.04.8) ... dpkg: error processing archive /tmp/apt-dpkg-install-q2lxQF/24-yaru-theme-icon_20.04.10.1_all.deb (--unpack): unable to open '/usr/share/icons/Yaru/256x256@2x/emblems/emblem-danger.png.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/icons/Yaru/256x256@2x/emblems/emblem-danger.png.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-10-18 (54 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: yaru-theme Title: package yaru-theme-icon 20.04.8 failed to install/upgrade: unable to open '/usr/share/icons/Yaru/256x256@2x/emblems/emblem-danger.png.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1907832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906977] Re: moving cursor over dock causes old window to appear
** Description changed: More generally, desktop mis-displays 3 Variations: a) 0) open a window/app 1) minimise a window/application, causing Desktop to be visible 2) move cursor to dock (to open new app) As soon as cursor hits dock, the graphic of the minimised window (graphic that would be shown by activating "Activities") appears. It can be cleared by sweeping a window over the desktop. It only happens once, once for every time you minimise a window. b) Click "Acivities" - then click again to restore view As soon as cursor hits dock, desktop goes corrupt (large parts blank out) c) Close window As b) + + By attempting to move an icon on the Desktop, the Desktop repairs + itself. Ubuntu 20.04.1 LTS Gnome 3.36.3 64-bit nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 6 12:11:40 2020 InstallationDate: Installed on 2016-09-01 (1556 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-12-05 (1 days ago) usr_lib_nautilus: dropbox 2018.11.08 -- 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/1906977 Title: moving cursor over dock causes old window to appear Status in nautilus package in Ubuntu: New Bug description: More generally, desktop mis-displays 3 Variations: a) 0) open a window/app 1) minimise a window/application, causing Desktop to be visible 2) move cursor to dock (to open new app) As soon as cursor hits dock, the graphic of the minimised window (graphic that would be shown by activating "Activities") appears. It can be cleared by sweeping a window over the desktop. It only happens once, once for every time you minimise a window. b) Click "Acivities" - then click again to restore view As soon as cursor hits dock, desktop goes corrupt (large parts blank out) c) Close window As b) By attempting to move an icon on the Desktop, the Desktop repairs itself. Ubuntu 20.04.1 LTS Gnome 3.36.3 64-bit nautilus: Installed: 1:3.36.3-0ubuntu1 Candidate: 1:3.36.3-0ubuntu1 Version table: *** 1:3.36.3-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1.1-1ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 6 12:11:40 2020 InstallationDate: Installed on 2016-09-01 (1556 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-12-05 (1 days ago) usr_lib_nautilus: dropbox 2018.11.08 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1906977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846334] Re: cupsd assert failure: free(): invalid pointer
This has been happening for ages now. 18.04 to 20.10 are all affected -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1846334 Title: cupsd assert failure: free(): invalid pointer Status in cups package in Ubuntu: Confirmed Bug description: Just running in the background, no user action (printing) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: cups-daemon 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-16.17-generic 5.3.1 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: free(): invalid pointer Date: Tue Oct 1 19:41:35 2019 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2019-02-09 (234 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) Lpstat: device for HP_LaserJet_CM1415fn_44A808_: implicitclass://HP_LaserJet_CM1415fn_44A808_/ device for Samsung_C48x_Series_SEC84251900EE44_: implicitclass://Samsung_C48x_Series_SEC84251900EE44_/ MachineType: Dell Inc. Latitude E6530 Papersize: letter PpdFiles: HP_LaserJet_CM1415fn_44A808_: LaserJet CM1415fn - IPP Everywhere Samsung_C48x_Series_SEC84251900EE44_: C48x Series - IPP Everywhere ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-16-generic root=UUID=4cc2c833-0db9-4a3d-84d1-9f00f5785fca ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f923ecb83a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f923ecb652a "free(): invalid pointer") at malloc.c:5332 _int_free (av=, p=, have_lock=0) at malloc.c:4173 ?? () from /lib/x86_64-linux-gnu/libcups.so.2 ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2 Title: cupsd assert failure: free(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A22 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA22:bd11/30/2018:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.sku: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1846334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display
Three additional points: -This occurs with ONE external HDMI monitor connected to the dock and running as the primary display. Need not be multi-monitor. All cases I've seen involve one external monitor. -I put log information in the notes for 1897185 to show the events that preceded the suspend. -I never saw this on LTS 20.04 until after the mid-September 2020 Ubuntu updates (including, as I recall, an upstream fix for a security vulnerability; updates to 20.04.1; and an nVidia driver update all of which occurred within roughly 2 weeks). Thanks. -- 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/1841826 Title: Going to sleep instead of logging in while lid closed & external display Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have the above described problem, which seems to be very similar to bug #1716160 - laptop is in docking station and 2 monitors are connected (HDMI, DVI) - If the lid is closed and I boot the laptop I can input my credentials in the login screen and after hitting ENTER the laptop goes to sleep - If I then press the power button of the docking station the laptop wakes up and goes straight to the ubuntu environment w/o any user identification The device is a Lenovo T420 with classic docking station. Ubuntu 18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior independent of the graphics used. I do not know what to do now since the latest state of bug #1716160 is "fix released" and so I guess it should be part of the ubuntu version I use? Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 20:10:15 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'show-battery-percentage' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-08-13 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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-settings-daemon/+bug/1841826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841826] Re: Going to sleep instead of logging in while lid closed & external display
A few things that may help with this, these were noted under bug 1897185. In looking at logs when this occurred (observed on ThinkPads including T440s, T570, T480 all docked and running lid-down with external display, keyboard, etc); this behavior occurred when: -using a third-party nVidia driver for discrete graphics card; or -when a Logitech USB dongle for a Logitech wireless mouse was plugged in to the dock and the mouse turned on during power up; or -when the Dropbox app was installed and automatically loaded during startup. The behavior could be avoided by: -using the Ubuntu xorg driver for the discrete graphics card; -turning off the Logitech mouse during startup; -turning off Dropbox synching and closing that app prior to shutdown so that it would not load automatically at startup. Sharing this in hopes that it may help with debugging, and to make reproducing the issue easier? Thanks. -- 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/1841826 Title: Going to sleep instead of logging in while lid closed & external display Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have the above described problem, which seems to be very similar to bug #1716160 - laptop is in docking station and 2 monitors are connected (HDMI, DVI) - If the lid is closed and I boot the laptop I can input my credentials in the login screen and after hitting ENTER the laptop goes to sleep - If I then press the power button of the docking station the laptop wakes up and goes straight to the ubuntu environment w/o any user identification The device is a Lenovo T420 with classic docking station. Ubuntu 18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior independent of the graphics used. I do not know what to do now since the latest state of bug #1716160 is "fix released" and so I guess it should be part of the ubuntu version I use? Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 20:10:15 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'show-battery-percentage' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-08-13 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash 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-settings-daemon/+bug/1841826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907798] Re: Crash during do-release-upgrade
Turns out, a lingering install of chromium-browser-l10n may have caused the problem: # apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: fonts-hack-ttf gcc-8-base:i386 gir1.2-ibus-1.0 gnustep-base-common gnustep-base-runtime gnustep-common gstreamer1.0-gl guile-2.0-libs kio-gdrive libargon2-0 libboost-date-time1.65.1 (snip) vlc-plugin-visualization x11proto-damage-dev x11proto-fixes-dev Use 'apt autoremove' to remove them. The following packages will be REMOVED: chromium-browser-l10n 0 upgraded, 0 newly installed, 1 to remove and 618 not upgraded. 5 not fully installed or removed. After this operation, 69.6 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 322207 files and directories currently installed.) Removing chromium-browser-l10n (1:85.0.4183.83-0ubuntu0.20.04.2) ... Setting up lm-sensors (1:3.6.0-2ubuntu1) ... Setting up libglew2.1:amd64 (2.1.0-4) ... Setting up sysstat (12.2.0-2) ... Installing new version of config file /etc/init.d/sysstat ... Installing new version of config file /etc/sysstat/sysstat ... Installing new version of config file /etc/sysstat/sysstat.ioconf ... Removing obsolete conffile /etc/profile.d/sysstat.sh ... Setting up libglew-dev:amd64 (2.1.0-4) ... Processing triggers for systemd (245.4-4ubuntu3.3) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for ureadahead (0.100.0-21) ... ureadahead will be reprofiled on next reboot Processing triggers for libc-bin (2.31-0ubuntu9.1) ... Correcting dependencies... Done The following packages were automatically installed and are no longer required: chromium-browser-l10n chromium-codecs-ffmpeg-extra fonts-hack-ttf gcc-8-base:i386 gir1.2-ibus-1.0 gnustep-base-common gnustep-base-runtime gnustep-common gstreamer1.0-gl guile-2.0-libs (snip) vlc-plugin-samba vlc-plugin-video-splitter vlc-plugin-visualization x11proto-damage-dev x11proto-fixes-dev Use 'apt autoremove' to remove them. The following additional packages will be installed: chromium-browser The following packages will be upgraded: chromium-browser 1 upgraded, 0 newly installed, 0 to remove and 617 not upgraded. 5 not fully installed or removed. Need to get 0 B/48.3 kB of archives. After this operation, 234 MB disk space will be freed. Do you want to continue? [Y/n] ^C # apt remove chromium-browser Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: chromium-browser-l10n : Depends: chromium-browser (>= 1:85.0.4183.83-0ubuntu0.20.04.2) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). root@routert:~# apt --fix-broken install^C root@routert:~# apt remove chromium-browser-l10n Reading package lists... Done Building dependency tree Reading state information... Done # Somehow, apt still wanted to upgrade the chromium-browser packgage, so I removed that: # apt remove chromium-browser And after a dist-upgrade all appears to be working now. -- 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/1907798 Title: Crash during do-release-upgrade Status in chromium-browser package in Ubuntu: New Bug description: While doing a do-release upgrade from 18.04 to 20.04, I got an error. The script wanted to install the Chromium snap and apparently while doing that, it failed. Original summary generated by Launchpad: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18 Uname: Linux 4.15.0-126-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DRM.card0-HDMI-A-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: Off status: connected edid-base64: modes: 1024x768 800x600 800x600 848x480 640x480 Date: Fri Dec 11 11:37:46 2020 Desktop-Session: 'None' 'None' '/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-12-03 (1103 days ago) InstallationMedia: Kubuntu
[Desktop-packages] [Bug 1899667] Re: LO can't send email, probably an apparmour problem
The same happens on Ubuntu Gnome versions. It looks like apparmour problem. I did next steps to make it work: ln -s /etc/apparmor.d/usr.lib.libreoffice.program.oosplash /etc/apparmor.d/disable/ apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.program.oosplash ln -s /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin /etc/apparmor.d/disable/ apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.program.soffice.bin ln -s /etc/apparmor.d/usr.lib.libreoffice.program.senddoc /etc/apparmor.d/disable/ apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.program.senddoc And after that I had to replace sensible-lomua with thunderbird inside LO Tools -> Settings -> Internet -> E-mail client. I don't know why sensbile-lomua does not exist anymore and nothing else works. Even if I put xdg-email or just thunderbird. Without apparmor changes it does nothing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1899667 Title: LO can't send email, probably an apparmour problem Status in kmail package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: LO can't send email: LibreOffice was unable to find a working email configuration. I'm pretty sure this is an apparmour profile problem since LO seems to want RW perms on something and AA seems not to want to give it. There lies the full extent on mu debugging expertise in this area. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Oct 13 17:01:43 2020 InstallationDate: Installed on 2017-03-26 (1297 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-10-08 (4 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1899667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1900452] Re: /usr/bin/ubuntu-drivers:KeyError:__getitem__:/usr/bin/ubuntu-drivers@434:__call__:main:invoke:invoke:invoke:new_func:invoke:list:get_linux_modules_metapackage:get_
I can't reproduce the problem using the package in -proposed. :~$ apt-cache policy ubuntu-drivers-common ubuntu-drivers-common: Installed: 1:0.8.6.2 Candidate: 1:0.8.6.2 Version table: *** 1:0.8.6.2 500 500 http://archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:0.8.6.1 500 500 http://it.archive.ubuntu.com/ubuntu groovy/main amd64 Packages :~$ ubuntu-drivers list nvidia-driver-418-server, (kernel modules provided by linux-modules-nvidia-418-server-generic-hwe-20.04-edge) nvidia-driver-455, (kernel modules provided by linux-modules-nvidia-455-generic-hwe-20.04-edge) nvidia-driver-450-server, (kernel modules provided by linux-modules-nvidia-450-server-generic-hwe-20.04-edge) nvidia-driver-450, (kernel modules provided by linux-modules-nvidia-450-generic-hwe-20.04-edge) nvidia-driver-440-server, (kernel modules provided by linux-modules-nvidia-440-server-generic-hwe-20.04-edge) :~$ ubuntu-drivers list --gpgpu nvidia-driver-450, (kernel modules provided by linux-modules-nvidia-450-generic-hwe-20.04-edge) nvidia-driver-418-server, (kernel modules provided by linux-modules-nvidia-418-server-generic-hwe-20.04-edge) nvidia-driver-450-server, (kernel modules provided by linux-modules-nvidia-450-server-generic-hwe-20.04-edge) nvidia-driver-440-server, (kernel modules provided by linux-modules-nvidia-440-server-generic-hwe-20.04-edge) nvidia-driver-455, (kernel modules provided by linux-modules-nvidia-455-generic-hwe-20.04-edge) ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1900452 Title: /usr/bin/ubuntu-drivers:KeyError:__getitem__:/usr/bin/ubuntu- drivers@434:__call__:main:invoke:invoke:invoke:new_func:invoke:list:get_linux_modules_metapackage:get_linux_image_from_meta:__getitem__ Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Groovy: Fix Committed Bug description: SRU request: [Impact] * Listing the supported drivers can fail if the linux-restricted-modules for it are not available in the archive. * These changes unify the code for listing drivers (whether --gpgpu is passed in or not) and make it more robust. [Test Case] * Install ubuntu-drivers-common (1:0.8.6.2) from -proposed. * Call "ubuntu-drivers list" and "ubuntu-drivers list --gpgpu", and make sure that neither crashes ubuntu-drivers. [Regression Potential] * Low, the code should catch all the KeyErrors now. The Ubuntu Error Tracker has been receiving reports about a problem regarding ubuntu-drivers-common. This problem was most recently seen with package version 1:0.8.4~0.20.04.3, the problem page at https://errors.ubuntu.com/problem/db3639ed31f86cf7cd56ed9de6898519d045469d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1900452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899667] Re: LO can't send email, probably an apparmour problem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1899667 Title: LO can't send email, probably an apparmour problem Status in kmail package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: LO can't send email: LibreOffice was unable to find a working email configuration. I'm pretty sure this is an apparmour profile problem since LO seems to want RW perms on something and AA seems not to want to give it. There lies the full extent on mu debugging expertise in this area. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Oct 13 17:01:43 2020 InstallationDate: Installed on 2017-03-26 (1297 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-10-08 (4 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1899667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899667] Re: LO can't send email, probably an apparmour problem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kmail (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1899667 Title: LO can't send email, probably an apparmour problem Status in kmail package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: LO can't send email: LibreOffice was unable to find a working email configuration. I'm pretty sure this is an apparmour profile problem since LO seems to want RW perms on something and AA seems not to want to give it. There lies the full extent on mu debugging expertise in this area. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.25 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: KDE Date: Tue Oct 13 17:01:43 2020 InstallationDate: Installed on 2017-03-26 (1297 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-10-08 (4 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmail/+bug/1899667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907798] Re: Crash during do-release-upgrade
** Package changed: ubuntu => chromium-browser (Ubuntu) ** Tags removed: need-duplicate-check -- 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/1907798 Title: Crash during do-release-upgrade Status in chromium-browser package in Ubuntu: New Bug description: While doing a do-release upgrade from 18.04 to 20.04, I got an error. The script wanted to install the Chromium snap and apparently while doing that, it failed. Original summary generated by Launchpad: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18 Uname: Linux 4.15.0-126-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DRM.card0-HDMI-A-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: Off status: connected edid-base64: modes: 1024x768 800x600 800x600 848x480 640x480 Date: Fri Dec 11 11:37:46 2020 Desktop-Session: 'None' 'None' '/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-12-03 (1103 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InstalledPlugins: Load-Avg-1min: 0.65 Load-Processes-Running-Percent: 0.2% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-126-generic root=UUID=480b8792-a570-441d-b8c6-27b031b55c17 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-12-11 (0 days ago) dmi.bios.date: 01/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A88M Pro3+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd01/11/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MPro3+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1907798/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907798] [NEW] Crash during do-release-upgrade
You have been subscribed to a public bug: While doing a do-release upgrade from 18.04 to 20.04, I got an error. The script wanted to install the Chromium snap and apparently while doing that, it failed. Original summary generated by Launchpad: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-126.129-generic 4.15.18 Uname: Linux 4.15.0-126-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 DRM.card0-HDMI-A-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: Off status: connected edid-base64: modes: 1024x768 800x600 800x600 848x480 640x480 Date: Fri Dec 11 11:37:46 2020 Desktop-Session: 'None' 'None' '/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-12-03 (1103 days ago) InstallationMedia: Kubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) InstalledPlugins: Load-Avg-1min: 0.65 Load-Processes-Running-Percent: 0.2% MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-126-generic root=UUID=480b8792-a570-441d-b8c6-27b031b55c17 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-12-11 (0 days ago) dmi.bios.date: 01/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: FM2A88M Pro3+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd01/11/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88MPro3+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check third-party-packages -- Crash during do-release-upgrade https://bugs.launchpad.net/bugs/1907798 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1065126]
*** Bug 1679561 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1065126 Title: "Always do this from now on" does not work Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Downloading an unknown file type in Firefox displays a dialog for choosing which application to use for opening the file. The dialog contains a check box labelled "Always do this action from now on". Checking this option does not work: When I download a file of the same type next time, the same dialog is displayed again. This feature is broken for as long as I can remember (> 10 years). It's time it was fixed (or removed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruediger 2536 F pulseaudio BuildID: 20120907231657 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20bb,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Channel: Unavailable Date: Wed Oct 10 18:17:44 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 172.31.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 172.31.0.0/20 dev wlan0 proto kernel scope link src 172.31.9.26 metric 2 MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.2 totem-mozilla 3.0.1-0ubuntu21.1 icedtea-6-plugin 1.2-2ubuntu1.2 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago) dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 6457BBG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6457BBG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1065126/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653351]
*** Bug 1681092 has been marked as a duplicate of this bug. *** -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Confirmed Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653351]
*** Bug 1585532 has been marked as a duplicate of this bug. *** -- 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/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Confirmed Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1907782] [NEW] ERROR Service took too long to respond. Disconnecting client.
Public bug reported: Hi Team! I saw the other bug which happened, when bpool is not imported, but my bpool is imported, so I think it is another problem and so another bug. I am running ubunto focal (20.04.1) with zsys 0.4.8. When I do /sbin/zsysctl -vvv boot commit I get ... DEBUG ZFS: ending transaction DEBUG ZFS: transaction done DEBUG ZFS: transaction done ZSys is adding automatic system snapshot to GRUB menu DEBUG Sourcing file `/etc/default/grub' DEBUG Sourcing file `/etc/default/grub.d/init-select.cfg' DEBUG Generating grub configuration file ... DEBUG level=debug msg="Didn't receive any information from service in 30s" level=error msg="Service took too long to respond. Disconnecting client." Iported zpools: # zpool list NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 1,88G 717M 1,17G- - -37% 1.00xONLINE - rpool 944G 570G 374G- -14%60% 1.00xONLINE - ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Attachment added: "/sbin/zsysctl -vvv boot commit" https://bugs.launchpad.net/bugs/1907782/+attachment/5442715/+files/zsysctl_boot_commit.out -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1907782 Title: ERROR Service took too long to respond. Disconnecting client. Status in zsys package in Ubuntu: New Bug description: Hi Team! I saw the other bug which happened, when bpool is not imported, but my bpool is imported, so I think it is another problem and so another bug. I am running ubunto focal (20.04.1) with zsys 0.4.8. When I do /sbin/zsysctl -vvv boot commit I get ... DEBUG ZFS: ending transaction DEBUG ZFS: transaction done DEBUG ZFS: transaction done ZSys is adding automatic system snapshot to GRUB menu DEBUG Sourcing file `/etc/default/grub' DEBUG Sourcing file `/etc/default/grub.d/init-select.cfg' DEBUG Generating grub configuration file ... DEBUG level=debug msg="Didn't receive any information from service in 30s" level=error msg="Service took too long to respond. Disconnecting client." Iported zpools: # zpool list NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 1,88G 717M 1,17G- - -37% 1.00xONLINE - rpool 944G 570G 374G- -14%60% 1.00xONLINE - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1907782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903230] Re: Mutter release 3.36.7
Yes, that's Ubuntu bug 1900906. You can see the list of fixes expected here: https://bugs.launchpad.net/ubuntu/+source/mutter/+bugs?field.searchtext==-importance%3Alist=FIXRELEASED =fixed-in-3.36.7 ** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #1413 https://gitlab.gnome.org/GNOME/mutter/-/issues/1413 -- 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/1903230 Title: Mutter release 3.36.7 Status in mutter package in Ubuntu: Triaged Bug description: We should release mutter 3.36.7 to focal, for bug 1900906, bug 1894596 and ...? [Impact] This is the current GNOME 3.36.x stable update, including some fixes (especially crashes and memory leaks) and translation updates. https://gitlab.gnome.org/GNOME/mutter/-/blob/gnome-3-36/NEWS 3.36.7 == * Fix Night Light updates after DPMS [Jonas, Benjamin; #1392] * Fix IM handling on X11 [Carlos; #1413] * Fix resizing of attached modal dialogs on wayland [Jonas; !1446] * Fix jumps when resizing windows using discrete steps [Jonas; #1447] * Fixed crashes [Marco; !1371, #1345] * Plugged Memory leaks [Ray; !1449, !1451] * Misc. bug fixes and cleanups [Jonas, Carlos, Robert; !1218, !1460, !1463] Contributors: Marco Trevisan (Treviño), Benjamin Berg, Carlos Garnacho, Robert Mader, Ray Strode, Jonas Ådahl Translators: Juliano de Souza Camargo [pt] [Test case] The update is part of GNOME stable updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working well. [Regression potential] There have been fixes in nightlight mode, IM handling in X11 and resizing windows in Wayland. All of those should not regress after the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1903230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876352] Re: [ubuntu-dock] App Grid icons out of alignment when opening from overview
Updated to latest version and this bug still here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1876352 Title: [ubuntu-dock] App Grid icons out of alignment when opening from overview Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Affected version: Ubuntu 20.04 Gnome Shell Version 3.36.1 Only tested on xorg Bug summary: When opening the App Grid (aka "Show Applications) from the window overview (I don't know the technical terms) the icons shift out of alignment. This gets worse if you have multiple pages of apps (as I do), and it gets even worse the more you open and close the App Grid in this manner. I cannot see the same bug if you just open the App Grid from the desktop. Steps to reproduce: 1. Open the overview window using the Super Key 2. Click the "Show Applications" icon 3. You will see the icons in the App Grid shift downwards 4. Scroll down to see the icons move further out of alignment What did GNOME Shell do that was unexpected?: Display the App Window icons out of alignment when accessing the app grid via the window overview (pressing the Super key) What did you expect to happen: I expected the icons to display properly. Video of the bug: https://www.youtube.com/watch?v=IJ3EYZ2qoK4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 19:16:06 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-14 (169 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1876352/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
