[Desktop-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes Status in gnome-shell package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Description: I recently noticed a strange behavior on my (pretty vanilla) Ubuntu 18.04.2 LTS. Every time I copy some text from GNOME Terminal, using keyboard or mouse, it triggers a little hard drive activity. Intrigued, I decided to see what was going on (persistent clipboard data?). After some investigation, I found out that the activity is due to a file being written to whenever I do a copy in GNOME Terminal (or in other apps): ~/.config/nautilus/desktop-metadata The small file seems to record the nautilus view settings and the trash icon state, has no apparent relation to functions of the clipboard, and does not mutate following each write (the content stays unchanged). I also tested to see if the same happens on a different computer running 18.04.2 desktop live usb, and the answer is yes. So this shouldn't be something particular to my system. Steps to reproduce: * Boot your computer using live CD or usb created with: ubuntu-18.04.2-desktop-amd64.iso You can obtain it from: http://releases.ubuntu.com/18.04/ last modified: 2019-02-10 00:27 sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4) * Start Gnome Terminal, copy some text from there, and note the current time when you perform the copying * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's been modified at the same time you did the copying * Repeat as many times as you like Expected behavior: Copying text in Gnome should not trigger writes to some arbitrary file (and should not trigger any disk IO at all). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836881] Re: Xorg freeze
If your "mouse works fine" then Xorg is still working and it's only gnome-shell that's frozen, so reassigning... ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Summary changed: - Xorg freeze + gnome-shell freeze -- 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/1836881 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: My gnome session freezes, mouse works fine but cannot start applications. I am able to enter one of the tty terminals and kill the session. This happens a few times a day and started a week ago probably. Douglas ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 12:29:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 4.15.0-52-generic, x86_64: installed nvidia, 418.56, 4.15.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1208] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1207] InstallationDate: Installed on 2018-01-13 (550 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 002: ID 0461:4e81 Primax Electronics, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator PH317-51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=455417ef-94fe-4ab8-97b7-0b992c951267 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienna_KLS dmi.board.vendor: KBL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnPredatorPH317-51:pvrV1.05:rvnKBL:rnSienna_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH317-51 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes Status in gnome-shell package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Description: I recently noticed a strange behavior on my (pretty vanilla) Ubuntu 18.04.2 LTS. Every time I copy some text from GNOME Terminal, using keyboard or mouse, it triggers a little hard drive activity. Intrigued, I decided to see what was going on (persistent clipboard data?). After some investigation, I found out that the activity is due to a file being written to whenever I do a copy in GNOME Terminal (or in other apps): ~/.config/nautilus/desktop-metadata The small file seems to record the nautilus view settings and the trash icon state, has no apparent relation to functions of the clipboard, and does not mutate following each write (the content stays unchanged). I also tested to see if the same happens on a different computer running 18.04.2 desktop live usb, and the answer is yes. So this shouldn't be something particular to my system. Steps to reproduce: * Boot your computer using live CD or usb created with: ubuntu-18.04.2-desktop-amd64.iso You can obtain it from: http://releases.ubuntu.com/18.04/ last modified: 2019-02-10 00:27 sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4) * Start Gnome Terminal, copy some text from there, and note the current time when you perform the copying * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's been modified at the same time you did the copying * Repeat as many times as you like Expected behavior: Copying text in Gnome should not trigger writes to some arbitrary file (and should not trigger any disk IO at all). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- 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/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes Status in gnome-shell package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Description: I recently noticed a strange behavior on my (pretty vanilla) Ubuntu 18.04.2 LTS. Every time I copy some text from GNOME Terminal, using keyboard or mouse, it triggers a little hard drive activity. Intrigued, I decided to see what was going on (persistent clipboard data?). After some investigation, I found out that the activity is due to a file being written to whenever I do a copy in GNOME Terminal (or in other apps): ~/.config/nautilus/desktop-metadata The small file seems to record the nautilus view settings and the trash icon state, has no apparent relation to functions of the clipboard, and does not mutate following each write (the content stays unchanged). I also tested to see if the same happens on a different computer running 18.04.2 desktop live usb, and the answer is yes. So this shouldn't be something particular to my system. Steps to reproduce: * Boot your computer using live CD or usb created with: ubuntu-18.04.2-desktop-amd64.iso You can obtain it from: http://releases.ubuntu.com/18.04/ last modified: 2019-02-10 00:27 sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4) * Start Gnome Terminal, copy some text from there, and note the current time when you perform the copying * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's been modified at the same time you did the copying * Repeat as many times as you like Expected behavior: Copying text in Gnome should not trigger writes to some arbitrary file (and should not trigger any disk IO at all). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836881] Re: gnome-shell freeze
Next time the problem happens, log into a tty and find the PID of the frozen gnome-shell process. Then run: apport-cli --hanging -P PID where PID is the process ID of the frozen gnome-shell process (which is the one running as your own user ID, not gdm). That should create a new bug/crash report. Please send us a link to that. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1836881 Title: gnome-shell freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: My gnome session freezes, mouse works fine but cannot start applications. I am able to enter one of the tty terminals and kill the session. This happens a few times a day and started a week ago probably. Douglas ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 12:29:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 4.15.0-52-generic, x86_64: installed nvidia, 418.56, 4.15.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1208] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1207] InstallationDate: Installed on 2018-01-13 (550 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 002: ID 0461:4e81 Primax Electronics, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator PH317-51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=455417ef-94fe-4ab8-97b7-0b992c951267 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienna_KLS dmi.board.vendor: KBL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnPredatorPH317-51:pvrV1.05:rvnKBL:rnSienna_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH317-51 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836881/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
** No longer affects: ubuntu ** Tags added: performance -- 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/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes Status in gnome-shell package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: Description: I recently noticed a strange behavior on my (pretty vanilla) Ubuntu 18.04.2 LTS. Every time I copy some text from GNOME Terminal, using keyboard or mouse, it triggers a little hard drive activity. Intrigued, I decided to see what was going on (persistent clipboard data?). After some investigation, I found out that the activity is due to a file being written to whenever I do a copy in GNOME Terminal (or in other apps): ~/.config/nautilus/desktop-metadata The small file seems to record the nautilus view settings and the trash icon state, has no apparent relation to functions of the clipboard, and does not mutate following each write (the content stays unchanged). I also tested to see if the same happens on a different computer running 18.04.2 desktop live usb, and the answer is yes. So this shouldn't be something particular to my system. Steps to reproduce: * Boot your computer using live CD or usb created with: ubuntu-18.04.2-desktop-amd64.iso You can obtain it from: http://releases.ubuntu.com/18.04/ last modified: 2019-02-10 00:27 sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4) * Start Gnome Terminal, copy some text from there, and note the current time when you perform the copying * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's been modified at the same time you did the copying * Repeat as many times as you like Expected behavior: Copying text in Gnome should not trigger writes to some arbitrary file (and should not trigger any disk IO at all). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1836960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793496] Re: scaling changes when closing/re-opening the lid
** Tags added: xrandr-scaling -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1793496 Title: scaling changes when closing/re-opening the lid Status in Mutter: New Status in mutter package in Ubuntu: Fix Released Bug description: scaling changes when closing/re-opening the lid. Seen in bionic. Mz scaling is set to 100%, but the laptop is considered highdpi by mutter, and during suspend/resume it changes back to default ignoring settings. $ xprop -spy -root RESOURCE_MANAGER [...] RESOURCE_MANAGER(STRING) = "*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n" RESOURCE_MANAGER(STRING) = "*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n" xrandr Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 309mm x 174mm 2560x1440 60.00*+ 59.9959.9959.9659.95 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1793496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1836960 Title: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes Status in Ubuntu: New Status in gnome-shell package in Ubuntu: New Status in nautilus package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Description: I recently noticed a strange behavior on my (pretty vanilla) Ubuntu 18.04.2 LTS. Every time I copy some text from GNOME Terminal, using keyboard or mouse, it triggers a little hard drive activity. Intrigued, I decided to see what was going on (persistent clipboard data?). After some investigation, I found out that the activity is due to a file being written to whenever I do a copy in GNOME Terminal (or in other apps): ~/.config/nautilus/desktop-metadata The small file seems to record the nautilus view settings and the trash icon state, has no apparent relation to functions of the clipboard, and does not mutate following each write (the content stays unchanged). I also tested to see if the same happens on a different computer running 18.04.2 desktop live usb, and the answer is yes. So this shouldn't be something particular to my system. Steps to reproduce: * Boot your computer using live CD or usb created with: ubuntu-18.04.2-desktop-amd64.iso You can obtain it from: http://releases.ubuntu.com/18.04/ last modified: 2019-02-10 00:27 sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4) * Start Gnome Terminal, copy some text from there, and note the current time when you perform the copying * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's been modified at the same time you did the copying * Repeat as many times as you like Expected behavior: Copying text in Gnome should not trigger writes to some arbitrary file (and should not trigger any disk IO at all). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1836960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
In that same update, I also upgraded the Mesa package: 2019-07-07 06:50:41 upgrade libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:41 status half-configured libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:41 status unpacked libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:41 status half-installed libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:42 status half-installed libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:42 status unpacked libegl-mesa0:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:42 status unpacked libegl-mesa0:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:42 upgrade libgbm1:amd64 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:42 status half-configured libgbm1:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:43 status unpacked libgbm1:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:43 status half-installed libgbm1:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:43 status half-installed libgbm1:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:43 status unpacked libgbm1:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:43 status unpacked libgbm1:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:43 install libllvm8:i386 1:8-3~ubuntu18.04.1 2019-07-07 06:50:43 status half-installed libllvm8:i386 1:8-3~ubuntu18.04.1 2019-07-07 06:50:48 status unpacked libllvm8:i386 1:8-3~ubuntu18.04.1 2019-07-07 06:50:48 status unpacked libllvm8:i386 1:8-3~ubuntu18.04.1 2019-07-07 06:50:49 upgrade libgl1-mesa-dri:amd64 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:49 status half-configured libgl1-mesa-dri:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:49 status unpacked libgl1-mesa-dri:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:49 status half-configured libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:49 status half-installed libgl1-mesa-dri:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:51 status half-installed libgl1-mesa-dri:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:51 status unpacked libgl1-mesa-dri:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:51 status unpacked libgl1-mesa-dri:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:51 upgrade libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:51 status half-configured libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:51 status unpacked libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:52 status half-installed libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:53 status half-installed libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:54 status unpacked libgl1-mesa-dri:i386 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:54 status unpacked libgl1-mesa-dri:i386 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:54 install libllvm8:amd64 1:8-3~ubuntu18.04.1 2019-07-07 06:50:54 status half-installed libllvm8:amd64 1:8-3~ubuntu18.04.1 2019-07-07 06:50:58 status unpacked libllvm8:amd64 1:8-3~ubuntu18.04.1 2019-07-07 06:50:58 status unpacked libllvm8:amd64 1:8-3~ubuntu18.04.1 2019-07-07 06:50:59 upgrade libglx-mesa0:i386 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:50:59 status half-configured libglx-mesa0:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:59 status unpacked libglx-mesa0:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:59 status half-configured libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:59 status half-installed libglx-mesa0:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:50:59 status half-installed libglx-mesa0:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:00 status unpacked libglx-mesa0:i386 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:51:00 status unpacked libglx-mesa0:i386 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:51:00 upgrade libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:51:00 status half-configured libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:00 status unpacked libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:00 status half-installed libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:01 status half-installed libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:01 status unpacked libglx-mesa0:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:51:01 status unpacked libglx-mesa0:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:51:01 upgrade libglapi-mesa:amd64 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1 2019-07-07 06:51:01 status half-configured libglapi-mesa:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:01 status unpacked libglapi-mesa:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:01 status half-configured libglapi-mesa:i386 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:02 status half-installed libglapi-mesa:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:02 status half-installed libglapi-mesa:amd64 18.2.8-0ubuntu0~18.04.2 2019-07-07 06:51:02 status unpacked libglapi-mesa:amd64 19.0.2-1ubuntu1.1~18.04.1 2019-07-07
[Desktop-packages] [Bug 1836979] [NEW] Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
Public bug reported: I’m not exactly sure if this belongs here, libva, mesa, or upstream somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that program is. Kodi has worked just fine on my system, as recently as July 7th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to- desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- XBMC PPA) since its release in June, but in between July 7th and 16th, I did upgrade Nouveau: 2019-07-07 06:51:44 configure libdrm-nouveau2:amd64 2.4.97-ubuntu1~18.04.1 2019-07-07 06:51:44 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status half-configured libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status installed libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 configure libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status unpacked libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status half-configured libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-07 06:51:44 status installed libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 (Another reason I’m guessing this is a Nouveau problem is because I later tried switching to the official NVidia drivers, didn’t get this bug, and then later encountered a distinct yet worse bug that locks up the whole system. So, now I’m back to using Nouveau.) I tried looking in Xorg.0.log: [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620 [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines: [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz eP) …that’s all that appears in the log when I try to load Kodi and a crash happens. I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if you need more information, I’ve attached a hardinfo report, too. I hope this bug can get fixed, soon. Thanks! ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Information on Tina’s hardware" https://bugs.launchpad.net/bugs/1836979/+attachment/5277708/+files/hardinfo_report_2019-07-17.html ** Description changed: I’m not exactly sure if this belongs here, libva, mesa, or upstream somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that program is. Kodi has worked just fine on my system, as recently as July 7th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to- desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- - XBMC PPA) for months, but in between July 7th and 16th, I did upgrade - Nouveau: + XBMC PPA) since its release in June, but in between July 7th and 16th, I + did upgrade Nouveau: 2019-07-16 17:33:05 upgrade libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:05 status half-configured libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:05 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:05 status half-installed libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:05 status half-installed libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:05 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:05 status unpacked libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:06 upgrade libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:06 status half-configured libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 2019-07-16 17:33:06 status unpacked libdrm-nouveau2:i386
[Desktop-packages] [Bug 1768169] Re: touchscreen doesn't work properly after stylus detection
The problem should be fixed in git, and available in the 1.14.0. I don't think there's a workaround other than building from source; but it should be possible to address it that way. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1768169 Title: touchscreen doesn't work properly after stylus detection Status in xinput package in Ubuntu: Confirmed Bug description: I have a HP Pavilion x360 convertible 15 br0xx. This laptop has a multitouch touchscreen and an active pen/stylus. On ubuntu 16.04, the touchscreen used with fingers and the pen/stylus work properly. The touchscreen was identified as «ELAN0732:00 04F3:24B8» as slave pointer and the pen as «ELAN0732:00 04F3:24B8 Pen» as slave pointer too. But, on ubuntu 18.04 bionic with gnome shell, the pen/stylus is identified «ELAN0732:00 04F3:24B8 Pen» as slave keyboard instead as slave pointer. Touchscreen work well until pen/stylus is used. At this point, a new device «ELAN0732:00 04F3:24B8 Pen Pen (0)» is enabled. The touchscreen stops working and the pen/styles works but with some issues. ~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=15 [slave pointer (2)] ⎜ ↳ ELAN0732:00 04F3:24B8 id=10 [slave pointer (2)] ⎜ ↳ ELAN0732:00 04F3:24B8 Pen Pen (0) id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ HP Wide Vision HD Camera: HP Wi id=9[slave keyboard (3)] ↳ Intel Virtual Button driver id=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=16 [slave keyboard (3)] ↳ HP Wireless hotkeys id=17 [slave keyboard (3)] ↳ ELAN0732:00 04F3:24B8 Pen id=11 [slave keyboard (3)] After disable devices id=11 and id=18, touchscreen recovers its multitouch feature. There is no combination enabling/disabling ids 10, 11 and 18, to get multitouch and pen working together. On Wayland session, I get the same behavior. Note: Ubuntu 18.04 LTS clean installation with «minimal install option» and no other customization. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1768169/+subscriptions -- Mailing list: https://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 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
Bug solved! In my case, the Laine gnome-shell extension was causing all the problems. when I turned the Laine extension off both google-chrome and chromium versions 75 (newest updates) worked again. Both video and audio playback ran normally again. On Tue, Jul 16, 2019 at 2:51 PM BavarianPH wrote: > ** Attachment added: "Security_log" > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1835623/+attachment/5277514/+files/log_messages_Security.log > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1835623 > > Title: > Google Chrome Linux version 75 freezes and then crashes when trying to > play any video > > Status in chromium-browser package in Ubuntu: > New > > Bug description: > (upstream bug report: > https://bugs.chromium.org/p/chromium/issues/detail?id=983203) > > Ubuntu 18.04 > I expect Chrome to play videos. > When I try to play any video on Google Chrome for Linux, any version of > 75 or higher, Google Chrome freezes. > Chrome 75 will allow sound but no video. > All mouse clicks become unresponsive. > Attempting to close Chrome after many mouse clicks causes Chrome to > crash. > Even worse it often also crashes Ubuntu 18.04. > Google Chrome 74 or lower work without any problems playing videos. > It is a Google Chrome Linux version 75 or higher problem. > I cannot believe that neither Google or Ubuntu or any other Linux OS > seem to completely ignore this extremely serious problem. > I am forced to install Google Chrome 71 to fix video playback problem. > I posted on Ubuntu ask, and show over 90 views but no comments. > One answer confirms that he has the exact same problem. > --- > ProblemType: Bug > ApportVersion: 2.20.9-0ubuntu7.6 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Desktop-Session: >'ubuntu' >'/etc/xdg/xdg-ubuntu:/etc/xdg' >'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' > DetectedPlugins: > > DistroRelease: Ubuntu 18.04 > Env: >'None' >'None' > InstallationDate: Installed on 2019-05-02 (66 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20181019) > Load-Avg-1min: 1.47 > Load-Processes-Running-Percent: 0.1% > MachineType: MSI MS-7641 > NonfreeKernelModules: nvidia_modeset nvidia > Package: chromium-browser 75.0.3770.90-0ubuntu0.18.04.1 > PackageArchitecture: amd64 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic > root=UUID=7181ee96-0bd0-4b3c-9100-fa205ef6bd1d ro quiet splash vt.handoff=1 > ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 > Tags: bionic > Uname: Linux 4.15.0-55-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm adm cdrom cdrom dip dip lpadmin lpadmin plugdev plugdev > sambashare sambashare sudo sudo > _MarkForUpload: True > dmi.bios.date: 04/20/2015 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: V25.1 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: 760GMA-P34(FX) (MS-7641) > dmi.board.vendor: MSI > dmi.board.version: 5.0 > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: MSI > dmi.chassis.version: 5.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrV25.1:bd04/20/2015:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0: > dmi.product.family: To Be Filled By O.E.M. > dmi.product.name: MS-7641 > dmi.product.version: 5.0 > dmi.sys.vendor: MSI > etcconfigcpepperflashpluginnonfree: >flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" >flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f > 2 | sed -e "s/,/./g"` >CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso > --ppapi-flash-version=$flashversion" > modified.conffile..etc.default.chromium-browser: [deleted] > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1835623/+subscriptions > -- 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/1835623 Title: Google Chrome Linux version 75 freezes and then crashes when trying to play any video Status in chromium-browser package in Ubuntu: New Bug description: (upstream bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=983203) Ubuntu 18.04 I expect Chrome to play videos. When I try to play any video on Google Chrome for Linux, any version of 75 or higher, Google Chrome freezes. Chrome 75 will allow sound but no video. All mouse clicks become unresponsive. Attempting to close Chrome after many mouse
[Desktop-packages] [Bug 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
Bug solved! In my case, the Laine gnome-shell extension was causing all the problems. when I turned the Laine extension off both google-chrome and chromium versions 75 (newest updates) worked again. Both video and audio playback ran normally again. -- 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/1835623 Title: Google Chrome Linux version 75 freezes and then crashes when trying to play any video Status in chromium-browser package in Ubuntu: New Bug description: (upstream bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=983203) Ubuntu 18.04 I expect Chrome to play videos. When I try to play any video on Google Chrome for Linux, any version of 75 or higher, Google Chrome freezes. Chrome 75 will allow sound but no video. All mouse clicks become unresponsive. Attempting to close Chrome after many mouse clicks causes Chrome to crash. Even worse it often also crashes Ubuntu 18.04. Google Chrome 74 or lower work without any problems playing videos. It is a Google Chrome Linux version 75 or higher problem. I cannot believe that neither Google or Ubuntu or any other Linux OS seem to completely ignore this extremely serious problem. I am forced to install Google Chrome 71 to fix video playback problem. I posted on Ubuntu ask, and show over 90 views but no comments. One answer confirms that he has the exact same problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: DistroRelease: Ubuntu 18.04 Env: 'None' 'None' InstallationDate: Installed on 2019-05-02 (66 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20181019) Load-Avg-1min: 1.47 Load-Processes-Running-Percent: 0.1% MachineType: MSI MS-7641 NonfreeKernelModules: nvidia_modeset nvidia Package: chromium-browser 75.0.3770.90-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=7181ee96-0bd0-4b3c-9100-fa205ef6bd1d ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-55-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm adm cdrom cdrom dip dip lpadmin lpadmin plugdev plugdev sambashare sambashare sudo sudo _MarkForUpload: True dmi.bios.date: 04/20/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.1 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 760GMA-P34(FX) (MS-7641) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.1:bd04/20/2015:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7641 dmi.product.version: 5.0 dmi.sys.vendor: MSI etcconfigcpepperflashpluginnonfree: flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so" flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"` CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion" modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1835623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836209] Re: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9
I am currently doing improvements on the test script, making them available here: https://code.launchpad.net/~till-kamppeter/network-manager/+git/network- manager/+merge/369586 I already added timrout s to the GLIb main loops so that in case of a failure here nm.py continues with the other tests and the log of the failure in the main loop does not get lost. If the main loops hang indefinitely, autopkgtest kills the script and no results are available. Next step is improving the script for events taking too long to happen. Especially things like waiting for a hard-coded time interval and then checking a state ones (and fail if the desired state did not get reached, in check_connected_device_config()) I will replace by repeated checking over a given time interval, like assertEventually() does). Probably I will also make certain timeouts longer. ** Changed in: network-manager (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1836209 Title: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9 Status in network-manager package in Ubuntu: In Progress Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/n/network-manager/20190710_160945_9116e@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/n/network-manager/20190710_110735_e5ce3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1836209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1603324] Re: file-roller crashed with SIGSEGV in confirmation_dialog_response()
** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1603324 Title: file-roller crashed with SIGSEGV in confirmation_dialog_response() Status in file-roller package in Ubuntu: Confirmed Bug description: Error after unzip a file. It seems to have unzipped it correctly though ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: file-roller 3.20.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jul 15 14:53:45 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2012-11-25 (1328 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120627) ProcCmdline: file-roller --extract-here --notify file:///home/username/aaa/bbb/ccc/ddd.zip file:///home/username/aaa/bbb/ccc/eee.zip ProcEnviron: LANGUAGE=en_SG:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_SG.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: file-roller crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to yakkety on 2015-03-14 (488 days ago) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1603324/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741027] Re: [SRU] Screen sharing panels abort using an non-existent vino gsettings key
@Khurshid: Maybe I'm missing something, but to me these desired 18.04 uploads don't seem to be very sponsor friendly. * I see a 18.04 repository for unity-control-center (just created a link to it), but it does not seem to include the changelog update. * As regards unity-settings-daemon I see neither a repository nor debdiff for 18.04. So what is there to sponsor? * No bionic bug tasks - I just added those. Once it's clear what the desired uploads are, I think you should subscribe ubuntu-sponsors so this bug gets listed here: http://reqorts.qa.ubuntu.com/reports/sponsoring/ ** Also affects: vino (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: unity-control-center (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: unity-settings-daemon (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: vino (Ubuntu Bionic) ** Changed in: unity-control-center (Ubuntu Bionic) Importance: Undecided => High ** Changed in: unity-control-center (Ubuntu Bionic) Status: New => In Progress ** Changed in: unity-control-center (Ubuntu Bionic) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) ** Changed in: unity-settings-daemon (Ubuntu Bionic) Importance: Undecided => High ** Changed in: unity-settings-daemon (Ubuntu Bionic) Status: New => In Progress ** Changed in: unity-settings-daemon (Ubuntu Bionic) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1741027 Title: [SRU] Screen sharing panels abort using an non-existent vino gsettings key Status in unity-control-center package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in vino package in Ubuntu: Invalid Status in unity-control-center source package in Bionic: In Progress Status in unity-settings-daemon source package in Bionic: In Progress Bug description: *Impact This happens because Gnome removed that particular gsettings key. The removal did not happen with the ui removal but rather much later than that. That is why it doesn't work with the latest version of vino. As of now If users try to open the new sharing panel, unity-control- center will crash. This sort behavior is not desired on LTS release (18.04). Test Case 1) Go to unity-control-center 2) Click sharing (Remote desktop) * Regression potential None The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+17.10.20171225-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/be6d095e2145d77c79a6e47e17c94dfe70bcaa0a 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/. Specifically, the error report "Settings schema 'org.gnome.Vino' does not contain a key named 'enabled' " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1785649] Re: [MIR] gupnp-dlna
** Changed in: gupnp-dlna (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gupnp-dlna in Ubuntu. https://bugs.launchpad.net/bugs/1785649 Title: [MIR] gupnp-dlna Status in gupnp-dlna package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries, including the gupnp-dlna one * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is not being used during build, we are going to look at changing that * Dependendies The package uses standard desktop libraries that are already in main (gstreamer, glib) * Standards compliance the package is using standard packaging (dh10), the standards-version is 3.9.8, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp-dlna/+bug/1785649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
I'm testing now, and will report later. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay: keep buffer pool around when flushing/seeking - rtpssrcdemux: Forward serialized events to all pads - qmlglsink: Handle OPENGL header guard changes - qtdemux: fix track language code parsing; ignore corrupted CTTS box - qtmux: Correctly set tkhd width/height to the display
[Desktop-packages] [Bug 1836759] Re: [SRU] libreoffice 6.2.5 for disco
** Changed in: libreoffice-l10n (Ubuntu) Status: In Progress => Fix Released ** Changed in: libreoffice (Ubuntu) Status: In Progress => Fix Released -- 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/1836759 Title: [SRU] libreoffice 6.2.5 for disco Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Bug description: [Impact] * LibreOffice 6.2.5 is in its fifth bugfix release of the 6.2 line. Version 6.2.5 is currently in Eoan. For a list of fixed bugs compared to 6.2.4 see: https://wiki.documentfoundation.org/Releases/6.2.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.2.5/RC2#List_of_fixed_bugs (that's a total of 118 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 118 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1836759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835285] Re: PDF files don't open; "Failed to load backend for 'application/pdf': libpdfdocument.so" and "Invalid ELF header".
Hi Sebastien.
Thank You for an answer. And I apologize for such a long time without my
answer. (An accident, nothing serious).
So Sebastien, please tell me, which informations exactly do you need?
I'm thinking about a `journalctl -b 0` command, of course. Is there
something specific, that you want or need to gather?
I'm asking, because there is not *any* informations about Evince or
loading backend for 'application/pdf' - for example - in system log
files, such as »/var/log/{syslog,kern.log}«, even right after trying to
open '.pdf' or 'djvu' files etc. (as you asked for it in your comment).
I mean nothing valuable, that can help to diagnose this problem.
Yes, there is the same problem with '.djvu' files - they cannot be
opened via Evince. Summarizing: I have problems not only with '.pdf',
but with '.djvu' files also. I have no idea what about other supported
file formats (please see 4. and Evince AppArmor profile), because I
can't test them, right now. And honestly, I don't know if I will be able
to do this. Sorry. (So, I updated the bug report and added this
information).
Sebastien, you also asked about the result of the `debsums(1)` for
'libevdocument3-4', right? I had to install `debsums` package first but
here it is:
,[ $ debsums libevdocument3-4 ]
| /usr/lib/i386-linux-gnu/evince/4/backends/comicsdocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/djvudocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/dvidocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/libcomicsdocument.so
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/libdjvudocument.so
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/libdvidocument.so
FAILED
| /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so
FAILED
| /usr/lib/i386-linux-gnu/evince/4/backends/libpsdocument.so
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/libtiffdocument.so
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/libxpsdocument.so
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/pdfdocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/psdocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/tiffdocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/evince/4/backends/xpsdocument.evince-backend
OK
| /usr/lib/i386-linux-gnu/libevdocument3.so.4.0.0
OK
| /usr/share/doc/libevdocument3-4/AUTHORS
OK
| /usr/share/doc/libevdocument3-4/NEWS.gz
OK
| /usr/share/doc/libevdocument3-4/README
OK
| /usr/share/doc/libevdocument3-4/TODO
OK
| /usr/share/doc/libevdocument3-4/changelog.Debian.gz
OK
| /usr/share/doc/libevdocument3-4/copyright
OK
| /usr/share/lintian/overrides/libevdocument3-4
OK
`
As We can see, there are two 'FAILED' results. So the file's MD5 sum
does not match, right? What do you think about this? Is this a bug or
something on my side went wrong?
Sebastien, I apologize You once again, for such a long time without
answer. Best regards.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1835285
Title:
PDF files don't open; "Failed to load backend for 'application/pdf':
libpdfdocument.so" and "Invalid ELF header".
Status in evince package in Ubuntu:
Incomplete
Bug description:
Hello.
On Wed, Jun 19. 2019, Evince has been updated to version
'3.18.2-1ubuntu4.5' [1]. This update added, among other things, some
hardening from Ubuntu 18.10 Release. However, now, it is impossible to
open any '.pdf' files. When I try to open such file, there is an
information (on the red background) in the main Evince window. And It
looks this way:
,[ Opening '.pdf' error ]
|
| Cannot open document „file:///home/user/Docs/foo-bar.pdf”.
| Failed to load backend for 'application/pdf':
| /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF
| header
|
`
There is a reference to »/usr/lib/i386-linux-
gnu/evince/4/backends/libpdfdocument.so«. According to `dpkg(1)`
command this file is a part of the 'libevdocument3-4' package, which
is installed already (version '3.18.2-1ubuntu4.5'). I also tried to
open '.pdf' file via terminal, but nothing changed. Here are the
results:
,[ $ evince Docs/foo-bar.pdf ]
|
| (evince:26918): EvinceDocument-WARNING **:
| /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF
| header
|
| (evince:26918): EvinceDocument-WARNING **:
|
[Desktop-packages] [Bug 1836759] Re: [SRU] libreoffice 6.2.5 for disco
This bug was fixed in the package libreoffice - 1:6.2.5-0ubuntu0.19.04.1 --- libreoffice (1:6.2.5-0ubuntu0.19.04.1) disco-security; urgency=medium * New upstream release (LP: #1836759) * Fixes CVE-2019-9848: LibreLogo arbitrary script execution * Fixes CVE-2019-9849: Remote bullet graphics retrieved in 'stealth mode' -- Marcus Tomlinson Tue, 16 Jul 2019 16:02:55 +0100 -- 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/1836759 Title: [SRU] libreoffice 6.2.5 for disco Status in libreoffice package in Ubuntu: In Progress Status in libreoffice-l10n package in Ubuntu: In Progress Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Bug description: [Impact] * LibreOffice 6.2.5 is in its fifth bugfix release of the 6.2 line. Version 6.2.5 is currently in Eoan. For a list of fixed bugs compared to 6.2.4 see: https://wiki.documentfoundation.org/Releases/6.2.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.2.5/RC2#List_of_fixed_bugs (that's a total of 118 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 118 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1836759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836759] Re: [SRU] libreoffice 6.2.5 for disco
This bug was fixed in the package libreoffice-l10n - 1:6.2.5-0ubuntu0.19.04.1 --- libreoffice-l10n (1:6.2.5-0ubuntu0.19.04.1) disco-security; urgency=medium * New upstream release (LP: #1836759) * Fixes CVE-2019-9848: LibreLogo arbitrary script execution * Fixes CVE-2019-9849: Remote bullet graphics retrieved in 'stealth mode' -- Marcus Tomlinson Tue, 16 Jul 2019 16:02:55 +0100 ** Changed in: libreoffice-l10n (Ubuntu Disco) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9848 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9849 ** Changed in: libreoffice (Ubuntu Disco) Status: In Progress => Fix Released -- 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/1836759 Title: [SRU] libreoffice 6.2.5 for disco Status in libreoffice package in Ubuntu: In Progress Status in libreoffice-l10n package in Ubuntu: In Progress Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Bug description: [Impact] * LibreOffice 6.2.5 is in its fifth bugfix release of the 6.2 line. Version 6.2.5 is currently in Eoan. For a list of fixed bugs compared to 6.2.4 see: https://wiki.documentfoundation.org/Releases/6.2.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.2.5/RC2#List_of_fixed_bugs (that's a total of 118 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 118 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1836759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836759] Re: [SRU] libreoffice 6.2.5 for disco
** Changed in: libreoffice-l10n (Ubuntu Disco) Status: New => In Progress ** Changed in: libreoffice-l10n (Ubuntu) Status: New => In Progress ** Changed in: libreoffice (Ubuntu Disco) Status: New => In Progress ** Changed in: libreoffice (Ubuntu) Status: New => In Progress -- 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/1836759 Title: [SRU] libreoffice 6.2.5 for disco Status in libreoffice package in Ubuntu: In Progress Status in libreoffice-l10n package in Ubuntu: In Progress Status in libreoffice source package in Disco: In Progress Status in libreoffice-l10n source package in Disco: In Progress Bug description: [Impact] * LibreOffice 6.2.5 is in its fifth bugfix release of the 6.2 line. Version 6.2.5 is currently in Eoan. For a list of fixed bugs compared to 6.2.4 see: https://wiki.documentfoundation.org/Releases/6.2.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/6.2.5/RC2#List_of_fixed_bugs (that's a total of 118 bugs) * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Test Case] * No specific test case, bugs fixed upstream hopefully come with unit/regression tests, and the release itself is extensively exercised upstream (both in an automated manner and manually) by a community of testers. Each minor release normally goes through two release candidates. * The libreoffice packages include autopkgtests, those should be run and verified to pass. * General smoke testing of all the applications in the office suite should be carried out. [Regression Potential] * A minor release with a total of 118 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1836759/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835285] Re: PDF files don't open; "Failed to load backend for 'application/pdf': libpdfdocument.so" and "Invalid ELF header".
** Summary changed: - PDF files do not open. 'Failed to load backend for 'application/pdf': libpdfdocument.so' and 'Invalid ELF header'. + PDF files don't open; "Failed to load backend for 'application/pdf': libpdfdocument.so" and "Invalid ELF header". ** Description changed: Hello. On Wed, Jun 19. 2019, Evince has been updated to version '3.18.2-1ubuntu4.5' [1]. This update added, among other things, some hardening from Ubuntu 18.10 Release. However, now, it is impossible to open any '.pdf' files. When I try to open such file, there is an information (on the red background) in the main Evince window. And It looks this way: - - ,[ Evince .pdf issue ] + ,[ Opening '.pdf' error ] | | Cannot open document „file:///home/user/Docs/foo-bar.pdf”. | Failed to load backend for 'application/pdf': | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF | header | ` - - There is a reference to '/usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so'. According to dpkg(1) command this file is a part of the 'libevdocument3-4' package, which is already installed (version '3.18.2-1ubuntu4.5'). I also tried to open '.pdf' file via terminal, but nothing changed. Here are the results: - + There is a reference to »/usr/lib/i386-linux- + gnu/evince/4/backends/libpdfdocument.so«. According to `dpkg(1)` command + this file is a part of the 'libevdocument3-4' package, which is + installed already (version '3.18.2-1ubuntu4.5'). I also tried to open + '.pdf' file via terminal, but nothing changed. Here are the results: ,[ $ evince Docs/foo-bar.pdf ] | | (evince:26918): EvinceDocument-WARNING **: | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF | header | | (evince:26918): EvinceDocument-WARNING **: | /usr/lib/i386-linux-gnu/evince/4/backends/libpdfdocument.so: Invalid ELF | header | ` + I think, that the whole problem is/could be related with AppArmor and + Evince profile changes in the latest update, because - for example - day + before, before update, everything was okay. Anyway, described + problem/issue started to happen right after Evince update. (To check + differences between AppArmor profile versions, please see 2. and 3.). + There is one more thing to notice: Evince profile, has never been + changed by the User. - I think, that the whole problem is related with AppArmor changes in the latest update, because - for example - day before everything was okay. The described problem started right after Evince updated to the latest version. (To check differences between versions, please see 2. and 3.). The 'Evince' profile has never been changed by the Users. + If it's about AppArmor: I've tried to change Evince profile mode from + 'enforce' to 'complain'. Unfortunately, nothing changed. There wasn't + any valuable entries in system log files etc. (I'm sorry, but for now, I + can not check other variants/solutions, such as: (a) disable Evince + profile via `aa-disable(8)` command or (b) make links between + »/etc/apparmor.d/usr.bin.evince« file and »/etc/apparmor.d/disable/« + directory, next use `apparmor_parser(8)` command to remove profile etc.) - If it's about AppArmor: I've tried to change Evince profile mode form 'enforce' to 'complain'. Unfortunately, nothing changed. There wasn't any valuable entries in system log files etc. (I'm sorry, but for now, I can not check other variants/solutions, such as: (a) disabling Evince profile with 'aa-disable(8)' command or (b) making links between '/etc/apparmor.d/usr.bin.evince' and '/etc/apparmor.d/disable/' directory, next using 'apparmor_parser(8)' command to remove profile etc.) - + ✖ NOTE: to make some more tests, I've tried to open '.djvu' file, but + without success. It seems, that there is exactly the same informations + as with '.pdf' files. Of course, Evince + (»/etc/apparmor.d/usr.bin.evince«) profile contains rule to open such + file format etc. and many others, see 4. So, according to all of this, + maybe "Summary" should be changed to reflect this situation? Maybe + something like: "PDF and other files don't open; "Failed to load (...)". + + Sebastien, what do You think?. + + Here are some additional informations: ✗ Description: Ubuntu 16.04.6 LTS ✗ Release: 16.04 ✗ Architecture: x86_32/i386 - ✗ Linux: 4.4.0-154-generic (4.4.0-155-generic is already installed, but reboot is needed) + ✗ Linux: 4.4.0-155-generic ✓ AppArmor: 2.10.95-0ubuntu2.11 ✓ Evince: 3.18.2-1ubuntu4.5 - Best regards. __ [1] https://lists.ubuntu.com/archives/xenial-changes/2019-June/024691.html [2] http://launchpadlibrarian.net/429511526/evince_3.18.2-1ubuntu4.4_3.18.2-1ubuntu4.5.diff.gz [3] http://launchpadlibrarian.net/429293224/evince_3.18.2-1ubuntu4.1_3.18.2-1ubuntu4.5.diff.gz + [4]
[Desktop-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
Comments #17, #18, #19 are false positives - there aren't any regressions. Amr Ibrahim, if you wanted to test this that'd be appreciated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1832123 Title: [SRU] Bugfix release 1.14.5 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: Fix Committed Status in gst-plugins-bad1.0 source package in Bionic: Fix Committed Status in gst-plugins-base1.0 source package in Bionic: Fix Committed Status in gst-plugins-good1.0 source package in Bionic: Fix Committed Status in gst-plugins-ugly1.0 source package in Bionic: Fix Committed Status in gst-python1.0 source package in Bionic: Fix Committed Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: Fix Committed Status in gstreamer-vaapi source package in Bionic: Fix Committed Status in gstreamer1.0 source package in Bionic: Fix Committed Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. --- Highlighted bugfixes in 1.14.5 GStreamer core - aggregator: take the pad lock around queue gap event removal - aggregator: don’t leak gap buffer when out of segment - buffer: fix possible memory corruption in gst_buffer_foreach_meta() when removing metas - bus: Make removing of signal/bus watches thread-safe - bus: Don’t allow removing signal watches with gst_bus_remove_watch() - controlbinding: Check if the weak pointer was cleared before explicitly removing it - ptp clock: Wait for ANNOUNCE before selecting a master; increase tolerance for late follow-up and delay-resp - segment: Allow stop == -1 in gst_segment_to_running_time() and negative rate - g-i: annotations fixes gst-plugins-base - audioconvert: fix endianness conversion for unpacked formats (e.g. S24_32BE) - audioringbuffer: Fix wrong memcpy address when reordering channels - decodebin2: Make sure to remove pad probes when freeing GstDecodeGroup - glviewconvert: fix output when a transformation matrix is used - glupload: prevent segfault when updating caps - gl/egl: Determine correct format on dmabuf import - glupload: dmabuf: be explicit about gl formats used - id3tag: validate the year from v1 tags before passing to GstDateTime - rtpbasepayload: fix sequence numbers when using buffer lists - rtspconnection: fix security issue, potential heap overflow (CVE-2019-9928) - rtspconnection: fix GError set over the top of a previous GError - rtspconnection: do not duplicate authentication headers - subparse: don’t assert when failing to parse subrip timestamp - video: various convert sample frame fixes - video-converter: fix conversion from I420_10LE/BE, I420_12LE/BE, A420_10LE/BE to BGRA/RGBA which created corrupted output - video-format: Fix GBRA_10/12 alpha channel pixel strides gst-plugins-good - flv: Use 8kHz sample rate for alaw/mulaw audio - flvdemux: Do not error out if the first added and chained pad is not linked - flvmux: try harder to make sure timestamps are always increasing - gdkpixbufdec: output a TIME segment which is what’s expected for raw video - matroskademux: fix handling of MS ACM audio - matroska: fix handling of FlagInterlaced - pulsesink: Deal with not being able to convert a format to caps - rtph265depay, rtph264depay; aggregation packet marker handling fixes - rtpmp4gdepay: detect broken senders who send AAC with ADTS frames - rtprawdepay: keep buffer pool around when flushing/seeking - rtpssrcdemux: Forward serialized events to all pads - qmlglsink: Handle OPENGL header guard changes - qtdemux: fix track language
[Desktop-packages] [Bug 1741027] Re: [SRU] Screen sharing panels abort using an non-existent vino gsettings key
@Ninad It needs to be sponsored (who has merge access) for 18.04. I have asked in the mailing list here https://lists.launchpad.net/unity7maintainers/msg00026.html, You can also ask in #ubuntu-desktop on irc.freenode.net but be polite. Meanwhile you can use unity-7 maintainers PPA. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1741027 Title: [SRU] Screen sharing panels abort using an non-existent vino gsettings key Status in unity-control-center package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Status in vino package in Ubuntu: Invalid Bug description: *Impact This happens because Gnome removed that particular gsettings key. The removal did not happen with the ui removal but rather much later than that. That is why it doesn't work with the latest version of vino. As of now If users try to open the new sharing panel, unity-control- center will crash. This sort behavior is not desired on LTS release (18.04). Test Case 1) Go to unity-control-center 2) Click sharing (Remote desktop) * Regression potential None The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+17.10.20171225-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/be6d095e2145d77c79a6e47e17c94dfe70bcaa0a 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/. Specifically, the error report "Settings schema 'org.gnome.Vino' does not contain a key named 'enabled' " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 298268] Re: shortcuts for view resize are not displayed in menu
No reply to comment #2 from reporter Report did not expire due to bug watch Issue refers to the old interface Aspect ratios changed in new interface Upstream report closed 2018-02-10 "RESOLVED OBSOLETE" Closing as report is no longer valid ** Changed in: gtk+2.0 (Ubuntu) Status: Incomplete => Invalid ** Changed in: totem (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/298268 Title: shortcuts for view resize are not displayed in menu Status in GTK+: Expired Status in gtk+2.0 package in Ubuntu: Invalid Status in totem package in Ubuntu: Invalid Bug description: Binary package hint: totem Shortcuts exist in Totem to resize the movie window to different zoom ratios: 1:1, 2:1, 1:2. There are keyboard shortcuts for these (namely '1', '2', and '0') but they are not displayed in the menu. Displaying keyboard shortcuts in the menus is the most usable way for a user to discover what those shortcuts are, and so they should most definitely be displayed there. Please add the keyboard shortcuts for these commands to the Totem menus. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/298268/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1577527] Re: Calendar Theme Issue
** Package changed: calendar (Ubuntu) => gnome-calendar (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1577527 Title: Calendar Theme Issue Status in gnome-calendar package in Ubuntu: New Bug description: When search for Calendar in Dash and then open Calendar there are little white edges at the egde of the calendar with Ambiance theme enabled? But when change the theme to Radiance or a community created theme the white edges are gone? This issue is in Ubuntu 16.04 x64. I dont know if its only me or someone else has this issue? /Martin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1577527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1405005] Re: GNOME Calendar doesn't show correct first day of the week
** Package changed: calendar (Ubuntu) => gnome-calendar (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1405005 Title: GNOME Calendar doesn't show correct first day of the week Status in gnome-calendar package in Ubuntu: New Bug description: Hi, I'm using the PT-pt version of Ubuntu and since the beginning I noticed that Ubuntu's Calendar starts with the wrong day. Instead of starting with Sunday it starts with Monday. That is more a cultural issue than other thing, but it's also a mistake. I know I can change it, but I'd like to see it as default (or at least you could let us change the first day of the week, it would be also easier for you). Ubuntu 14.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1405005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1577527] [NEW] Calendar Theme Issue
You have been subscribed to a public bug: When search for Calendar in Dash and then open Calendar there are little white edges at the egde of the calendar with Ambiance theme enabled? But when change the theme to Radiance or a community created theme the white edges are gone? This issue is in Ubuntu 16.04 x64. I dont know if its only me or someone else has this issue? /Martin. ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New -- Calendar Theme Issue https://bugs.launchpad.net/bugs/1577527 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar 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 1405005] [NEW] GNOME Calendar doesn't show correct first day of the week
You have been subscribed to a public bug: Hi, I'm using the PT-pt version of Ubuntu and since the beginning I noticed that Ubuntu's Calendar starts with the wrong day. Instead of starting with Sunday it starts with Monday. That is more a cultural issue than other thing, but it's also a mistake. I know I can change it, but I'd like to see it as default (or at least you could let us change the first day of the week, it would be also easier for you). Ubuntu 14.04.1 LTS ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: calendar day portuguese week -- GNOME Calendar doesn't show correct first day of the week https://bugs.launchpad.net/bugs/1405005 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar 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 1801540] Re: Microphone distorted sound on ALC892/1220 on AMD chipsets
May as well join the fun. Believed I tried every suggested work around
above, still got crackling.
In my case the crackling is present on the line-in 3.5mm jack plug and
not a microphone.
I run:
X470 GAMING PRO (MS-7B79) motherboard with a ALC892, Ryzen 2700, Radeon
RX Vega 54. Running Ubuntu 19.04, Kernel 5.0.0-20-generic (was hoping
kernel 5 would improve things).
I did notice that the crackling reduced a bit when using this setting in
/etc/default.pa
### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect use_ucm=0 tsched=0
.else
### Use the static hardware detection module (for systems that lack udev suppor$
load-module module-detect tsched=0
.endif
I use a Loopback (# pactl load-module module-loopback latency_msec=1) to pipe
some line in audio (chiptune device('s)) into PulseAudio if that's something
useful to know.
Really annoying problem, makes me feel ashamed using Linux, really nice
up to date computer (hardware) and some trivial piece of sillycon
working with every other OS refuses to work on Linux. Don't know who to
blame, but blaming I do!
USB soundcapture isn't really the thing I'm looking for. Unnecessary
latency is often a thing I try to avoid.
Who wants to trade a X470 GAMING PRO for a X470 board that has working
sound on Linux??
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1801540
Title:
Microphone distorted sound on ALC892/1220 on AMD chipsets
Status in Linux:
Confirmed
Status in linux package in Ubuntu:
Incomplete
Status in pulseaudio package in Ubuntu:
Confirmed
Bug description:
Not sure if I'll report this upstream but there is definitely an issue
with microphone recording on my desktop, this is not happening on my
laptop which has a different codec.
Already tried all workarounds possible, no luck. Only with my desktop
with this particular motherboard. No issues in Windows, the sound
recorded in there is distorted and has some static and robotic tone on
high-pitch.
alsa-info on the attachments
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1696277] Re: package fonts-unfonts-core 1.0.3.is.1.0.2-080608-10ubuntu1 failed to install/upgrade: pacote fonts-unfonts-core não está pronto para configuração não posso config
Maybe it's because of dpkg, apt, bad connection, unexpected interrupts, etc. This error happens with any packages in the error messages but it's never by bugs from those packages. ** Changed in: fonts-unfonts-core (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-unfonts-core in Ubuntu. https://bugs.launchpad.net/bugs/1696277 Title: package fonts-unfonts-core 1.0.3.is.1.0.2-080608-10ubuntu1 failed to install/upgrade: pacote fonts-unfonts-core não está pronto para configuração não posso configurar (estado atual 'half-installed') Status in fonts-unfonts-core package in Ubuntu: Invalid Bug description: Happened when i tried to download gksu nautilus. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-10ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue Jun 6 20:51:04 2017 ErrorMessage: pacote fonts-unfonts-core não está pronto para configuração não posso configurar (estado atual 'half-installed') InstallationDate: Installed on 2017-06-05 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: fonts-unfonts-core Title: package fonts-unfonts-core 1.0.3.is.1.0.2-080608-10ubuntu1 failed to install/upgrade: pacote fonts-unfonts-core não está pronto para configuração não posso configurar (estado atual 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-unfonts-core/+bug/1696277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792662] Re: Korean (Hangul) keyboard of IBUS In Hangul mode, some programs do not work with enter, arrow keys, and backspace bar.
See https://github.com/libhangul/ibus-hangul/issues/70 tl;dr It cannot be fixed in ibus-hangul. Qt should be fixed. ** Bug watch added: github.com/libhangul/ibus-hangul/issues #70 https://github.com/libhangul/ibus-hangul/issues/70 ** Changed in: ibus-hangul (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-hangul in Ubuntu. https://bugs.launchpad.net/bugs/1792662 Title: Korean (Hangul) keyboard of IBUS In Hangul mode, some programs do not work with enter, arrow keys, and backspace bar. Status in ibus-hangul package in Ubuntu: Invalid Bug description: An error occurred while using 18.04 LTS. Prior to 17.10, there were no such errors. In some programs in Hangul mode, input keys other than English and Hangul are not used. SpeedCrunch does not even allow numeric keys. Error editing text in krita-4.0.4-x86_64. krita-4.0.4-x86_64 SpeedCrunch 0.12 (Qt 5.9.2) IBus 1.5.17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-hangul/+bug/1792662/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885525] Re: Deleting a Gmail Message Always Sends Item to [Gmail]/Trash
In the absence of a reply to comment #65, I can confirm that this is still an issue with Thunderbird 60.8.0, tested in Ubuntu 19.10 (dev). ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Confirmed -- 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/885525 Title: Deleting a Gmail Message Always Sends Item to [Gmail]/Trash Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Thunderbird 7.0.1, Ubuntu 11.10 Gmail accounts do not obey the setting in Account Settings --> [Account] --> Server Settings --> When I delete a message I changed this to move the message to Gmail's "All Mail" folder, attempting to imitate the Gmail web interface's "Archive" option. However, regardless of setting, the item always moved to Trash. This persisted after restart of the client. The settings save, but have no effect. Caveat: This was tested on two Google Apps for Domains accounts, though I suspect this behavior will happen with gmail.com accounts as well. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/885525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1793496] Re: scaling changes when closing/re-opening the lid
fyi, with the packages provided by Marco I still can reproduce the issue with bionic. -- 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/1793496 Title: scaling changes when closing/re-opening the lid Status in Mutter: New Status in mutter package in Ubuntu: Fix Released Bug description: scaling changes when closing/re-opening the lid. Seen in bionic. Mz scaling is set to 100%, but the laptop is considered highdpi by mutter, and during suspend/resume it changes back to default ignoring settings. $ xprop -spy -root RESOURCE_MANAGER [...] RESOURCE_MANAGER(STRING) = "*customization:\t-color\nXft.dpi:\t192\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t48\nXcursor.theme:\tDMZ-White\n" RESOURCE_MANAGER(STRING) = "*customization:\t-color\nXft.dpi:\t96\nXft.antialias:\t1\nXft.hinting:\t1\nXft.hintstyle:\thintslight\nXft.rgba:\trgb\nXcursor.size:\t24\nXcursor.theme:\tDMZ-White\n" xrandr Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 8192 x 8192 eDP-1 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 309mm x 174mm 2560x1440 60.00*+ 59.9959.9959.9659.95 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1793496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836805] Re: screen frozen after reboot
** Package changed: ubuntu => gdm3 (Ubuntu) ** Tags added: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1836805 Title: screen frozen after reboot Status in gdm3 package in Ubuntu: New Bug description: After I installed Ubuntu 19.04 (fresh install with hard drive erasing), I was able to login once just after install. But then after reboot, the screen freezes in the middle of the boot process and I never get the login banner. I was able to launch the recovery mode and get some information through journalctl command and it seems that the problem is related to a Wayland server crash. I don't really know if the problem comes from Wayland or Gnome. The first worrying error message is : "gnome_shell[1165]: Failed to apply DRM plane transform 0: Permission non accordée" (ie, Permission denied in french) Thanks to the recovery mode I was able to upgrade via "apt-get update" and "apt-get upgrade", but the symptoms were the same after a reboot I uncommented the "Enable=true" flag of the [debug] section of /etc/gdm3/custom.conf and I provide and extract of the journalctl output related to the error as an attachment to this report (journalctl_extract.txt part). I also provide some system information (system.txt pat). I hope this may help to solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1836805/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836805] [NEW] screen frozen after reboot
You have been subscribed to a public bug: After I installed Ubuntu 19.04 (fresh install with hard drive erasing), I was able to login once just after install. But then after reboot, the screen freezes in the middle of the boot process and I never get the login banner. I was able to launch the recovery mode and get some information through journalctl command and it seems that the problem is related to a Wayland server crash. I don't really know if the problem comes from Wayland or Gnome. The first worrying error message is : "gnome_shell[1165]: Failed to apply DRM plane transform 0: Permission non accordée" (ie, Permission denied in french) Thanks to the recovery mode I was able to upgrade via "apt-get update" and "apt-get upgrade", but the symptoms were the same after a reboot I uncommented the "Enable=true" flag of the [debug] section of /etc/gdm3/custom.conf and I provide and extract of the journalctl output related to the error as an attachment to this report (journalctl_extract.txt part). I also provide some system information (system.txt pat). I hope this may help to solve the issue. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- screen frozen after reboot https://bugs.launchpad.net/bugs/1836805 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 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 1164016] Re: restore type-ahead find
So mate used to be great but doesn't seem to be a solution anymore either, type-ahead-find seemingly has been replaced for search-as-you- type in mate sometimes this summer as well, too. +1 for replacement, it could at least be a configuration option -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835650] Re: firefox fails to open private sessions from bash
Sorry for the delay.
I see what you mean, it seems true that firefox (suddenly?) adheres to
the documentation (and hasn't done so in the past?).
So in future we have to keep in mind that
$firefox -private
does not open a private window (anymore!) if another instance of firefox is
already running, and that
$firefox -private URL
does not open said URL in a private window (anymore!) (which it did for a long
time and until the recent past, and which seems much more sensible).
Counterintuitive and probably misleading, but once learned it's possible to
accept, I guess...
Thanks for the headsup!
--
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/1835650
Title:
firefox fails to open private sessions from bash
Status in firefox package in Ubuntu:
Invalid
Bug description:
running
% firefox -private URL
or
% firefox -private-toggle URL
from a cli used to start firefox in private mode. This does not work
(in my setup) anymore.
[ctrl]-[shift]-p and "new private window" from the file menu also does
not always open private windows, anymore.
I'm wondering if this is a security bug (it clearly is a privacy bug)..
1)
$ lsb_release -rd
Description: Ubuntu 19.04
Release: 19.04
2)
$ apt-cache policy firefox
firefox:
Installed: 67.0.4+build1-0ubuntu0.19.04.1
Candidate: 67.0.4+build1-0ubuntu0.19.04.1
Version table:
*** 67.0.4+build1-0ubuntu0.19.04.1 500
500 http://de.archive.ubuntu.com/ubuntu disco-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu disco-security/main amd64
Packages
100 /var/lib/dpkg/status
66.0.3+build1-0ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu disco/main amd64 Packages
3) What I expect to happen
Opening a private window from the command line typing
firefox -private URL
should open the URL in a private window
4) What happens instead
Upon the given command firefox opens the URL, but not in a private window and
leaves the URL in the history of the browser.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: firefox 67.0.4+build1-0ubuntu0.19.04.1
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: thorsten 2262 F pulseaudio
BuildID: 20190620151128
Channel: Unavailable
CurrentDesktop: MATE
Date: Sun Jul 7 13:22:56 2019
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2019-04-10 (87 days ago)
InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
IpRoute:
default via 192.168.178.1 dev wlp61s0 proto dhcp metric 600
169.254.0.0/16 dev wlp61s0 scope link metric 1000
192.168.178.0/24 dev wlp61s0 proto kernel scope link src 192.168.178.24
metric 600
MostRecentCrashID: bp-86cfd7c5-fc1a-482b-b67f-a018b1180516
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:1151
PrefSources:
/usr/lib/firefox/defaults/pref/all-ubuntumate.js
prefs.js
Profiles: Profile0 (Default) - LastVersion=67.0.4/20190620151128 (In use)
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/13/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET49W (1.26 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S29W00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L8S29W00:pvrThinkPadT480s:rvnLENOVO:rn20L8S29W00:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S29W00
dmi.product.sku: LENOVO_MT_20L8_BU_Think_FM_ThinkPad T480s
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1835650/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1440372] Re: please port duplicity to Python3
New version uploaded https://launchpad.net/ubuntu/+source/duplicity/0.8.01-0ubuntu1 Some tests are failing on ppc64el though now, help with those would be welcome ** Changed in: duplicity (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1440372 Title: please port duplicity to Python3 Status in Duplicity: Fix Released Status in duplicity package in Ubuntu: Fix Committed Status in duplicity source package in Eoan: Fix Committed Bug description: There is still the goal to remove Python2 from the desktop images, and to use Python3 only. deja-dup should be ported to Python3. There seems to be some progress upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1440372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836881] [NEW] Xorg freeze
Public bug reported: My gnome session freezes, mouse works fine but cannot start applications. I am able to enter one of the tty terminals and kill the session. This happens a few times a day and started a week ago probably. Douglas ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 12:29:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 4.15.0-52-generic, x86_64: installed nvidia, 418.56, 4.15.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1208] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1207] InstallationDate: Installed on 2018-01-13 (550 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. Bus 001 Device 003: ID 04ca:3016 Lite-On Technology Corp. Bus 001 Device 002: ID 0461:4e81 Primax Electronics, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator PH317-51 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=455417ef-94fe-4ab8-97b7-0b992c951267 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienna_KLS dmi.board.vendor: KBL dmi.board.version: V1.05 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnPredatorPH317-51:pvrV1.05:rvnKBL:rnSienna_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH317-51 dmi.product.version: V1.05 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze 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/1836881 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: My gnome session freezes, mouse works fine but cannot start applications. I am able to enter one of the tty terminals and kill the session. This happens a few times a day and started a week ago probably. Douglas ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 17 12:29:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 4.15.0-52-generic, x86_64: installed nvidia, 418.56, 4.15.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:1208] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Ti Mobile] [1025:1207] InstallationDate: Installed on 2018-01-13 (550 days ago)
[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
The official fix landed upstream last night. It is fixed in mutter version 3.33.4 and later. -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation Status in GNOME Shell: New Status in mutter package in Ubuntu: In Progress Status in mutter source package in Bionic: Confirmed Status in mutter source package in Disco: Confirmed Status in mutter source package in Eoan: In Progress Bug description: https://trello.com/c/i5hENxSO Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 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: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
Hello, A few weeks ago we fixed this bug with this script: https://slimbook.es/tutoriales/linux/422-fixing-the-broken-desktop- after-resuming-from-a-suspension-in-gnome I hope it helps someone. -- 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/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation Status in GNOME Shell: New Status in mutter package in Ubuntu: In Progress Status in mutter source package in Bionic: Confirmed Status in mutter source package in Disco: Confirmed Status in mutter source package in Eoan: In Progress Bug description: https://trello.com/c/i5hENxSO Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 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: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1832124] Re: Right-click file on desktop > Move to Trash frequently crashes gnome-shell
Also happens in X11 with Ubuntu 19.04. Often moving anything in the desktop to trash restarts the shell or simply hangs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1832124 Title: Right-click file on desktop > Move to Trash frequently crashes gnome- shell Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: In 19.04 Disco fully up to date. Reproduced on two different machines: 1. Log into Wayland session (did not try with X) 2. touch ~/Desktop/testfile 3. Right-click testfile on Desktop > Move to Trash -> gnome-shell crashes in around 50% of instances in my case. I did not find out what's the difference. I do run a few other gnome-shell extensions, but all from the Ubuntu repos except for Remove Accessibility. There are quite some occurrences of org.gnome.Shell.desktop in journalctl, though I didn't correlate yet as the issues seems easy to repro. If you can't repro, pls let me know and I can look for clues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01.3-1~ubuntu19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 9 12:51:20 2019 InstallationDate: Installed on 2018-09-13 (268 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-12 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1832124/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1663528] Re: pulseaudio assert failure: pulseaudio: mixer.c:929: snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
I don't understand how we're getting two instances of this crash in
version 1:11.1-1ubuntu7.3.
It sounds like either someone built their own package by the same name,
or errors.ubuntu.com is not grouping the crashes correctly.
I say this because the fix does:
+++ pulseaudio/src/modules/alsa/module-alsa-card.c
@@ -625,7 +625,8 @@ static pa_hook_result_t card_suspend_changed
if (card->suspend_cause == 0) {
/* We were unsuspended, update jack state in case it changed while we
were suspended */
PA_HASHMAP_FOREACH(jack, u->jacks, state) {
-report_jack_state(jack->melem, 0);
+if (jack->melem)
+report_jack_state(jack->melem, 0);
}
}
Yet errors.ubuntu.com is saying it is still crashing due to a NULL
melem:
report_jack_state (melem=0x0, mask=mask@entry=0)
card_suspend_changed
That NULL should be impossible with the patch.
I think most likely errors.ubuntu.com is grouping similar assertions in
mixer.c:929 incorrectly. And it only shows the full symbolic stack trace
from some older instance of the crash -- not the ones from version
1:11.1-1ubuntu7.3.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1663528
Title:
pulseaudio assert failure: pulseaudio: mixer.c:929:
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
Status in PulseAudio:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Bionic:
Fix Committed
Status in pulseaudio source package in Cosmic:
Fix Released
Status in pulseaudio source package in Disco:
Fix Released
Status in pulseaudio source package in Eoan:
Fix Released
Bug description:
[Impact]
https://errors.ubuntu.com/problem/a8bcc8185d5b1da4614bcdcf99daf57011bf9250
https://errors.ubuntu.com/problem/5e10f78db7c4d1d3ab1cd6cd5d0b7cda2299eaad
https://errors.ubuntu.com/problem/0f07e226e7db1d0fb140736a956760871e695669
This is one of the top pulseaudio crashes in Ubuntu 18.04 according to:
https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year
[Test Case]
No manual test case known. Just watch errors.ubuntu.com to check for
recurrences.
[Regression Potential]
Low. The fix is already in PulseAudio 12 so has been used in Ubuntu
18.10 and later for a year so far.
[Other Info]
SRU sponsorship tracked in bug 1556439.
[Original Report]
Sidenote: Imediatly got that crash after the apt-xapian-index one (
lp:1663524 ); does not know if it can exist a possible relationship
between them.
Got an other crash, and that time 'sound' is fully lost (pulseaudio
not reloaded). Wonder if lp:1662860 can be concerned.
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: pulseaudio 1:10.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.9.0-16.17-generic 4.9.6
Uname: Linux 4.9.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
AssertionMessage: pulseaudio: mixer.c:929:
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: oem4084 F pulseaudio
/dev/snd/controlC0: oem4084 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Feb 10 09:55:45 2017
ExecutablePath: /usr/bin/pulseaudio
ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: pulseaudio
StacktraceTop:
__assert_fail_base (fmt=,
assertion=assertion@entry=0x7f92818e7188 "mixer",
file=file@entry=0x7f92818e7419 "mixer.c", line=line@entry=929,
function=function@entry=0x7f92818e76a0 "snd_mixer_elem_get_callback_private")
at assert.c:92
__GI___assert_fail (assertion=0x7f92818e7188 "mixer", file=0x7f92818e7419
"mixer.c", line=929, function=0x7f92818e76a0
"snd_mixer_elem_get_callback_private") at assert.c:101
snd_mixer_elem_get_callback_private () from
/usr/lib/x86_64-linux-gnu/libasound.so.2
?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
?? () from /usr/lib/pulse-10.0/modules/module-alsa-card.so
Title: pulseaudio assert failure: pulseaudio: mixer.c:929:
snd_mixer_elem_get_callback_private: Assertion `mixer' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom colord dip lpadmin nvidia-persistenced plugdev
sambashare sudo users
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
[Desktop-packages] [Bug 1836209] Re: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9
** Changed in: network-manager (Ubuntu) Importance: Low => High ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1836209 Title: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9 Status in network-manager package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/n/network-manager/20190710_160945_9116e@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/n/network-manager/20190710_110735_e5ce3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1836209/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832988] Re: Intel 8260 Bluetooth not working
https://lkml.org/lkml/2019/7/17/116 ** Changed in: linux (Ubuntu) Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1832988 Title: Intel 8260 Bluetooth not working Status in gnome-bluetooth package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Expected behaviour: I can enable bluetooth in the system settings, and pair with my other devices. Actual behaviour: Always displays as 'off' in the settings dialog, and won't turn on. Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes. "dmesg | grep -i bluetooth" reports the following: ``` [ 14.445902] Bluetooth: Core ver 2.22 [ 14.445918] Bluetooth: HCI device and connection manager initialized [ 14.445921] Bluetooth: HCI socket layer initialized [ 14.445923] Bluetooth: L2CAP socket layer initialized [ 14.445929] Bluetooth: SCO socket layer initialized [ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 14.499050] Bluetooth: hci0: Device revision is 5 [ 14.499052] Bluetooth: hci0: Secure boot is enabled [ 14.499053] Bluetooth: hci0: OTP lock is enabled [ 14.499053] Bluetooth: hci0: API lock is enabled [ 14.499054] Bluetooth: hci0: Debug lock is disabled [ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38) [ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.497806] Bluetooth: BNEP filters: protocol multicast [ 15.497810] Bluetooth: BNEP socket layer initialized ``` "lsb_release -rd" reports the following: ``` Description: Ubuntu 19.04 Release: 19.04 ``` "cat /proc/version_signature" reports the following: ``` Ubuntu 5.0.0-16.17-generic 5.0.8 ``` "apt-cache policy linux-firmware" reports the following: ``` linux-firmware: Installed: 1.178.1 Candidate: 1.178.1 Version table: *** 1.178.1 500 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages 100 /var/lib/dpkg/status 1.178 500 500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 2314 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 16 12:31:07 2019 InstallationDate: Installed on 2019-06-02 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc. Bus 001 Device 003: ID 5986:066d Acer, Inc Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: PC Specialist Limited N15_17RD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: N15_17RD dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N15_17RD dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist Limited To manage notifications about this bug go to:
[Desktop-packages] [Bug 1836851] [NEW] /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_put:profile_new_connection
*** This bug is a duplicate of bug 1690052 *** https://bugs.launchpad.net/bugs/1690052 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:11.1-1ubuntu7.2, the problem page at https://errors.ubuntu.com/problem/215a0c1d7c39152b104eca0369f9ea0b76a04e7a 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/. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic wily -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1836851 Title: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_put:profile_new_connection Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:11.1-1ubuntu7.2, the problem page at https://errors.ubuntu.com/problem/215a0c1d7c39152b104eca0369f9ea0b76a04e7a 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/pulseaudio/+bug/1836851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836851] Re: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_put:profile_new_connection
*** This bug is a duplicate of bug 1690052 *** https://bugs.launchpad.net/bugs/1690052 ** This bug has been marked a duplicate of bug 1690052 pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1836851 Title: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_put:profile_new_connection Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:11.1-1ubuntu7.2, the problem page at https://errors.ubuntu.com/problem/215a0c1d7c39152b104eca0369f9ea0b76a04e7a 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/pulseaudio/+bug/1836851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1690052] Re: pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state()
** Summary changed: - pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() from endpoint_set_configuration() from endpoint_handler() + pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() ** Tags added: cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690052 Title: pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() Status in pulseaudio package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/49a8e58cea0b15b22d3a3cdbb1d736e619467e34 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 you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836850] Re: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:profile_new_connection:profile_handler
*** This bug is a duplicate of bug 1690052 *** https://bugs.launchpad.net/bugs/1690052 ** This bug has been marked a duplicate of bug 1690052 pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1836850 Title: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:profile_new_connection:profile_handler Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/fae9d4e8e68acd1bce20c4c187d94c1e66cb5202 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/pulseaudio/+bug/1836850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836849] Re: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_unlink:rfcomm_io_callback
*** This bug is a duplicate of bug 1690052 *** https://bugs.launchpad.net/bugs/1690052 ** This bug has been marked a duplicate of bug 1690052 pulseaudio crashed with SIGABRT in transport_state_changed_cb() from pa_hook_fire() from pa_bluetooth_transport_set_state() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1836849 Title: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_unlink:rfcomm_io_callback Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/23c16d54f398bab7ef2d00f464fb9617535fab5d 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/pulseaudio/+bug/1836849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836849] [NEW] /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_unlink:rfcomm_io_callback
*** This bug is a duplicate of bug 1690052 *** https://bugs.launchpad.net/bugs/1690052 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/23c16d54f398bab7ef2d00f464fb9617535fab5d 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/. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1836849 Title: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:pa_bluetooth_transport_unlink:rfcomm_io_callback Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/23c16d54f398bab7ef2d00f464fb9617535fab5d 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/pulseaudio/+bug/1836849/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836850] [NEW] /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:profile_new_connection:profile_handler
*** This bug is a duplicate of bug 1690052 *** https://bugs.launchpad.net/bugs/1690052 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/fae9d4e8e68acd1bce20c4c187d94c1e66cb5202 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/. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic wily xenial yakkety zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1836850 Title: /usr/bin/pulseaudio:6:transport_state_changed_cb:pa_hook_fire:pa_bluetooth_transport_set_state:profile_new_connection:profile_handler Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:12.2-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/fae9d4e8e68acd1bce20c4c187d94c1e66cb5202 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/pulseaudio/+bug/1836850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1768169] Re: touchscreen doesn't work properly after stylus detection
I have HP Spectre X360 13" 2019 Model, and have the same problem. After the touch pen/stylus is detected, finger touch stops working. Is there any workaround or command to get it working again? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1768169 Title: touchscreen doesn't work properly after stylus detection Status in xinput package in Ubuntu: Confirmed Bug description: I have a HP Pavilion x360 convertible 15 br0xx. This laptop has a multitouch touchscreen and an active pen/stylus. On ubuntu 16.04, the touchscreen used with fingers and the pen/stylus work properly. The touchscreen was identified as «ELAN0732:00 04F3:24B8» as slave pointer and the pen as «ELAN0732:00 04F3:24B8 Pen» as slave pointer too. But, on ubuntu 18.04 bionic with gnome shell, the pen/stylus is identified «ELAN0732:00 04F3:24B8 Pen» as slave keyboard instead as slave pointer. Touchscreen work well until pen/stylus is used. At this point, a new device «ELAN0732:00 04F3:24B8 Pen Pen (0)» is enabled. The touchscreen stops working and the pen/styles works but with some issues. ~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpadid=15 [slave pointer (2)] ⎜ ↳ ELAN0732:00 04F3:24B8 id=10 [slave pointer (2)] ⎜ ↳ ELAN0732:00 04F3:24B8 Pen Pen (0) id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ HP Wide Vision HD Camera: HP Wi id=9[slave keyboard (3)] ↳ Intel Virtual Button driver id=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ HP WMI hotkeys id=16 [slave keyboard (3)] ↳ HP Wireless hotkeys id=17 [slave keyboard (3)] ↳ ELAN0732:00 04F3:24B8 Pen id=11 [slave keyboard (3)] After disable devices id=11 and id=18, touchscreen recovers its multitouch feature. There is no combination enabling/disabling ids 10, 11 and 18, to get multitouch and pen working together. On Wayland session, I get the same behavior. Note: Ubuntu 18.04 LTS clean installation with «minimal install option» and no other customization. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1768169/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
