[Desktop-packages] [Bug 1828699] Re: Nautilus does not show file copy progress bar
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1828699 Title: Nautilus does not show file copy progress bar Status in nautilus package in Ubuntu: Expired Bug description: On a fresh install of Ubuntu 19.04, when I copy files using nautilus there is not progress bar. $ lsb_release -rd Description: Ubuntu 19.04 Release: 19.04 $ apt-cache policy nautilus nautilus: Installed: 1:3.32.0-0ubuntu2 Candidate: 1:3.32.0-0ubuntu2 Version table: *** 1:3.32.0-0ubuntu2 500 500 http://ch.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun May 12 00:35:52 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(967, 550)' b'org.gnome.nautilus.preferences' b'always-use-location-entry' b'true' b'org.gnome.nautilus.preferences' b'executable-text-activation' b"'ask'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2019-05-06 (5 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1828699/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836290] Re: gnome-shell crashed sig SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' faile
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1836290 Title: gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-0ubuntu1.18.10.1, the problem page at https://errors.ubuntu.com/problem/16980e5f7b42fc2050966cb19d62ef34794d6d3e 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/gnome-shell/+bug/1836290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836290] Re: gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' fail
** Summary changed: - gnome-shell crashed sig SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. + gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. -- 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/1836290 Title: gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-0ubuntu1.18.10.1, the problem page at https://errors.ubuntu.com/problem/16980e5f7b42fc2050966cb19d62ef34794d6d3e 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/gnome-shell/+bug/1836290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836290] Re: gnome-shell crashed sig SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' faile
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1836290 Title: gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-0ubuntu1.18.10.1, the problem page at https://errors.ubuntu.com/problem/16980e5f7b42fc2050966cb19d62ef34794d6d3e 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/gnome-shell/+bug/1836290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836290] Re: gnome-shell crashed sig SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' faile
** Summary changed: - /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. + gnome-shell crashed sig SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. ** Tags added: nouveau ** Also affects: mesa (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/1836290 Title: gnome-shell crashed with SIGABRT in assertion failure: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-0ubuntu1.18.10.1, the problem page at https://errors.ubuntu.com/problem/16980e5f7b42fc2050966cb19d62ef34794d6d3e 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/gnome-shell/+bug/1836290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836290] [NEW] /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed.
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-0ubuntu1.18.10.1, the problem page at https://errors.ubuntu.com/problem/16980e5f7b42fc2050966cb19d62ef34794d6d3e 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: gnome-shell (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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1836290 Title: /usr/bin/gnome-shell:gnome-shell: ../src/gallium/drivers/nouveau/nvc0/nvc0_state_validate.c:258: nvc0_validate_fb: Assertion `!fb->zsbuf' failed. Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.2-0ubuntu1.18.10.1, the problem page at https://errors.ubuntu.com/problem/16980e5f7b42fc2050966cb19d62ef34794d6d3e 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/gnome-shell/+bug/1836290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 991002] Re: Use the modern English name Bangla instead of Bengali for the language code bn
This bug was fixed in the package ibus - 1.5.19-4ubuntu2 --- ibus (1.5.19-4ubuntu2) eoan; urgency=medium * debian/patches/git-support-common_name-in-ISO-639.patch: - Use "Bangla" instead of "Bengali" when labeling bn IBus input methods for the UIs (LP: #991002). -- Gunnar Hjalmarsson Wed, 10 Jul 2019 18:46:00 +0200 ** Changed in: ibus (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/991002 Title: Use the modern English name Bangla instead of Bengali for the language code bn Status in CLDR: Fix Released Status in GLibC: Fix Released Status in gnome-desktop: New Status in ibus: Fix Released Status in xkeyboard-config: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Released Status in iso-codes package in Ubuntu: Fix Released Status in langpack-locales package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in localechooser package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in iso-codes package in Debian: Fix Released Status in xkeyboard-config package in Debian: Fix Released Bug description: The official name for the state language for Bangladesh is Bangla, as detailed on section 3, part 1 of the Bangladesh constitution (http://www1.umn.edu/humanrts/research/bangladesh-constitution.pdf). However, language selector continues to refer to this language as Bengali (Bangladeh). While Bengali has been historically used as the english name for the language during colonial periods, the name 'Bangla' is more widely used nowadays. It is also the name with which native speakers identify the language. This package uses Bengali(Bangladesh) as the identifier for language code bn-BD. Please change the name to Bangla(Bangladesh). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: language-selector-gnome 0.79 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 29 16:14:25 2012 PackageArchitecture: all ProcEnviron: LANGUAGE=bn_BD:bn:en_IN:en_GB:en PATH=(custom, no user) LANG=bn_BD.UTF-8 SHELL=/bin/bash SourcePackage: language-selector UpgradeStatus: Upgraded to precise on 2012-03-19 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/cldr/+bug/991002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
https://crbug.com/ Issue 983203 in chromium: video playback fails and freezes chromium and Ubuntu and then crashes Inbox x Updates x dalecur… via monorail 12:55 PM (8 hours ago) to me Comment #1 on issue 983203 by dalecur...@chromium.org: video playback fails and freezes chromium and Ubuntu and then crashes https://bugs.chromium.org/p/chromium/issues/detail?id=983203#c1 Sorry we don't provide support for Chromium builds. You'll need to see if the issue reproduces with an official Google Chrome build: https://www.google.com/chrome/ The official build should generate a crash report in chrome://crashes then. Have you tried this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1835623 Title: Google Chrome Linux version 75 freezes and then crashes when trying to play any video Status in chromium-browser package in Ubuntu: Incomplete Bug description: 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 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
since I cannot give a an error report about chromium or chrome You cannot possibly say that my bug report is incomplete. -- 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: Incomplete Bug description: 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 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
chrome://crashes does not give a crash report after chrome 75 freezes and then crashes HELP! chromium 75 is the same, no crash report -- 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: Incomplete Bug description: 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 1816702] Re: Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless keyboard attached)
I'll have to re-test this; just did a Lubuntu 19.10 (daily) QA-test on the j3400 mentioned, and it was woken using power-button and only wacom- pen was required to resume session. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1816702 Title: Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless keyboard attached) Status in gnome-power-manager package in Ubuntu: New Bug description: Ubuntu 19.04 QA-TEST on tablet.pc (wacom pen) motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series) The test went really well, but I noticed I couldn't wake it if left alone and screen dims & thus locks using tablet buttons or pen (& its button). This is [most] likely device specific & is very MINOR. It woke perfectly when keyboard/stand was attached, but not with the device's arrow keys, button, or any on screen mouse movement (using pen, including pen button). If the device dimmed screen with onscreen keyboard no longer visible, and I couldn't wake it. The result was you had to connect keyboard/stand in order to wake device... The track-pad on the keyboard/stand woke machine too, but that required keyboard to be attached. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-power-manager 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 20 07:00:51 2019 LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1816702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1830867] Re: [ThinkPad X1 Carbon 6th] Crackling sound with HDMI
** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1830867 Title: [ThinkPad X1 Carbon 6th] Crackling sound with HDMI Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, I have a new laptop and I cannot manage to have a clean and stable sound with HDMI. It happens every time I play a track on Spotify (desktop and web), sometimes from a VLC radio or a youtube video, never from a video with VLC yet. I'm attaching a record of what I hear when I play a track from Spotify. I created two reports. One during a Spotify playing, when it is crackling and after the sound started to crackle everywhere: http://alsa-project.org/db/?f=4e7d724718a48179fa2f3740d5f3e634ad75def9 Another after a fresh reboot, where the sound is correct with at least YouTube: http://alsa-project.org/db/?f=2ec68f888bb93a0de648d48fd720f54cee644564 Just after this last report, the sound is still crackling with Spotify and VLC radio. Not with Youtube. A diff on theses files gives some differences I find suspect. Are there expected ? Do you have an idea where the problem comes from ? Thank you for your support ! Edouard --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edouard1677 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-05-28T23:16:01.413832 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language
This bug has only been reported against Ubuntu 18.10 most recently, which reaches end of life this month. Please let us know if you are experiencing this bug on any other release so that this bug won't get automatically closed. -- 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/1652618 Title: Impossible to unlock the screen when using non-English language Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Add another keyboard layout, e.g. Russian. Set key combination to switch languages to Capslock 2. Change keyboard layout to Russian. 3. Lock the screen with Ctrl-Alt-l 4. Try to unlock the screen No matter what it's impossible now to unlock the screen. Changing keyboard layout with key combination or using mouse doesn't help. System always reports invalid password. It works absolutely fine if keyboard layout before locking the screen was English. I was able to reproduce it on clean 16.10 install in VM. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.20.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 26 16:43:30 2016 DisplayManager: lightdm InstallationDate: Installed on 2016-09-16 (100 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1652618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836278] [NEW] GDM seems to be crashing with multiple monitors
Public bug reported: Boot process halts at the point it normally runs gdm, it seems to keep re-trying. I learned that if I turn off the third and fourth monitor it will successfully run the desktop without crashing on the first two monitors. Once desktop (X) is fully operational, I can turn on third and fourth monitor and the workspace is initialized and I have (4) working monitors. I have never reported a bug before please excuse any faux pas. Best Regards, and wanted to say Thanks! for all the wonderful and amazing software. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 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 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 18:36:14 2019 InstallationDate: Installed on 2019-01-10 (182 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1836278 Title: GDM seems to be crashing with multiple monitors Status in gdm3 package in Ubuntu: New Bug description: Boot process halts at the point it normally runs gdm, it seems to keep re-trying. I learned that if I turn off the third and fourth monitor it will successfully run the desktop without crashing on the first two monitors. Once desktop (X) is fully operational, I can turn on third and fourth monitor and the workspace is initialized and I have (4) working monitors. I have never reported a bug before please excuse any faux pas. Best Regards, and wanted to say Thanks! for all the wonderful and amazing software. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.4 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 CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 18:36:14 2019 InstallationDate: Installed on 2019-01-10 (182 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1836278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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]
Created attachment 283631 alsa-info on MSI X370 Krait Gaming (MS-7A33) Adding alsa-info, same problem as everyone else - playback is perfect, mic recording crackles. This seems like a rather popular chipset, are we all gonna have to buy USB dongles?! -- 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 1801540]
Tried everything, including downgrade to a previous kernel, same behavior. The only thing I get in dmesg now is: [3.146686] hdaudio hdaudioC0D0: Unable to bind the codec [3.150739] hdaudio hdaudioC1D0: Unable to bind the codec Really useful. -- 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 1801540]
Same Bug on Manjaro with kernel 5.2 and the MSI X370 Titanium / ALC1220 -- 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 1801540]
Same here. Running on Asus Rog Strix b350-f Gaming. OS: Ubuntu 19.04 - Kernel 5.0.20 - Gnome 3.32 Noticed that when I use Xorg, my input from webcam works out of the box on discord. Now on wayland I need to set tsched=0. Looking at the syslog says that discord was trying to use 48kHz instead of the default 44.1kHz. Already tryied to set "alternative frequency" to 44.1kHz like the default frequency, without success. Now using a usb audio to workaround. -- 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 1801540]
After purging VFIO finally the PCI audio cards works again even after reenabling it. However now from the front panel only the right channel works from the front jack, from the back both works correctly. I don't really understand anything now; nor what the problem is. I'll try to replay some interesting commands from the decoded win dump, hoping for the best; however with all this random problems popping up, I'll really doubt that I will be able to fix anything. -- 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 1801540]
Created attachment 283619 alsa-info now completely ignores my PCI audio cards -- 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 1801540]
Well, another update that probably will be the last one from me, since I'm beginning to really hate ALSA. Decided today to try to test some parameters; I had left the audio card loaded with VFIO module since the command dump. Today I've decided to retry to use it, so I've removed the VFIO stubs from modprobe, rebooted and... no PCI audio card. Disabled IOMMU to force load the modules (something like this was already seen by me; even when VFIO wasn't asked to bind it, it would bind it anyway), no PCI audio card. lsmod says that the module is loaded on the audio card, however no audio from any PCI devices, even the audio from the GPU. I'll attach alsa-info. Just for reference on your list, when the module was working, I had output working fine, but input crackling. -- 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 1801540]
I have the same problem, input crackling, output ok. My setup: ASUS PRIME X470-PRO (ALC1220, latest bios 5007), Ryzen 2700X, 32GB ECC RAM, Kernel 4.19.58. This is really annoying, I'm using a USB dongle for mic input as workaround, but the SNR is not as good as the onboard audio. Tried to fiddle with ALSA kernel module param and pulse audio param, without success. -- 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 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation
I fixed the workaround script mentioned above here:
https://gist.github.com/satmandu/2f2da70a7a6bbbacdba01ef8fb8c18f4
This "works" on my system.
(dbus-send doesn't get the right info to work unless you give it the
info of the logged in user, which "machinectl shell" can do.)
Hopefully the fix gets merged soon and I can stop using this ugly hack.
:)
#!/bin/bash
# Place file in /lib/systemd/system-sleep/
# Run chmod +x on the file.
# This works around the wallpaper corruption on resume from suspend with Nvidia
GPUs
# reported at https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084
# and due to this feature of the Nvidia driver:
#
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
# Adapted from Paul Knopf
(https://gitlab.gnome.org/GNOME/gnome-shell/issues/1084)
# and via
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407/comments/22
# Note that this does show the user's screen when coming out of sleep briefly.
# machinectl can be found in the systemd-container package on Ubuntu.
PROGNAME=$(/usr/bin/basename "$0")
state=$1
action=$2
function log {
/usr/bin/logger -i -t "$PROGNAME" "$*"
}
log "Running $action $state"
if [[ $state == post ]]; then
log "WAKE UP"
pid_Gnome=($(/usr/bin/pgrep gnome-session))
pid_Gnome=("${pid_Gnome[@]%%:*}")
command="/usr/bin/dbus-send --type=method_call --dest=org.gnome.Shell
/org/gnome/Shell org.gnome.Shell.Eval "string:global.reexec_self\(\)""
for i in "${pid_Gnome[@]}"
do
user=$(/bin/ps -o user= -p $i)
log $i $user
if [ "$user" != "gdm" ]; then
log "machinectl shell $user@.host $command"
/bin/machinectl shell $user@.host $command
fi
done
fi
exit 0
--
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
Re: [Desktop-packages] [Bug 1776030] Re: Backup fails with "an unknown error"
Are those files you need backed up? Otherwise, you can put them in the
"folders to be ignored" list.
On 7/11/19 4:19 PM, Filofel wrote:
> Michael (#7):
> 18.04.2 x64:
> I uninstalled deja-dup and duplicity then did what you suggested (snap
> install etc.).
> It mostly solved the problem I had (#6).
> Thanks!
>
> Still, the backup ended with the following error message:
>
> Backup Finished
>
> Could not back up the following files. Please make sure you are able to
> open them.
>
> /home/philippe/.cache/deconf
> /home/philippe/.dbus
>
> Anything I could do to fix those?
>
--
John F. Ervin
jer...@cfl.rr.com
407-679-6514
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1776030
Title:
Backup fails with "an unknown error"
Status in deja-dup package in Ubuntu:
Confirmed
Bug description:
Trying to a backup to a network drive. Yesterday Backup decided to do
the preiodic full backup. But it fails, and I get the following error
information with the "unknown error" message:
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1522, in do_backup
check_last_manifest(col_stats) # not needed for full backup
File "/usr/bin/duplicity", line 1227, in check_last_manifest
last_backup_set.check_manifests()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 201,
in check_manifests
remote_manifest = self.get_remote_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 242,
in get_remote_manifest
return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 188, in
from_string
vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 388, in
from_string
raise VolumeInfoError("Start or end index not set")
VolumeInfoError: Start or end index not set
lsb_release -rd >
Description: Ubuntu 18.04 LTS
Release: 18.04
apt-cache policy deja-dup >
deja-dup:
Installed: 37.1-2fakesync1
Candidate: 37.1-2fakesync1
Version table:
*** 37.1-2fakesync1 500
500 http://la-mirrors.evowise.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: deja-dup 37.1-2fakesync1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 9 21:14:08 2018
InstallationDate: Installed on 2016-02-26 (834 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to bionic on 2018-05-03 (37 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1776030/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1776030] Re: Backup fails with "an unknown error"
Michael (#7):
18.04.2 x64:
I uninstalled deja-dup and duplicity then did what you suggested (snap install
etc.).
It mostly solved the problem I had (#6).
Thanks!
Still, the backup ended with the following error message:
Backup Finished
Could not back up the following files. Please make sure you are able to
open them.
/home/philippe/.cache/deconf
/home/philippe/.dbus
Anything I could do to fix those?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to deja-dup in Ubuntu.
https://bugs.launchpad.net/bugs/1776030
Title:
Backup fails with "an unknown error"
Status in deja-dup package in Ubuntu:
Confirmed
Bug description:
Trying to a backup to a network drive. Yesterday Backup decided to do
the preiodic full backup. But it fails, and I get the following error
information with the "unknown error" message:
Traceback (innermost last):
File "/usr/bin/duplicity", line 1555, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
File "/usr/bin/duplicity", line 1522, in do_backup
check_last_manifest(col_stats) # not needed for full backup
File "/usr/bin/duplicity", line 1227, in check_last_manifest
last_backup_set.check_manifests()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 201,
in check_manifests
remote_manifest = self.get_remote_manifest()
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 242,
in get_remote_manifest
return manifest.Manifest().from_string(manifest_buffer)
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 188, in
from_string
vi = VolumeInfo().from_string(match.group(1))
File "/usr/lib/python2.7/dist-packages/duplicity/manifest.py", line 388, in
from_string
raise VolumeInfoError("Start or end index not set")
VolumeInfoError: Start or end index not set
lsb_release -rd >
Description: Ubuntu 18.04 LTS
Release: 18.04
apt-cache policy deja-dup >
deja-dup:
Installed: 37.1-2fakesync1
Candidate: 37.1-2fakesync1
Version table:
*** 37.1-2fakesync1 500
500 http://la-mirrors.evowise.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: deja-dup 37.1-2fakesync1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 9 21:14:08 2018
InstallationDate: Installed on 2016-02-26 (834 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: deja-dup
UpgradeStatus: Upgraded to bionic on 2018-05-03 (37 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1776030/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835922] Re: missing gl* symbols in version 19.0.2
Also facing same issue and downgrading to 18.0.0~rc5-1ubuntu1 version works fine locally. However for heroku hosting (heroku-18 stack), specifying 18.0.0~rc5-1ubuntu1 release in Aptfile doesn't install correctly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835922 Title: missing gl* symbols in version 19.0.2 Status in mesa package in Ubuntu: Confirmed Bug description: Linking with libosmesa6-dev version 19.0.2 will fail because all the gl* symbols are missing: ``` [100%] Linking CXX executable bin/minko-converter ../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o): In function `jas_stream_tmpfile': jas_stream.c:(.text+0x6fd): warning: the use of `tmpnam' is dangerous, better use `mkstemp' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::clear(unsigned int, float, float, float, float, float, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0xb3): undefined reference to `glDepthMask' OpenGLES2Context.cpp:(.text+0xd9): undefined reference to `glClearDepth' OpenGLES2Context.cpp:(.text+0xe7): undefined reference to `glClearColor' OpenGLES2Context.cpp:(.text+0xfc): undefined reference to `glClearStencil' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, unsigned int, int)': OpenGLES2Context.cpp:(.text+0x120): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, int)': OpenGLES2Context.cpp:(.text+0x153): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadVertexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x191): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadIndexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x1db): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x297): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x2aa): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x2b9): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteIndexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x332): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x345): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x354): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::setVertexBufferAt(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0x527): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x559): undefined reference to `glVertexAttribPointer' OpenGLES2Context.cpp:(.text+0x59a): undefined reference to `glDisableVertexAttribArray' OpenGLES2Context.cpp:(.text+0x61e): undefined reference to `glEnableVertexAttribArray' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::createVertexAttributeArray()': OpenGLES2Context.cpp:(.text+0x65f): undefined reference to `glGenVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexAttributeArray(unsigned int)': OpenGLES2Context.cpp:(.text+0x6b3): undefined reference to `glDeleteVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadCubeTextureData(unsigned int, minko::render::CubeTexture::Face, unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x6e4): undefined reference to `glBindTexture' OpenGLES2Context.cpp:(.text+0x736): undefined reference to `glTexImage2D' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadTexture2dData(unsigned int, unsigned int, unsigned int, unsigned int,
[Desktop-packages] [Bug 1835922] Re: missing gl* symbols in version 19.0.2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1835922 Title: missing gl* symbols in version 19.0.2 Status in mesa package in Ubuntu: Confirmed Bug description: Linking with libosmesa6-dev version 19.0.2 will fail because all the gl* symbols are missing: ``` [100%] Linking CXX executable bin/minko-converter ../smartshape-engine/build/plugin/devil/bin/libminko-plugin-devil.a(jas_stream.c.o): In function `jas_stream_tmpfile': jas_stream.c:(.text+0x6fd): warning: the use of `tmpnam' is dangerous, better use `mkstemp' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::clear(unsigned int, float, float, float, float, float, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0xb3): undefined reference to `glDepthMask' OpenGLES2Context.cpp:(.text+0xd9): undefined reference to `glClearDepth' OpenGLES2Context.cpp:(.text+0xe7): undefined reference to `glClearColor' OpenGLES2Context.cpp:(.text+0xfc): undefined reference to `glClearStencil' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, unsigned int, int)': OpenGLES2Context.cpp:(.text+0x120): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::drawTriangles(unsigned int, int)': OpenGLES2Context.cpp:(.text+0x153): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadVertexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x191): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadIndexBufferData(unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x1db): undefined reference to `glBindBuffer' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x297): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x2aa): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x2b9): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteIndexBuffer(unsigned int)': OpenGLES2Context.cpp:(.text+0x332): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x345): undefined reference to `glBufferData' OpenGLES2Context.cpp:(.text+0x354): undefined reference to `glDeleteBuffers' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::setVertexBufferAt(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int)': OpenGLES2Context.cpp:(.text+0x527): undefined reference to `glBindBuffer' OpenGLES2Context.cpp:(.text+0x559): undefined reference to `glVertexAttribPointer' OpenGLES2Context.cpp:(.text+0x59a): undefined reference to `glDisableVertexAttribArray' OpenGLES2Context.cpp:(.text+0x61e): undefined reference to `glEnableVertexAttribArray' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::createVertexAttributeArray()': OpenGLES2Context.cpp:(.text+0x65f): undefined reference to `glGenVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::deleteVertexAttributeArray(unsigned int)': OpenGLES2Context.cpp:(.text+0x6b3): undefined reference to `glDeleteVertexArrays' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadCubeTextureData(unsigned int, minko::render::CubeTexture::Face, unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x6e4): undefined reference to `glBindTexture' OpenGLES2Context.cpp:(.text+0x736): undefined reference to `glTexImage2D' ../smartshape-engine/build/framework/bin/libminko-framework.a(OpenGLES2Context.cpp.o): In function `minko::render::OpenGLES2Context::uploadTexture2dData(unsigned int, unsigned int, unsigned int, unsigned int, void*)': OpenGLES2Context.cpp:(.text+0x7c5): undefined reference to
[Desktop-packages] [Bug 1652618] Re: Impossible to unlock the screen when using non-English language
Hello Guys, this bug sucks! Please fix it soon. -- 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/1652618 Title: Impossible to unlock the screen when using non-English language Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Add another keyboard layout, e.g. Russian. Set key combination to switch languages to Capslock 2. Change keyboard layout to Russian. 3. Lock the screen with Ctrl-Alt-l 4. Try to unlock the screen No matter what it's impossible now to unlock the screen. Changing keyboard layout with key combination or using mouse doesn't help. System always reports invalid password. It works absolutely fine if keyboard layout before locking the screen was English. I was able to reproduce it on clean 16.10 install in VM. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.20.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Dec 26 16:43:30 2016 DisplayManager: lightdm InstallationDate: Installed on 2016-09-16 (100 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-shell UpgradeStatus: Upgraded to yakkety on 2016-12-09 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1652618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1584386] Re: Main monitor doesn't wake up after system suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1584386 Title: Main monitor doesn't wake up after system suspend Status in xorg package in Ubuntu: Confirmed Bug description: If I lock my Unity session (Super+L) and power down my two monitors using external power switch, when after a few minutes I restore the power to monitors and wake up Ubuntu only my VGA connected LG display wakes up. My main monitor - a DisplayPort connected Dell U2410 wakes up only for a brief moment (it's power led goes blue from yellow) but before any picture would be displayed it goes back to sleep mode (led goes yellow again). All of this is true only for X session. If I switch to tty1 (Ctrl+Alt+F1) the Dell wakes up correctly and shows tty1. Going back to X (Ctrl+Alt+F7) causes this monitor to go to power save mode again. The only means for me to get my main display back in X is to restart the computer, as logging in and out of X doesn't help. I have also tried running Displays configuration tool while in X, but what it only does is that once I click "Detect Displays" button Dell's power led goes blue for a brief moment and then immediately back to yellow (power save mode). I haven't encountered such behavior with Ubuntu 14.04, nor have I experienced right after migrating to 16.04. I believe this regression showed up with some update within the last two weeks. Both monitors are hooked up to AMD Radeon 5850 graphics card. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 BootLog: Scanning for Btrfs filesystems Ubuntu_Root: clean, 690241/3670016 files, 6292028/14652416 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat May 21 21:22:43 2016 DistUpgraded: 2016-04-23 22:19:53,020 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cypress PRO [Radeon HD 5850] [1002:6899] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Cypress PRO [Radeon HD 5850] [1002:0b00] InstallationDate: Installed on 2015-08-22 (272 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7583 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=a709e3c2-0c9b-4102-8135-3a38cc17bd0b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-04-23 (27 days ago) dmi.bios.date: 08/18/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.11 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P55-GD65 (MS-7583) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.11:bd08/18/2011:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7583:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnP55-GD65(MS-7583):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7583 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat May 21 20:49:42 2016 xserver.configfile: default xserver.errors:
[Desktop-packages] [Bug 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
I just discovered that I can play audio but chromium freezes as well. Also after clicking in chromium many times chromium crashes, and Ubuntu crashes but not always. It seems that in chromium 75 the media process is started and then blocked. Whatever they added to control media playing seems to be the issue in version 75. Windows 10 chrome 75 seems to work fine -- 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: Incomplete Bug description: 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 1836237] [NEW] Left click doesn't work after resume from suspend
Public bug reported: I am using latest KDE, but I've observed it on Gnome too (on PopOS 18.04, based on Ubuntu). Probably a core bug in the libinput driver. I have to xinput enable/disable my mouse every time I resume from suspend. This bug is about 2 years old: https://askubuntu.com/questions/1083505/ubuntu-18-04-touchpad-not-fully- working-after-wake-from-suspend ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-libinput 0.28.2-2 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Thu Jul 11 20:23:40 2019 DistUpgraded: 2019-04-27 18:56:54,539 DEBUG new topwidget None DistroCodename: disco DistroVariant: ubuntu InstallationDate: Installed on 2018-11-15 (238 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-20-generic root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to disco on 2019-04-27 (75 days ago) dmi.bios.date: 03/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GJET98WW (2.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQCTO1WW dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1836237 Title: Left click doesn't work after resume from suspend Status in xserver-xorg-input-libinput package in Ubuntu: New Bug description: I am using latest KDE, but I've observed it on Gnome too (on PopOS 18.04, based on Ubuntu). Probably a core bug in the libinput driver. I have to xinput enable/disable my mouse every time I resume from suspend. This bug is about 2 years old: https://askubuntu.com/questions/1083505/ubuntu-18-04-touchpad-not- fully-working-after-wake-from-suspend ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xserver-xorg-input-libinput 0.28.2-2 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: KDE Date: Thu Jul 11 20:23:40 2019 DistUpgraded: 2019-04-27 18:56:54,539 DEBUG new topwidget None DistroCodename: disco DistroVariant: ubuntu InstallationDate: Installed on 2018-11-15 (238 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: LENOVO 20AQCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-20-generic root=/dev/mapper/kubuntu--vg-root ro psmouse.synaptics_intertouch=0 quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-libinput UpgradeStatus: Upgraded to disco on 2019-04-27 (75 days ago) dmi.bios.date: 03/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GJET98WW (2.48 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET98WW(2.48):bd03/20/2018:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50510PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQCTO1WW dmi.product.sku: LENOVO_MT_20AQ_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A
[Desktop-packages] [Bug 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video
I just filed a bug report on https://crbug.com/ -- 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: Incomplete Bug description: 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 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
For the record our plan is to backport the trigger processing fixes and that work is being tracked in bug 1828639. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1834583] Re: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus
In any case, When I close any dialog popup from java apps (Jdeveloper, NetBeans, SQLDeveloper) then I get gnome-shell running at 100% of processor and graphical interface hangs. I've checked for my mutter installed version: 3.32.2+git20190626-1ubuntu1~19.04.1 (/var/lib/apt/lists/archive.ubuntu .com_ubuntu_dists_disco-proposed_main_binary-amd64_Packages) (/var/lib/dpkg/status) Downgrading mutter and libmutter as Iliyas indicated, I can avoid the problem. Thanks to Ilyas and thanks to everyone. -- 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/1834583 Title: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus() Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: [ Description ] On my eaon system, closing any dialog in CLion (a Java program, which might be relevant) results in GNOME Shell hanging. I believe this to be a recent (in the last week or so, maybe?) regression. [ Test case ] $ sudo snap install clion - Start clion, open a file - Hit Ctrl+Shift+F - Select Directory -> Click "..." to select the path - Hit OK / Cancel - The dialog should show and the shell should be responsive [ Regression potential ] The wrong window or no window is focused when a window is destroyed. ProblemType: HangDistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 28 17:27:00 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/usr/bin/fish RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_private_get () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_free_chain_with_offset () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to eoan on 2019-05-31 (27 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1834583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816947] Re: [Dell XPS L321X] The touchpad doesn't work unless the cursor is moved slowly.
** Changed in: libinput Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1816947 Title: [Dell XPS L321X] The touchpad doesn't work unless the cursor is moved slowly. Status in libinput: Fix Released Status in libinput package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: The touchpad doesn't work unless the cursor is moved slowly. WORKAROUND: Execute at a terminal: sudo modprobe -r psmouse sudo modprobe psmouse proto=imps ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.402 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 02:56:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:052e] LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) MachineType: Dell Inc. Dell System XPS L321X ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L321X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1 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+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperVersion: 1.394 CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:052e] LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Dell System XPS L321X Package: libinput (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Tags: bionic ubuntu Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/27/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd12/27/2011:svnDellInc.:pnDellSystemXPSL321X:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L321X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1825981] Re: /usr/lib/tracker/tracker-extract:6:mem_error:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:thread_memory_magazine2_unload
** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825981 Title: /usr/lib/tracker/tracker- extract:6:mem_error:slab_allocator_free_chunk:magazine_cache_trim:magazine_cache_push_magazine:thread_memory_magazine2_unload Status in tracker package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding tracker. This problem was most recently seen with package version 2.1.6-1, the problem page at https://errors.ubuntu.com/problem/b99e01aacdc0c848c2170270ddbb577546a03a73 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/tracker/+bug/1825981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1834583] Re: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus
@vorlon, yes, you are right, already unchecked it. Did not know that I have checked proposed. It is my bad. -- 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/1834583 Title: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus() Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: [ Description ] On my eaon system, closing any dialog in CLion (a Java program, which might be relevant) results in GNOME Shell hanging. I believe this to be a recent (in the last week or so, maybe?) regression. [ Test case ] $ sudo snap install clion - Start clion, open a file - Hit Ctrl+Shift+F - Select Directory -> Click "..." to select the path - Hit OK / Cancel - The dialog should show and the shell should be responsive [ Regression potential ] The wrong window or no window is focused when a window is destroyed. ProblemType: HangDistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 28 17:27:00 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/usr/bin/fish RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_private_get () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_free_chain_with_offset () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to eoan on 2019-05-31 (27 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1834583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1834583] Re: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus
Ilyas, this bug was never released into a stable release of Ubuntu, it was identified while the change was present only in the devel series and in disco-proposed. If you are unhappy dealing with bugs of this sort, I strongly recommend that you not opt in to the proposed pocket, which contains packages they have not yet completed QA and been released to all users for general consumption. -- 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/1834583 Title: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus() Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: [ Description ] On my eaon system, closing any dialog in CLion (a Java program, which might be relevant) results in GNOME Shell hanging. I believe this to be a recent (in the last week or so, maybe?) regression. [ Test case ] $ sudo snap install clion - Start clion, open a file - Hit Ctrl+Shift+F - Select Directory -> Click "..." to select the path - Hit OK / Cancel - The dialog should show and the shell should be responsive [ Regression potential ] The wrong window or no window is focused when a window is destroyed. ProblemType: HangDistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 28 17:27:00 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/usr/bin/fish RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_private_get () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_free_chain_with_offset () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to eoan on 2019-05-31 (27 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1834583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704210] Re: NetworkManager does not disable accept_ra when a managed device is set to ipv6 method=ignore
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1704210 Title: NetworkManager does not disable accept_ra when a managed device is set to ipv6 method=ignore Status in network-manager package in Ubuntu: Confirmed Bug description: As per the title; it looks (at first glance anyway, running TestNetworkManager.test_eth_dhcp6_off integration test from nplan) like NM does not set accept_ra to false, or provide a method for specifying whether you want to accept IPv6 RAs on that device. When IPv6 is disabled, we might also not want the kernel to heed RAs and create SLAAC addresses. NM already is able to disable accept_ra, since it does so when a device transitions to UNAVAILABLE or DISCONNECTED in some cases (see src/devices/nm-device.c). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1704210/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1834583] Re: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus
On Ubuntu 19.04 run the following command to fix it (downgrading): sudo apt install \ gir1.2-mutter-4=3.32.0+git20190410-1ubuntu1 \ libmutter-4-0=3.32.0+git20190410-1ubuntu1 \ mutter=3.32.0+git20190410-1ubuntu1 \ mutter-common=3.32.0+git20190410-1ubuntu1 -- 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/1834583 Title: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus() Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: [ Description ] On my eaon system, closing any dialog in CLion (a Java program, which might be relevant) results in GNOME Shell hanging. I believe this to be a recent (in the last week or so, maybe?) regression. [ Test case ] $ sudo snap install clion - Start clion, open a file - Hit Ctrl+Shift+F - Select Directory -> Click "..." to select the path - Hit OK / Cancel - The dialog should show and the shell should be responsive [ Regression potential ] The wrong window or no window is focused when a window is destroyed. ProblemType: HangDistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 28 17:27:00 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/usr/bin/fish RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_private_get () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_free_chain_with_offset () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to eoan on 2019-05-31 (27 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1834583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818812] Re: glib: Fix named destinations
I can't do it myself, I'll have to ask upstream to do it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1818812
Title:
glib: Fix named destinations
Status in poppler package in Ubuntu:
Fix Released
Bug description:
IMPACT
---
Evince does not follow internal links in some PDF research articles (affects
Evince 3.28.4 + Poppler 0.62.0 on Ubuntu 18.04)
https://gitlab.gnome.org/GNOME/evince/issues/1070
PDF's link annotation does not work in Evince 3.30.2
https://gitlab.gnome.org/GNOME/evince/issues/1027
Evince does not follow internal links in some PDF research articles. The
internal links are used for easy and fast navigation to pages, figures,
references and equations.
qpdfview (poppler-qt5 viewer) can follow the internal links in those files
just fine.
DOI of one of the affected documents:
http://dx.doi.org/10.1016/j.apenergy.2016.10.058
Upstream fix:
https://gitlab.freedesktop.org/poppler/poppler/commit/44505cb397c46baa7dd4a0456f737f36e6d19ad0
TEST CASE
--
Clicking on the following parts should work after the fix is committed:
- Superscripts next to the authors names
- Citations in page 17 (e.g. [1], [9,11-18], [25-30])
- Figure and Table links in page 17 (Fig 1 and Table 1 at the beginning of
section 2)
- Equations in page 19 (they stay in the same page as the equations are very
close to their links)
REGRESSION POTENTIAL
-
This is quoted from the upstream commit:
"Named destinations may be described by bytestrings, containing
embedded NULs and not being NUL terminated. That means they cannot be
exposed directly as char*.
The alternatives are to escape the string from the internal representation
when exposing it in the API (e.g. in PopplerDest.named_dest), or to add
parallel API exposing it as GString, or GBytes. This patch chooses the first
option, since the presence of these named destionations in the public, not
sealed, PopplerDest struct means that the second option would need more API
additions. The chosen option is simpler, and does not need the API users to
adapt unless they create the named dest strings
themselves, or consume them in ways other than calling poppler APIs.
The escaping scheme chosen simply replaces embedded NUL with "\0" and
escapes a literal backslash with "\\". This is a minimal ABI change
in that some strings that previously worked unchanged as destinations
(those containing backslash) now don't work, but on the other hand,
previously it was impossible to use any destinations containing
embedded NULs.
Add poppler_named_dest_{from,to}_bytestring() to perform that
conversion, and clarify the documentation for when you need them."
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libpoppler-glib8 0.62.0-2ubuntu2.7
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Wed Mar 6 10:57:53 2019
InstallationDate: Installed on 2018-11-29 (96 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: poppler
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1818812/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-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] [NEW] network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9
Public bug reported: 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 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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 1834583] Re: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus
current workaround is to downgrade packages gir1.2-mutter-4 libmutter-4-0-dbgsym mutter to version from disco-updates (easier to do it with aptitude) don't forget to add disco-updates to sources.list (if u have eoan) deb http://ru.archive.ubuntu.com/ubuntu/ disco-updates universe -- 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/1834583 Title: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus() Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: [ Description ] On my eaon system, closing any dialog in CLion (a Java program, which might be relevant) results in GNOME Shell hanging. I believe this to be a recent (in the last week or so, maybe?) regression. [ Test case ] $ sudo snap install clion - Start clion, open a file - Hit Ctrl+Shift+F - Select Directory -> Click "..." to select the path - Hit OK / Cancel - The dialog should show and the shell should be responsive [ Regression potential ] The wrong window or no window is focused when a window is destroyed. ProblemType: HangDistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 28 17:27:00 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/usr/bin/fish RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_private_get () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_free_chain_with_offset () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to eoan on 2019-05-31 (27 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1834583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1834583] Re: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus
@fasaxc, can you explain this step more detailed please. Thanks. I am on linux for almost 12years but now I am thinking of buying MacBook. I am really sick of bugs like this one. So unprofessional :(( -- 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/1834583 Title: [eoan][regression] GNOME Shell hangs when closing a Java dialog; hung in (varying functions under) meta_stack_get_default_focus_window() from meta_window_x11_focus() Status in Mutter: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: [ Description ] On my eaon system, closing any dialog in CLion (a Java program, which might be relevant) results in GNOME Shell hanging. I believe this to be a recent (in the last week or so, maybe?) regression. [ Test case ] $ sudo snap install clion - Start clion, open a file - Hit Ctrl+Shift+F - Select Directory -> Click "..." to select the path - Hit OK / Cancel - The dialog should show and the shell should be responsive [ Regression potential ] The wrong window or no window is focused when a window is destroyed. ProblemType: HangDistroRelease: Ubuntu 19.10 Package: gnome-shell 3.32.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 28 17:27:00 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/usr/bin/fish RelatedPackageVersions: mutter-common 3.32.2+git20190626-1ubuntu1 Signal: 6SourcePackage: gnome-shell StacktraceTop: __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 () () at /lib/x86_64-linux-gnu/libc.so.6 g_private_get () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_free_chain_with_offset () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to eoan on 2019-05-31 (27 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1834583/+subscriptions -- Mailing list: https://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 1722256] Re: Wifi connection status icon shows a "?" question mark when connected
I will gather more info next time I see this. Rózsa Sándor ezt írta (időpont: 2019. júl. 11., Cs 15:42): > Hi, > > I am using Ubuntu 18.04 LTS. > > Cheers > Sándor > > Daniel van Vugt ezt írta (időpont: 2019. > júl. 11., Cs 3:50): > >> Sounds related, and maybe that's where the bug is. Although it's not an >> Ubuntu-specific issue... >> >> https://bugzilla.gnome.org/show_bug.cgi?id=750260 >> >> That said, I haven't seen this bug in a long time. If you do see it, >> what release are you using? >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1722256 >> >> Title: >> Wifi connection status icon shows a "?" question mark when connected >> >> Status in GNOME Shell: >> Confirmed >> Status in OEM Priority Project: >> Confirmed >> Status in gnome-shell package in Ubuntu: >> Triaged >> >> Bug description: >> https://bugzilla.gnome.org/show_bug.cgi?id=750260 >> >> Wifi connection status icon on the top bar shows a "?" even when >> connected to a wifi network. >> --- >> ApportVersion: 2.20.7-0ubuntu2 >> Architecture: amd64 >> CurrentDesktop: ubuntu:GNOME >> DisplayManager: gdm3 >> DistroRelease: Ubuntu 17.10 >> InstallationDate: Installed on 2017-09-28 (11 days ago) >> InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 >> (20170926) >> Package: gnome-shell 3.26.1-0ubuntu1 >> PackageArchitecture: amd64 >> ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 >> Tags: artful wayland-session >> Uname: Linux 4.13.0-12-generic x86_64 >> UpgradeStatus: No upgrade log present (probably fresh install) >> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo >> _MarkForUpload: True >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/gnome-shell/+bug/1722256/+subscriptions >> > -- 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/1722256 Title: Wifi connection status icon shows a "?" question mark when connected Status in GNOME Shell: Confirmed Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: https://bugzilla.gnome.org/show_bug.cgi?id=750260 Wifi connection status icon on the top bar shows a "?" even when connected to a wifi network. --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Package: gnome-shell 3.26.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722256/+subscriptions -- Mailing list: https://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 1722256] Re: Wifi connection status icon shows a "?" question mark when connected
Hi, I am using Ubuntu 18.04 LTS. Cheers Sándor Daniel van Vugt ezt írta (időpont: 2019. júl. 11., Cs 3:50): > Sounds related, and maybe that's where the bug is. Although it's not an > Ubuntu-specific issue... > > https://bugzilla.gnome.org/show_bug.cgi?id=750260 > > That said, I haven't seen this bug in a long time. If you do see it, > what release are you using? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1722256 > > Title: > Wifi connection status icon shows a "?" question mark when connected > > Status in GNOME Shell: > Confirmed > Status in OEM Priority Project: > Confirmed > Status in gnome-shell package in Ubuntu: > Triaged > > Bug description: > https://bugzilla.gnome.org/show_bug.cgi?id=750260 > > Wifi connection status icon on the top bar shows a "?" even when > connected to a wifi network. > --- > ApportVersion: 2.20.7-0ubuntu2 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DisplayManager: gdm3 > DistroRelease: Ubuntu 17.10 > InstallationDate: Installed on 2017-09-28 (11 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 > (20170926) > Package: gnome-shell 3.26.1-0ubuntu1 > PackageArchitecture: amd64 > ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 > Tags: artful wayland-session > Uname: Linux 4.13.0-12-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1722256/+subscriptions > -- 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/1722256 Title: Wifi connection status icon shows a "?" question mark when connected Status in GNOME Shell: Confirmed Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: https://bugzilla.gnome.org/show_bug.cgi?id=750260 Wifi connection status icon on the top bar shows a "?" even when connected to a wifi network. --- ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-09-28 (11 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Package: gnome-shell 3.26.1-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Tags: artful wayland-session Uname: Linux 4.13.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1722256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1830867] Re: [ThinkPad X1 Carbon 6th] Crackling sound with HDMI
** Changed in: linux (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1830867 Title: [ThinkPad X1 Carbon 6th] Crackling sound with HDMI Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Hello, I have a new laptop and I cannot manage to have a clean and stable sound with HDMI. It happens every time I play a track on Spotify (desktop and web), sometimes from a VLC radio or a youtube video, never from a video with VLC yet. I'm attaching a record of what I hear when I play a track from Spotify. I created two reports. One during a Spotify playing, when it is crackling and after the sound started to crackle everywhere: http://alsa-project.org/db/?f=4e7d724718a48179fa2f3740d5f3e634ad75def9 Another after a fresh reboot, where the sound is correct with at least YouTube: http://alsa-project.org/db/?f=2ec68f888bb93a0de648d48fd720f54cee644564 Just after this last report, the sound is still crackling with Spotify and VLC radio. Not with Youtube. A diff on theses files gives some differences I find suspect. Are there expected ? Do you have an idea where the problem comes from ? Thank you for your support ! Edouard --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edouard1677 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-05-28T23:16:01.413832 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1830867] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1830867 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1830867 Title: [ThinkPad X1 Carbon 6th] Crackling sound with HDMI Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: Hello, I have a new laptop and I cannot manage to have a clean and stable sound with HDMI. It happens every time I play a track on Spotify (desktop and web), sometimes from a VLC radio or a youtube video, never from a video with VLC yet. I'm attaching a record of what I hear when I play a track from Spotify. I created two reports. One during a Spotify playing, when it is crackling and after the sound started to crackle everywhere: http://alsa-project.org/db/?f=4e7d724718a48179fa2f3740d5f3e634ad75def9 Another after a fresh reboot, where the sound is correct with at least YouTube: http://alsa-project.org/db/?f=2ec68f888bb93a0de648d48fd720f54cee644564 Just after this last report, the sound is still crackling with Spotify and VLC radio. Not with Youtube. A diff on theses files gives some differences I find suspect. Are there expected ? Do you have an idea where the problem comes from ? Thank you for your support ! Edouard --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edouard1677 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-28 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: pulseaudio 1:12.2-2ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Tags: disco Uname: Linux 5.0.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-05-28T23:16:01.413832 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830867/+subscriptions -- Mailing list: https://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 1836051] Re: autamatic sleep notification cannot close
all right guis. I put my pc to sleep mode , not to Turn off. Attachment ,Notification in the middle is not goin to dissapear.. st 10. 7. 2019 o 17:01 Gunnar Hjalmarsson <1836...@bugs.launchpad.net> napísal(a): > ** Package changed: ubuntu-docs (Ubuntu) => gnome-control-center > (Ubuntu) > > ** Changed in: gnome-control-center (Ubuntu) >Status: Invalid => New > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1836051 > > Title: > autamatic sleep notification cannot close > > Status in gnome-control-center package in Ubuntu: > New > > Bug description: > I put my computer to sleep mode. 4 hours set afer no use. Vhen > notification appeared, I put comp to sleep. After woke up, > notification is still and can not close thru X. ubuntu-bug 18.04.2 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1836051/+subscriptions > ** Attachment added: "IMG_8952.JPG" https://bugs.launchpad.net/bugs/1836051/+attachment/5276501/+files/IMG_8952.JPG -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1836051 Title: autamatic sleep notification cannot close Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I put my computer to sleep mode. 4 hours set afer no use. Vhen notification appeared, I put comp to sleep. After woke up, notification is still and can not close thru X. ubuntu-bug 18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1836051/+subscriptions -- Mailing list: https://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 1817537] Re: libsoup should support ntlmv2
Sorry to say that unfortunately it's not working here. Authentication through ntlm still not working: - installed package from proposed: --- libsoup2.4 (2.62.1-1ubuntu0.2) bionic; urgency=medium * debian/patches/git_ntlmv2_support.patch, debian/patches/git_ntlmv2_test.patch: - include upstream changes for NTLMv2 responses support, that's required for evolution-ews to be able to connect some exchange servers, also include corresponding code tests (lp: #1817537) -- Sebastien Bacher Tue, 09 Jul 2019 17:00:43 +0200 --- - rebooted - same problem: using ntlm in Evolution still not possible, authentication not working. Thanks for your work! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsoup2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1817537 Title: libsoup should support ntlmv2 Status in libsoup2.4 package in Ubuntu: Fix Released Status in libsoup2.4 source package in Bionic: Fix Committed Bug description: * Impact Without NTLMv2 support evolution-ews can't connect to some exchange servers * Test case Try connecting from evolution-ews to an exchange server which enforces NTLMV2 * Regression potential The change adds extra cases in the ntlm handling support, it should impact existing feature but check out for any potential regression in libsoup user (check at least evolution and epiphany-browser). Note that the patch include additional code tests --- Our Exchange admins recently made NTLMv2 obligatory. Since then interaction with Exchange through Evolution isn't possible anymore. In newer versions of libsoup that has been implemented, see https://gitlab.gnome.org/GNOME/evolution-ews/issues/38 Could that be backported to Ubuntu 18.04? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libsoup2.4-1 2.62.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Feb 25 12:10:26 2019 SourcePackage: libsoup2.4 UpgradeStatus: Upgraded to bionic on 2018-09-27 (150 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1817537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 177929] Re: Should autodetect filename character encoding in zip files
*** This bug is a duplicate of bug 580961 *** https://bugs.launchpad.net/bugs/580961 Не могу прочитать zip-файлы с кириллическими именами файлов, созданными в Windows. -- 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/177929 Title: Should autodetect filename character encoding in zip files Status in file-roller package in Ubuntu: Triaged Status in xarchiver package in Ubuntu: Fix Released Bug description: Binary package hint: file-roller Many compressed file such as zip don't specify filename encoding. But file-roller read every file as UTF-8, so it sometimes makes encoding problem. I think may be, you could think that it's not a big problem or it's not a bug or we don't need those feature. If you deal with only English it's not a problem at all. But it's a big problem for East Asian people such as Chinese, Japanese and Korean. Because zip file is still popular. And many people compress zip file in Windows, and share the zip files. Windows don't use UTF-8. Many CJK people want to uncompress these zip files. There are some way to solve this problem (by another software). But all are too complex to Ubuntu newbies. I wish file-roller support encoding select function. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/177929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract
In the directory there are 10666 files, total size 735,5 MB. There are 723 .dds files with a total size of 248.2 MB >Could you run `tracker extract *` inside the problematic directory and see what happens There are various sub-directories with .dds files, running tracker inside them gives very similar outputs. Two outputs here https://pastebin.com/NTzha2Ww and here https://pastebin.com/MEiTzZPq It however doesn't loop forever, it just gives one error message for every single dds file and then exists properly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: Confirmed Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835936] Re: gnome-control-center crash ubuntu 18.04.2
** Package changed: ubuntu => gnome-control-center (Ubuntu) ** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1835936 Title: gnome-control-center crash ubuntu 18.04.2 Status in gnome-control-center package in Ubuntu: New Bug description: Ubuntu 18.04.02 fresh installed on Virtualbox 6.0.8 including Guest Additions on host Mac Pro running 10.14.5 Mojave in April 2019. Ubuntu system has latest patches EXCEPT mutter-2 (which cause login GUI to fail after reboot). crash logs for gnome-control-center, gnome-shell and seahorse attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1835936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835936] [NEW] gnome-control-center crash ubuntu 18.04.2
You have been subscribed to a public bug: Ubuntu 18.04.02 fresh installed on Virtualbox 6.0.8 including Guest Additions on host Mac Pro running 10.14.5 Mojave in April 2019. Ubuntu system has latest patches EXCEPT mutter-2 (which cause login GUI to fail after reboot). crash logs for gnome-control-center, gnome-shell and seahorse attached ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- gnome-control-center crash ubuntu 18.04.2 https://bugs.launchpad.net/bugs/1835936 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center 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 1832123] Autopkgtest regression report (gst-plugins-base1.0/1.14.5-0ubuntu1~18.04.1)
All autopkgtests for the newly accepted gst-plugins-base1.0 (1.14.5-0ubuntu1~18.04.1) for bionic have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic -- 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
[Desktop-packages] [Bug 1832123] Autopkgtest regression report (gst-plugins-good1.0/1.14.5-0ubuntu1~18.04.1)
All autopkgtests for the newly accepted gst-plugins-good1.0 (1.14.5-0ubuntu1~18.04.1) for bionic have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic -- 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
[Desktop-packages] [Bug 1832123] Autopkgtest regression report (gstreamer1.0/1.14.5-0ubuntu1~18.04.1)
All autopkgtests for the newly accepted gstreamer1.0 (1.14.5-0ubuntu1~18.04.1) for bionic have finished running. There have been regressions in tests triggered by the package. Please visit the sru report page and investigate the failures. https://people.canonical.com/~ubuntu-archive/pending-sru.html#bionic -- 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
[Desktop-packages] [Bug 1835956] Re: Deleting "Input Sources" not in use, affects the ones in use.
I tried to reproduce this (on 19.04). Added these layouts: 1. Spanish (Latin American) 2. Spanish (Win Keys) 3. Spanish (dead tilde) 4. Spanish Then I activated them in that order (and used each of them to type some characters). With "Spanish" (shown as "es₄") active I used Region & Language to remove the other Spanish variants. "Spanish" was changed to be shown as "es" (as expected) but I couldn't observe any problems to keep typing using the Spanish layout. So however you proceed with this, I think it's necessary that you make up a reproducible use case. If you succeed in that, then please be very specific about which keys don't result in the expected symbols. The "Show Keyboard Layout" option is useful to see which layout is active. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1835956 Title: Deleting "Input Sources" not in use, affects the ones in use. Status in gnome-control-center package in Ubuntu: Incomplete Bug description: I have a notebook, with an english keyboard layout, so "English (Us, intl, with dead keys) was my only option in "Region & Language / Input Sources". Now I want to use an external keyboard, which has a spanish distribution, so I tried adding "Spanish" (Let's call it "es1") to my "Input Sources" list. This is not quite my distribution, so I added a few more to try: "Spanish (with Sun Dead keys)" (es2), "Spanish (Latin American, with Sun dead keys)" (es3) and "Spanish (Win keys)" (es4). So after trying all this 4 options in spanish layouts, I decided that I want to use the (es4) option, because it fits my keyboard exactly, and I won't be needing any of the others spanish options. Just want to keep one for english and one for spanish. Now comes the strange behaviour: while "es4" is still my layout option in use, I go to "Input Sources" configuration and delete the input sources I won't be using (es1, es2 and es3). After deleting, I only have two options, one for english and one for spanish. The available keyboard layout for spanish is the same one I chose before, "Spanish (Win keys), but after deleting the other ones, this layout doesn't fit my keyboard any more. Some keys don't give me the same characters as they did when I was trying all the options and had the others layouts installed, but not in use. I've also noticed that installing a keyboard layout behaves different depending on whether there are other layouts installed or not. For example, if I install and use "Spanish" layout, when there is only "English" I don't get the same results if I install and use it when there are other "Spanish input sources" already installed. Cheers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4 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 CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Jul 9 16:37:29 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-07-05 (369 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1835956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] Please test proposed package
Hello Amr, or anyone else affected, Accepted gstreamer1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gstreamer1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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
[Desktop-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gstreamer-vaapi into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gstreamer- vaapi/1.14.5-0ubuntu1~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gstreamer1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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 -
[Desktop-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gstreamer-editing-services1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gstreamer-editing-services1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gstreamer-vaapi (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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
[Desktop-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gst-rtsp-server1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst-rtsp- server1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gstreamer-editing-services1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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
[Desktop-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gst-python1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- python1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gst-rtsp-server1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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 -
[Desktop-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gst-plugins-bad1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- plugins-bad1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gst-plugins-base1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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 -
[Desktop-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gst-plugins-ugly1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- plugins-ugly1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gst-python1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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 -
[Desktop-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gst-plugins-base1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- plugins-base1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gst-plugins-good1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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 -
[Desktop-packages] [Bug 1832123] Please test proposed package
Hello Amr, or anyone else affected, Accepted gst-plugins-good1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- plugins-good1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gst-plugins-ugly1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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 -
[Desktop-packages] [Bug 1832123] Re: [SRU] Bugfix release 1.14.5
Hello Amr, or anyone else affected, Accepted gst-libav1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst- libav1.0/1.14.5-0ubuntu1~18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gst-libav1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic ** Changed in: gst-plugins-bad1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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 -
[Desktop-packages] [Bug 1298534] Re: Mint 16 / 64-bit unable to mount via usb DROID Mini
Fixed in 1.1.7 upstream, so 1.1.10-2ubuntu1 in Ubuntu 16.04 has the fix.
** Project changed: linuxmint => libmtp (Ubuntu)
** Changed in: libmtp (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libmtp in Ubuntu.
https://bugs.launchpad.net/bugs/1298534
Title:
Mint 16 / 64-bit unable to mount via usb DROID Mini
Status in libmtp package in Ubuntu:
Fix Released
Bug description:
Installed 'mtp-tools' following instructions for "MTP' device recognition as
listed on http://www.linuxmint.com/. Have created file
'etc/udev/rules.d/51-android.rules which contains:
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="2e67", MODE="0666"
ownership is root:root and permissions 775
DROID mini still doesn't mount and am returned with:
noname@nonameM-A:~ > mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
Device 0 (VID=22b8 and PID=2e67) is UNKNOWN.
**
Please report this VID/PID and the device model to the libmtp development team
**
Found 1 device(s):
22b8:2e67 @ bus 1, dev 11
Attempting to connect device(s)
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session,
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get
object handles.
Error 2: Error 02fe: PTP: Protocol error, data expected
USB low-level info:
bcdUSB: 512
bDeviceClass: 0
bDeviceSubClass: 0
bDeviceProtocol: 0
idVendor: 22b8
idProduct: 2e67
IN endpoint maxpacket: 512 bytes
OUT endpoint maxpacket: 512 bytes
Raw device info:
Bus location: 1
Device number: 11
Device entry info:
Vendor: (null)
Vendor id: 0x22b8
Product: (null)
Vendor id: 0x2e67
Device flags: 0x08008106
Configuration 0, interface 0, altsetting 0:
Interface description contains the string "MTP"
Device recognized as MTP, no further probing.
Device info:
Manufacturer: motorola
Model: XT1030
Device version: 1.0
Serial number: TA6260EEFY
Vendor extension ID: 0x0006
Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
mot-mobility.com/DSU: 1.2
Detected object size: 64 bits
Extensions:
microsoft.com: 1.0
android.com: 1.0
Supported operations:
1001: get device info
1002: Open session
1003: Close session
1004: Get storage IDs
1005: Get storage info
1006: Get number of objects
1007: Get object handles
1008: Get object info
1009: Get object
100a: Get thumbnail
100b: Delete object
100c: Send object info
100d: Send object
1014: Get device property description
1015: Get device property value
1016: Set device property value
1017: Reset device property value
101b: Get partial object
9801: Get object properties supported
9802: Get object property description
9803: Get object property value
9804: Set object property value
9805: Get object property list
9810: Get object references
9811: Set object references
95c1: Get Partial Object (64bit Offset)
95c2: Send Partial Object
95c3: Truncate Object
95c4: Begin Edit Object
95c5: End Edit Object
9001: Unknown (9001)
9002: Unknown (9002)
9003: Unknown (9003)
9004: Unknown (9004)
9005: Unknown (9005)
9006: Unknown (9006)
9007: Unknown (9007)
9008: Unknown (9008)
9009: Unknown (9009)
900a: Unknown (900a)
900b: Unknown (900b)
900c: Unknown (900c)
Events supported:
0x4002
0x4003
0x4004
0x4005
Device Properties Supported:
0xd401: Synchronization Partner
0xd402: Friendly Device Name
0x5003: Image Size
Playable File (Object) Types and Object Properties Supported:
3000: Undefined Type
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM
[Desktop-packages] [Bug 1529999] Re: reporting per mtp-detect: droid razr hd not recognized
Fixed in Ubuntu 16.04 which has 1.1.10-2ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/152 Title: reporting per mtp-detect: droid razr hd not recognized Status in libmtp package in Ubuntu: Fix Released Bug description: On Ubuntu 12.04lts, mtp-detect reporst the following about a USB- connected Verizon DROID MAXX HD smartphone. Request that this be fixed. Device 0 (VID=22b8 and PID=2e62) is UNKNOWN. Please report this VID/PID and the device model to the libmtp development team PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device libmtp version: 1.1.3 Listing raw device(s) Found 1 device(s): 22b8:2e62 @ bus 2, dev 10 Attempting to connect device(s) Android device detected, assigning default bug flags USB low-level info: Interface has a kernel driver attached. bcdUSB: 512 bDeviceClass: 0 bDeviceSubClass: 0 bDeviceProtocol: 0 idVendor: 22b8 idProduct: 2e62 IN endpoint maxpacket: 512 bytes OUT endpoint maxpacket: 512 bytes Raw device info: Bus location: 2 Device number: 10 Device entry info: Vendor: (null) Vendor id: 0x22b8 Product: (null) Vendor id: 0x2e62 Device flags: 0x08008106 Configuration 0, interface 0, altsetting 0: Interface description contains the string "MTP" Device recognized as MTP, no further probing. Device info: Manufacturer: motorola Model: DROID RAZR HD Device version: 1.0 Serial number: Vendor extension ID: 0x0006 Vendor extension description: microsoft.com: 1.0; android.com: 1.0; mot-mobility.com/DSU: 1.2 Detected object size: 64 bits Extensions: microsoft.com: 1.0 android.com: 1.0 Supported operations: 1001: get device info 1002: Open session 1003: Close session 1004: Get storage IDs 1005: Get storage info 1006: Get number of objects 1007: Get object handles 1008: Get object info 1009: Get object 100a: Get thumbnail 100b: Delete object 100c: Send object info 100d: Send object 1014: Get device property description 1015: Get device property value 1016: Set device property value 1017: Reset device property value 101b: Get partial object 9801: Get object properties supported 9802: Get object property description 9803: Get object property value 9804: Set object property value 9805: Get object property list 9810: Get object references 9811: Set object references 95c1: Unknown (95c1) 95c2: Unknown (95c2) 95c3: Unknown (95c3) 95c4: Unknown (95c4) 95c5: Unknown (95c5) 9001: Unknown (9001) 9002: Unknown (9002) 9003: Unknown (9003) 9004: Unknown (9004) 9005: Unknown (9005) 9006: Unknown (9006) 9007: Unknown (9007) 9008: Unknown (9008) 9009: Unknown (9009) 900a: Unknown (900a) 900b: Unknown (900b) 900c: Unknown (900c) Events supported: 0x4002 0x4003 0x4004 0x4005 Device Properties Supported: 0xd401: Synchronization Partner 0xd402: Friendly Device Name 0x5003: Image Size Playable File (Object) Types and Object Properties Supported: 3000: Undefined Type dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY dc04: Object Size UINT64 data type READ ONLY dc07: Object File Name STRING data type GET/SET dc09: Date Modified STRING data type DATETIME FORM READ ONLY dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY dc44: Name STRING data type READ ONLY dc4e: Date Added STRING data type DATETIME FORM READ ONLY 3001: Association/Directory dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY dc04: Object Size UINT64 data type READ ONLY dc07: Object File Name STRING data type GET/SET dc09: Date Modified STRING data type DATETIME FORM READ ONLY dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY dc44: Name STRING data type READ ONLY dc4e: Date Added STRING data type DATETIME FORM READ ONLY 3004: Text dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY dc02:
[Desktop-packages] [Bug 1298534] [NEW] Mint 16 / 64-bit unable to mount via usb DROID Mini
You have been subscribed to a public bug:
Installed 'mtp-tools' following instructions for "MTP' device recognition as
listed on http://www.linuxmint.com/. Have created file
'etc/udev/rules.d/51-android.rules which contains:
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="2e67", MODE="0666"
ownership is root:root and permissions 775
DROID mini still doesn't mount and am returned with:
noname@nonameM-A:~ > mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
Device 0 (VID=22b8 and PID=2e67) is UNKNOWN.
**
Please report this VID/PID and the device model to the libmtp development team
**
Found 1 device(s):
22b8:2e67 @ bus 1, dev 11
Attempting to connect device(s)
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session,
trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object
handles.
Error 2: Error 02fe: PTP: Protocol error, data expected
USB low-level info:
bcdUSB: 512
bDeviceClass: 0
bDeviceSubClass: 0
bDeviceProtocol: 0
idVendor: 22b8
idProduct: 2e67
IN endpoint maxpacket: 512 bytes
OUT endpoint maxpacket: 512 bytes
Raw device info:
Bus location: 1
Device number: 11
Device entry info:
Vendor: (null)
Vendor id: 0x22b8
Product: (null)
Vendor id: 0x2e67
Device flags: 0x08008106
Configuration 0, interface 0, altsetting 0:
Interface description contains the string "MTP"
Device recognized as MTP, no further probing.
Device info:
Manufacturer: motorola
Model: XT1030
Device version: 1.0
Serial number: TA6260EEFY
Vendor extension ID: 0x0006
Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
mot-mobility.com/DSU: 1.2
Detected object size: 64 bits
Extensions:
microsoft.com: 1.0
android.com: 1.0
Supported operations:
1001: get device info
1002: Open session
1003: Close session
1004: Get storage IDs
1005: Get storage info
1006: Get number of objects
1007: Get object handles
1008: Get object info
1009: Get object
100a: Get thumbnail
100b: Delete object
100c: Send object info
100d: Send object
1014: Get device property description
1015: Get device property value
1016: Set device property value
1017: Reset device property value
101b: Get partial object
9801: Get object properties supported
9802: Get object property description
9803: Get object property value
9804: Set object property value
9805: Get object property list
9810: Get object references
9811: Set object references
95c1: Get Partial Object (64bit Offset)
95c2: Send Partial Object
95c3: Truncate Object
95c4: Begin Edit Object
95c5: End Edit Object
9001: Unknown (9001)
9002: Unknown (9002)
9003: Unknown (9003)
9004: Unknown (9004)
9005: Unknown (9005)
9006: Unknown (9006)
9007: Unknown (9007)
9008: Unknown (9008)
9009: Unknown (9009)
900a: Unknown (900a)
900b: Unknown (900b)
900c: Unknown (900c)
Events supported:
0x4002
0x4003
0x4004
0x4005
Device Properties Supported:
0xd401: Synchronization Partner
0xd402: Friendly Device Name
0x5003: Image Size
Playable File (Object) Types and Object Properties Supported:
3000: Undefined Type
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME FORM READ ONLY
3001: Association/Directory
dc01: Storage ID UINT32 data type ANY 32BIT VALUE form READ ONLY
dc02: Object Format UINT16 data type ANY 16BIT VALUE form READ ONLY
dc03: Protection Status UINT16 data type ANY 16BIT VALUE form READ ONLY
dc04: Object Size UINT64 data type READ ONLY
dc07: Object File Name STRING data type GET/SET
dc09: Date Modified STRING data type DATETIME FORM READ ONLY
dc0b: Parent Object UINT32 data type ANY 32BIT VALUE form READ ONLY
dc41: Persistant Unique Object Identifier UINT128 data type READ ONLY
dc44: Name STRING data type READ ONLY
dc4e: Date Added STRING data type DATETIME
Re: [Desktop-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile
On Thursday 11 July 2019 10:22:53 Markus Reuther wrote: > I am also affected by this issue: I would like to use my Jabra ENVOLVE > 65 headset with A2DP for the headphones in combination with the > microphone of the headset at the same time. Does your headset supports such feature? Ideally it is presented by vendor that this feature is supported? If yes, can you please describe how you are enabling this feature on headset? So we can look how to process it in pulseaudio. -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 508522] Re: Mic is not available with A2DP Bluetooth profile
I am also affected by this issue: I would like to use my Jabra ENVOLVE 65 headset with A2DP for the headphones in combination with the microphone of the headset at the same time. Hope that A2DP (for the headphones) and HSP/HFP (for the microphone) can be used simultaneously via Bluetooth and that someone finds out how and that someone fixes this. While this is not fixed I can not use my headset for voip calls under Ubuntu (18.04) (HSP/HFP quality is too poor for a multiple-hour call). -- 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/508522 Title: Mic is not available with A2DP Bluetooth profile Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1828393] Re: Unable to use bluetooth headset with mic and a2dp audio
*** This bug is a duplicate of bug 508522 *** https://bugs.launchpad.net/bugs/508522 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1828393 Title: Unable to use bluetooth headset with mic and a2dp audio Status in pulseaudio package in Ubuntu: Confirmed Bug description: Every device supports high fidelity audio while using headset with mic. This needs to enable two profiles at once: headset_head_unit and a2dp_sink. Right now this is impossible and I need to switch between profiles when listening to music and joining a call. In any case, the sound quality of HSP/HFP used in the headset_head_unit profile is horrible to have a call. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 9 13:20:26 2019 InstallationDate: Installed on 2018-11-20 (169 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET35W (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET35W(1.17):bd12/21/2018:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFCTO1WW dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1828393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1786344] Re: Default IBus input method ignored in live session
This bug was fixed in the package gnome-settings-daemon - 3.28.1-0ubuntu1.3 --- gnome-settings-daemon (3.28.1-0ubuntu1.3) bionic; urgency=medium * debian/patches/ubuntu_ibus_configs.patch: - Always call add_ibus_sources_from_locale() during the first run of g-s-d. This ensures that an IBus method is included in "live sessions" when applicable (LP: #1786344). * debian/patches/keyboard-Enable-ibus-for-OSK-purposes.patch: - Refreshed -- Gunnar Hjalmarsson Fri, 21 Jun 2019 11:58:00 +0200 ** Changed in: gnome-settings-daemon (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1786344 Title: Default IBus input method ignored in live session Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Released Bug description: [Impact] If you * start your computer with a bootable USB stick or DVD with the 18.04.2 desktop ISO * wait until Ubiquity's welcome screen shows up (only possible on systems with legacy BIOS; bug #1766047) * select a language which requires an input method for typing * click the "Try Ubuntu" button no IBus method is made easily available via the input source indicator in the session you enter. If you for instance select zh_CN as language and "Try Ubuntu", you would expect to enter a session with the "Intelligent Pinyin" method included among the available input sources. The proposed fix should ensure that an IBus method is always available in "live sessions" in languages which are prepared for it. [Test Case] 1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is not included among your available input sources. 2. Generate the Chinese locale: sudo locale-gen zh_CN.UTF-8 3. Add to ~/.profile this line: export LC_CTYPE=zh_CN.UTF-8 4. Remove the gnome-settings-daemon stamp file: rm ~/.local/share/gnome-settings-daemon/input-sources-converted 5. Log out and log in again. => Find that the "Intelligent Pinyin" method was not added (since the sources already in the list prevented it from being added). 6. Install gnome-settings-daemon from bionic-proposed. 7. Repeat step 4 and 5. => Find that the "Intelligent Pinyin" method was added. [Regression Potential] The proposed upload includes a small change which specifically addresses the issue as described above. I find that the risk for adverse side effects is low. [Original description] Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't input Chinese character. From Settings -> Regions and Languages, selected Intelligent Pinyin, also could not input Chinese. --- 18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and Languages，选择 智能拼音，也无法输入中文。 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1786344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833555] Update Released
The verification of the Stable Release Update for ubuntu-report has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1833555
Title:
Add OEM->Family
Status in ubuntu-report package in Ubuntu:
Fix Released
Status in ubuntu-report source package in Bionic:
Fix Released
Bug description:
[Impact]
Some OEM store the commercial name of the product into the Family field of
the system information record of smbios.
This update retrieves this information from
/sys/class/dmi/id/product_family and adds it to the OEM->Family field
[Test Case]
From a terminal run the command:
$ ubuntu-report show
Verify that it contains a field OEM/Family and it matches the content
of /sys/class/dmi/id/product_family
The output should look like:
"OEM": {
"Vendor": "Dell Inc.",
"Product": "Inspiron 7472",
"Family": "Inspiron"
},
It is possible that the field is empty.
[Regression Potential]
Very low. This field didn't exist before and it is covered by a full
regression test suite.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-report 1.5.1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 20 14:49:35 2019
Dependencies:
gcc-9-base 9.1.0-4ubuntu1
libc6 2.29-0ubuntu2
libgcc1 1:9.1.0-4ubuntu1
libidn2-0 2.0.5-1
libunistring2 0.9.10-1ubuntu2
InstallationDate: Installed on 2014-07-15 (1801 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
SourcePackage: ubuntu-report
UpgradeStatus: Upgraded to eoan on 2018-03-24 (452 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1833555/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1786344] Update Released
The verification of the Stable Release Update for gnome-settings-daemon has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1786344 Title: Default IBus input method ignored in live session Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Released Bug description: [Impact] If you * start your computer with a bootable USB stick or DVD with the 18.04.2 desktop ISO * wait until Ubiquity's welcome screen shows up (only possible on systems with legacy BIOS; bug #1766047) * select a language which requires an input method for typing * click the "Try Ubuntu" button no IBus method is made easily available via the input source indicator in the session you enter. If you for instance select zh_CN as language and "Try Ubuntu", you would expect to enter a session with the "Intelligent Pinyin" method included among the available input sources. The proposed fix should ensure that an IBus method is always available in "live sessions" in languages which are prepared for it. [Test Case] 1. Install ibus-libpinyin and make sure that "Intelligent Pinyin" is not included among your available input sources. 2. Generate the Chinese locale: sudo locale-gen zh_CN.UTF-8 3. Add to ~/.profile this line: export LC_CTYPE=zh_CN.UTF-8 4. Remove the gnome-settings-daemon stamp file: rm ~/.local/share/gnome-settings-daemon/input-sources-converted 5. Log out and log in again. => Find that the "Intelligent Pinyin" method was not added (since the sources already in the list prevented it from being added). 6. Install gnome-settings-daemon from bionic-proposed. 7. Repeat step 4 and 5. => Find that the "Intelligent Pinyin" method was added. [Regression Potential] The proposed upload includes a small change which specifically addresses the issue as described above. I find that the risk for adverse side effects is low. [Original description] Ubuntu 18.10 iso (2018.8.7), select Simplified Chinese for booting, can't input Chinese character. From Settings -> Regions and Languages, selected Intelligent Pinyin, also could not input Chinese. --- 18.10 镜像（2018.8.7）选择简体中文开机，无法输入中文。由 Settings -> Regions and Languages，选择 智能拼音，也无法输入中文。 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1786344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833555] Re: Add OEM->Family
This bug was fixed in the package ubuntu-report - 1.3.2
---
ubuntu-report (1.3.2) bionic; urgency=medium
* Add product_family to OEM information (LP: #1833555)
-- Jean-Baptiste Lallement Mon,
24 Jun 2019 11:10:02 +0200
** Changed in: ubuntu-report (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1833555
Title:
Add OEM->Family
Status in ubuntu-report package in Ubuntu:
Fix Released
Status in ubuntu-report source package in Bionic:
Fix Released
Bug description:
[Impact]
Some OEM store the commercial name of the product into the Family field of
the system information record of smbios.
This update retrieves this information from
/sys/class/dmi/id/product_family and adds it to the OEM->Family field
[Test Case]
From a terminal run the command:
$ ubuntu-report show
Verify that it contains a field OEM/Family and it matches the content
of /sys/class/dmi/id/product_family
The output should look like:
"OEM": {
"Vendor": "Dell Inc.",
"Product": "Inspiron 7472",
"Family": "Inspiron"
},
It is possible that the field is empty.
[Regression Potential]
Very low. This field didn't exist before and it is covered by a full
regression test suite.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-report 1.5.1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 20 14:49:35 2019
Dependencies:
gcc-9-base 9.1.0-4ubuntu1
libc6 2.29-0ubuntu2
libgcc1 1:9.1.0-4ubuntu1
libidn2-0 2.0.5-1
libunistring2 0.9.10-1ubuntu2
InstallationDate: Installed on 2014-07-15 (1801 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
SourcePackage: ubuntu-report
UpgradeStatus: Upgraded to eoan on 2018-03-24 (452 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1833555/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1773839] Re: zip compressed archives ignore/hide symlinks
** Tags added: desktop-sru-wishlist -- 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/1773839 Title: zip compressed archives ignore/hide symlinks Status in file-roller package in Ubuntu: Fix Released Bug description: When opening zip compressed archives that contain symlinks to files in the same folder/archive, the symlinks are 1. not shown in file-roller/Archive Manager 2. not extracted upon archive extraction This only happens with zip archives. *.tar.xz archives show the symlinks and will be extracted as expected. A possible workaround is to select "Extract here" from the archive's context menu (right-click in Nautilus/Files) which restores the symlinks as expected. However without prior knowledge of this behavior this can cause major problems when extracting archives such as binary development libraries whose build/linking process relies on the correct symlinks being present. Platform: Description: Ubuntu 18.04 LTS Release: 18.04 Package Version: file-roller: Installed: 3.28.0-1ubuntu1 Candidate: 3.28.0-1ubuntu1 Version table: *** 3.28.0-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I have attached a zip archive containing a folder with an empty file and a symlink towards that file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1773839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718727] Re: gnome-control-center crashed with SIGSEGV in nm_device_filter_connections()
** Tags added: desktop-sru-wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1718727 Title: gnome-control-center crashed with SIGSEGV in nm_device_filter_connections() Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Crash when open printer settings ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Sep 21 13:08:40 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2016-08-02 (414 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727) ProcCmdline: gnome-control-center printers SegvAnalysis: Segfault happened at: 0x7f1112c62233 : mov0x8(%r12),%eax PC (0x7f1112c62233) ok source "0x8(%r12)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: nm_device_filter_connections () at /usr/lib/x86_64-linux-gnu/libnm.so.0 net_device_get_valid_connections () () () g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in nm_device_filter_connections() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxsf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1718727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779050] Re: /usr/bin/gnome-control-center:6:g_assertion_message:g_assertion_message_expr:_gtk_builder_get_widget:screen_sharing_hide_cb:g_closure_invoke
** Tags added: desktop-sru-wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1779050 Title: /usr/bin/gnome-control- center:6:g_assertion_message:g_assertion_message_expr:_gtk_builder_get_widget:screen_sharing_hide_cb:g_closure_invoke Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.28.1-0ubuntu5, the problem page at https://errors.ubuntu.com/problem/6e8f205b4e6ab5e65fec15669d6f6b2f8f3a8be8 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/gnome-control-center/+bug/1779050/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836168] Re: Xorg freeze
1. Does the mouse pointer also freeze? 2. Does the bug occur if you log into Gnome Shell instead? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: nvidia -- 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/1836168 Title: Xorg freeze Status in Ubuntu: Incomplete Bug description: I use packages for my astronomy data analysis, after the recent update I am unable to open them. Every time I try the dialog box opens and just freezes. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 16:21:54 2019 DistUpgraded: 2019-07-03 23:09:43,158 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-51-generic, x86_64: installed nvidia, 390.116, 4.15.0-52-generic, x86_64: installed nvidia, 390.116, 4.15.0-54-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8368] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:8368] InstallationDate: Installed on 2017-12-02 (586 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 003: ID 0bda:58eb Realtek Semiconductor Corp. Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cc5xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=9c7988f6-034d-45d2-bc6f-72ad962f2b90 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2019-07-03 (7 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8368 dmi.board.vendor: HP dmi.board.version: 46.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd07/28/2017:svnHP:pnHPPavilionLaptop15-cc5xx:pvrType1ProductConfigId:rvnHP:rn8368:rvr46.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc5xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Thu Jul 11 13:53:22 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1836168/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835488] Re: hp-toolbox constantly shows printer as unavailable, but printer prints and hp-info / hp-doctor see the printer
I am currently using hplip 3.19.1 which is not exactly the latest and greatest, but should be fairly recent being the version provided by ubuntu 19.04. In fact, the latest hplip is 3.19.6. The printer I am encountering issues with hp-toolbox is an HP Color Laserjet PRO M281fdw, which should be in full support in hplip 3.19.1. As a matter of fact, support for this printer was introduced with hplip 3.18.5. Incidentally, I have tried hp-toolbox with a network connected HP laserjet pro M201dw and it works with that printer. My issue may sound like "CR 59273 – Supplies and status information are not displayed in the hp-toolbox" in the hplip release notes but this is fixed in 3.18.7 which is older than mine, so it cannot be. The hplip release notes do not report any other bug fixed in versions of hplip more recent than mine (it is mainly the enablement of new printers and scanners), so updating to the latest hplip does not seem sensible. In fact hplip from the hplip site is not packaged and if you install it, you then risk having issues updating your distro in the future. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1835488 Title: hp-toolbox constantly shows printer as unavailable, but printer prints and hp-info / hp-doctor see the printer Status in hplip package in Ubuntu: New Bug description: Seen with hp-toolbox on disco. HP-toolbox constantly indicates printer as "busy, powered down or unplugged" with an HP Color Laserjet Pro M281 connected to the network via wifi. Printer uri is like hp:/net/HP_ColorLaserJet_MFP_M278-M281?ip=xxx.yyy.zzz.www Notwithstanding the hp-toolbox failure, printer prints, scans and other hp- tools seem to work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: hplip 3.19.1+dfsg0-1 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 5 09:10:45 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (2030 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-20-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor SourcePackage: hplip UpgradeStatus: Upgraded to disco on 2019-06-12 (22 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1835488/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_
My issue is in Xenial, so, no luck in testing that. -- 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/1556439 Title: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile 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/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 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. [Original Report] Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1556439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778069] Re: [xfce] nautilus don't open files if set as default file manager
status: Fix Committed → Fix Released for 19.04. Good, but please also release for 18.04 as it is LTS. -- 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/1778069 Title: [xfce] nautilus don't open files if set as default file manager Status in Exo: Fix Released Status in exo package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Invalid Status in xubuntu-default-settings package in Ubuntu: Fix Released Status in nautilus package in Debian: New Bug description: If Nautilus is set as the preferred file manager with exo-preferred- applications, it no longer opens files. It opens only directories, .desktop files and executable files. Trying to open a file, be using Enter or with double mouse click, as a text file or a video makes Nautilus window blink for a instant and nothing happens. To be able to open the files, it's needed to choose to open with another application and then choose the application. Once Nautilus is unset as the default file manager (Thunar is chosen, for example), it starts to work fine again, opening files properly. Nautilus' Debian Sid version do not have this problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 Uname: Linux 4.17.2-041702-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jun 21 10:55:41 2018 InstallationDate: Installed on 2017-06-13 (372 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2017-10-20 (244 days ago) usr_lib_nautilus: dropbox 2015.10.28 To manage notifications about this bug go to: https://bugs.launchpad.net/exo/+bug/1778069/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818812] Re: glib: Fix named destinations
Would be probably fine for a SRU but the patch doesn't apply cleanly to
the current bionic version, could you try to backport/rebase it?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1818812
Title:
glib: Fix named destinations
Status in poppler package in Ubuntu:
Fix Released
Bug description:
IMPACT
---
Evince does not follow internal links in some PDF research articles (affects
Evince 3.28.4 + Poppler 0.62.0 on Ubuntu 18.04)
https://gitlab.gnome.org/GNOME/evince/issues/1070
PDF's link annotation does not work in Evince 3.30.2
https://gitlab.gnome.org/GNOME/evince/issues/1027
Evince does not follow internal links in some PDF research articles. The
internal links are used for easy and fast navigation to pages, figures,
references and equations.
qpdfview (poppler-qt5 viewer) can follow the internal links in those files
just fine.
DOI of one of the affected documents:
http://dx.doi.org/10.1016/j.apenergy.2016.10.058
Upstream fix:
https://gitlab.freedesktop.org/poppler/poppler/commit/44505cb397c46baa7dd4a0456f737f36e6d19ad0
TEST CASE
--
Clicking on the following parts should work after the fix is committed:
- Superscripts next to the authors names
- Citations in page 17 (e.g. [1], [9,11-18], [25-30])
- Figure and Table links in page 17 (Fig 1 and Table 1 at the beginning of
section 2)
- Equations in page 19 (they stay in the same page as the equations are very
close to their links)
REGRESSION POTENTIAL
-
This is quoted from the upstream commit:
"Named destinations may be described by bytestrings, containing
embedded NULs and not being NUL terminated. That means they cannot be
exposed directly as char*.
The alternatives are to escape the string from the internal representation
when exposing it in the API (e.g. in PopplerDest.named_dest), or to add
parallel API exposing it as GString, or GBytes. This patch chooses the first
option, since the presence of these named destionations in the public, not
sealed, PopplerDest struct means that the second option would need more API
additions. The chosen option is simpler, and does not need the API users to
adapt unless they create the named dest strings
themselves, or consume them in ways other than calling poppler APIs.
The escaping scheme chosen simply replaces embedded NUL with "\0" and
escapes a literal backslash with "\\". This is a minimal ABI change
in that some strings that previously worked unchanged as destinations
(those containing backslash) now don't work, but on the other hand,
previously it was impossible to use any destinations containing
embedded NULs.
Add poppler_named_dest_{from,to}_bytestring() to perform that
conversion, and clarify the documentation for when you need them."
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libpoppler-glib8 0.62.0-2ubuntu2.7
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Wed Mar 6 10:57:53 2019
InstallationDate: Installed on 2018-11-29 (96 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: poppler
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1818812/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1818812] Re: glib: Fix named destinations
The issue was fixed in 0.73 which is in Disco
** Changed in: poppler (Ubuntu)
Importance: Undecided => Low
** Changed in: poppler (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1818812
Title:
glib: Fix named destinations
Status in poppler package in Ubuntu:
Fix Released
Bug description:
IMPACT
---
Evince does not follow internal links in some PDF research articles (affects
Evince 3.28.4 + Poppler 0.62.0 on Ubuntu 18.04)
https://gitlab.gnome.org/GNOME/evince/issues/1070
PDF's link annotation does not work in Evince 3.30.2
https://gitlab.gnome.org/GNOME/evince/issues/1027
Evince does not follow internal links in some PDF research articles. The
internal links are used for easy and fast navigation to pages, figures,
references and equations.
qpdfview (poppler-qt5 viewer) can follow the internal links in those files
just fine.
DOI of one of the affected documents:
http://dx.doi.org/10.1016/j.apenergy.2016.10.058
Upstream fix:
https://gitlab.freedesktop.org/poppler/poppler/commit/44505cb397c46baa7dd4a0456f737f36e6d19ad0
TEST CASE
--
Clicking on the following parts should work after the fix is committed:
- Superscripts next to the authors names
- Citations in page 17 (e.g. [1], [9,11-18], [25-30])
- Figure and Table links in page 17 (Fig 1 and Table 1 at the beginning of
section 2)
- Equations in page 19 (they stay in the same page as the equations are very
close to their links)
REGRESSION POTENTIAL
-
This is quoted from the upstream commit:
"Named destinations may be described by bytestrings, containing
embedded NULs and not being NUL terminated. That means they cannot be
exposed directly as char*.
The alternatives are to escape the string from the internal representation
when exposing it in the API (e.g. in PopplerDest.named_dest), or to add
parallel API exposing it as GString, or GBytes. This patch chooses the first
option, since the presence of these named destionations in the public, not
sealed, PopplerDest struct means that the second option would need more API
additions. The chosen option is simpler, and does not need the API users to
adapt unless they create the named dest strings
themselves, or consume them in ways other than calling poppler APIs.
The escaping scheme chosen simply replaces embedded NUL with "\0" and
escapes a literal backslash with "\\". This is a minimal ABI change
in that some strings that previously worked unchanged as destinations
(those containing backslash) now don't work, but on the other hand,
previously it was impossible to use any destinations containing
embedded NULs.
Add poppler_named_dest_{from,to}_bytestring() to perform that
conversion, and clarify the documentation for when you need them."
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libpoppler-glib8 0.62.0-2ubuntu2.7
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Wed Mar 6 10:57:53 2019
InstallationDate: Installed on 2018-11-29 (96 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
SourcePackage: poppler
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1818812/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836168] [NEW] Xorg freeze
Public bug reported: I use packages for my astronomy data analysis, after the recent update I am unable to open them. Every time I try the dialog box opens and just freezes. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 11 16:21:54 2019 DistUpgraded: 2019-07-03 23:09:43,158 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-51-generic, x86_64: installed nvidia, 390.116, 4.15.0-52-generic, x86_64: installed nvidia, 390.116, 4.15.0-54-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8368] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:8368] InstallationDate: Installed on 2017-12-02 (586 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 003: ID 0bda:58eb Realtek Semiconductor Corp. Bus 001 Device 002: ID 3938:1031 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cc5xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=9c7988f6-034d-45d2-bc6f-72ad962f2b90 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to bionic on 2019-07-03 (7 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8368 dmi.board.vendor: HP dmi.board.version: 46.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd07/28/2017:svnHP:pnHPPavilionLaptop15-cc5xx:pvrType1ProductConfigId:rvnHP:rn8368:rvr46.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc5xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Thu Jul 11 13:53:22 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1836168 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I use packages for my astronomy data analysis, after the recent update I am unable to open them. Every time I try the dialog box opens and just freezes. 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 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .tmp.unity_support_test.1:
[Desktop-packages] [Bug 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_
I've been using 1:11.1-1ubuntu7.3 for a couple of weeks already and have had no problems. But I would rather someone actually affected by this crash responds to comment #36. -- 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/1556439 Title: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile 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/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 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. [Original Report] Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1556439/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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've been using 1:11.1-1ubuntu7.3 for a couple of weeks already and have had no problems. But I would rather someone actually affected by this crash responds to comment #26. -- 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 dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1663528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835956] Re: Deleting "Input Sources" not in use, affects the ones in use.
> but I'm not sure if I understand what you mean by "not only after adding > but continuing after a session restart using the indicator/keybindings and > not the settings?" Sorry, what I wrote was not really clear. The way things work is that gnome-control-center is used to add layouts to the session configuration. It's only used during that initial step where you go through the settings UI -> region to add things If you reboot your computer and log in the layouts should be listed in the top left indicator and you should be able to cycle through them. If the 'wrong keys' problem is still happening at this point the problem is probably not with how gnome-control-center apply the changes, it's either with how the system handle the layouts configured or gnome- control-center applying a wrong configuration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1835956 Title: Deleting "Input Sources" not in use, affects the ones in use. Status in gnome-control-center package in Ubuntu: New Bug description: I have a notebook, with an english keyboard layout, so "English (Us, intl, with dead keys) was my only option in "Region & Language / Input Sources". Now I want to use an external keyboard, which has a spanish distribution, so I tried adding "Spanish" (Let's call it "es1") to my "Input Sources" list. This is not quite my distribution, so I added a few more to try: "Spanish (with Sun Dead keys)" (es2), "Spanish (Latin American, with Sun dead keys)" (es3) and "Spanish (Win keys)" (es4). So after trying all this 4 options in spanish layouts, I decided that I want to use the (es4) option, because it fits my keyboard exactly, and I won't be needing any of the others spanish options. Just want to keep one for english and one for spanish. Now comes the strange behaviour: while "es4" is still my layout option in use, I go to "Input Sources" configuration and delete the input sources I won't be using (es1, es2 and es3). After deleting, I only have two options, one for english and one for spanish. The available keyboard layout for spanish is the same one I chose before, "Spanish (Win keys), but after deleting the other ones, this layout doesn't fit my keyboard any more. Some keys don't give me the same characters as they did when I was trying all the options and had the others layouts installed, but not in use. I've also noticed that installing a keyboard layout behaves different depending on whether there are other layouts installed or not. For example, if I install and use "Spanish" layout, when there is only "English" I don't get the same results if I install and use it when there are other "Spanish input sources" already installed. Cheers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.4 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 CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Jul 9 16:37:29 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-07-05 (369 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1835956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 991002] Re: Use the modern English name Bangla instead of Bengali for the language code bn
** Changed in: ibus Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/991002 Title: Use the modern English name Bangla instead of Bengali for the language code bn Status in CLDR: Fix Released Status in GLibC: Fix Released Status in gnome-desktop: New Status in ibus: Fix Released Status in xkeyboard-config: Fix Released Status in gnome-control-center package in Ubuntu: Fix Released Status in ibus package in Ubuntu: Fix Committed Status in iso-codes package in Ubuntu: Fix Released Status in langpack-locales package in Ubuntu: Fix Released Status in language-selector package in Ubuntu: Fix Released Status in localechooser package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in iso-codes package in Debian: Fix Released Status in xkeyboard-config package in Debian: Fix Released Bug description: The official name for the state language for Bangladesh is Bangla, as detailed on section 3, part 1 of the Bangladesh constitution (http://www1.umn.edu/humanrts/research/bangladesh-constitution.pdf). However, language selector continues to refer to this language as Bengali (Bangladeh). While Bengali has been historically used as the english name for the language during colonial periods, the name 'Bangla' is more widely used nowadays. It is also the name with which native speakers identify the language. This package uses Bengali(Bangladesh) as the identifier for language code bn-BD. Please change the name to Bangla(Bangladesh). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: language-selector-gnome 0.79 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Apr 29 16:14:25 2012 PackageArchitecture: all ProcEnviron: LANGUAGE=bn_BD:bn:en_IN:en_GB:en PATH=(custom, no user) LANG=bn_BD.UTF-8 SHELL=/bin/bash SourcePackage: language-selector UpgradeStatus: Upgraded to precise on 2012-03-19 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/cldr/+bug/991002/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ $ sudo cp linux-firmware/iwlwifi-8000C-36.ucode /lib/firmware/ $ sudo reboot -- 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 1835957] Re: cupsd gobbles up resources
OK, I did the downgrade again, without the -dev packages. There was no error message this time about "libscupsfilters". But there still is a sticky message on my screen's menu bar that goes like "An error occurred, please run Package Manager or apt-get in a terminal..." Then:"Error: BrokenCount>0". Yes, I have a Samsung Unified Driver installed – since several years. That is, it has been in use well before the current resources problem surfaced. Meanwhile, the downgraded seems to be running pretty quietly. It's not even in the Top60 of the listing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1835957 Title: cupsd gobbles up resources Status in cups package in Ubuntu: Incomplete Bug description: My computer has got very slow since 4 or 5 weeks. Finally, I checked resource usage with and the culprit seems to be cupsd. Here is an output line from a few minutes after boot: 30900 root 20 0 305452 287396 5768 S 5,3 9,3 0:41.34 cupsd Then after an hour and a half (with nothing printed): 30900 root 20 0 2565692 2,125g 2240 R 79,0 71,9 93:01.45 cupsd So %CPU grows 5,3 -> 79,0 and %MEM, 9,3 -> 71,9. Not good. A user on a local forum asked whether printing anything helped, and, certainly, it did. After I did (print something), cupsd was happy with less than 1% of CPU and MEM. So if I print something after every boot, the problem does go away. But that is not really a solution, is it? Running Lubuntu 16.04.6 LTS (32-bit). cups version is 2.1.3-4ubuntu0.9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1835957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1313863] Re: totem-video-thumbnailer crashed with SIGSEGV in g_slice_alloc()
*** This bug is a duplicate of bug 1289125 *** https://bugs.launchpad.net/bugs/1289125 ** This bug has been marked a duplicate of bug 1289125 totem-video-thumbnailer crashed with SIGSEGV in magazine_chain_pop_head() from g_slice_alloc() from g_slice_alloc0() from gst_video_decoder_new_frame() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1313863 Title: totem-video-thumbnailer crashed with SIGSEGV in g_slice_alloc() Status in totem package in Ubuntu: Incomplete Bug description: When I open a folder with some video files, the Totem thumbnailer crashes and only a part of the thumbnails are created. The strange thing is that the video files are all of the same type. For example I have a folder with 10 video files of this type: - container: Matroska (mkv) - video encoder: H.264 - audio encoder: AC-3 (ATSC A/52) and the totem thumbnailer creates only 4 thumbnails, and for the other files there is the default icon. Previously I had Ubuntu 12.04 installed, and the Totem thumbnailer worked very well with these same video files and all the others. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: totem 3.10.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Sun Apr 27 19:14:00 2014 ExecutablePath: /usr/bin/totem-video-thumbnailer InstallationDate: Installed on 2014-04-23 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 file:///media/username/Verbatim2/Fringe/Stagione1/Fringe.S01E01.720p.HDTV.x264-E7.mkv /tmp/.gnome_desktop_thumbnail.K7XYEX ProcEnviron: LANGUAGE=it_CH:it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_CH.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fc85ac1e297 :mov (%rbx),%rax PC (0x7fc85ac1e297) ok source "(%rbx)" (0x0001) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_alloc0 () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0 Title: totem-video-thumbnailer crashed with SIGSEGV in g_slice_alloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1313863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798313] Re: traceoute6 gives error sendto: Invalid argument
I've tested the 3:20161105-1ubuntu3 version in proposed and it fixes the bug for me. I've changed the tag accordingly. The Autopkgtest regression report doesn't seem to have anything to do with the package itself. But the testing framework seems to be failing. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1798313 Title: traceoute6 gives error sendto: Invalid argument Status in Iputils: Fix Released Status in iputils package in Ubuntu: Fix Released Status in iputils source package in Bionic: Fix Committed Status in iputils package in Debian: Fix Released Bug description: * Impact Using IPv6 the routing command returns Invalid argument errors * Test case When running the following command all get is an error. (traceroute6.db works) # traceroute6.iputils 2001:4860:4860:: traceroute to 2001:4860:4860:: (2001:4860:4860::) from 2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets sendto: Invalid argument * Regression potential Check that the command behave correclty on IPv4 and IP6 Ips -- This seems like a regression of Debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843264 Package version installed: iputils-tracepath 3:20161105-1ubuntu2 amd64 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/iputils/+bug/1798313/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
