[Desktop-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
Ahh yes, there everything is in /dev/snd, so really starting to feel like a pulseaudio bug. $ ls /dev/snd by-pathcontrolC1 hwC1D0pcmC0D0p pcmC1D3p pcmC1D8p timer controlC0 hwC0D0 pcmC0D0c pcmC0D1p pcmC1D7p seq I'll try the USB boot thing this aft and get back to you. -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801787] [NEW] /usr/bin/nautilus:double free or corruption (out)
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 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: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1801787 Title: /usr/bin/nautilus:double free or corruption (out) Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 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/nautilus/+bug/1801787/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774587] Re: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer
** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 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/. - Similar crash in Fedora: - https://bugzilla.redhat.com/attachment.cgi?id=1492907 + Similar crash in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1638389 + Trace at: https://bugzilla.redhat.com/attachment.cgi?id=1492907 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/43301aeee406cdbd57ba7d571ff838f0340d72a2 https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 https://errors.ubuntu.com/problem/7e550b34e134ed57f0684a8c554e3219191cd7f9 Similar but related to this thread (so likely the same issue): https://errors.ubuntu.com/problem/b0ad24ee4008e11e2adf5d14b6b0463e14aa8637 https://errors.ubuntu.com/problem/cec510782baf291622cd2bdd5a3761d27d587523 https://errors.ubuntu.com/problem/a829a6947498ae1bc279781b820f2409238af3a0 https://errors.ubuntu.com/problem/5ac15513eba57b72b1b09bafc448ffa1a7f3aa7f -- 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/1774587 Title: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer Status in nautilus package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 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/. Similar crash in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1638389 Trace at: https://bugzilla.redhat.com/attachment.cgi?id=1492907 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/43301aeee406cdbd57ba7d571ff838f0340d72a2 https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 https://errors.ubuntu.com/problem/7e550b34e134ed57f0684a8c554e3219191cd7f9 Similar but related to this thread (so likely the same issue): https://errors.ubuntu.com/problem/b0ad24ee4008e11e2adf5d14b6b0463e14aa8637 https://errors.ubuntu.com/problem/cec510782baf291622cd2bdd5a3761d27d587523 https://errors.ubuntu.com/problem/a829a6947498ae1bc279781b820f2409238af3a0 https://errors.ubuntu.com/problem/5ac15513eba57b72b1b09bafc448ffa1a7f3aa7f To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774587] Re: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer
** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 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/. Similar crash in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1638389 Trace at: https://bugzilla.redhat.com/attachment.cgi?id=1492907 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/43301aeee406cdbd57ba7d571ff838f0340d72a2 https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 https://errors.ubuntu.com/problem/7e550b34e134ed57f0684a8c554e3219191cd7f9 Similar but related to this thread (so likely the same issue): https://errors.ubuntu.com/problem/b0ad24ee4008e11e2adf5d14b6b0463e14aa8637 https://errors.ubuntu.com/problem/cec510782baf291622cd2bdd5a3761d27d587523 https://errors.ubuntu.com/problem/a829a6947498ae1bc279781b820f2409238af3a0 https://errors.ubuntu.com/problem/5ac15513eba57b72b1b09bafc448ffa1a7f3aa7f + https://errors.ubuntu.com/problem/c3b2e8a30a1ccdd23e1155f0c0067a89dea5eb6a -- 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/1774587 Title: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer Status in nautilus package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 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/. Similar crash in Fedora: https://bugzilla.redhat.com/show_bug.cgi?id=1638389 Trace at: https://bugzilla.redhat.com/attachment.cgi?id=1492907 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/43301aeee406cdbd57ba7d571ff838f0340d72a2 https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 https://errors.ubuntu.com/problem/7e550b34e134ed57f0684a8c554e3219191cd7f9 Similar but related to this thread (so likely the same issue): https://errors.ubuntu.com/problem/b0ad24ee4008e11e2adf5d14b6b0463e14aa8637 https://errors.ubuntu.com/problem/cec510782baf291622cd2bdd5a3761d27d587523 https://errors.ubuntu.com/problem/a829a6947498ae1bc279781b820f2409238af3a0 https://errors.ubuntu.com/problem/5ac15513eba57b72b1b09bafc448ffa1a7f3aa7f https://errors.ubuntu.com/problem/c3b2e8a30a1ccdd23e1155f0c0067a89dea5eb6a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801731] Re: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: new libgs9-common package pre-installation script subprocess returned error exit stat
Looks like that there is still some problem with the recent security update. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1801731 Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: new libgs9-common package pre-installation script subprocess returned error exit status 1 Status in ghostscript package in Ubuntu: New Bug description: A week ago I had a problem with viewing EPS-files. (Now again). I posted the following bug-description: https://tex.stackexchange.com/questions/457182/problems-after-installing-ubuntu-18-04-and-eps I tried to reinstall libgs9, without result. There are especially problems with viewing EPS-files again, however the original problem is solved. I tried epstopdf and get: epstopdf myfile.eps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- currentshared .currentglobal epstopdf ($Id: epstopdf.pl 45306 2017-09-14 21:41:37Z karl $) 2.27 !!! Error: Writing to gs failed, error code 255 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Mon Nov 5 14:41:59 2018 ErrorMessage: new libgs9-common package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-10-25 (740 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ghostscript Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: new libgs9-common package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-10-27 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1801731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797322] Re: gsd-rfkill-manager fails to receive rfkill event
This bug was fixed in the package gnome-settings-daemon - 3.28.1-0ubuntu1.1 --- gnome-settings-daemon (3.28.1-0ubuntu1.1) bionic; urgency=medium * debian/patches/git_binary_encoding.patch: - backport fix from upstream to resolve suspend/resume rfk issues (lp: #1797322) -- Sebastien Bacher Tue, 23 Oct 2018 17:11:07 +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/1797322 Title: gsd-rfkill-manager fails to receive rfkill event Status in OEM Priority Project: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Released Bug description: [Impact] The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. gsd-rfkill-manager will fail to receive rfkill event if rfkill-idx is larger than 127. Settings will always shows Bluetooth is off after resume. The solution is to set the encoding of GIOChannel as NULL (binary data). [Test Case] 1) Enable the -proposed repository, and install new "gnome-settings- daemon-schemas" and "gnome-settings-daemon" 2) Reboot system 3) Run suspend/resume test more than 127 times and then check if BT settings still works well. [Regression Potential] Low. The default encoding for GIOChannel is wrong. Just set correct encoding to receive rfkill event. --- The default encoding for GIOChannel is UTF-8, but rfkill event is binary data. If the value is invalid UTF-8, gsd-rfkill-manager will fail to receive rfkill event. Steps: Run suspend/resume Test (> 127 times) Failure Rate: 100% In some platforms, bt will be re-probed after s3. If bt is re-probed, rfkill-idx will increase. And, 128 is the first invalid UTF-8 $ rfkill list ID TYPE DEVICE SOFT HARD 1 wlan phy0 unblocked unblocked 128 bluetooth hci0 unblocked unblocked Error Message: gnome-settings-daemon/plugins/rfkill/rfkill-glib.c gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: g_io_channel_fill_buffer: cur_len=0, read_size=8 gsd-rfkill[2062]: g_io_channel_read_chars: 5 *bytes_read=8 gsd-rfkill[2062]: event_cb: 1 read=8 gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=0 gsd-rfkill[2062]: event_cb: 1 source->encoded_read_buf->len=0 gsd-rfkill[2062]: RFKILL event: idx 127 type 2 (BLUETOOTH) op 1 (DEL) soft 0 hard 0 gsd-rfkill[2062]: event_cb: 2 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 2 read=0 gsd-rfkill[2062]: event_cb: 2 source->read_buf->len=8 gsd-rfkill[2062]: event_cb: g_list_length=1 gsd-rfkill[2062]: Removed Bluetooth rfkill with ID 127 gsd-rfkill[2062]: event_cb: 1 g_io_channel_read_chars gsd-rfkill[2062]: event_cb: 1 read=0T gsd-rfkill[2062]: event_cb: 1 source->read_buf->len=16 gsd-rfkill[2062]: event_cb: g_list_length=0 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1797322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801780] [NEW] Unable to select Yaru sound theme in sound effects
Public bug reported: Release of Ubuntu: 18.10 Version of gnome-control-center: 1:3.30.1-1ubuntu2 Expected: Under the sound settings menu, The "default" setting in the sound effects tab should set the sound scheme to the now default "Yaru". "Yaru" should also be listed as an entry. What happened instead: Under the sound settings menu, The "default" setting in the sound effects tab sets /org/gnome/desktop/sound/theme-name to "freedesktop" instead of the default "Yaru". Furthermore, "Yaru" is not listed as an entry in this tab at all. Users now have to reset the sound effect by using the "Use default value" toggle in dconf-editor. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 20:45:14 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-10-29 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1801780 Title: Unable to select Yaru sound theme in sound effects Status in gnome-control-center package in Ubuntu: New Bug description: Release of Ubuntu: 18.10 Version of gnome-control-center: 1:3.30.1-1ubuntu2 Expected: Under the sound settings menu, The "default" setting in the sound effects tab should set the sound scheme to the now default "Yaru". "Yaru" should also be listed as an entry. What happened instead: Under the sound settings menu, The "default" setting in the sound effects tab sets /org/gnome/desktop/sound/theme-name to "freedesktop" instead of the default "Yaru". Furthermore, "Yaru" is not listed as an entry in this tab at all. Users now have to reset the sound effect by using the "Use default value" toggle in dconf-editor. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 20:45:14 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-10-29 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) 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/1801780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801780] Re: Unable to select Yaru sound theme in sound effects
** Description changed: Release of Ubuntu: 18.10 Version of gnome-control-center: 1:3.30.1-1ubuntu2 Expected: - Under the sound settings menu, The "default" setting in the sound effects tab should set the sound scheme to the now default "Yaru". "Yaru" should also be listed as an entry. + Under the sound settings menu, the "default" setting in the sound effects tab should set the sound scheme to the now default "Yaru". "Yaru" should also be listed as an entry. What happened instead: - Under the sound settings menu, The "default" setting in the sound effects tab sets /org/gnome/desktop/sound/theme-name to "freedesktop" instead of the default "Yaru". Furthermore, "Yaru" is not listed as an entry in this tab at all. Users now have to reset the sound effect by using the "Use default value" toggle in dconf-editor. + The "default" setting in the sound effects tab sets /org/gnome/desktop/sound/theme-name to "freedesktop" instead of the default "Yaru" if the scheme was already changed from the default value. I had to reset the sound effect by using the "Use default value" toggle in dconf-editor. Interestingly, if the sound scheme is already set to "Yaru", selecting the "default" option in the sound effects tab keeps the scheme set to "Yaru". + Furthermore, "Yaru" is not listed as an entry in this tab at all. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 20:45:14 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-10-29 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1801780 Title: Unable to select Yaru sound theme in sound effects Status in gnome-control-center package in Ubuntu: New Bug description: Release of Ubuntu: 18.10 Version of gnome-control-center: 1:3.30.1-1ubuntu2 Expected: Under the sound settings menu, the "default" setting in the sound effects tab should set the sound scheme to the now default "Yaru". "Yaru" should also be listed as an entry. What happened instead: The "default" setting in the sound effects tab sets /org/gnome/desktop/sound/theme-name to "freedesktop" instead of the default "Yaru" if the scheme was already changed from the default value. I had to reset the sound effect by using the "Use default value" toggle in dconf-editor. Interestingly, if the sound scheme is already set to "Yaru", selecting the "default" option in the sound effects tab keeps the scheme set to "Yaru". Furthermore, "Yaru" is not listed as an entry in this tab at all. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 20:45:14 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-10-29 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) 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/1801780/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774587] Re: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer
** Summary changed: - nautilus crashes in gtk_recent_manager_move_item -> g_bookmark_file_move_item -> free(): invalid pointer + nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer -- 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/1774587 Title: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer Status in nautilus package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 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/. https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801791] [NEW] /usr/bin/nautilus:11:_int_malloc:__GI___libc_malloc:g_malloc:g_strdup:g_mount_spec_set_with_len_internal
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/b0ad24ee4008e11e2adf5d14b6b0463e14aa8637 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: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1801791 Title: /usr/bin/nautilus:11:_int_malloc:__GI___libc_malloc:g_malloc:g_strdup:g_mount_spec_set_with_len_internal Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/b0ad24ee4008e11e2adf5d14b6b0463e14aa8637 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/nautilus/+bug/1801791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801795] Re: /usr/bin/nautilus:munmap_chunk(): invalid pointer
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 ** This bug has been marked a duplicate of bug 1774587 nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer -- 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/1801795 Title: /usr/bin/nautilus:munmap_chunk(): invalid pointer Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/5ac15513eba57b72b1b09bafc448ffa1a7f3aa7f 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/nautilus/+bug/1801795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801795] [NEW] /usr/bin/nautilus:munmap_chunk(): invalid pointer
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/5ac15513eba57b72b1b09bafc448ffa1a7f3aa7f 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: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1801795 Title: /usr/bin/nautilus:munmap_chunk(): invalid pointer Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/5ac15513eba57b72b1b09bafc448ffa1a7f3aa7f 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/nautilus/+bug/1801795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801791] Re: /usr/bin/nautilus:11:_int_malloc:__GI___libc_malloc:g_malloc:g_strdup:g_mount_spec_set_with_len_internal
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 ** This bug has been marked a duplicate of bug 1774587 nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer -- 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/1801791 Title: /usr/bin/nautilus:11:_int_malloc:__GI___libc_malloc:g_malloc:g_strdup:g_mount_spec_set_with_len_internal Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/b0ad24ee4008e11e2adf5d14b6b0463e14aa8637 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/nautilus/+bug/1801791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801792] Re: /usr/bin/nautilus:double free or corruption (fasttop)
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 ** This bug has been marked a duplicate of bug 1774587 nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer -- 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/1801792 Title: /usr/bin/nautilus:double free or corruption (fasttop) Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/cec510782baf291622cd2bdd5a3761d27d587523 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/nautilus/+bug/1801792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801792] [NEW] /usr/bin/nautilus:double free or corruption (fasttop)
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/cec510782baf291622cd2bdd5a3761d27d587523 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: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1801792 Title: /usr/bin/nautilus:double free or corruption (fasttop) Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/cec510782baf291622cd2bdd5a3761d27d587523 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/nautilus/+bug/1801792/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798399] Re: totem silently fails to create screenshot gallery
This bug was fixed in the package totem - 3.26.2-1ubuntu2 --- totem (3.26.2-1ubuntu2) cosmic; urgency=medium * d/p/gallery-don-t-use-command-line-options-that-got-removed-f.patch, d/p/screenshot-fix-invalid-free-created-by-the-previous-chang.patch: - backport fixes to make the gallery plugin work again (lp: #1798399) -- Sebastien Bacher Thu, 25 Oct 2018 17:26:01 +0200 ** Changed in: totem (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1798399 Title: totem silently fails to create screenshot gallery Status in totem package in Ubuntu: Fix Released Status in totem source package in Bionic: New Status in totem source package in Cosmic: Fix Released Bug description: *Impact The gallery plugin/menu option doesn't work * Test case - open a video - open the menu and click on the gallery option - validate making a gallery with the default options -> the picked filename should exist and be a gallery if pictures from the video * Regression potential The changes are restricted to the screenshot plugin, so make sure that one works -- https://gitlab.gnome.org/GNOME/totem/issues/268 --- https://gitlab.gnome.org/GNOME/totem/merge_requests/18/ --- Package totem 3.26.0-0ubuntu6 totem 3.26.0 running on Ubuntu 18.04 silently fails to create screenshot gallery. I'm assuming that this has something to do with totem-video-thumbnailer. Steps to reproduce: totem-video-thumbnailer -g 20 inputvideo outputpng I can reproduce this result with both HEVC and AVC encoded videos. I haven't been able to test other codecs, but the error indicates the codec isn't the problem. totem 3.18.1 under Ubuntu 16.04 does not have this problem. Any further information required I will be happy to produce within my abilities. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-19 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: totem 3.26.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic wayland-session Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1798399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796550] Update Released
The verification of the Stable Release Update for upower 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 upower in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: * Impact keyboard backlight control keys don't work in cosmic * Test case On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level * Regression potential The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working --- https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798399] Re: totem silently fails to create screenshot gallery
** Also affects: totem (Ubuntu Bionic) Importance: Undecided Status: New -- 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/1798399 Title: totem silently fails to create screenshot gallery Status in totem package in Ubuntu: Fix Released Status in totem source package in Bionic: New Status in totem source package in Cosmic: Fix Released Bug description: *Impact The gallery plugin/menu option doesn't work * Test case - open a video - open the menu and click on the gallery option - validate making a gallery with the default options -> the picked filename should exist and be a gallery if pictures from the video * Regression potential The changes are restricted to the screenshot plugin, so make sure that one works -- https://gitlab.gnome.org/GNOME/totem/issues/268 --- https://gitlab.gnome.org/GNOME/totem/merge_requests/18/ --- Package totem 3.26.0-0ubuntu6 totem 3.26.0 running on Ubuntu 18.04 silently fails to create screenshot gallery. I'm assuming that this has something to do with totem-video-thumbnailer. Steps to reproduce: totem-video-thumbnailer -g 20 inputvideo outputpng I can reproduce this result with both HEVC and AVC encoded videos. I haven't been able to test other codecs, but the error indicates the codec isn't the problem. totem 3.18.1 under Ubuntu 16.04 does not have this problem. Any further information required I will be happy to produce within my abilities. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-09-19 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: totem 3.26.0-0ubuntu6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic wayland-session Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1798399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
The uncommenting #WaylandEnable=false worked a treat for me as with the previous posters. This is the answer to this problem and needs pinning to the thread! -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801786] [NEW] /usr/bin/nautilus:11:__GI___libc_free:g_free:g_bookmark_file_move_item:gtk_recent_manager_move_item:nautilus_recent_update_file_moved
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 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: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1801786 Title: /usr/bin/nautilus:11:__GI___libc_free:g_free:g_bookmark_file_move_item:gtk_recent_manager_move_item:nautilus_recent_update_file_moved Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 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/nautilus/+bug/1801786/+subscriptions -- Mailing list: https://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 1800555] Re: Computer slow. Error reports appear.
My system is running much better. Thank you. From: Daniel van Vugt To: larma...@yahoo.com Sent: Thursday, November 1, 2018 9:41 PM Subject: [Bug 1800555] Re: Computer slow. Error reports appear. ** Tags added: radeon -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1800555 Title: Computer slow. Error reports appear. Status in xorg-server package in Ubuntu: New Bug description: Computer slow. Error reports appear. Says system is running on low graphics sometimes. Makes me log in most of the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Stopped WPA supplicant. [[0;32m OK [0m] Started Show Plymouth Boot Screen. Starting Hold until boot process finishes up... CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 29 17:37:27 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1] InstallationDate: Installed on 2016-09-11 (778 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard p6710f ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.07 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: 4CE0480TV4 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6710f dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 29 17:32:25 2018 xserver.configfile: default xserver.devices: input Power Button KEYBOARD, id 6 input Power Button KEYBOARD, id 7 input CHICONY HP USB Multimedia Keyboard KEYBOARD, id 8 input CHICONY HP USB Multimedia Keyboard KEYBOARD, id 9 input Logitech USB Optical Mouse MOUSE, id 10 xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800555/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1800555 Title: Computer slow. Error reports appear. Status in xorg-server package in Ubuntu: New Bug description: Computer slow. Error reports appear. Says system is running on low graphics sometimes. Makes me log in most of the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Stopped WPA supplicant. [[0;32m OK [0m] Started Show Plymouth Boot Screen. Starting Hold until boot
[Desktop-packages] [Bug 1801786] Re: /usr/bin/nautilus:11:__GI___libc_free:g_free:g_bookmark_file_move_item:gtk_recent_manager_move_item:nautilus_recent_update_file_moved
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 ** This bug has been marked a duplicate of bug 1774587 nautilus crashes in gtk_recent_manager_move_item -> g_bookmark_file_move_item -> free(): invalid pointer -- 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/1801786 Title: /usr/bin/nautilus:11:__GI___libc_free:g_free:g_bookmark_file_move_item:gtk_recent_manager_move_item:nautilus_recent_update_file_moved Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 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/nautilus/+bug/1801786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801784] Re: /usr/bin/nautilus:11:tcache_get:__GI___libc_malloc:g_markup_collect_attributes:is_file_valid_recursive:recent_thread_func
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 ** This bug has been marked a duplicate of bug 1774587 nautilus crashes in gtk_recent_manager_move_item -> g_bookmark_file_move_item -> free(): invalid pointer -- 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/1801784 Title: /usr/bin/nautilus:11:tcache_get:__GI___libc_malloc:g_markup_collect_attributes:is_file_valid_recursive:recent_thread_func Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0~ubuntu18.04.2, the problem page at https://errors.ubuntu.com/problem/7e550b34e134ed57f0684a8c554e3219191cd7f9 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/nautilus/+bug/1801784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801784] [NEW] /usr/bin/nautilus:11:tcache_get:__GI___libc_malloc:g_markup_collect_attributes:is_file_valid_recursive:recent_thread_func
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0~ubuntu18.04.2, the problem page at https://errors.ubuntu.com/problem/7e550b34e134ed57f0684a8c554e3219191cd7f9 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: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- 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/1801784 Title: /usr/bin/nautilus:11:tcache_get:__GI___libc_malloc:g_markup_collect_attributes:is_file_valid_recursive:recent_thread_func Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0~ubuntu18.04.2, the problem page at https://errors.ubuntu.com/problem/7e550b34e134ed57f0684a8c554e3219191cd7f9 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/nautilus/+bug/1801784/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801785] [NEW] /usr/bin/nautilus:11:_int_malloc:_int_realloc:__GI___libc_realloc:g_markup_collect_attributes:is_file_valid_recursive
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0~ubuntu18.04.2, the problem page at https://errors.ubuntu.com/problem/43301aeee406cdbd57ba7d571ff838f0340d72a2 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: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- 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/1801785 Title: /usr/bin/nautilus:11:_int_malloc:_int_realloc:__GI___libc_realloc:g_markup_collect_attributes:is_file_valid_recursive Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0~ubuntu18.04.2, the problem page at https://errors.ubuntu.com/problem/43301aeee406cdbd57ba7d571ff838f0340d72a2 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/nautilus/+bug/1801785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801796] [NEW] boltd running on a system with no thunderbolt devices
Public bug reported: I notice on my Cosmic system that boltd is running. This system has no thunderbolt devices, so having this daemon running is a waste of resources. Please fix this package to only start if devices are present, or if it must be started, to shut down on idle if no devices are discovered. ** Affects: bolt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1801796 Title: boltd running on a system with no thunderbolt devices Status in bolt package in Ubuntu: New Bug description: I notice on my Cosmic system that boltd is running. This system has no thunderbolt devices, so having this daemon running is a waste of resources. Please fix this package to only start if devices are present, or if it must be started, to shut down on idle if no devices are discovered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bolt/+bug/1801796/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801804] [NEW] /usr/bin/nautilus:11:nautilus_query_matches_string:recent_thread_func:g_thread_proxy:start_thread:clone
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/dc2906efffd8825626072ed9a92ce045cb9e67e7 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: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1801804 Title: /usr/bin/nautilus:11:nautilus_query_matches_string:recent_thread_func:g_thread_proxy:start_thread:clone Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/dc2906efffd8825626072ed9a92ce045cb9e67e7 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/nautilus/+bug/1801804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801787] Re: /usr/bin/nautilus:double free or corruption (out)
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 ** This bug has been marked a duplicate of bug 1774587 nautilus crashes in gtk_recent_manager_move_item -> g_bookmark_file_move_item -> free(): invalid pointer -- 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/1801787 Title: /usr/bin/nautilus:double free or corruption (out) Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 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/nautilus/+bug/1801787/+subscriptions -- Mailing list: https://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 1800555] Re: Computer slow. Error reports appear.
My system is running much better. Thank you. From: Marc Deslauriers To: larma...@yahoo.com Sent: Thursday, November 1, 2018 12:46 PM Subject: [Bug 1800555] Re: Computer slow. Error reports appear. Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1800555 Title: Computer slow. Error reports appear. Status in xorg package in Ubuntu: New Bug description: Computer slow. Error reports appear. Says system is running on low graphics sometimes. Makes me log in most of the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Stopped WPA supplicant. [[0;32m OK [0m] Started Show Plymouth Boot Screen. Starting Hold until boot process finishes up... CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 29 17:37:27 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1] InstallationDate: Installed on 2016-09-11 (778 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard p6710f ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.07 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: 4CE0480TV4 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6710f dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 29 17:32:25 2018 xserver.configfile: default xserver.devices: input Power Button KEYBOARD, id 6 input Power Button KEYBOARD, id 7 input CHICONY HP USB Multimedia Keyboard KEYBOARD, id 8 input CHICONY HP USB Multimedia Keyboard KEYBOARD, id 9 input Logitech USB Optical Mouse MOUSE, id 10 xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1800555/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1800555 Title: Computer slow. Error reports appear. Status in xorg-server package in Ubuntu: New Bug description: Computer slow. Error reports appear. Says system is running on low graphics sometimes. Makes me log in most of the
[Desktop-packages] [Bug 1774587] Re: nautilus crashes in gtk_recent_manager_move_item -> g_bookmark_file_move_item -> free(): invalid pointer
** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 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/. - - Similar crash in Fedora: - https://bugzilla.redhat.com/attachment.cgi?id=1492907 ** Changed in: nautilus (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 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/. + + https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 + https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 -- 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/1774587 Title: nautilus crashes in gtk_recent_manager_move_item -> g_bookmark_file_move_item -> free(): invalid pointer Status in nautilus package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 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/. https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1774587/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774587] Re: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer
** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 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/. + Similar crash in Fedora: + https://bugzilla.redhat.com/attachment.cgi?id=1492907 + https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 + https://errors.ubuntu.com/problem/43301aeee406cdbd57ba7d571ff838f0340d72a2 + https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 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/. Similar crash in Fedora: https://bugzilla.redhat.com/attachment.cgi?id=1492907 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/43301aeee406cdbd57ba7d571ff838f0340d72a2 https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 + https://errors.ubuntu.com/problem/7e550b34e134ed57f0684a8c554e3219191cd7f9 ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 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/. Similar crash in Fedora: https://bugzilla.redhat.com/attachment.cgi?id=1492907 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/43301aeee406cdbd57ba7d571ff838f0340d72a2 https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 https://errors.ubuntu.com/problem/7e550b34e134ed57f0684a8c554e3219191cd7f9 + + Similar but related to this thread (so likely the same issue): + https://errors.ubuntu.com/problem/b0ad24ee4008e11e2adf5d14b6b0463e14aa8637 ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 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/. Similar crash in Fedora: https://bugzilla.redhat.com/attachment.cgi?id=1492907 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/43301aeee406cdbd57ba7d571ff838f0340d72a2 https://errors.ubuntu.com/problem/166f7c223d662a4ca21a08a0361dceb453ab16a1 https://errors.ubuntu.com/problem/7e550b34e134ed57f0684a8c554e3219191cd7f9 Similar but related to this thread (so likely the same issue): https://errors.ubuntu.com/problem/b0ad24ee4008e11e2adf5d14b6b0463e14aa8637 + https://errors.ubuntu.com/problem/cec510782baf291622cd2bdd5a3761d27d587523 + https://errors.ubuntu.com/problem/a829a6947498ae1bc279781b820f2409238af3a0 + https://errors.ubuntu.com/problem/5ac15513eba57b72b1b09bafc448ffa1a7f3aa7f -- 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/1774587 Title: nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer Status in nautilus package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about
[Desktop-packages] [Bug 1774588] Re: /usr/bin/nautilus:malloc(): memory corruption (fast)
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 ** This bug has been marked a duplicate of bug 1774587 nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer -- 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/1774588 Title: /usr/bin/nautilus:malloc(): memory corruption (fast) Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.3-0ubuntu4, the problem page at https://errors.ubuntu.com/problem/a829a6947498ae1bc279781b820f2409238af3a0 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/nautilus/+bug/1774588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801803] Re: /usr/bin/nautilus:malloc_consolidate(): invalid chunk size
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 ** This bug has been marked a duplicate of bug 1774587 nautilus crashes in recent_thread_func -> is_file_valid_recursive -> g_local_file_query_info -> free(): invalid pointer -- 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/1801803 Title: /usr/bin/nautilus:malloc_consolidate(): invalid chunk size Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/c3b2e8a30a1ccdd23e1155f0c0067a89dea5eb6a 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/nautilus/+bug/1801803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801803] [NEW] /usr/bin/nautilus:malloc_consolidate(): invalid chunk size
*** This bug is a duplicate of bug 1774587 *** https://bugs.launchpad.net/bugs/1774587 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/c3b2e8a30a1ccdd23e1155f0c0067a89dea5eb6a 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: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1801803 Title: /usr/bin/nautilus:malloc_consolidate(): invalid chunk size Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/c3b2e8a30a1ccdd23e1155f0c0067a89dea5eb6a 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/nautilus/+bug/1801803/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1736164] Re: deja-dup/duplicity backup fails with UnicodeDecodeError
Same exact error in:
* Ubuntu 18.04 kernel 4.15.0-38-generic
* duplicity 0.7.17
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 1523, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 453, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 42:
ordinal not in range(128)
It could be great if the error message could include the file path that
induced the decodification error.
--
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/1736164
Title:
deja-dup/duplicity backup fails with UnicodeDecodeError
Status in Déjà Dup:
Triaged
Status in Duplicity:
New
Status in deja-dup package in Ubuntu:
Triaged
Status in deja-dup package in Fedora:
In Progress
Bug description:
See: https://bugzilla.redhat.com/show_bug.cgi?id=1470873
Description of problem:
With the update from Fedora 25 to Fedora 26 Workstation, backups with
deja-dup/duplicity are failing
Version-Release number of selected component (if applicable):
duplicity 0.7.13.1
deja-dup 34.3
How reproducible:
Always (scheduled and manually started backup)
Steps to Reproduce:
1. Wait for the scheduled backup to start or start it via the "Backup now"
button
2. Some or a large number of files might get backed up, then the backup stops
with "Failed with an unknown error"
3.
Actual results:
Backup fails
Expected results:
Backup completes as it always did
Additional info:
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1540, in
with_tempdir(main)
File "/usr/bin/duplicity", line 1534, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1385, in main
do_backup(action)
File "/usr/bin/duplicity", line 1516, in do_backup
incremental_backup(sig_chain)
File "/usr/bin/duplicity", line 668, in incremental_backup
globals.backend)
File "/usr/bin/duplicity", line 453, in write_multivol
(tdp, dest_filename, vol_num)))
File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line
146, in schedule_task
return self.__run_synchronously(fn, params)
File "/usr/lib64/python2.7/site-packages/duplicity/asyncscheduler.py", line
172, in __run_synchronously
ret = fn(*params)
File "/usr/bin/duplicity", line 452, in
vol_num: put(tdp, dest_filename, vol_num),
File "/usr/bin/duplicity", line 341, in put
backend.put(tdp, dest_filename)
File "/usr/lib64/python2.7/site-packages/duplicity/backend.py", line 376,
in inner_retry
% exception_traceback())
File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 51, in
exception_traceback
return uexc(msg)
File "/usr/lib64/python2.7/site-packages/duplicity/util.py", line 79, in
uexc
e = unicode(e).encode('utf-8')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 746:
ordinal not in range(128)
To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/1736164/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791936] Re: GNOME system-monitor cpu graph color does not update or persist
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-system-monitor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1791936 Title: GNOME system-monitor cpu graph color does not update or persist Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: 1. Description: Ubuntu 18.04.1 LTS Release: 18.04 2. gnome-system-monitor: Installed: (none) Candidate: 3.28.2-0ubuntu1 Version table: 3.28.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.1-1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3. I expect the colors to update in the graph and persist across application exit. 4. When I choose a different color for my cpu graphs the color does not update in the actual graph. Also when I close the app and open it again the colors seem to reset to default. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1791936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1791936] Re: GNOME system-monitor cpu graph color does not update or persist
Still affects current version 18.04.1 LTS. Colors do not persist on exit and do not affect graph. ** Attachment added: "Screenshot from 2018-11-05 18-07-39.png" https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1791936/+attachment/5209459/+files/Screenshot%20from%202018-11-05%2018-07-39.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1791936 Title: GNOME system-monitor cpu graph color does not update or persist Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: 1. Description: Ubuntu 18.04.1 LTS Release: 18.04 2. gnome-system-monitor: Installed: (none) Candidate: 3.28.2-0ubuntu1 Version table: 3.28.2-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 3.28.1-1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3. I expect the colors to update in the graph and persist across application exit. 4. When I choose a different color for my cpu graphs the color does not update in the actual graph. Also when I close the app and open it again the colors seem to reset to default. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1791936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801832] [NEW] Input method toggled when entering numbers with the numeric pad
You have been subscribed to a public bug: Ubuntu 18.04 LTS During the Chinese character input mode, when I enter numbers using the numeric pad, the input method will be switched to English automatically, which is very annoying. Any suggestions? ** Affects: ibus (Ubuntu) Importance: Undecided Status: New -- Input method toggled when entering numbers with the numeric pad https://bugs.launchpad.net/bugs/1801832 You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus 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 1801757] Re: all app indicators disappear
Can you please take a screenshot or photo of before and after? ** Also affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1801757 Title: all app indicators disappear Status in gnome-shell package in Ubuntu: Incomplete Status in gnome-shell-extension-appindicator package in Ubuntu: Incomplete Bug description: Occasionally all of my app indicators just disappear. Right now, for example the only icons in my top bar are the wifi icon, the volume icon, and the battery charge icon. Everything else is gone. The applications associated with the missing indicators, e.g., Dropbox, Cloud Station Drive, Pritunl, Shutter, are still running, but their app indicators are no longer there. The only way I've found to get them back is to log out and log back in. I have no idea what provokes this behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 11:37:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-27 (39 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1801757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black
The machine seems to have an Intel CPU/GPU from 2009, which makes me think this might be related somehow to bug 1727356. Can you please try booting Ubuntu 18.10 as a test? http://releases.ubuntu.com/18.10/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1801747 Title: External display not recognized, internal one goes to black Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2018-10-19 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU0012B8R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801832] [NEW] Input method toggled when using the numeric pad
Public bug reported: Ubuntu 18.04 LTS During the Chinese character input mode, when I enter numbers using the numeric pad, the input method will be switched to English automatically, which is very annoying. Any suggestions? ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Package changed: epiphany-browser (Ubuntu) => ibus (Ubuntu) ** Summary changed: - Input method toggled when entering numbers with the numeric pad + Input method toggled when using the numeric pad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1801832 Title: Input method toggled when using the numeric pad Status in ibus package in Ubuntu: New Bug description: Ubuntu 18.04 LTS During the Chinese character input mode, when I enter numbers using the numeric pad, the input method will be switched to English automatically, which is very annoying. Any suggestions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1801832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black
This may be a regression, please try older kernels like v4.4. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1801747 Title: External display not recognized, internal one goes to black Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2018-10-19 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU0012B8R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758035] Re: [regression] gnome-shell crashed with SIGTRAP in g_realloc_n() from g_log_structured()
That sounds plausible. Also there are zero reports of this crash after gnome-shell 3.28.0. So zero crashes in Ubuntu 18.10, and zero crashes since the final release of Ubuntu 18.04. The only systems still crashing seem to be pre-release bionic systems that haven't been updated for most of the year. I think this looks fixed already. Maybe fixed as early as the final release of 18.04. ** Changed in: glib2.0 (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: glib2.0 (Ubuntu Bionic) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: gnome-shell (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: gnome-shell (Ubuntu Bionic) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: glib2.0 (Ubuntu Bionic) Status: Confirmed => Incomplete ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gnome-shell (Ubuntu Bionic) Status: Confirmed => Incomplete ** Changed in: glib2.0 (Ubuntu) Status: Incomplete => Fix Released ** Changed in: glib2.0 (Ubuntu Bionic) Status: Incomplete => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released ** Changed in: gnome-shell (Ubuntu Bionic) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1758035 Title: [regression] gnome-shell crashed with SIGTRAP in g_realloc_n() from g_log_structured() Status in glib2.0 package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Released Bug description: https://errors.ubuntu.com/problem/bf61cf0ebedaacbd48f7c12574f551fea3f706c7 https://errors.ubuntu.com/problem/bc2bd5031309e8cf2314785805634f998452e937 https://errors.ubuntu.com/problem/f30049f514bf17053fe0461bf2b0890e46ad32dd --- Freshly installed bionic. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Mar 22 12:22:58 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-03-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180321) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_realloc_n () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: gnome-shell crashed with signal 5 in g_realloc_n() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1758035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1458329] Re: hplip has wrong order of udev rules ⇒ scanner ACLs not set
[Expired for hplip (Ubuntu) because there has been no activity for 60
days.]
** Changed in: hplip (Ubuntu)
Status: Incomplete => Expired
--
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/1458329
Title:
hplip has wrong order of udev rules ⇒ scanner ACLs not set
Status in hplip package in Ubuntu:
Expired
Bug description:
hplip installs 56-hpmud.rules in /lib/udev/rules.d/, which comes
*after* 40-libsane.rules. For HP scanners recognized by
56-hpmud.rules, but not by 40-libsane.rules, ENV{libsane_matched} is
set to ‘yes’, which is correct. But as 56-hpmud.rules is evaluated
*after* 40-libsane.rules, the rule from 40-libsane.rules which has
‘RUN+="/bin/setfacl -m g:scanner:rw $env{DEVNAME}"’ is not executed
anymore. This leads to the ACLs for the scanner group *not* being set
for the device.
In my case, the device is 03f0:4f11 (an HP OfficeJet 5610, known as
“Hewlett-Packard OfficeJet 5600”). hplip version is 3.14.3-0ubuntu3.2
on Ubuntu 14.04.2 LTS (trusty).
What I tried: copied /lib/udev/rules.d/56-hpmud.rules to
/etc/udev/rules.d/10-localoverride.rules – worked fine, ACLs set
properly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1458329/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1479555] Re: package hplip-data 3.14.3-0ubuntu3.3 failed to install/upgrade: Extrahierte Daten für »./usr/share/hplip/data/pcl/colorcal1_450.pcl.gz« können nicht nach »/usr/sha
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- 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/1479555 Title: package hplip-data 3.14.3-0ubuntu3.3 failed to install/upgrade: Extrahierte Daten für »./usr/share/hplip/data/pcl/colorcal1_450.pcl.gz« können nicht nach »/usr/share/hplip/data/pcl/colorcal1_450.pcl.gz.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms Status in hplip package in Ubuntu: Expired Bug description: always get an error message at startup. seems to be an version inconsistency ProblemType: Package DistroRelease: Ubuntu 14.04 Package: hplip-data 3.14.3-0ubuntu3.3 ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22 Uname: Linux 3.13.0-58-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 CupsErrorLog: E [18/Jul/2015:23:16:54 +0200] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [18/Jul/2015:23:33:16 +0200] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [30/Jul/2015:01:25:00 +0200] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. Date: Mon Jul 13 22:13:40 2015 DuplicateSignature: package:hplip-data:3.14.3-0ubuntu3.3:Extrahierte Daten für »./usr/share/hplip/data/pcl/colorcal1_450.pcl.gz« können nicht nach »/usr/share/hplip/data/pcl/colorcal1_450.pcl.gz.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms ErrorMessage: Extrahierte Daten für »./usr/share/hplip/data/pcl/colorcal1_450.pcl.gz« können nicht nach »/usr/share/hplip/data/pcl/colorcal1_450.pcl.gz.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms InstallationDate: Installed on 2012-07-31 (1093 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) Lpstat: device for HP_Color_LaserJet_2840: hp:/net/HP_Color_LaserJet_2840?ip=192.168.1.3 device for HP_Color_LaserJet_2840_fax: hpfax:/net/HP_Color_LaserJet_2840?ip=192.168.1.3 Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox PackageArchitecture: all Papersize: a4 PpdFiles: HP_Color_LaserJet_2840_fax: HP Fax hpcups HP_Color_LaserJet_2840: HP Color LaserJet 2800 Foomatic/Postscript ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-58-generic root=UUID=5b1f9d19-0cdf-4d86-9123-640fca404ee9 ro quiet splash vt.handoff=7 SourcePackage: hplip Title: package hplip-data 3.14.3-0ubuntu3.3 failed to install/upgrade: Extrahierte Daten für »./usr/share/hplip/data/pcl/colorcal1_450.pcl.gz« können nicht nach »/usr/share/hplip/data/pcl/colorcal1_450.pcl.gz.dpkg-new« kopiert werden: Unerwartetes Ende der Datei oder des Datenstroms UpgradeStatus: Upgraded to trusty on 2014-04-22 (463 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1479555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1436464] Re: P2035 is always in "Device communication error" state
[Expired for hplip (Ubuntu) because there has been no activity for 60 days.] ** Changed in: hplip (Ubuntu) Status: Incomplete => Expired -- 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/1436464 Title: P2035 is always in "Device communication error" state Status in hplip package in Ubuntu: Expired Bug description: The system is KUbuntu 14.04. HPLIP version is 3.15.2 compiled for KUbuntu 14.04 (sources and patches are taken from 15.04 - http://packages.ubuntu.com/vivid/hplip). I have a P2035 printer. It works fine, but hp-info always shows that the printer is in "Device communication error" state: $ hp-info -i ... Status History (most recent first): Date/Time Code Status DescriptionUser Job ID - 03/25/15 10:24:12 5012 Device communication error hpluna0 03/25/15 10:14:58 1009 The printer is out of paper root 3 03/25/15 10:14:58 5012 Device communication error hpluna0 03/25/15 10:13:39 500Started a print job root 3 03/25/15 10:13:39 501Print job has completed root 2 03/25/15 10:13:34 5012 Device communication error hpluna0 03/25/15 10:03:39 1009 The printer is out of paper root 2 03/25/15 10:03:38 5012 Device communication error hpluna0 03/25/15 10:02:20 500Started a print job root 2 03/25/15 10:02:20 5012 Device communication error hpluna0 03/25/15 09:54:03 501Print job has completed root 1 03/25/15 09:53:59 5012 Device communication error hpluna0 03/25/15 09:52:40 500Started a print job root 1 03/25/15 09:52:40 5012 Device communication error hpluna0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1436464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
@amri, Could you please report this bug to the GDM developers?; https://gitlab.gnome.org/GNOME/gdm/issues ** Changed in: nvidia-graphics-drivers-375 (Ubuntu) Status: Won't Fix => Invalid ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: Confirmed => Invalid -- 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/1705369 Title: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Invalid Status in nvidia-graphics-drivers-384 package in Ubuntu: Invalid Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS; or * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then run: sudo update-initramfs and reboot. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801813] Re: gvfsd-mtp crashed with SIGSEGV
*** This bug is a duplicate of bug 1706097 *** https://bugs.launchpad.net/bugs/1706097 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1706097, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1801813/+attachment/5209476/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1801813/+attachment/5209478/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1801813/+attachment/5209482/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1801813/+attachment/5209483/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1801813/+attachment/5209484/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1801813/+attachment/5209485/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1801813/+attachment/5209486/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1706097 gvfsd-mtp crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1801813 Title: gvfsd-mtp crashed with SIGSEGV Status in gvfs package in Ubuntu: New Bug description: I haven't even activated MTP on the phone I attached. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gvfs-backends 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 17:31:57 2018 ExecutablePath: /usr/lib/gvfs/gvfsd-mtp InstallationDate: Installed on 2017-10-13 (388 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171012) ProcCmdline: /usr/lib/gvfs/gvfsd-mtp --spawner :1.22 /org/gtk/gvfs/exec_spaw/30 SegvAnalysis: Segfault happened at: 0x7f653438358a:mov0x18(%r12),%rax PC (0x7f653438358a) ok source "0x18(%r12)" (0x0018) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: () at /usr/lib/x86_64-linux-gnu/gvfs/libgvfsdaemon.so () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gvfsd-mtp crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-06-25 (133 days ago) UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1801813/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747175] Re: [Inspiron 5559, Realtek ALC3234, Black Headphone Out, Front] No sound at all
My problem is with Intel on board sound. alsamixer shows as: [PCH]: HDA-Intel - HDA Intel PCH │ │ HDA Intel PCH at 0xdc24 irq 127 │ Unable to raise the indicated level on either of the Speaker channels. The alsamixer display for those stays at 00. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1747175 Title: [Inspiron 5559, Realtek ALC3234, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: My internal speaker works fine People say it is a problem of ALSADRIVER Headphone jack works in windows Issue lies with ubuntu ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-112.135-lowlatency 4.4.98 Uname: Linux 4.4.0-112-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harish 2674 F pulseaudio CurrentDesktop: XFCE Date: Sat Feb 3 23:42:53 2018 InstallationDate: Installed on 2016-07-06 (577 days ago) InstallationMedia: Ubuntu-Studio 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: harish 2674 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Inspiron 5559, Realtek ALC3234, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 04D1V1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd08/25/2016:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn04D1V1:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5559 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1747175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
Yes, I suspected as much. System76 wouldn't ship a laptop without working audio on Ubuntu. It sounds like that machine has gone through a couple of upgrades: DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) I can't tell what has been broken in the process, but it does look like pulseaudio since 'pacmd' isn't working for you. I suggest: (a) Try to reinstall pulseaudio packages, like: sudo apt install --reinstall pulseaudio or (b) Back up your data and then reinstall fresh from http://releases.ubuntu.com/18.10/ We may never know what went wrong on the machine before 18.10 reaches end of life in July 2019. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Triaged ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Medium -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Triaged Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801731] Re: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: new libgs9-common package pre-installation script subprocess returned error exit stat
It looks like you manually copied files into the /usr/share/ghostscript/9.25/iccprofiles directory to try and fix an upgrade issue. Please do the following to fix the issue: sudo rmdir /usr/share/ghostscript/9.25/iccprofiles sudo apt-get install --reinstall libgs9-common ** Changed in: ghostscript (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ghostscript in Ubuntu. https://bugs.launchpad.net/bugs/1801731 Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: new libgs9-common package pre-installation script subprocess returned error exit status 1 Status in ghostscript package in Ubuntu: Incomplete Bug description: A week ago I had a problem with viewing EPS-files. (Now again). I posted the following bug-description: https://tex.stackexchange.com/questions/457182/problems-after-installing-ubuntu-18-04-and-eps I tried to reinstall libgs9, without result. There are especially problems with viewing EPS-files again, however the original problem is solved. I tried epstopdf and get: epstopdf myfile.eps Unrecoverable error: typecheck in .bind Operand stack: --nostringval-- typecheck --nostringval-- currentshared .currentglobal epstopdf ($Id: epstopdf.pl 45306 2017-09-14 21:41:37Z karl $) 2.27 !!! Error: Writing to gs failed, error code 255 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Mon Nov 5 14:41:59 2018 ErrorMessage: new libgs9-common package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-10-25 (740 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ghostscript Title: package libgs9-common 9.25~dfsg+1-0ubuntu0.18.04.1 failed to install/upgrade: new libgs9-common package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-10-27 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1801731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801602] Re: Gnome 3 fullscreen doesn't work for some applications
Please: 1. Log into a Xorg session 2. Open a Terminal window 3. Reproduce the bug 4. Alt+Tab to the terminal and run: xwininfo -all > window_info.txt 5. When the crosshair mouse pointer appears use it to click on the affected game window. 6. Send us the resulting file 'window_info.txt' ** Tags added: bionic ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1801602 Title: Gnome 3 fullscreen doesn't work for some applications Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Using Gnome 3 or Ubuntu session (default in 18.04) when you try to run some game in fullscreen mode instead it opens at top left small window. This happens for example for Way to Go! Steam game and perhaps any SDL 1 game. It's easy to reproduce, install a game using SDL 1 library for example abe (apt install abe) and try to run it. There are two kinds of effect, the abe and perhaps other games from Ubuntu repository fails to run properly fullscreen only on first use after login. On second and further run they launch properly on fullscreen. The Steam game (Way to Go !) fails to run fullscreen each time. Sometimes you see only part of the game screen at top left window and you even can't operate it, sometimes whole screen is shown. When you manage to reach game settings switching fullscreen on and off few times makes the fullscreen run properly. The problem doesn't exist for example using Unity or Windowmaker sessions. It exists using any Gnome 3 Xorg sessions, even the classic one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1801602/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
** Changed in: mutter (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Status in mutter source package in Cosmic: Fix Released Bug description: [ Impact ] In some early intel GPUs gdm can't start in wayland mode, and so gnome-shell [ Test case ] - Start the pc or logout/end session - Try to login with the "Ubuntu on Wayland" session - Ubuntu should start [ Regression potential ] Possible false positive on wayland support check on some cards --- https://gitlab.gnome.org/GNOME/mutter/issues/127 --- Wayland sessions (including the login screen itself) don't start up on older Intel GPUs. --- Workaround: Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false --- $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOMEDisplayManager: gdm3DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-05-04 (539 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: gnome-shell 3.26.1-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful package-from-proposed third-party-packages Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790030] Re: [16329:16329:0831/041258.345888:ERROR:account_tracker.cc(253)] OnGetTokenFailure: Invalid credentials (1).
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1790030 Title: [16329:16329:0831/041258.345888:ERROR:account_tracker.cc(253)] OnGetTokenFailure: Invalid credentials (1). Status in chromium-browser package in Ubuntu: Expired Bug description: Using PPAPI flash. --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version= jjp@jjp-N55SF:~$ [16329:16329:0831/041258.345888:ERROR:account_tracker.cc(253)] OnGetTokenFailure: Invalid credentials (1). Starting [16329:16353:0831/041308.710876:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.710959:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.711023:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.711086:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.711173:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.711274:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.711366:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.711466:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.711557:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.711649:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.711747:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.711837:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.711924:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.712018:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.712131:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.712223:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.712336:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.712650:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.712704:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.712836:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.712899:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.712982:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041308.713085:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041309.706696:ERROR:service_manager_context.cc(250)] Attempting to run unsupported native service: /usr/lib/chromium-browser/chrome_renderer.service [16329:16353:0831/041309.706771:ERROR:service_manager_context.cc(250)] Attempting to run
[Desktop-packages] [Bug 1789911] Re: Uninstalled software [still] appears as "installed" [after uninstallation]
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1789911 Title: Uninstalled software [still] appears as "installed" [after uninstallation] Status in gnome-software package in Ubuntu: Expired Bug description: gnome-software center for Ubuntu 18.04 LTS is not removing Gnome Extensions and programs from the "installed" list after I remove/uninstall them. In addition, newly installed Gnome Extensions are not appearing as "installed." ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 30 10:07:14 2018 InstallationDate: Installed on 2018-08-17 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InstalledPlugins: gnome-software-plugin-flatpak 3.28.1-0ubuntu4.18.04.2 gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.2 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1789911/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1794544] Re: [SRU] 2.56.3
Version 2.56.3 installed here from proposed, works properly. marco@tricky:/tmp:✓ $ apt-cache policy libglib2.0-0 libglib2.0-0: Installato: 2.56.3-0ubuntu0.18.04.1 Candidato: 2.56.3-0ubuntu0.18.04.1 Tabella versione: *** 2.56.3-0ubuntu0.18.04.1 100 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 2.56.2-0ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.56.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1794544 Title: [SRU] 2.56.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Committed Bug description: [ Description ] The third stable release in the 2.56 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. * New upstream release (LP: #xxx) + The documentation for G_GNUC_MALLOC has changed to be more restrictive to avoid miscompilations; you should check whether any uses of it in your code are appropriate + Fix cancellation of g_subprocess_communicate_async() calls + Bug fixes: + /network-monitor/create-in-thread fails in (LXC) containers on glib-2-56 + GBookmarkFile: nullptr access in current_element + GBookmarkFile: heap-buffer-overflow in g_utf8_get_char + Backport g_subprocess_communicate() cancellation fixes from !266 to glib-2-56 (LP: #1789476) + Many uses of G_GNUC_MALLOC are incorrect + Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw + Fix persistent CI failure on glib-2-56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1794544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716056] Re: Multiple context menus appearing
How can you say that it was resolved? I still have this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1716056 Title: Multiple context menus appearing Status in gnome-shell-extension-appindicator package in Ubuntu: In Progress Status in gnome-shell-extension-appindicator source package in Artful: In Progress Bug description: I have dropbox installed on my up to date 17.10 system. Clicking the dropbox icon triggers multiple menus, over the top of eachother (see screenshot). One is a gnome style menu, the other is a white native dropbox menu. I'd imagine I should really only see one menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-appindicator 17.10 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 23:09:09 2017 Dependencies: InstallationDate: Installed on 2017-08-02 (37 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1716056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
@Sebastien: Yes, enable/disable airplane mode works from gnome-control-center. It also works to disalbe it from the Gnome panel manu. (Remember that it previously also could be enabled and disabled with the dedicated Fn+Pos1 key as long as xkb-data was 2.23). As for the verification-failed: I obviously accept the maintainers' decision. If you think that the xkb-data update is the right path forward despite this regression, by all means please go ahead. It would be good to fix the regression though. It seems that a very similar machine is sold as a Developer Edition with Ubuntu (Dell Precision 5530, https://bartongeorge.io/2018/05/24/welcome-the-new-dell-precision- developer-editions/) The failed disable of the airplane mode (i.e., failed re-enable of Wifi/BT) leaves this in journalctl: Nov 06 00:00:49 chronic systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 06 00:00:49 chronic NetworkManager[777]: [1541458849.3593] manager: rfkill: WiFi now enabled by radio killswitch Nov 06 00:00:49 chronic systemd[1]: Started Load/Save RF Kill Switch Status. Nov 06 00:00:50 chronic kernel: ath10k_pci :02:00.0: Unknown eventid: 118809 Nov 06 00:00:50 chronic kernel: ath10k_pci :02:00.0: Unknown eventid: 90118 Nov 06 00:00:50 chronic kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2459] device (wlp2s0): device not up after timeout! Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2462] manager: rfkill: WiFi now disabled by radio killswitch Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2514] manager: rfkill: WWAN hardware radio set enabled Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2516] audit: op="radio-control" arg="wwan-enabled" pid=2286 uid=1000 result="success" Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2584] manager: rfkill: WWAN hardware radio set disabled Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2586] audit: op="radio-control" arg="wwan-enabled" pid=2286 uid=1000 result="success" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xkeyboard-config source package in Cosmic: Fix Committed Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801205] Re: Can't mount veracrypt volumes
I'm just trying the GUI way not the CLI way (which I'm not familiar with.) ** Attachment added: "Print Screen of Gnome Disks and it's behavior after "mounting" a Veracrypt file." https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1801205/+attachment/5209475/+files/Captura%20de%20pantalla%20de%202018-11-05%2018-26-03.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1801205 Title: Can't mount veracrypt volumes Status in gnome-disk-utility package in Ubuntu: New Bug description: Using mount from nautilus (open with) or right from Gnome Disk, the file in question is "mounted" as a loop device. Therefore, no opening of that container nor questions about how to open the file. This is Ubuntu 18.10 from 18.04. Already tried 18.10 on a VM (Live session) and Gnome on Xorg & Wayland. Also tryed Tail in order to see the Veracrypt property working. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-disk-utility 3.30.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Nov 1 18:35:17 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-08 (146 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-disk-utility UpgradeStatus: Upgraded to cosmic on 2018-10-30 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1801205/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1621732] Re: gedit doesn't show last newline
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gedit (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1621732 Title: gedit doesn't show last newline Status in gedit package in Ubuntu: Confirmed Bug description: echo 'foo' | tee -a testfile od -t x1 testfile 000 66 6f 6f 0a 004 gedit testfile It shows foo as if it doesn't end in a linefeed. In other words I'd expect the last place I could set the cursor as below the line with foo but instead the last place is right after the last o. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gedit 3.18.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 9 00:39:20 2016 InstallationDate: Installed on 2013-10-23 (1051 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1621732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789476] Re: glib apps using GSubprocess communicate might crash on g_subprocess_communicate_cancelled
Test case works as expected. marco@tricky:/tmp:✓ $ apt-cache policy libglib2.0-0 libglib2.0-0: Installato: 2.56.3-0ubuntu0.18.04.1 Candidato: 2.56.3-0ubuntu0.18.04.1 Tabella versione: *** 2.56.3-0ubuntu0.18.04.1 100 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 2.56.2-0ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.56.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages marco@tricky:/tmp:✓ $ gjs /tmp/subprocess-cancelled.js (gjs:8606): Gjs-WARNING **: 22:08:37.297: JS ERROR: Gio.IOErrorEnum: L'operazione è stata annullata @/tmp/subprocess-cancelled.js:10:5 @/tmp/subprocess-cancelled.js:16:5 ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1789476 Title: glib apps using GSubprocess communicate might crash on g_subprocess_communicate_cancelled Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Fix Committed Bug description: [ Impact ] Glib apps using subprocess communicate and cancellable is cancelled crashes [ Test case ] Run the attached example with gjs subprocess-cancelled.js Should not crash, or running: valgrind gjs subprocess-cancelled.js should not return any read error (as the one mentioned below) [ Regression potential ] Really low, the only thing that could happen is that the subprocess isn't really cancelled. --- Fixed upstream in https://gitlab.gnome.org/GNOME/glib/merge_requests/266 #0 g_cancellable_cancel (cancellable=0x6) at ../../glib/gio/gcancellable.c:486 #1 0x77ab8d1d in g_subprocess_communicate_cancelled (user_data=) at ../../glib/gio/gsubprocess.c:1535 -- ==25871== Memcheck, a memory error detector ==25871== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==25871== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==25871== Command: gjs /tmp/subprocess-cancelled.js ==25871== ==25871== Warning: set address range perms: large range [0x377ee1e21000, 0x377f21e21000) (noaccess) ==25871== Invalid read of size 8 ==25871==at 0x4EC5604: g_subprocess_communicate_cancelled (gsubprocess.c:1535) ==25871==by 0x547A0F4: g_main_dispatch (gmain.c:3177) ==25871==by 0x547A0F4: g_main_context_dispatch (gmain.c:3830) ==25871==by 0x547A4BF: g_main_context_iterate.isra.26 (gmain.c:3903) ==25871==by 0x547A54B: g_main_context_iteration (gmain.c:3964) ==25871==by 0x6C4EDAD: ffi_call_unix64 (in /usr/lib/x86_64-linux-gnu/libffi.so.6.0.4) ==25871==by 0x6C4E71E: ffi_call (in /usr/lib/x86_64-linux-gnu/libffi.so.6.0.4) ==25871==by 0x5775607: ??? (in /usr/lib/libgjs.so.0.0.0) ==25871==by 0x5776F53: ??? (in /usr/lib/libgjs.so.0.0.0) ==25871==by 0x8A3FF6B: CallJSNative (jscntxtinlines.h:239) ==25871==by 0x8A3FF6B: js::InternalCallOrConstruct(JSContext*, JS::CallArgs const&, js::MaybeConstruct) (Interpreter.cpp:447) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1789476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
I've already tried reinstalling pulseaudio, and it doesn't do anything. I can't really afford to reinstall my work laptop right now, I really need it to just, you know, work. ;) but I also need working sound so I'm not really sure what to do. is there really no way to debug pulseaudio and why it's broken? if not, are there supported alternate audio servers for ubuntu which will work with everything? -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Triaged Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Status: New => In Progress ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Medium ** Changed in: glib2.0 (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Description changed: - Unknown circumstances + Happens when there's a "rename" to a file to its same value, no known + reproducer though. + + Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 - ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AssertionMessage: munmap_chunk(): invalid pointer CurrentDesktop: ubuntu:GNOME Date: Mon Apr 2 09:04:45 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-03-31 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) - LANG=en_GB.UTF-8 - Signal: 6SourcePackage: nautilus + LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid pointer") at malloc.c:5350 munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846 __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117 g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus assert failure: munmap_chunk(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: -- 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/1760569 Title: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved Status in glib2.0 package in Ubuntu: In Progress Status in nautilus package in Ubuntu: Triaged Bug description: Happens when there's a "rename" to a file to its same value, no known reproducer though. Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456 https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9 ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 AssertionMessage: munmap_chunk(): invalid pointer CurrentDesktop: ubuntu:GNOME Date: Mon Apr 2 09:04:45 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2018-03-31 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid pointer") at malloc.c:5350 munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846 __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117 g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus assert failure: munmap_chunk(): invalid pointer UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black
Also, do you think this might be bug 1723025? ** Also affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete -- 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/1801747 Title: External display not recognized, internal one goes to black Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2018-10-19 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU0012B8R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1727356] Re: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc)
** Tags added: testcase -- 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/1727356 Title: Login screen never appears on early generation Intel GPUs (Core2 and Atom etc) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: In Progress Status in mutter source package in Cosmic: Fix Released Bug description: [ Impact ] In some early intel GPUs gdm can't start in wayland mode, and so gnome-shell [ Test case ] - Start the pc or logout/end session - Try to login with the "Ubuntu on Wayland" session - Ubuntu should start [ Regression potential ] Possible false positive on wayland support check on some cards --- https://gitlab.gnome.org/GNOME/mutter/issues/127 --- Wayland sessions (including the login screen itself) don't start up on older Intel GPUs. --- Workaround: Ctrl+Alt+F4, log in, edit /etc/gdm3/custom.conf and uncomment the line: #WaylandEnable=false --- $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOMEDisplayManager: gdm3DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-05-04 (539 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: gnome-shell 3.26.1-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful package-from-proposed third-party-packages Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801757] Re: all app indicators disappear
Thanks. It sounds like the problem is confined to the 'gnome-shell-extension- appindicator' package. ** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1801757 Title: all app indicators disappear Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: Occasionally all of my app indicators just disappear. Right now, for example the only icons in my top bar are the wifi icon, the volume icon, and the battery charge icon. Everything else is gone. The applications associated with the missing indicators, e.g., Dropbox, Cloud Station Drive, Pritunl, Shutter, are still running, but their app indicators are no longer there. The only way I've found to get them back is to log out and log back in. I have no idea what provokes this behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 11:37:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-27 (39 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1801757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799001] Re: Theming does not work on LXQt
This bug was fixed in the package libreoffice - 1:6.1.2-0ubuntu4 --- libreoffice (1:6.1.2-0ubuntu4) disco; urgency=medium * Make LibreOffice under the LXQt desktop environment use the Breeze theme as the default (LP: #1799001). -- Simon Quigley Sat, 03 Nov 2018 16:08:28 -0500 ** Changed in: libreoffice (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1799001 Title: Theming does not work on LXQt Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Cosmic: In Progress Bug description: [Impact] Without this change, LibreOffice does not correctly use the Breeze theme, which is needed for consistency with the rest of the Lubuntu, LXQt-based desktop. At times, it is even hard to use because of the inconsistent theming which can hide buttons at times. [Test Case] Update to the version of LibreOffice with this patch and open it on a Lubuntu 18.10 installation. It should use the Breeze theming rather than the stock GTK theming on startup. [Regression Potential] Little to none. If for some reason the criteria that is used to check for the LXQt desktop no longer works, which is unlikely in a stable release, this will no longer work. [Other Info] I submitted these upstream (as my first patches \o/): https://gerrit.libreoffice.org/61641 https://gerrit.libreoffice.org/61751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1799001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
Booting off USB, sound works fine, soundcards show up correctly. So... it's something that got messed up in the upgrade from 18.04, I guess? -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790100] Re: unable to write ~ and ^ chars in the terminal
I still have the problem in gnome terminal, it didn't go away... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1790100 Title: unable to write ~ and ^ chars in the terminal Status in vte2.91 package in Ubuntu: Fix Released Bug description: Hello, I am using Ubuntu 18.10 and since the last update, I am unable to write ~ and ^ chars in the terminal, in both gnome-terminal and Geany (both using libvte2.91). I don't have this issue with other applications (terminator, xterm, Firefox, Gedit, etc.). But note that now, when I type ^ for the first time in Gedit for example, I see this char but underlined. If I type it a second type (or press space), it is transformed in ^ without line under it. This is a new behaviour that can cause this bug in libvte. Please tell me if I need to join other info! Thanks! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libvte-2.91-0 0.52.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 31 11:17:43 2018 InstallationDate: Installed on 2015-08-10 (1116 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: vte2.91 UpgradeStatus: Upgraded to cosmic on 2016-04-29 (854 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1790100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801470] Re: Double password to login after screen locked
Also affects 'gnome-shell' since that is the package which provides the login/lock screen GUI. ** Tags added: radeon ** Summary changed: - Double password to login after screen locked + [radeon] Double password to login after screen locked ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New -- 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/1801470 Title: [radeon] Double password to login after screen locked Status in gdm3 package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: After every the screen is blocked, I have to write twice the password. The first time the top bar is available but the user as seen on the blocked screen still on. Then, I have to "cancel" the process which drop down the "curtain" and then I have to enter the password yet again. That happens since the update from 18.04 to 18.10. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.1-1ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 2 22:44:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-06-08 (148 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to cosmic on 2018-10-30 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799994] Re: gdm3: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1
I'm not sure we should be looking in gdm here. Tim has mentioned several times that kernel 4.15.0-36-generic works and kernel 4.15.0-38 fails. I wonder though, if the Nvidia driver might have just failed to build for the newer kernels. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gdm3: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 + Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 ** Summary changed: - Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 + Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 using kernel 4.15.0-38, but 4.15.0-36-generic works -- 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/174 Title: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 using kernel 4.15.0-38, but 4.15.0-36-generic works Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime- select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 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:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available
[Desktop-packages] [Bug 1801786] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved
*** This bug is a duplicate of bug 1760569 *** https://bugs.launchpad.net/bugs/1760569 ** Tags added: rls-bb-incoming -- 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/1801786 Title: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved Status in nautilus package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.26.4-0ubuntu7, the problem page at https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45 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/nautilus/+bug/1801786/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1739931] Re: Separator lines in shell popup menus are too faint to see
** Changed in: gnome-shell (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: gnome-shell (Ubuntu Bionic) Status: Fix Committed => In Progress ** Changed in: gnome-shell (Ubuntu Bionic) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1739931 Title: Separator lines in shell popup menus are too faint to see Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Status in gnome-shell source package in Bionic: In Progress Status in gnome-shell-extension-ubuntu-dock source package in Bionic: Won't Fix Status in ubuntu-themes source package in Bionic: Won't Fix Bug description: [ Impact ] Separators in gnome-shell menuitems are not visible [ Test case ] 1. Right - Click on a dock icon 2. Separators between menu items should be visible [ Regression potential ] Nothing known when I click on the dock icons, some of the lines in the popup menus are blank and some of them appear to be incorrect. see top left of attached screenshot. ProblemType: BugDistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 23 22:24:40 2017 InstallationDate: Installed on 2016-08-18 (492 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1743058] Re: Input field height changes slightly when entering in st password fields.
** Changed in: gnome-shell (Ubuntu Bionic) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: gnome-shell (Ubuntu Bionic) Importance: Undecided => Low -- 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/1743058 Title: Input field height changes slightly when entering in st password fields. Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Bug description: It appears there is the font/height rendering issue in multiple places. With the textentry "jumping" in height slightly upon entering anything. I have observed this on the login screen password entry screen, lockscreen entry, and the gnome pin entry for my ssh/gpg smartcard. It almost feels as if the "dots" of the hidden password are either of larger font size and/or bold, whilst an empty text field and/or unfocused text field font is either smaller and or regular (non-bold). Resulting in a rendering / layout jiggles. [ Impact ] Password input field increase the vertical size as soon as the user types something [ Test case ] 1. Run: pkexec true 2. Start typing something 3. The input field should not resize vertically This works only in case the big-font a11y option is not enabled [ Regression potential ] Input Text entries might be slightly taller than they were To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743058/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801757] Re: all app indicators disappear
Before, it looks like the attached (though there is also a Shutter indicator, which disappears while I'm taking the screen capture). Afterwards everything to the left of the wifi indicator (i.e., the Yubioath Desktop indicator and everything to the left of it) is gone. ** Attachment added: "Selection_007.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1801757/+attachment/5209492/+files/Selection_007.png ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Incomplete => 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/1801757 Title: all app indicators disappear Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-appindicator package in Ubuntu: New Bug description: Occasionally all of my app indicators just disappear. Right now, for example the only icons in my top bar are the wifi icon, the volume icon, and the battery charge icon. Everything else is gone. The applications associated with the missing indicators, e.g., Dropbox, Cloud Station Drive, Pritunl, Shutter, are still running, but their app indicators are no longer there. The only way I've found to get them back is to log out and log back in. I have no idea what provokes this behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 11:37:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-27 (39 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1801757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892
Probably the FreeBSD is working as Windows, they use the software de- noise filter when users record sound. Please test with "pactl load-module module-echo-cancel", then choose echo-cancelled record device from gnome-sound-setting->input tab. Now record sth, and play it. Is it better now? If there is sth in the kernel driver to introduce the noise, the thing I can figure out so far is change the micbias reference voltag: Right now the reference for two mics: Rear Mic: Pin-ctls: 0x21: IN VREF_50 Front Mic: Pin-ctls: 0x24: IN VREF_80 You can try to set them with different value like "HIZ 50 GRD 80 100", maybe some value can improve the sound quality. The patch_realtek.c has some sample code to set verf. -- 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 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New 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/ubuntu/+source/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 1798943] Re: keyboard backlighting not working on function keys
Please try updating your system, in case bug 1796550 fixed it. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Incomplete ** Tags added: cosmic -- 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/1798943 Title: keyboard backlighting not working on function keys Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: The keyboard backlighting is not working on function keys. Pressing one of the function key responsible with the backlighting I'm getting this error in Logs: gsd-power: gsd_power_backlight_abs_to_percentage: assertion 'max > min' failed The keyboard brightness option from the settings doesn't appear anymore. Also, the keyboard backlighting was working in Ubuntu 18.04 but it doesn't since I upgrade to Ubuntu 18.10. It can be turned off manually with the command: echo 0 | sudo tee /sys/class/leds/smc\:\:kbd_backlight/brightness ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-settings-daemon 3.30.1.2-1ubuntu2 Uname: Linux 4.18.15-041815-generic Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: 20th of October SourcePackage: gnome-settings-daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798943/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
The PulseAudio developers should be able to help you with more advanced debugging. You can log a bug to get help from them at: https://gitlab.freedesktop.org/groups/pulseaudio/-/issues -- 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/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Triaged Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797862] Re: Cannot turn off keyboard backlight
Maybe merge with bug 1791372? ** No longer affects: upower (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1797862 Title: Cannot turn off keyboard backlight Status in linux package in Ubuntu: Confirmed Bug description: /sys/class/leds $ ls asus-wireless::airplane input10::capslock input10::compose input10::kana input10::numlock input10::scrolllock input4::capslock input4::numlock input4::scrolllock phy0-led There isn't any asus kbd backlight folder. `xset led off` doesn't work for me. And I can only use fn to control volume (f1/f2/f3). The leds kills my battery $ sudo dmidecode -t 1; lsb_release -a # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 3.0.0 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: ASUSTeK COMPUTER INC. Product Name: FX503VD Version: 1.0 Serial Number: H9NRCX00M803374 UUID: 524E3948-5843-3030-4D38-30373441 Wake-up Type: Power Switch SKU Number: Family: FX No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 Codename: cosmic ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/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.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-0ubuntu11 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 15 17:13:35 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-10-generic, x86_64: installed nvidia, 390.87, 4.18.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1b90] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:1b90] InstallationDate: Installed on 2018-10-10 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. FX503VD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: FX dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797862/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292398] Re: Second screen position isn't saved from one session to another
I think that's possibly a different bug. Suspend/hibernate and resume is the same session. This bug was about different sessions. -- 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/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Incomplete Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801522] Re: Ubuntu 18.10 boots into black screen
Please: 1. Run 'apport-collect 1801522' to send us more information about the machine. 2. Reproduce the problem, reboot and then in recovery mode run this command: journalctl -b-1 > prev_boot.txt and send us the file 'prev_boot.txt'. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Tags added: black-screen cosmic nvidia -- 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/1801522 Title: Ubuntu 18.10 boots into black screen Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I just upgraded from Ubuntu 18.04 to Ubuntu 18.10 on a Windows 10 dual boot machine. The machine has a Nvidia GeForce GTX 1080 GPU. I have tried to diagnose and fix the problem using prior posted solutions, such as video card issues with nomodeset(https://askubuntu.com/questions/162075/my-computer-boots- to-a-black-screen-what-options-do-i-have-to-fix-it and https://askubuntu.com/questions/1087559/cant-boot-ubuntu-properly- after-dual-boot-installation-with-windows-10) but this did not work, and the boot script no longer contains "quiet splash" anyways. Also in the boot script I set acpi = off but then I get another error, perhaps for another thread (PKCS#7 signature not signed with a trusted key), and the boot instead crashes on this error. In recovery mode (4.18.0-10-generic) I tried running fsck but could not unmount the partition. I am using 97% of my bootloader partition so I ran recovery mode's clean but that also did not fix the issue. I am not sure what else I should try - I anxiously await and appreciate any further guidance you may have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1801522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)
The machine is stuck in recovery mode, according to the kernel command line: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04 -ec8b-462c-ba66-4f45c229353c ro recovery nomodeset To fix this, you need to reboot and then press Esc as soon as the purple screen appears. Now select the proper kernel that is not recovery mode. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1801716 Title: Xorg freeze (black screen after ubuntu logo during boot) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I experienced this bug ever since I have upgraded my laptop from 16.04. But it got resolved in my last update after I reported the bug. However, I forgot to go back to Launchpad to mark it as resolved and now the problem comes again after I just updated the system. So, as the title stated, I can't get in the system due to the infinite black screen I am facing. I am only able to report this bug under the recovery mode. Besides, there's something wrong with the lock screen too. I can't get back to the system if I just put the system into "sleep mode". Black screen again! What's worst, the brightness of my display can't be adjusted as well! I feel like being blind at night! Please help!!! Thank you! And I think there might be the compatibility problem between my laptop and the new desktop -- Gnome, which is the default in 18.04. What should do? I really love using Ubuntu, as I really learned a lot in these days I used it as my study os for CS. Any help is appreciated, thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.17.0-041700rc3-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 19:49:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 08) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:15fd] InstallationDate: Installed on 2018-04-04 (215 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK COMPUTER INC. T300FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset Renderer: Software SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T300FA.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T300FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT300FA.214:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnT300FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T300FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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: Tue Nov 6 03:47:33 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black
** Tags added: multimonitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1801747 Title: External display not recognized, internal one goes to black Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Hi, I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu 18.04.1 I face a problem on ALL of them, as soon as I connect an external screen, doesn't matter VGA or HDMI, the internal screen goes black, only mouse icon is their, blinking from time to time but reacting. External screen does show nothing but there is no "no signal" info what means that source is recognized. As soon as I release the video cable from external display, the internal one come back to live after few seconds. The BIOS was updated to latest available. Daniel tootai@hirondelle:~$ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Mon Nov 5 16:30:38 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:3072] InstallationDate: Installed on 2018-10-19 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP ProBook 4510s ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.18 dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0F dmi.chassis.asset.tag: CNU0012B8R dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4510s dmi.product.version: F.18 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)
Thanks for all you guys reply!! And since there are two different suggestion, so I will reply respectively. To Cristian, Yes, the issue I am facing happens after I upgraded from Ubuntu 16.04 to 18.04. But no, or correctly, I don't know. As I followed what you suggested and do the test with the installation of latest kernel, V4.19, I can't even get to the phase where I can see the Ubuntu logo! Only a screen filled with error messages, which I took the photo and attach it as follow. So, let me rephrase what happened again. I headed to the kernel mainline page under V4.19. And download these three, as I followed the steps in the https://wiki.ubuntu.com/Kernel/MainlineBuilds: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-headers-4.19.1-041901_4.19.1-041901.201811041431_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-headers-4.19.1-041901-generic_4.19.1-041901.201811041431_i386.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-image-4.19.1-041901-generic_4.19.1-041901.201811041431_i386.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-modules-4.19.1-041901-generic_4.19.1-041901.201811041431_i386.deb and after 'wget' done in the terminal (the files have been downloaded in the folder I chose) I use the command: "sudo dpkg -i *.deb" Then reboot. Then what's on the screen was what you see in the attachment. I think it might be my laptop does not support this kernel? Since my laptop is so weird, meaning the screen of my laptop is touch-screen and detachable. So, sorry for your inconvenience of making the Ubuntu be compatible with my rare device, sorry. As for Daniel, So thank you for your advice, however, the issue I am facing is not when I tried to get in recovery mode or I was stuck at the recovery mode. No. I am only in the recovery mode is because this is the only way I can report this bug because I can not get in when it's in the regular mode and for some reason, I am able to access the Ubuntu when I am in the recovery mode. And this is how I get in: When I stuck at the black screen which show up after the Ubuntu logo. I did turn off the laptop forcefully buy long press the "turn on laptop" button, then turn on again. But this time I switch from "Ubuntu" to "Advance something something option" and get to the menu where I can chose to boot under the recovery mode. When I selected recovery mode, press enter, after all those scripts loading finish, and press "enter" or enter "Y" for one or two times, I reach to another menu where I can see, "Resume something" (or some words else but it's the first option in the menu), then I chose it, press enter, here I am! So... was I clear in my above description? And thank you all so much for the help and suggestion! All your active reply is why I love Ubuntu so much, even my device is such a pain, which I am sorry! ** Attachment added: "The error in the boot screen when I tried to boot in kernel V4.19" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801716/+attachment/5209502/+files/error-message-on-the-screen-when-boot-v419.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1801716 Title: Xorg freeze (black screen after ubuntu logo during boot) Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I experienced this bug ever since I have upgraded my laptop from 16.04. But it got resolved in my last update after I reported the bug. However, I forgot to go back to Launchpad to mark it as resolved and now the problem comes again after I just updated the system. So, as the title stated, I can't get in the system due to the infinite black screen I am facing. I am only able to report this bug under the recovery mode. Besides, there's something wrong with the lock screen too. I can't get back to the system if I just put the system into "sleep mode". Black screen again! What's worst, the brightness of my display can't be adjusted as well! I feel like being blind at night! Please help!!! Thank you! And I think there might be the compatibility problem between my laptop and the new desktop -- Gnome, which is the default in 18.04. What should do? I really love using Ubuntu, as I really learned a lot in these days I used it as my study os for CS. Any help is appreciated, thanks in advance! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 4.17.0-041700rc3-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 5 19:49:36 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu
[Desktop-packages] [Bug 1800465] Re: Vulkan error when using NVIDIA-Prime
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1800465 Title: Vulkan error when using NVIDIA-Prime Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-prime package in Ubuntu: Confirmed Bug description: After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils, switching to NVIDIA and then running vulkaninfo or vulkan-cube works perfectly. But when you reboot and update, then switch to Intel, then back to Nvidia, all Vulkan programs give an "Assertion `!err' failed." Vulkaninfo: === Presentable Surfaces: = GPU id : 0 (GeForce GTX 960M) Surface type : VK_KHR_xcb_surface vulkaninfo: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253: AppDumpSurfaceFormats: Assertion `!err' failed. Annullato (core dump creato) Vulkancube: vulkan-cube: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: demo_init_vk_swapchain: Assertion `!err' failed. Annullato (core dump creato) I still have not found a workaround for that, the only way to get it working again is to reinstall everything. - Install Ubuntu 18.10 - Install proprietary 390 NVIDIA drivers - Switch NVIDIA-Prime to NVIDIA - Testing the vulkan capabilities works - Updating the system then switching to intel - Reboot - Switch to nvida - Now all Vulkan programs when using NVIDIA give that error To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800465] Re: Vulkan error when using NVIDIA-Prime
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-prime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1800465 Title: Vulkan error when using NVIDIA-Prime Status in NVIDIA Drivers Ubuntu: New Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-prime package in Ubuntu: Confirmed Bug description: After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils, switching to NVIDIA and then running vulkaninfo or vulkan-cube works perfectly. But when you reboot and update, then switch to Intel, then back to Nvidia, all Vulkan programs give an "Assertion `!err' failed." Vulkaninfo: === Presentable Surfaces: = GPU id : 0 (GeForce GTX 960M) Surface type : VK_KHR_xcb_surface vulkaninfo: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253: AppDumpSurfaceFormats: Assertion `!err' failed. Annullato (core dump creato) Vulkancube: vulkan-cube: /build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: demo_init_vk_swapchain: Assertion `!err' failed. Annullato (core dump creato) I still have not found a workaround for that, the only way to get it working again is to reinstall everything. - Install Ubuntu 18.10 - Install proprietary 390 NVIDIA drivers - Switch NVIDIA-Prime to NVIDIA - Testing the vulkan capabilities works - Updating the system then switching to intel - Reboot - Switch to nvida - Now all Vulkan programs when using NVIDIA give that error To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]
Now tracking in both: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae ** Description changed: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca + https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO 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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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: Mon Oct 16 18:18:18 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.3-1ubuntu1.2 ** Summary changed: - Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] + Xwayland/Xorg crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] ** Summary changed: -
[Desktop-packages] [Bug 1801870] Re: /usr/lib/xorg/Xorg:6:st_renderbuffer_delete:_mesa_reference_renderbuffer_:_mesa_reference_renderbuffer:_mesa_free_framebuffer_data:_mesa_destroy_framebuffer
*** This bug is a duplicate of bug 1754693 *** https://bugs.launchpad.net/bugs/1754693 ** This bug has been marked a duplicate of bug 1754693 Xwayland/Xorg crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1801870 Title: /usr/lib/xorg/Xorg:6:st_renderbuffer_delete:_mesa_reference_renderbuffer_:_mesa_reference_renderbuffer:_mesa_free_framebuffer_data:_mesa_destroy_framebuffer Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.1-3ubuntu2, the problem page at https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae 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/xorg-server/+bug/1801870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1801870] [NEW] /usr/lib/xorg/Xorg:6:st_renderbuffer_delete:_mesa_reference_renderbuffer_:_mesa_reference_renderbuffer:_mesa_free_framebuffer_data:_mesa_destroy_framebuffer
*** This bug is a duplicate of bug 1754693 *** https://bugs.launchpad.net/bugs/1754693 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.1-3ubuntu2, the problem page at https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae 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: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic kylin-17.10 xenial yakkety zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1801870 Title: /usr/lib/xorg/Xorg:6:st_renderbuffer_delete:_mesa_reference_renderbuffer_:_mesa_reference_renderbuffer:_mesa_free_framebuffer_data:_mesa_destroy_framebuffer Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.1-3ubuntu2, the problem page at https://errors.ubuntu.com/problem/a1e7fe67e388164abd73462b322cb79ac2773fae 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/xorg-server/+bug/1801870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798790] Re: Ubuntu 18.10 login screen never appears when using the Nvidia driver
** Changed in: mutter (Ubuntu) Importance: Undecided => High -- 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/1798790 Title: Ubuntu 18.10 login screen never appears when using the Nvidia driver Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/435 --- The boot process hangs with the last message being "started bpfilter". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]
I have the same issue on 18.04, Wayland: ``` $ snap list skype Name VersionRev Tracking Publisher Notes skype 8.33.0.41 63 stableskype✓ classic ``` -- 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/1754693 Title: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps] Status in mesa package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO 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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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: Mon Oct 16 18:18:18 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version:
[Desktop-packages] [Bug 1095498] Re: Printing PDFs with images is hideously slow on HP LaserJet 3030 MFP
Hey! I am using Ricoh Printer SC-602: here some problems which generated by printer as well as below: I also try at http://printertechsupportnumbers.com/blog/how-to-fix-ricoh-printer-offline-error/ but not getting proper solution, if anybody having solution for this error just share here. Communication problem between BICU hard disk drive board Communication problem between BCU and fuser control unit on Aficio 400, 401, 500 Communication problem between Hard disk drive board and SBICU Aficio 550/650 Communication problem between BICU and hard disk drive board Aficio 551, 551P, 700, 700P -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1095498 Title: Printing PDFs with images is hideously slow on HP LaserJet 3030 MFP Status in system-config-printer package in Ubuntu: Confirmed Bug description: Printing anything with graphics from Firefix (such as a Google Maps page), or a PDF file containing graphics, takes a ridiculously long time to print, often several minutes per page. This is with a directly-attached USB postscript printer (an HP 3030 mfp). The exact same content prints in only 2 seconds when printed from Windows 7 running in a VM, to the same printer via an independent print server (avoiding CUPS in the Ubuntu host). NOTE: If the page in Firefox is first printed "to file" and PDF is selected, the very long delay happens when printing the resulting PDF using the "lpr" command. If, instead, "print to file" is done from Firefox and Postscript is selected, the resulting .ps file prints much faster (still 10x slower than printing from Windows 7, but much faster than printing the equivalent PDF). So there must be something bogus in how CUPS handles PDF files containging images. STEPS TO REPRODUCE: 1. Visit https://maps.google.com/ in Firefox on Ubuntu 2. Search for "San Francisco" and click the print icon (in the left bar near the top). 3. A printable map is displayed; hit ^P to print it to a postscript printer (1-2 minute delay before the page prints) Do exactly the same on a Windows 7 system and printing starts in about 2 seconds. Alternatively, try printing the attached PDF and PS files. The PDF is hideously slow (minutes), but the PS is only slow (about 10 seconds to print on my system).Compared to 2 seconds when printed from Windows. All the same content. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: cups 1.5.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Wed Jan 2 17:14:16 2013 InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for hp-LaserJet-3030: hp:/usb/hp_LaserJet_3030?serial=00CNBM066305 device for hp-LaserJet-3030-Fax: hpfax:/usb/hp_LaserJet_3030?serial=00CNBM066305 device for PDF: cups-pdf:/ MachineType: System manufacturer System Product Name MarkForUpload: True Papersize: letter PpdFiles: hp-LaserJet-3030: HP LaserJet 3020 3030 Postscript (recommended) PDF: Generic CUPS-PDF Printer hp-LaserJet-3030-Fax: HP Fax hpcups ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=8aaca318-f079-4a4f-95c0-735aa54bed2d ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to precise on 2012-08-10 (145 days ago) dmi.bios.date: 09/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6T 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.:bvr1408:bd09/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1095498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799430] Re: Icon dock visible on lock screen
@Plurto your workaround was successful for my case as well. Thanks. Weird bug, transparency affecting clicks and interaction through a lock screen. -- 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/1799430 Title: Icon dock visible on lock screen Status in gnome-shell-extension-dashtodock package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When locking the machine with alt-L the icon dock is still visible. After Login, the dock does not get adjusted to the top menu. In rare cases, the dock does not respond any more. This requires a reboot of the machine ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: mutter 3.30.1-1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 23 12:59:27 2018 InstallationDate: Installed on 2018-04-30 (176 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: mutter UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
