[Desktop-packages] [Bug 1863714] [NEW] package libevdocument3-4:amd64 3.18.2-1ubuntu4.6 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
Public bug reported: Don't have any ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libevdocument3-4:amd64 3.18.2-1ubuntu4.6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Feb 10 19:38:30 2020 DpkgHistoryLog: Start-Date: 2020-02-10 19:35:55 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), libsystemd0:i386 (229-4ubuntu21.21, 229-4ubuntu21.27), sudo:amd64 (1.8.16-0ubuntu1.8, 1.8.16-0ubuntu1.9), udev:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), libudev1:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), libudev1:i386 (229-4ubuntu21.21, 229-4ubuntu21.27), systemd-sysv:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), firefox-locale-en:amd64 (72.0.1+build1-0ubuntu0.16.04.1, 72.0.2+build1-0ubuntu0.16.04.1), firefox-locale-nl:amd64 (72.0.1+build1-0ubuntu0.16.04.1, 72.0.2+build1-0ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), systemd:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), firefox:amd64 (72.0.1+build1-0ubuntu0.16.04.1, 72.0.2+build1-0ubuntu0.16.04.1), libexiv2-14:amd64 (0.25-2.1ubuntu16.04.5, 0.25-2.1ubuntu16.04.6) ErrorMessage: vereistenproblemen - blijft ongeconfigureerd InstallationDate: Installed on 2017-02-14 (1098 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-173-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: evince Title: package libevdocument3-4:amd64 3.18.2-1ubuntu4.6 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd UpgradeStatus: Upgraded to xenial on 2020-02-18 (0 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1863714 Title: package libevdocument3-4:amd64 3.18.2-1ubuntu4.6 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd Status in evince package in Ubuntu: New Bug description: Don't have any ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libevdocument3-4:amd64 3.18.2-1ubuntu4.6 ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Mon Feb 10 19:38:30 2020 DpkgHistoryLog: Start-Date: 2020-02-10 19:35:55 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), libsystemd0:i386 (229-4ubuntu21.21, 229-4ubuntu21.27), sudo:amd64 (1.8.16-0ubuntu1.8, 1.8.16-0ubuntu1.9), udev:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), libudev1:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), libudev1:i386 (229-4ubuntu21.21, 229-4ubuntu21.27), systemd-sysv:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), firefox-locale-en:amd64 (72.0.1+build1-0ubuntu0.16.04.1, 72.0.2+build1-0ubuntu0.16.04.1), firefox-locale-nl:amd64 (72.0.1+build1-0ubuntu0.16.04.1, 72.0.2+build1-0ubuntu0.16.04.1), libpam-systemd:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), systemd:amd64 (229-4ubuntu21.21, 229-4ubuntu21.27), firefox:amd64 (72.0.1+build1-0ubuntu0.16.04.1, 72.0.2+build1-0ubuntu0.16.04.1), libexiv2-14:amd64 (0.25-2.1ubuntu16.04.5, 0.25-2.1ubuntu16.04.6) ErrorMessage: vereistenproblemen - blijft ongeconfigureerd InstallationDate: Installed on 2017-02-14 (1098 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-173-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: evince Title: package libevdocument3-4:amd64 3.18.2-1ubuntu4.6 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd UpgradeStatus: Upgraded to xenial on 2020-02-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1863714/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857869] Re: Red fill the search stop icon
** Changed in: nautilus Status: Unknown => New -- 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/1857869 Title: Red fill the search stop icon Status in Nautilus: New Status in nautilus package in Ubuntu: Triaged Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) It might be better if the search stop icon was red filled. Similar to a stop sign. 4) The search stop icon is white filled. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1857869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863463] Re: Firefox 75 requires nodejs >= 10.19
** Description changed: Firefox trunk, to become version 75.0 in April 2020, has bumped its nodejs requirement to 10.19 (https://bugzilla.mozilla.org/show_bug.cgi?id=1547823). + + Firefox 75 Beta starts on March 9th. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1863463 Title: Firefox 75 requires nodejs >= 10.19 Status in firefox package in Ubuntu: New Status in nodejs package in Ubuntu: New Bug description: Firefox trunk, to become version 75.0 in April 2020, has bumped its nodejs requirement to 10.19 (https://bugzilla.mozilla.org/show_bug.cgi?id=1547823). Firefox 75 Beta starts on March 9th. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1863463/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package asterisk - 1:16.2.1~dfsg-2ubuntu1 --- asterisk (1:16.2.1~dfsg-2ubuntu1) focal; urgency=medium * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) -- Andreas Hasenack Wed, 12 Feb 2020 19:54:27 -0300 ** Changed in: asterisk (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to redland in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in gnunet package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: In Progress Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-mono (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-extra in Ubuntu. https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-themes-extra (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-extra in Ubuntu. https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: humanity-icon-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-extra in Ubuntu. https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: adwaita-icon-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-extra in Ubuntu. https://bugs.launchpad.net/bugs/1861558 Title: Snap 'ed applicaitons have garbage on top of the window Close [x] button Status in adwaita-icon-theme package in Ubuntu: Confirmed Status in gnome-themes-extra package in Ubuntu: Confirmed Status in humanity-icon-theme package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Status in ubuntu-mono package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 19.10 installed 2. Install GNOME application as a Snap - for example with sudo snap install gedit gnome-calculator 3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the one of the following: * Adwaita * DMZ-Black * DMZ-White * hicolor * HighContrast * Humanity * Humanity-Dark * LoginIcons For example - Adwaita theme with Adwaita icon set. 4. Open GNOME Calculator as a Snap application: /snap/bin/gnome-calculator Expected result: * GNOME Calculator looks as any other GTK application Actual result: * GNOME Calculator has garbage on top of the window Close [x] button --- Notes: 1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868 2. one can use the script below to check all possible Theme<->Icon combinations: ``` #!/bin/bash DISPLAY=:0 for t in $(ls -1 /usr/share/themes/) do for i in $(ls -1 /usr/share/icons/) do echo -e "\nTheme: $t, Icons: $i\n" gsettings set org.gnome.desktop.interface gtk-theme "$t" gsettings set org.gnome.desktop.interface icon-theme "$i" /snap/bin/gnome-calculator #read -r -s -p "Press for next theme" done done ``` ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: snapd 2.41+19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 1 17:55:09 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1653351] Re: Have option to not automatically open next email
** Changed in: thunderbird Importance: Wishlist => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1653351 Title: Have option to not automatically open next email Status in Mozilla Thunderbird: Confirmed Status in Ubuntu GNOME: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: I have found that with Thunderbird if I open an email and then press a button such as the "Junk" or "Delete" button, it will automatically move on and open the next email. Now as I get a lot of spam on this email in the inbox with the spam filter not properly configured yet, it would be very useful if there were an option to disable this automatically opening the next email feature. So that it would just go to the blank screen in the email display section. Quite a few people I know for similar reasons say they would like an option like this so that malicious emails don't accidentally get opened. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1653351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1853731] Re: [snap] chromium stops working after a while, fails to render new tabs/pages
[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/1853731 Title: [snap] chromium stops working after a while, fails to render new tabs/pages Status in chromium-browser package in Ubuntu: Expired Bug description: name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: beta refresh-date: 2 days ago, at 15:17 AEDT channels: stable:78.0.3904.108 2019-11-21 (949) 160MB - candidate: 78.0.3904.108 2019-11-22 (952) 160MB - beta: 79.0.3945.45 2019-11-22 (951) 155MB - edge: 80.0.3962.2 2019-11-11 (945) 155MB - installed: 79.0.3945.45 (951) 155MB - I recently upgraded to Ubuntu 19.10. I have an old Nvidia card which relies on the 340 drivers, so I cannot use Wayland. I can launch Chromium browser ok, but then, after what seems like an interdeterminate period of time, new "things" will fail to render in the interface, and the only solution is to killall chrome. When the issue kicks in, existing webpages are fine, but following fail: * Navigate to a new web page (tab is blank) * Open a new tab (tab is blank) * Open a new window (entire window is blank) Chromium continues to respond to keystrokes, and you can see it loading things in the status bar, just the display does not render. Killing chromium and restarting it works until it happens again. I understand this is vague and would appreciate information on how to report problems with the chromium snap. apport tells me it can't do it, because it's a snap. Am happy to supply additional info if it happens again, as long as I know what I need to report. I switched to the beta snap after experiencing the problem with the stable snap. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sdc1 ext4 2.7T 865G 1.8T 34% /home tmpfs tmpfs 3.9G 103M 3.8G 3% /dev/shm /dev/sdc1 ext4 2.7T 865G 1.8T 34% /home DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2016-01-21 (1422 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. P55A-UD4 NonfreeKernelModules: nvidia Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-25-generic root=UUID=c8c5f257-b889-41be-8ee5-fbb3abe7711e ro nomodeset quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 (29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916}) Snap.ChromiumVersion: Chromium 79.0.3945.79 snap Tags: eoan snap Uname: Linux 5.3.0-25-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-02 (42 days ago) UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/16/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F15 dmi.board.name: P55A-UD4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF15:bd09/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD4 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2018-11-10T13:06:57.396750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1853731/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856941] Re: chinese input option just qwerty
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1856941 Title: chinese input option just qwerty Status in gnome-control-center package in Ubuntu: Expired Bug description: Not sure where to report this, but this is where to reproduce, at least: to reproduce 1) click on triangle at top right hand corner of screen to get menu 2) click on settings icon 3) click on language and region 4) click on + 5) click on ... 6) click on other 7) click on chinese 8) click on add 9) you should now have a 'chinese' input source. click on that 10) click on keyboard icon this shows just a plain qwerty keyboard alternatively click on the input language option at the top of the screen select chinese (zh) start typing on an input field somewhere result: qwerty, not chinese input. what should happen the chinese (zh) input should actually generate chinese characters. or something ubuntu: 18.04 bionic gnome-control-center: 3.28.2-0ubuntu0.18.04.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1856941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863026] Re: Remove my_bool typedef workaround
This bug was fixed in the package argus-clients - 1:3.0.8.2-5ubuntu1 --- argus-clients (1:3.0.8.2-5ubuntu1) focal; urgency=medium * d/p/mysql8_my_bool.patch: Reintroduce my_bool to fix build with MySQL 8. (LP: #1863026) -- Andreas Hasenack Wed, 12 Feb 2020 19:47:54 -0300 ** Changed in: argus-clients (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to redland in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: In Progress Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: In Progress Status in dballe package in Ubuntu: In Progress Status in gambas3 package in Ubuntu: In Progress Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in gnunet package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: In Progress Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747487] Re: Sonido
*** This bug is a duplicate of bug 1682322 *** https://bugs.launchpad.net/bugs/1682322 ** This bug has been marked a duplicate of bug 1682322 PCI/internal sound card not detected dummy drive only on Dell Inspiron 5567 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1747487 Title: Sonido Status in xorg package in Ubuntu: New Bug description: No me reproduce sonido ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 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 Feb 5 12:24:37 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0767] InstallationDate: Installed on 2018-01-14 (21 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 5567 ProcEnviron: LANGUAGE=es_CR:es PATH=(custom, no user) LANG=es_CR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed root=UUID=6c7bacd6-3cb7-45a1-aae6-01b254d6be95 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.9 dmi.board.name: 01W6F7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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 Feb 5 12:20:03 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1317 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1747487/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1682322] Re: PCI/internal sound card not detected dummy drive only on Dell Inspiron 5567
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1682322 Title: PCI/internal sound card not detected dummy drive only on Dell Inspiron 5567 Status in alsa-driver package in Ubuntu: Confirmed Bug description: only the dummy drive is showing in my sound preferences ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', '/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Apr 13 12:53:46 2017 InstallationDate: Installed on 2017-04-05 (7 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.9 dmi.board.name: 01W6F7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1682322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1682322] Re: PCI/internal sound card not detected dummy drive only on Dell Inspiron 5567
** Summary changed: - PCI/internal sound card not detected dummy drive only + PCI/internal sound card not detected dummy drive only on Dell Inspiron 5567 -- 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/1682322 Title: PCI/internal sound card not detected dummy drive only on Dell Inspiron 5567 Status in alsa-driver package in Ubuntu: Confirmed Bug description: only the dummy drive is showing in my sound preferences ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp3', '/dev/dsp2', '/dev/dsp1', '/dev/dsp', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Apr 13 12:53:46 2017 InstallationDate: Installed on 2017-04-05 (7 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.9 dmi.board.name: 01W6F7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn01W6F7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1682322/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863400] Re: gnome-shell reports problem on boot
Yes, error report links are mostly anonymous. Except for your username but in this case it is user 121 which is the built-in user 'gdm' (owner of the login screen). I think it's generally just Bug Control members who can view the page so it is secure. Please share the bug link here. -- 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/1863400 Title: gnome-shell reports problem on boot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Problem reported at boot but does not seem to collect data and send, just does nothing. See attached screenshot of window. Still able to use laptop. This file exists in /var/crash -rw-r- 1 gdm whoopsie 21900809 Feb 14 22:01 _usr_bin_gnome-shell.121.crash The time of this file must have been at last shutdown which did take a little longer than usual. Description: Ubuntu 18.04.4 LTS Release: 18.04 gnome-shell: Installed: 3.28.4-0ubuntu18.04.3 Candidate: 3.28.4-0ubuntu18.04.3 Version table: *** 3.28.4-0ubuntu18.04.3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.3+git20190124-0ubuntu18.04.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.28.1-0ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 15 06:21:53 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-17 (454 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/1863400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863603] Re: [comet lake] Screen is scrambled/distored and flickers
*** This bug is a duplicate of bug 1855608 *** https://bugs.launchpad.net/bugs/1855608 Thanks for the bug report. This sounds like a kernel bug but are you able to provide additional photos of the bug under different conditions? ** Summary changed: - Screen is scrambled/distored and flickers + [comet lake] Screen is scrambled/distored and flickers ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1863603 Title: [comet lake] Screen is scrambled/distored and flickers Status in linux package in Ubuntu: New Bug description: The screen is distorted/scrambled every now and then. That is, it's like a few lines of pixels are repeated (so it's a normally a blur). The screen also flickers at times. This happens a few times a few. I've noticed that if I close the lid and let the screen dim/blank/suspend then normally is goes back to normal when it wakes up. To my knowledge his happens irrespective of what programs I use at the time. Dell XPS 13 (7390). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Feb 17 12:32:42 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-29-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-12-24 (54 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=c325f61e-5f45-4a7a-ada7-71dd6d7d4b42 ro resume=UUID=c325f61e-5f45-4a7a-ada7-71dd6d7d4b42 resume_offset=67694592 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/03/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863603/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Thanks for letting us know. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: New => Invalid ** Changed in: mutter (Ubuntu) Status: New => Invalid -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747878] Re: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provi
I agree, but we're not the developers of PulseAudio and we have thousands of software packages to get into Ubuntu... Polishing each one to reduce log noise is not usually something we have time to do. If you would like the issue fixed then please report it to the PulseAudio developers 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/1747878 Title: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Status in pulseaudio package in Ubuntu: Won't Fix Bug description: This is logged since a while on that desktop (default ubuntu install) [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Googling about it: https://stackoverflow.com/questions/37132033/ofono-dbus-introspection-method-not-found https://github.com/pulseaudio/pulseaudio/blob/master/src/modules/bluetooth/backend-ofono.c Also note Debian has more recent version: http://metadata.ftp-master.debian.org/changelogs/main/p/pulseaudio/pulseaudio_11.1-4_changelog note: that install has no 'ofono' package installed; and sound works as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem1319 F pulseaudio CurrentDesktop: GNOME Date: Wed Feb 7 10:49:34 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.00 dmi.board.name: B150M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1747878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827751] Re: Shield screen is displayed after blanking even when lock screen disabled
** Tags added: fixed-in-3.35.91 fixed-upstream -- 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/1827751 Title: Shield screen is displayed after blanking even when lock screen disabled Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Triaged Bug description: Ubuntu 19.04 Gnome Screen lock is set to off in Settings->Privacy. Blank Screen is set to 10 minutes in Settings->Power. On returning from Screen Blank, Lock Screen is present. Does not occur after manual suspend (ie closing laptop lid) and resuming. In dconf I have set org/gnome/desktop/lockdown/disable-lock-screen to true. org/gnome/desktop/screensaver/lock-enabled is set to false org/gnome/desktop/screensaver/ubuntu-lock-on-suspend is set to false ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 4 19:25:36 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-22 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: [modified] mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2019-04-24T23:58:15.215728 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1827751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863661] Re: CPU saturation
Please run 'top' to find out the name of the process(es) using the most CPU and tell us what they are. Or just attach a screenshot of the top window here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1863661 Title: CPU saturation Status in Ubuntu: Incomplete Bug description: CPU 2 saturates when launching certain disparate functions ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Mon Feb 17 17:58:46 2020 DistUpgraded: 2018-10-20 19:37:54,967 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: 8192cu, 1.11, 4.15.0-48-generic, x86_64: installed 8192cu, 1.11, 4.15.0-76-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a6c] InstallationDate: Installed on 2016-10-17 (1218 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Compaq-Presario VC886AA-ABF CQ5106FR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=1b622152-961b-43de-9f0f-16f62e22c3c5 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-20 (484 days ago) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.38 dmi.board.name: NARRA5 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 5.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.38:bd03/20/2009:svnCompaq-Presario:pnVC886AA-ABFCQ5106FR:pvr:rvnPEGATRONCORPORATION:rnNARRA5:rvr5.00:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: VC886AA-ABF CQ5106FR dmi.sys.vendor: Compaq-Presario version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Oct 13 17:58:53 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Entry Keyboard KEYBOARD, id 8 inputLogitech USB Optical Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1863661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862910] Re: gnome-shell leaking memory when a customized AppImageLauncher is running
** Also affects: appimagelauncher Importance: Undecided Status: New ** No longer affects: appimagelauncher -- 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/1862910 Title: gnome-shell leaking memory when a customized AppImageLauncher is running Status in gnome-shell package in Ubuntu: New Bug description: Edited description: To replicate the problem (on Ubuntu 19.10 running Ubuntu Gnome) 1. Install AppImageLauncher from https://github.com/TheAssassin/AppImageLauncher/releases by downloading version 2.1.0 deb file (appimagelauncher_2.1.0-travis897.d1be7e7.bionic_amd64.deb) and install it. If necessary run sudo apt install -f to fix missing dependencies. 2. Run it and change the appimage destination location to ~/apps/appimages. It is necessary to change it away from the default setting in order for the problem to appear, though probably the actual destination is not important). Ensure that Auto start auto- integration daemon is selected. 3. Download an appimage (I downloaded Cura 4.4.1 from https://github.com/Ultimaker/Cura/releases/tag/4.4.1) I don't know whether any appimage would do, probably it would. In fact I don't know whether this step and the next need to be done at all. 4. Open it with appimagelauncher (this can be done by double clicking it in nautilus) and tell it to move it and run the application. Then close the application. 5. It may be necessary to reboot at this point I don't know. 6. Logon using Ubuntu (Gnome) and watch the memory usage of gnome- shell. It may take a few minutes to get going but then the memory used will start increasing at several MB/minute. There is an issue open against appimage launcher which is likely the same problem. https://github.com/TheAssassin/AppImageLauncher/issues/294 Original description: On one of my machines which has been upgraded over several years and is now running 19.10 just one of the configured users appears to be seeing a dramatic memory leak in gnome-shell, even when nothing is happening on the UI. Immediately after logging on, using the Ubuntu selection from the logon screen, gnome shell shows as using about 134MB. From there it climbs at about 300MB per hour and after a few hours the machine grinds to a crawl, not surprisingly. This happens even if the user logs on and then the machine is left completely alone. Logout and back in frees all the memory. A test user I have configured sees no such problem. I have uninstalled all extensions apart from the system ones, disabled all the system ones and reset all the gnome settings using dconf reset -f /org/gnome/ to no avail. Also I have removed ~/.local/share/gnome-shell and allowed it to recreate it. Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2. I can't see anything obvious in the log. It must be something in my settings that is triggering it as the other user does not see it, but I have run out of ideas on what to try. See also bug #1856516 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 08:54:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2014-10-21 (1939 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863687] Re: gnome-software crashed with SIGSEGV in gs_plugin_add_updates()
*** This bug is a duplicate of bug 1861989 *** https://bugs.launchpad.net/bugs/1861989 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 #1861989, 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/1863687/+attachment/5329101/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1863687/+attachment/5329103/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1863687/+attachment/5329106/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1863687/+attachment/5329107/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1863687/+attachment/5329108/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1863687/+attachment/5329109/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1863687/+attachment/5329110/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1861989 ** 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 gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1863687 Title: gnome-software crashed with SIGSEGV in gs_plugin_add_updates() Status in gnome-software package in Ubuntu: New Bug description: An install of a few items ran. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Classic:GNOME Date: Mon Feb 17 18:54:45 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2020-01-27 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.2-0ubuntu2 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7ff236606b62 : mov 0x8(%rax),%eax PC (0x7ff236606b62) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: gs_plugin_add_updates () from /usr/lib/x86_64-linux-gnu/gs-plugins-13/libgs_plugin_snap.so ?? () ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gnome-software crashed with SIGSEGV in gs_plugin_add_updates() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1863687/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863608] Re: version 80 does not start using remote display (X11)
Same issue (version 80.0.3987.87-0ubuntu0.16.04.1 on 16.04 Xenial), although mine shows up as yellow-green. Downgrading to 79.0.3945.130-0ubuntu0.16.04.1 fixed the problem. For others experiencing the problem, I was able to find the three needed files (referenced in the bug description) here: https://launchpad.net /~canonical-chromium-builds/+archive/ubuntu/stage/+build/18619022 ** Attachment added: "Picture of the yellow-green window" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863608/+attachment/5329100/+files/2020-02-17%2017_40_43.png -- 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/1863608 Title: version 80 does not start using remote display (X11) Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium-browser version 80.0.3987.87-0ubuntu0.16.04.1_amd64 does not work when using remote display; the browser window is a solid pink area without any menu (see picture). Same with the (existing?) command line option "--disable-gpu" Downgrading to chromium-browser_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb chromium-browser-l10n_79.0.3945.130-0ubuntu0.16.04.1_all.deb chromium-codecs-ffmpeg-extra_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb resolve the issue. Description: Ubuntu 16.04.6 LTS All packages are up to date on 2020-02-17 on xenial, xenial-updates and xenial-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863608] Re: version 80 does not start using remote display (X11)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/1863608 Title: version 80 does not start using remote display (X11) Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium-browser version 80.0.3987.87-0ubuntu0.16.04.1_amd64 does not work when using remote display; the browser window is a solid pink area without any menu (see picture). Same with the (existing?) command line option "--disable-gpu" Downgrading to chromium-browser_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb chromium-browser-l10n_79.0.3945.130-0ubuntu0.16.04.1_all.deb chromium-codecs-ffmpeg-extra_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb resolve the issue. Description: Ubuntu 16.04.6 LTS All packages are up to date on 2020-02-17 on xenial, xenial-updates and xenial-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827751] Re: Shield screen is displayed after blanking even when lock screen disabled
** Changed in: gnome-shell Status: New => Fix Released -- 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/1827751 Title: Shield screen is displayed after blanking even when lock screen disabled Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Triaged Bug description: Ubuntu 19.04 Gnome Screen lock is set to off in Settings->Privacy. Blank Screen is set to 10 minutes in Settings->Power. On returning from Screen Blank, Lock Screen is present. Does not occur after manual suspend (ie closing laptop lid) and resuming. In dconf I have set org/gnome/desktop/lockdown/disable-lock-screen to true. org/gnome/desktop/screensaver/lock-enabled is set to false org/gnome/desktop/screensaver/ubuntu-lock-on-suspend is set to false ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 4 19:25:36 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-04-22 (12 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: [modified] mtime.conffile..etc.xdg.autostart.gnome-shell-overrides-migration.desktop: 2019-04-24T23:58:15.215728 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1827751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862847] Re: New Epson V19 scanner problems under Ubuntu 18.04.3
I followed the instructions in #2 above regarding FindRightPackage, and it printed sane-utils on my terminal regarding the scanimage command. Aptitude shows that the sane-utils package is indeed installed. But when I tried to follow the instructions in +editstatus, it refused the sane-utils entry saying that Ubuntu has no such package. It suggested the sane-backends package, so I put that in only because it allowed that. Thank you in advance for any help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1862847 Title: New Epson V19 scanner problems under Ubuntu 18.04.3 Status in sane-backends package in Ubuntu: New Bug description: Bought new Epson V19 scanner, and it works fine on my wife's computer running Windows 7, and also on my computer running Windows XP. Rebooted my computer into Ubuntu 18.04.3, and installed the driver packages recommended by Epson (version 3.61.0 for Ubuntu 18.04, 64 bit, release date 12-26-2019) using their install.sh file with the without-network option (imagescan 3.61.0, imagescan-plugin-gt-s650 1.0.2, and imagescan-plugin-ocr-engine 1.0.2). Looking at these packages using Aptitude, it appears that they are installed OK with no missing dependencies. Imagescan (on the graphical desktop) appears to find the scanner, and when you click to scan, you can hear the scanner seeming to run normally, but no image is produced at the end. Using the terminal, lsusb, sane-find-scanner, and scanimage -L all seem to work fine for finding the scanner. But when I try scanimage -T, no image file is produced, although you can hear the scanner appearing to do a normal scan. So it appears that all the control functions are working fine, but the problem is getting the scan data. I also tried the suggestions in this video (https://www.youtube.com/watch?v=8q82X7PpRaQ) titled "ubuntu 18.04 scanner problems how to fix them" concerning bug 1728012. In the end, nothing appears to have changed, so it appears I didn't make it any better or any worse. Any help would be greatly appreciated, including referring me to another place if I'm not posting in the right place yet. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1862847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1175882] Re: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images)
** Changed in: df-libreoffice Status: Incomplete => New -- 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/1175882 Title: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images) Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Bug description: Follow these steps to bring LibreOffice writer to a crawl: 1) Allow this page to fully load in firefox (in a new tab): http://www.amorosity.com/SlingBlade/ 2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire page's contents into memory). 3) Open LibreOffice writer, and paste your clipboard into it. I don't mind waiting for all the images to get loaded. The main point here, is that performance is not only slow during the initial paste. After the images get fully loaded into the word processing document, interacting with the document becomes impractical. Everything you try to do makes the application hang for several seconds. I have 4 gigabytes of RAM available for LibreOffice writer to use as it wishes, but it must be using some type of swap file (instead) while I'm modifying this large document. However, I have a really fast solid-state hard drive, so you'd think that even that would be fast on my machine. My machine should have the specs to enable me the ability to handle converting this large web page into a word processing document. Yes there are other ways to achieve what I'm trying to do, but this bug is about how LibreOffice can't handle the job. If it was programmed just right, it would make use of the resources my computer would gladly provide it, and scale up to this rather intensive task. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu May 2 23:09:24 2013 InstallationDate: Installed on 2013-04-02 (31 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862847] Re: New Epson V19 scanner problems under Ubuntu 18.04.3
** Package changed: ubuntu => sane-backends (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1862847 Title: New Epson V19 scanner problems under Ubuntu 18.04.3 Status in sane-backends package in Ubuntu: New Bug description: Bought new Epson V19 scanner, and it works fine on my wife's computer running Windows 7, and also on my computer running Windows XP. Rebooted my computer into Ubuntu 18.04.3, and installed the driver packages recommended by Epson (version 3.61.0 for Ubuntu 18.04, 64 bit, release date 12-26-2019) using their install.sh file with the without-network option (imagescan 3.61.0, imagescan-plugin-gt-s650 1.0.2, and imagescan-plugin-ocr-engine 1.0.2). Looking at these packages using Aptitude, it appears that they are installed OK with no missing dependencies. Imagescan (on the graphical desktop) appears to find the scanner, and when you click to scan, you can hear the scanner seeming to run normally, but no image is produced at the end. Using the terminal, lsusb, sane-find-scanner, and scanimage -L all seem to work fine for finding the scanner. But when I try scanimage -T, no image file is produced, although you can hear the scanner appearing to do a normal scan. So it appears that all the control functions are working fine, but the problem is getting the scan data. I also tried the suggestions in this video (https://www.youtube.com/watch?v=8q82X7PpRaQ) titled "ubuntu 18.04 scanner problems how to fix them" concerning bug 1728012. In the end, nothing appears to have changed, so it appears I didn't make it any better or any worse. Any help would be greatly appreciated, including referring me to another place if I'm not posting in the right place yet. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1862847/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1175882]
[Automated Action] NeedInfo-To-Unconfirmed -- 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/1175882 Title: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images) Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Bug description: Follow these steps to bring LibreOffice writer to a crawl: 1) Allow this page to fully load in firefox (in a new tab): http://www.amorosity.com/SlingBlade/ 2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire page's contents into memory). 3) Open LibreOffice writer, and paste your clipboard into it. I don't mind waiting for all the images to get loaded. The main point here, is that performance is not only slow during the initial paste. After the images get fully loaded into the word processing document, interacting with the document becomes impractical. Everything you try to do makes the application hang for several seconds. I have 4 gigabytes of RAM available for LibreOffice writer to use as it wishes, but it must be using some type of swap file (instead) while I'm modifying this large document. However, I have a really fast solid-state hard drive, so you'd think that even that would be fast on my machine. My machine should have the specs to enable me the ability to handle converting this large web page into a word processing document. Yes there are other ways to achieve what I'm trying to do, but this bug is about how LibreOffice can't handle the job. If it was programmed just right, it would make use of the resources my computer would gladly provide it, and scale up to this rather intensive task. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu May 2 23:09:24 2013 InstallationDate: Installed on 2013-04-02 (31 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1175882]
I can still reproduce this on Kubuntu 19.10. Here's a video of me reproducing it: https://youtu.be/EM26C_Q-hKA I was using GNOME when I first reported this bug. KDE is handling this better than GNOME did, but Libre Office Writer still becomes unusable after following the exact steps I outlined above. -- 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/1175882 Title: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images) Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Bug description: Follow these steps to bring LibreOffice writer to a crawl: 1) Allow this page to fully load in firefox (in a new tab): http://www.amorosity.com/SlingBlade/ 2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire page's contents into memory). 3) Open LibreOffice writer, and paste your clipboard into it. I don't mind waiting for all the images to get loaded. The main point here, is that performance is not only slow during the initial paste. After the images get fully loaded into the word processing document, interacting with the document becomes impractical. Everything you try to do makes the application hang for several seconds. I have 4 gigabytes of RAM available for LibreOffice writer to use as it wishes, but it must be using some type of swap file (instead) while I'm modifying this large document. However, I have a really fast solid-state hard drive, so you'd think that even that would be fast on my machine. My machine should have the specs to enable me the ability to handle converting this large web page into a word processing document. Yes there are other ways to achieve what I'm trying to do, but this bug is about how LibreOffice can't handle the job. If it was programmed just right, it would make use of the resources my computer would gladly provide it, and scale up to this rather intensive task. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu May 2 23:09:24 2013 InstallationDate: Installed on 2013-04-02 (31 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862847] [NEW] New Epson V19 scanner problems under Ubuntu 18.04.3
You have been subscribed to a public bug: Bought new Epson V19 scanner, and it works fine on my wife's computer running Windows 7, and also on my computer running Windows XP. Rebooted my computer into Ubuntu 18.04.3, and installed the driver packages recommended by Epson (version 3.61.0 for Ubuntu 18.04, 64 bit, release date 12-26-2019) using their install.sh file with the without-network option (imagescan 3.61.0, imagescan-plugin-gt-s650 1.0.2, and imagescan- plugin-ocr-engine 1.0.2). Looking at these packages using Aptitude, it appears that they are installed OK with no missing dependencies. Imagescan (on the graphical desktop) appears to find the scanner, and when you click to scan, you can hear the scanner seeming to run normally, but no image is produced at the end. Using the terminal, lsusb, sane-find-scanner, and scanimage -L all seem to work fine for finding the scanner. But when I try scanimage -T, no image file is produced, although you can hear the scanner appearing to do a normal scan. So it appears that all the control functions are working fine, but the problem is getting the scan data. I also tried the suggestions in this video (https://www.youtube.com/watch?v=8q82X7PpRaQ) titled "ubuntu 18.04 scanner problems how to fix them" concerning bug 1728012. In the end, nothing appears to have changed, so it appears I didn't make it any better or any worse. Any help would be greatly appreciated, including referring me to another place if I'm not posting in the right place yet. Thank you. ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- New Epson V19 scanner problems under Ubuntu 18.04.3 https://bugs.launchpad.net/bugs/1862847 You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends 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 1849859] Re: smb printing fails
thanks @jan.dolezal that worked for me. for others, in my /etc/cups/printer.conf: these two were key to getting printing working: AuthInfoRequired username,password DeviceURI smb://:@ in Printers > Additional Printer Settings > / properties, I also set the DEVICE URI (a windows printer via Samba) but DID NOT add authentication: so just: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863661] Re: CPU saturation
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1863661 Title: CPU saturation Status in xorg package in Ubuntu: New Bug description: CPU 2 saturates when launching certain disparate functions ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Mon Feb 17 17:58:46 2020 DistUpgraded: 2018-10-20 19:37:54,967 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: 8192cu, 1.11, 4.15.0-48-generic, x86_64: installed 8192cu, 1.11, 4.15.0-76-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a6c] InstallationDate: Installed on 2016-10-17 (1218 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Compaq-Presario VC886AA-ABF CQ5106FR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=1b622152-961b-43de-9f0f-16f62e22c3c5 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-20 (484 days ago) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.38 dmi.board.name: NARRA5 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 5.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.38:bd03/20/2009:svnCompaq-Presario:pnVC886AA-ABFCQ5106FR:pvr:rvnPEGATRONCORPORATION:rnNARRA5:rvr5.00:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: VC886AA-ABF CQ5106FR dmi.sys.vendor: Compaq-Presario version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Oct 13 17:58:53 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Entry Keyboard KEYBOARD, id 8 inputLogitech USB Optical Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1863661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863661] [NEW] CPU saturation
You have been subscribed to a public bug: CPU 2 saturates when launching certain disparate functions ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Mon Feb 17 17:58:46 2020 DistUpgraded: 2018-10-20 19:37:54,967 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: 8192cu, 1.11, 4.15.0-48-generic, x86_64: installed 8192cu, 1.11, 4.15.0-76-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company C61 [GeForce 6150SE nForce 430] [103c:2a6c] InstallationDate: Installed on 2016-10-17 (1218 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Compaq-Presario VC886AA-ABF CQ5106FR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=1b622152-961b-43de-9f0f-16f62e22c3c5 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-20 (484 days ago) dmi.bios.date: 03/20/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.38 dmi.board.name: NARRA5 dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 5.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.38:bd03/20/2009:svnCompaq-Presario:pnVC886AA-ABFCQ5106FR:pvr:rvnPEGATRONCORPORATION:rnNARRA5:rvr5.00:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.family: 103C_53316J dmi.product.name: VC886AA-ABF CQ5106FR dmi.sys.vendor: Compaq-Presario version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Oct 13 17:58:53 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Entry Keyboard KEYBOARD, id 8 inputLogitech USB Optical Mouse MOUSE, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- CPU saturation https://bugs.launchpad.net/bugs/1863661 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 1796437] Re: [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate()
*** This bug is a duplicate of bug 1745345 *** https://bugs.launchpad.net/bugs/1745345 Unable to log in to Xorg session. I got dumped back to the login screen. I was able to log in using Wayland. I did a full update in CLI but was still unable to successfully log in to Xorg. Running on KVM/virt-manager -- 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/1796437 Title: [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate() Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 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 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 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-1build1 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.ne
[Desktop-packages] [Bug 1849859] Re: smb printing fails
Tried just now. After reboot "AuthInfoRequired username,password" still there -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862767] Re: gnome-control-center crashes when try to open it
The output of the command you asked for is $ systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-02-17 08:51:10 -03; 5h 33min ago Docs: man:NetworkManager(8) Main PID: 1206 (NetworkManager) Tasks: 3 (limit: 4915) Memory: 22.7M CGroup: /system.slice/NetworkManager.service └─1206 /usr/sbin/NetworkManager --no-daemon fev 17 08:51:53 adcamp NetworkManager[1206]: [1581940313.9009] device (p2p-dev-wlp3s0): supplicant management interface state: com fev 17 08:51:53 adcamp NetworkManager[1206]: [1581940313.9421] device (wlp3s0): supplicant interface state: authenticating -> asso fev 17 08:51:53 adcamp NetworkManager[1206]: [1581940313.9422] device (p2p-dev-wlp3s0): supplicant management interface state: aut fev 17 08:51:53 adcamp NetworkManager[1206]: [1581940313.9453] device (wlp3s0): supplicant interface state: associating -> associa fev 17 08:51:53 adcamp NetworkManager[1206]: [1581940313.9453] device (p2p-dev-wlp3s0): supplicant management interface state: ass fev 17 08:51:54 adcamp NetworkManager[1206]: [1581940314.0257] device (wlp3s0): supplicant interface state: associated -> complete fev 17 08:51:54 adcamp NetworkManager[1206]: [1581940314.0274] device (p2p-dev-wlp3s0): supplicant management interface state: ass fev 17 08:55:57 adcamp NetworkManager[1206]: [1581940557.0456] agent-manager: req[0x5652c8d3ab10, :1.407/org.gnome.Shell.NetworkAg fev 17 09:00:01 adcamp NetworkManager[1206]: [1581940801.3983] dhcp4 (wlp3s0): state changed bound -> expire fev 17 09:00:01 adcamp NetworkManager[1206]: [1581940801.3985] device (wlp3s0): DHCPv4: 480 seconds grace period started As the other thread mentions, it seems that it has to do with the NetworkManager. Since mine was already running (as I understood from the output above), I restarted it with $systemctl restart NetworkManager and the settings are working again. But the outputs of the status seems the same to me. See, after restart $ systemctl status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-02-17 15:15:22 -03; 14s ago Docs: man:NetworkManager(8) Main PID: 9778 (NetworkManager) Tasks: 4 (limit: 4915) Memory: 7.7M CGroup: /system.slice/NetworkManager.service └─9778 /usr/sbin/NetworkManager --no-daemon fev 17 15:15:29 adcamp NetworkManager[9778]: [1581963329.8784] device (p2p-dev-wlp3s0): supplicant management interface state: dis fev 17 15:15:29 adcamp NetworkManager[9778]: [1581963329.8802] device (wlp3s0): supplicant interface state: authenticating -> asso fev 17 15:15:29 adcamp NetworkManager[9778]: [1581963329.8802] device (p2p-dev-wlp3s0): supplicant management interface state: aut fev 17 15:15:29 adcamp NetworkManager[9778]: [1581963329.8924] device (wlp3s0): supplicant interface state: associating -> associa fev 17 15:15:29 adcamp NetworkManager[9778]: [1581963329.8924] device (p2p-dev-wlp3s0): supplicant management interface state: ass fev 17 15:15:30 adcamp NetworkManager[9778]: [1581963330.0012] device (wlp3s0): supplicant interface state: associated -> complete fev 17 15:15:30 adcamp NetworkManager[9778]: [1581963330.0013] device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) fev 17 15:15:30 adcamp NetworkManager[9778]: [1581963330.0013] device (p2p-dev-wlp3s0): supplicant management interface state: ass fev 17 15:15:30 adcamp NetworkManager[9778]: [1581963330.0015] device (wlp3s0): state change: config -> ip-config (reason 'none', fev 17 15:15:30 adcamp NetworkManager[9778]: [1581963330.0020] dhcp4 (wlp3s0): activation: beginning transaction (timeout in 45 se However, the settings open only once. After closing it, it gives the same error. And if I restart the NetworkManager it opens again (once). -- 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/1862767 Title: gnome-control-center crashes when try to open it Status in gnome-control-center package in Ubuntu: Incomplete Bug description: gnome-control center crashes when trying to open it. Tested as following $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) When trying to open it through the graphical interface it dies silently. A message of error would help too. Additional information: $ lsb_release -rd Description: Ubun
[Desktop-packages] [Bug 1849859] Re: smb printing fails
It's correct. You need to stop, modify and start. If you modify the file while cupsd is running on restart you lose the changes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1648534] Re: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_in
** Changed in: gnome-software (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: gnome-software (Ubuntu) Status: Fix Committed => In Progress -- 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/1648534 Title: gnome-software crashed with SIGTRAP in g_wakeup_new from g_main_context_new from g_dbus_connection_send_message_with_reply_sync from g_dbus_connection_call_sync_internal from g_dbus_connection_call_sync Status in gnome-software package in Ubuntu: In Progress Status in gnome-software source package in Xenial: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1, the problem page at https://errors.ubuntu.com/problem/70c23d0f4e2be24b26672427d4218dc8f0823597 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1648534/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849859] Re: smb printing fails
Do not edit /etc/cups/printers.conf while cupsd is running, as cupsd is modifying it. So first stop cupsd: sudo systemctl stop cupsd then edit the file and after that start cupsd again: sudo systemctl start cupsd Note that you only can edit the properties of permanent print queues. Queues which get temporarily created by CUPS or cups-browsed will loose the changes once they get removed and re-created. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849859] Re: smb printing fails
Right! I have to try after reboot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747878] Re: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provi
The resolution makes me chuckle. If this is a warning or an error in my system log it means I need to pay attention to it. Otherwise the log entry should not be a warning or at least it should have verbiage hinting this is not really a warning for me (it even sounds oxymoron :D ) As a side note, if a project emits too many warnings that need to be ignored this leads to developers also ignoring or missing important and relevant warnings that otherwise would be noticed. It is a bad practice to leave warnings that can be ignored; its also often a sign that the project needs more attention or lacks competent supervision. -- 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/1747878 Title: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Status in pulseaudio package in Ubuntu: Won't Fix Bug description: This is logged since a while on that desktop (default ubuntu install) [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Googling about it: https://stackoverflow.com/questions/37132033/ofono-dbus-introspection-method-not-found https://github.com/pulseaudio/pulseaudio/blob/master/src/modules/bluetooth/backend-ofono.c Also note Debian has more recent version: http://metadata.ftp-master.debian.org/changelogs/main/p/pulseaudio/pulseaudio_11.1-4_changelog note: that install has no 'ofono' package installed; and sound works as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oem1319 F pulseaudio CurrentDesktop: GNOME Date: Wed Feb 7 10:49:34 2018 EcryptfsInUse: Yes ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.00 dmi.board.name: B150M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1747878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792932] Re: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
This bug was fixed in the package xorg-server - 2:1.19.6-1ubuntu4.4 --- xorg-server (2:1.19.6-1ubuntu4.4) bionic; urgency=medium * dont-init-glamor-on-llvmpipe.diff: Glamor shouldn't be used on llvmpipe, as it might end up crashing the server on a racy bootup. (LP: #1792932) -- Timo Aaltonen Mon, 21 Oct 2019 17:26:17 +0300 ** Changed in: xorg-server (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1792932 Title: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. Status in X.Org X server: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Confirmed Status in xorg-server source package in Bionic: Fix Released Status in xorg-server source package in Cosmic: Fix Released Bug description: https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280 https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80 --- Test Case: Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box Actual Result Black screen or dropped to the login screen if the user skips ubiquity-dm Workaround: Add nomodeset on the kernel command line or from the boot menu, press F6 then select nomodeset Possibly a duplicate of bug 1432137 Fix: Backport a patch from 1.20.2 Regression potential: None really, we've had this xserver version since 18.10 and in the HWE backport, this patch backport is for 18.04 stock xserver but should work the same. It just skips initializing glamor if the system is using software fallback. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AssertionMessage: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. CasperVersion: 1.395 CompositorRunning: None Date: Mon Sep 17 12:42:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916) 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 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92 __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101 dixRegisterPrivateKey () Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel
Re: [Desktop-packages] [Bug 1849859] Re: smb printing fails
This workaround don't work for my. The /etc/cups/printers.conf file is erased and automoatically rewiriter when the computer is initiated anf I find in this file the line "AuthInfoRequired none" instead of "AuthInfoRequired username,password" after I edited the file. Greetings El lun., 17 feb. 2020 a las 9:35, Diego (<1849...@bugs.launchpad.net>) escribió: > Thank you...It works > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1853743). > https://bugs.launchpad.net/bugs/1849859 > > Title: > smb printing fails > > Status in cups package in Ubuntu: > Confirmed > Status in samba package in Ubuntu: > Confirmed > Status in system-config-printer package in Ubuntu: > Confirmed > > Bug description: > when I connect to smb server (nas) permanently appears > > "Error while getting peer-to-peer dbus connection: Operation was > cancelled" > > The printer at this NAS doesn't work too. > > "held for authentication KeyError: 'auth-info-required'" > > The same printer at usb port works fine. > > Ubuntu development version 20.04 > system-config-printer version 1.5.11-4ubuntu1 > smbclient version 2:4.10.7+dfsg-0ubuntu3 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792932] Update Released
The verification of the Stable Release Update for xorg-server has completed successfully and the package is now being 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 xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1792932 Title: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. Status in X.Org X server: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Xenial: Confirmed Status in xorg-server source package in Bionic: Fix Released Status in xorg-server source package in Cosmic: Fix Released Bug description: https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280 https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80 --- Test Case: Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box Actual Result Black screen or dropped to the login screen if the user skips ubiquity-dm Workaround: Add nomodeset on the kernel command line or from the boot menu, press F6 then select nomodeset Possibly a duplicate of bug 1432137 Fix: Backport a patch from 1.20.2 Regression potential: None really, we've had this xserver version since 18.10 and in the HWE backport, this patch backport is for 18.04 stock xserver but should work the same. It just skips initializing glamor if the system is using software fallback. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AssertionMessage: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. CasperVersion: 1.395 CompositorRunning: None Date: Mon Sep 17 12:42:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916) 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 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92 __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101 dixRegisterPrivateKey () Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 versio
[Desktop-packages] [Bug 1862910] Re: gnome-shell leaking memory when a customized AppImageLauncher is running
I have opened a new issue on AppImageLauncher. https://github.com/TheAssassin/AppImageLauncher/issues/301 ** Bug watch added: github.com/TheAssassin/AppImageLauncher/issues #301 https://github.com/TheAssassin/AppImageLauncher/issues/301 -- 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/1862910 Title: gnome-shell leaking memory when a customized AppImageLauncher is running Status in gnome-shell package in Ubuntu: New Bug description: Edited description: To replicate the problem (on Ubuntu 19.10 running Ubuntu Gnome) 1. Install AppImageLauncher from https://github.com/TheAssassin/AppImageLauncher/releases by downloading version 2.1.0 deb file (appimagelauncher_2.1.0-travis897.d1be7e7.bionic_amd64.deb) and install it. If necessary run sudo apt install -f to fix missing dependencies. 2. Run it and change the appimage destination location to ~/apps/appimages. It is necessary to change it away from the default setting in order for the problem to appear, though probably the actual destination is not important). Ensure that Auto start auto- integration daemon is selected. 3. Download an appimage (I downloaded Cura 4.4.1 from https://github.com/Ultimaker/Cura/releases/tag/4.4.1) I don't know whether any appimage would do, probably it would. In fact I don't know whether this step and the next need to be done at all. 4. Open it with appimagelauncher (this can be done by double clicking it in nautilus) and tell it to move it and run the application. Then close the application. 5. It may be necessary to reboot at this point I don't know. 6. Logon using Ubuntu (Gnome) and watch the memory usage of gnome- shell. It may take a few minutes to get going but then the memory used will start increasing at several MB/minute. There is an issue open against appimage launcher which is likely the same problem. https://github.com/TheAssassin/AppImageLauncher/issues/294 Original description: On one of my machines which has been upgraded over several years and is now running 19.10 just one of the configured users appears to be seeing a dramatic memory leak in gnome-shell, even when nothing is happening on the UI. Immediately after logging on, using the Ubuntu selection from the logon screen, gnome shell shows as using about 134MB. From there it climbs at about 300MB per hour and after a few hours the machine grinds to a crawl, not surprisingly. This happens even if the user logs on and then the machine is left completely alone. Logout and back in frees all the memory. A test user I have configured sees no such problem. I have uninstalled all extensions apart from the system ones, disabled all the system ones and reset all the gnome settings using dconf reset -f /org/gnome/ to no avail. Also I have removed ~/.local/share/gnome-shell and allowed it to recreate it. Also I have removed .compiz, .config/dconf/user, .gconf, .gnome, .gnome2. I can't see anything obvious in the log. It must be something in my settings that is triggering it as the other user does not see it, but I have run out of ideas on what to try. See also bug #1856516 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 08:54:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2014-10-21 (1939 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141017) RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2020-01-27 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1862910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1710060] Re: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset
This is also an issue with Kubuntu 19.10 eoan 5.3.0-40-generic and pulseaudio 13.0 I use this headset interchangeably with Windows and it's not an issue there. I have noticed that using the bundle Jabra link 370 makes the headset work perfectly, it's just an issue when using it as USB headphone. Attached is the pulseaudio output from pacmd list-sinks ** Attachment added: "Output of pacmd list-sinks" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/+attachment/5329009/+files/pacmd%20list-sinks.txt -- 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/1710060 Title: Sound Chipmunks on playback with Jabra Evolve 65 UC Headset Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio package in Fedora: Confirmed Bug description: Whenever I choose the Jabra Evolve 65 UC Headset as the playback device, there are sound chipmunks. The same was the case with Jabra Motion Headset as well. But those two headsets worked perfectly in Windows, Mac OS and Android. There was a workaround mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1282285 by editing the contents of /etc/pulseaudio/daemon.conf : Changing ;default-sample-rate=44100 to default-sample-rate=48000 and then running pulseaudio -k made the sound on Jabra good (no more chipmunks). Also, when I opened the Sound Settings with the changes in daemon.conf in place, there seems to be some distortions in headset sound, which goes away few seconds after I close the sound settings window. This problem should be fixed, as many new Linux users will find it difficult to edit files requiring root access, and those who do not use command line won't be okay with it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76 Uname: Linux 4.4.0-89-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0p: itachi10880 F...m pulseaudio /dev/snd/controlC2: itachi10880 F pulseaudio /dev/snd/controlC1: itachi10880 F pulseaudio /dev/snd/controlC0: itachi10880 F pulseaudio CurrentDesktop: Unity Date: Thu Aug 10 21:11:18 2017 InstallationDate: Installed on 2016-08-27 (349 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-08-10T21:07:55.637386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1710060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863614] Re: file-roller crashed with SIGSEGV in _gdk_window_has_impl()
The file-roller has just received an update, but the message in the image below continues. [img]https://i.imgur.com/KdfrpHE.gif[/img] sudo apt dist-upgrade Lendo listas de pacotes... Pronto Construindo árvore de dependências Lendo informação de estado... Pronto Calculando atualização... Pronto Os pacotes a seguir serão atualizados: file-roller python-six python3-six snapd 4 pacotes atualizados, 0 pacotes novos instalados, 0 a serem removidos e 0 não atualizados. É preciso baixar 21,1 MB de arquivos. Depois desta operação, 11,3 MB adicionais de espaço em disco serão usados. Você quer continuar? [S/n] s Obter:1 http://archive.ubuntu.com/ubuntu focal/main amd64 python3-six all 1.14.0-2 [12,1 kB] Obter:2 http://archive.ubuntu.com/ubuntu focal/main amd64 file-roller amd64 3.35.91-1 [253 kB] Obter:3 http://archive.ubuntu.com/ubuntu focal/universe amd64 python-six all 1.14.0-2 [12,0 kB] Obter:4 http://archive.ubuntu.com/ubuntu focal/main amd64 snapd amd64 2.43.3+git1.8109f8 [20,8 MB] Baixados 21,1 MB em 40s (524 kB/s) (Lendo banco de dados ... 224689 ficheiros e directórios actualmente instalados. ) A preparar para desempacotar .../python3-six_1.14.0-2_all.deb ... A descompactar python3-six (1.14.0-2) sobre (1.13.0-1build1) ... A preparar para desempacotar .../file-roller_3.35.91-1_amd64.deb ... A descompactar file-roller (3.35.91-1) sobre (3.35.90-1) ... A preparar para desempacotar .../python-six_1.14.0-2_all.deb ... A descompactar python-six (1.14.0-2) sobre (1.13.0-1build1) ... A preparar para desempacotar .../snapd_2.43.3+git1.8109f8_amd64.deb ... A descompactar snapd (2.43.3+git1.8109f8) sobre (2.42.1+20.04) ... Configurando snapd (2.43.3+git1.8109f8) ... Instalando nova versão do arquivo de configuração /etc/apparmor.d/usr.lib.snapd. snap-confine.real ... snapd.failure.service is a disabled or a static unit, not starting it. snapd.snap-repair.service is a disabled or a static unit, not starting it. Configurando file-roller (3.35.91-1) ... Configurando python-six (1.14.0-2) ... Configurando python3-six (1.14.0-2) ... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering= 1) isn't supported in binary mode, the default buffer size will be used self.stdin = io.open(p2cwrite, 'wb', bufsize) A processar 'triggers' para desktop-file-utils (0.24-1ubuntu1) ... A processar 'triggers' para mime-support (3.64ubuntu1) ... A processar 'triggers' para hicolor-icon-theme (0.17-2) ... A processar 'triggers' para gnome-menus (3.32.0-1ubuntu1) ... A processar 'triggers' para libglib2.0-0:amd64 (2.63.3-3) ... A processar 'triggers' para man-db (2.9.0-2) ... A processar 'triggers' para bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1863614 Title: file-roller crashed with SIGSEGV in _gdk_window_has_impl() Status in file-roller package in Ubuntu: Incomplete Bug description: https://bugs.launchpad.net/ubuntu/+source/file-roller/+filebug/29ea5ed0-5189-11ea-b34a-002481e7f48a?field.title=file-roller+crashed+with+SIGSEGV+in+gdk_x11_window_get_xid%28%29 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: file-roller 3.35.90-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 14 14:06:14 2020 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2019-04-28 (295 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: file-roller --extract-here --notify file:///home/username/Downloads/youtube-dlg_0.4-1_webupd8_disco0_all.deb SegvAnalysis: Segfault happened at: 0x7f6b651f2a96:cmp%rdi,0xf8(%rdi) PC (0x7f6b651f2a96) ok source "%rdi" ok destination "0xf8(%rdi)" (0x00f8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_window_get_xid () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_show_uri_on_window () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () Title: file-roller crashed with SIGSEGV in gdk_x11_window_get_xid() UpgradeStatus: Upgraded to focal on 2020-02-04 (13 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1863614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More hel
[Desktop-packages] [Bug 1859730] Re: [comet lake] Gnome freezes, icons missing, graphics corruption
Hi everyone, I finally managed to make dell's technical service change my micron hard drive to a different one, obviously the computer didn't fail anymore. He never got stuck again. Also install ubuntu 18.04 offered in dell downloads, but I will return to ubuntu 20. Thank you all for your help. -- 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/1859730 Title: [comet lake] Gnome freezes, icons missing, graphics corruption Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: ack please.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.4.11-050411-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompositorRunning: None Date: Tue Jan 14 20:17:26 2020 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8286, 4.15.0-1042-oem, x86_64: installed backport-iwlwifi, 8286, 4.15.0-1066-oem, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2020-01-13 (1 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 7390 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_CL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.11-050411-generic root=UUID=8fd25548-00af-4395-92f0-5d7d27a54deb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859730/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863614] Re: file-roller crashed with SIGSEGV in _gdk_window_has_impl()
How can I remember if there is no time and date stamp when the error occurred, let alone what unzipped application was used? I only have the report sent via ubuntu-bug. Note: Ubuntu itself generated and identified the error sent in the usr / bin folder .. crash It may have been in any update via update or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1863614 Title: file-roller crashed with SIGSEGV in _gdk_window_has_impl() Status in file-roller package in Ubuntu: Incomplete Bug description: https://bugs.launchpad.net/ubuntu/+source/file-roller/+filebug/29ea5ed0-5189-11ea-b34a-002481e7f48a?field.title=file-roller+crashed+with+SIGSEGV+in+gdk_x11_window_get_xid%28%29 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: file-roller 3.35.90-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 14 14:06:14 2020 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2019-04-28 (295 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: file-roller --extract-here --notify file:///home/username/Downloads/youtube-dlg_0.4-1_webupd8_disco0_all.deb SegvAnalysis: Segfault happened at: 0x7f6b651f2a96:cmp%rdi,0xf8(%rdi) PC (0x7f6b651f2a96) ok source "%rdi" ok destination "0xf8(%rdi)" (0x00f8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_window_get_xid () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_show_uri_on_window () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () Title: file-roller crashed with SIGSEGV in gdk_x11_window_get_xid() UpgradeStatus: Upgraded to focal on 2020-02-04 (13 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1863614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863614] Re: file-roller crashed with SIGSEGV in _gdk_window_has_impl()
the gnome-software problem on the video is different from the segfault, there is no app log though. What did you do at the time you got the error? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1863614 Title: file-roller crashed with SIGSEGV in _gdk_window_has_impl() Status in file-roller package in Ubuntu: Incomplete Bug description: https://bugs.launchpad.net/ubuntu/+source/file-roller/+filebug/29ea5ed0-5189-11ea-b34a-002481e7f48a?field.title=file-roller+crashed+with+SIGSEGV+in+gdk_x11_window_get_xid%28%29 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: file-roller 3.35.90-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 14 14:06:14 2020 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2019-04-28 (295 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: file-roller --extract-here --notify file:///home/username/Downloads/youtube-dlg_0.4-1_webupd8_disco0_all.deb SegvAnalysis: Segfault happened at: 0x7f6b651f2a96:cmp%rdi,0xf8(%rdi) PC (0x7f6b651f2a96) ok source "%rdi" ok destination "0xf8(%rdi)" (0x00f8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_window_get_xid () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_show_uri_on_window () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () Title: file-roller crashed with SIGSEGV in gdk_x11_window_get_xid() UpgradeStatus: Upgraded to focal on 2020-02-04 (13 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1863614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1285444] Re: Login Successful, Desktop Never Loads
Are you sure it relates to the bug ? If your problem is related to gnome-shell it is a different bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1285444 Title: Login Successful, Desktop Never Loads Status in at-spi2-core package in Ubuntu: Triaged Bug description: Here is what I encounter 1. Boot computer, boot proceeds normally 2. Reach standard Ubuntu login screen, nothing seems to be amiss 3. Enter user name and password 4. Login disappears, just see the pink "Ubuntu 14.04" background The desktop never loads, not even after ~30 minutes. The launcher never appears, and the Desktop background never changes to the user- configured background. Other features: * Cursor works fine, it can be moved around the screen * No error messages pop up * ALT+F1 etc. can be used to switch to different TTYs; all files on the system appear to be intact * Print screen button works (I will upload a screen shot when I get a chance to copy it onto a USB drive) * Hitting power button pops up a window prompting the user to decide whether to shut down * CTRL+ALT+DELETE prompts the user to log out * Desktop does not load on any user accounts, including the guest account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1285444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849774] Re: [snap] mailto: links don't work in chromium
It appears xdg-open isn't always able to handle mailto: hyperlinks (see https://bugs.chromium.org/p/chromium/issues/detail?id=61942). I filed bug #1863625 to request an xdg-email wrapper in snapd. -- 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/1849774 Title: [snap] mailto: links don't work in chromium Status in chromium-browser package in Ubuntu: Fix Released Bug description: href="mailto:xyz"; links don't work in the chromium snap package anymore to open an external email client. It used to work fine in the non-snap Chromium deb package, before Ubuntu 19.10. In settings, if enabling "Allow sites to ask to become default handlers for protocols (recommended)", it is possible to set Gmail to be the default mailto handler, which works. But there seems to be no way to make the chromium snap open Evolution, Thunderbird or other external programs. Mailtos work fine in Firefox and chromium-based Brave browser (which pops up an xdg-open confirmation dialog box when a mailto link is clicked). Chromium Version 77.0.3865.120 (Official Build) snap (64-bit) Ubuntu Budgie 19.10, gnome 3.34.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863614] Re: file-roller crashed with SIGSEGV in _gdk_window_has_impl()
I can only reproduce one of the problems through the gif image below: If I know or there is a command that displays ONE log of the file-roller, I will execute it, if it is available. [img]https://i.imgur.com/KdfrpHE.gif[/img] summary:- file-roller crashed with SIGSEGV in gdk_x11_window_get_xid() + file-roller crashed with SIGSEGV in _gdk_window_has_impl() As reported, it crashes (!) When he does that, I have no idea. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1863614 Title: file-roller crashed with SIGSEGV in _gdk_window_has_impl() Status in file-roller package in Ubuntu: Incomplete Bug description: https://bugs.launchpad.net/ubuntu/+source/file-roller/+filebug/29ea5ed0-5189-11ea-b34a-002481e7f48a?field.title=file-roller+crashed+with+SIGSEGV+in+gdk_x11_window_get_xid%28%29 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: file-roller 3.35.90-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 14 14:06:14 2020 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2019-04-28 (295 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: file-roller --extract-here --notify file:///home/username/Downloads/youtube-dlg_0.4-1_webupd8_disco0_all.deb SegvAnalysis: Segfault happened at: 0x7f6b651f2a96:cmp%rdi,0xf8(%rdi) PC (0x7f6b651f2a96) ok source "%rdi" ok destination "0xf8(%rdi)" (0x00f8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_window_get_xid () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_show_uri_on_window () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () Title: file-roller crashed with SIGSEGV in gdk_x11_window_get_xid() UpgradeStatus: Upgraded to focal on 2020-02-04 (13 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1863614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862650] Re: Warnings about /usr/lib/tmpfiles.d/speech-dispatcher.conf on systemd upgrade
Just performed a 19.10 update and now also reports: Setting up systemd (242-7ubuntu3.7) ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1862650 Title: Warnings about /usr/lib/tmpfiles.d/speech-dispatcher.conf on systemd upgrade Status in speech-dispatcher package in Ubuntu: Confirmed Bug description: When upgrading to the latest systemd SRU: Setting up systemd (242-7ubuntu3.6) ... [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please upda te the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cach e; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-disp atcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speec h-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; ple ase update the tmpfiles.d/ drop-in file accordingly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: speech-dispatcher 0.9.1-2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: i3 Date: Mon Feb 10 10:50:26 2020 InstallationDate: Installed on 2019-08-13 (181 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: speech-dispatcher UpgradeStatus: Upgraded to eoan on 2020-01-10 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1862650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 241604] Re: Maximum zoom in Evince is 400%
** Tags removed: yakkety ** Tags added: eoan focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/241604 Title: Maximum zoom in Evince is 400% Status in Evince: Expired Status in evince package in Ubuntu: Triaged Bug description: Binary package hint: evince Evince zoom max is 400%, and in some pdf this is too small. I have to use xpdf to open some file in a usable way.. you should remove this limit ProblemType: Bug Architecture: i386 Date: Fri Jun 20 13:26:32 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evince NonfreeKernelModules: nvidia Package: evince 2.22.2-0ubuntu1 PackageArchitecture: i386 ProcEnviron: PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: evince Uname: Linux 2.6.24-19-generic i686 WORKAROUND: `gsettings set org.gnome.Evince page-cache-size 2014` To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/241604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862650] Re: Warnings about /usr/lib/tmpfiles.d/speech-dispatcher.conf on systemd upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: speech-dispatcher (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1862650 Title: Warnings about /usr/lib/tmpfiles.d/speech-dispatcher.conf on systemd upgrade Status in speech-dispatcher package in Ubuntu: Confirmed Bug description: When upgrading to the latest systemd SRU: Setting up systemd (242-7ubuntu3.6) ... [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please upda te the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cach e; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-disp atcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speec h-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; ple ase update the tmpfiles.d/ drop-in file accordingly. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: speech-dispatcher 0.9.1-2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: i3 Date: Mon Feb 10 10:50:26 2020 InstallationDate: Installed on 2019-08-13 (181 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: speech-dispatcher UpgradeStatus: Upgraded to eoan on 2020-01-10 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1862650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863614] Re: file-roller crashed with SIGSEGV in _gdk_window_has_impl()
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: file-roller (Ubuntu) Status: New => Incomplete ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1863614 Title: file-roller crashed with SIGSEGV in _gdk_window_has_impl() Status in file-roller package in Ubuntu: Incomplete Bug description: https://bugs.launchpad.net/ubuntu/+source/file-roller/+filebug/29ea5ed0-5189-11ea-b34a-002481e7f48a?field.title=file-roller+crashed+with+SIGSEGV+in+gdk_x11_window_get_xid%28%29 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: file-roller 3.35.90-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 14 14:06:14 2020 ExecutablePath: /usr/bin/file-roller InstallationDate: Installed on 2019-04-28 (295 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcCmdline: file-roller --extract-here --notify file:///home/username/Downloads/youtube-dlg_0.4-1_webupd8_disco0_all.deb SegvAnalysis: Segfault happened at: 0x7f6b651f2a96:cmp%rdi,0xf8(%rdi) PC (0x7f6b651f2a96) ok source "%rdi" ok destination "0xf8(%rdi)" (0x00f8) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: file-roller StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_x11_window_get_xid () from /lib/x86_64-linux-gnu/libgdk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_show_uri_on_window () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () Title: file-roller crashed with SIGSEGV in gdk_x11_window_get_xid() UpgradeStatus: Upgraded to focal on 2020-02-04 (13 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1863614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863621] [NEW] Add sysfs attribute to show remapped NVMe
Public bug reported: [Impact] Intel Rapid Storage Technology hides NVMe behind AHCI controller, to provide firmware base "fusion drive", like combining with Intel Optane. There's a driver to support this but upstream doesn't like it for reasons like NVMe quirks can't be applied when NVMe are behind AHCI controller. So we need to devise a mechanism to ask users to change BIOS storage settings. This patch only provides a new attribute to let userspace like distro installer know NVMe is remapped behind AHCI. [Fix] Add a new attribute to show that how many NVMes are remapped. [Test] After applying the patch, there's a new "remapped_nvme" under the AHCI PCI device sysfs. If there's no remapped NVMe: $ cat remapped_nvme 0 If there are two remapped NVMes: $ cat remapped_nvme 2 [Regression Potential] Low. It adds a new read only sysfs attribute, no actual functional change to the AHCI driver. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1863621 Title: Add sysfs attribute to show remapped NVMe Status in linux package in Ubuntu: New Status in linux source package in Focal: New Bug description: [Impact] Intel Rapid Storage Technology hides NVMe behind AHCI controller, to provide firmware base "fusion drive", like combining with Intel Optane. There's a driver to support this but upstream doesn't like it for reasons like NVMe quirks can't be applied when NVMe are behind AHCI controller. So we need to devise a mechanism to ask users to change BIOS storage settings. This patch only provides a new attribute to let userspace like distro installer know NVMe is remapped behind AHCI. [Fix] Add a new attribute to show that how many NVMes are remapped. [Test] After applying the patch, there's a new "remapped_nvme" under the AHCI PCI device sysfs. If there's no remapped NVMe: $ cat remapped_nvme 0 If there are two remapped NVMes: $ cat remapped_nvme 2 [Regression Potential] Low. It adds a new read only sysfs attribute, no actual functional change to the AHCI driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863157] Re: Petition to bring back file name copy/paste functionality in GTK file chooser
thanks! ** Changed in: gtk+3.0 (Ubuntu) Status: New => Triaged ** Also affects: gtk via https://gitlab.gnome.org/GNOME/gtk/issues/2443 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1863157 Title: Petition to bring back file name copy/paste functionality in GTK file chooser Status in GTK+: New Status in gtk+3.0 package in Ubuntu: Triaged Bug description: For a very long time, I've never/rarely needed to hand-type file paths/names - it is extremely slow, error-proning and requiring a lot more work (reading/clicking/moving cursors) to do this simple task. Instead, I use tabs in a terminal to navigate, pwd to print, and copy/paste to another file browser or window to use the full path. In many file browsers (like Thunar), I could also single click on the file, and directly paste it to the address bar and it directly gives the full file name. But this becomes increasingly difficult to do on the GTK file chooser rolled out sometimes ago. The file chooser window first removed the file path address bar, but at least there was a button I can click to show it to copy/paste. Then, even that button disappeared - after many frustrating hours, the only way to show the address bar is "Ctrl+L", after reading many similarly frustrated posts https://www.google.com/search?q=unable+to+type+path+dialog+ubuntu https://www.google.com/search?q=unable+to+type+path+dialog+site%3Aaskubuntu.com&oq=unable+to+type+path+dialog+site https://www.google.com/search?q=can+not+type+path+in+file+selector+linux+site:askubuntu.com From the long lists of complains that one can find online (I could easily find more), I think this just prove that removing/hiding the address bar is very counter intuitive and should be reverted. I see where this came from - to mimic Mac OS, like most GNOME style/appearance was trying to achieve, and this setting maybe cleaner and easier to attract less experienced users, but for people use Linux for work day-in-and-day-out, this is highly annoying and counter productive. Here I would like to petition to revert the change and bring back the address bar in the file chooser dialog (which is shared among not just GNOME, but other GTK based desktops, such as xfce), or at least bring back the button option. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1863157/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 241604] Re: Maximum zoom in Evince is 400%
** Description changed: Binary package hint: evince Evince zoom max is 400%, and in some pdf this is too small. I have to use xpdf to open some file in a usable way.. you should remove this limit ProblemType: Bug Architecture: i386 Date: Fri Jun 20 13:26:32 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evince NonfreeKernelModules: nvidia Package: evince 2.22.2-0ubuntu1 PackageArchitecture: i386 ProcEnviron: - PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games - LANG=it_IT.UTF-8 - SHELL=/bin/bash + PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games + LANG=it_IT.UTF-8 + SHELL=/bin/bash SourcePackage: evince Uname: Linux 2.6.24-19-generic i686 + + + WORKAROUND: + `gsettings set org.gnome.Evince page-cache-size 2014` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/241604 Title: Maximum zoom in Evince is 400% Status in Evince: Expired Status in evince package in Ubuntu: Triaged Bug description: Binary package hint: evince Evince zoom max is 400%, and in some pdf this is too small. I have to use xpdf to open some file in a usable way.. you should remove this limit ProblemType: Bug Architecture: i386 Date: Fri Jun 20 13:26:32 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evince NonfreeKernelModules: nvidia Package: evince 2.22.2-0ubuntu1 PackageArchitecture: i386 ProcEnviron: PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: evince Uname: Linux 2.6.24-19-generic i686 WORKAROUND: `gsettings set org.gnome.Evince page-cache-size 2014` To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/241604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856861] Re: Firefox 73 require C++17, not available in xenial
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6796 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6798 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6800 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-6801 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1856861 Title: Firefox 73 require C++17, not available in xenial Status in firefox package in Ubuntu: In Progress Bug description: Firefox trunk, to become version 73.0 in February 2020, has bumped its C++ requirement to C++17 (https://bugzilla.mozilla.org/show_bug.cgi?id=1560664). This requires a more recent version (>= 7) of libstdc++6 than what is currently available in xenial (5.4.0-6ubuntu1~16.04.12). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1856861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862767] Re: gnome-control-center crashes when try to open it
Thanks, in fact looking at the error it's similar to https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 Did you try to replace network-manager by another component or having it not working? What's the output of $ systemctl status NetworkManager ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #342 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342 -- 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/1862767 Title: gnome-control-center crashes when try to open it Status in gnome-control-center package in Ubuntu: Incomplete Bug description: gnome-control center crashes when trying to open it. Tested as following $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) When trying to open it through the graphical interface it dies silently. A message of error would help too. Additional information: $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 09:24:49 2020 InstallationDate: Installed on 2018-05-07 (644 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863608] [NEW] version 80 does not start using remote display (X11)
Public bug reported: chromium-browser version 80.0.3987.87-0ubuntu0.16.04.1_amd64 does not work when using remote display; the browser window is a solid pink area without any menu (see picture). Same with the (existing?) command line option "--disable-gpu" Downgrading to chromium-browser_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb chromium-browser-l10n_79.0.3945.130-0ubuntu0.16.04.1_all.deb chromium-codecs-ffmpeg-extra_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb resolve the issue. Description: Ubuntu 16.04.6 LTS All packages are up to date on 2020-02-17 on xenial, xenial-updates and xenial-security ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Picture of the pink window" https://bugs.launchpad.net/bugs/1863608/+attachment/5328938/+files/20200217_110715_t1.jpg -- 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/1863608 Title: version 80 does not start using remote display (X11) Status in chromium-browser package in Ubuntu: New Bug description: chromium-browser version 80.0.3987.87-0ubuntu0.16.04.1_amd64 does not work when using remote display; the browser window is a solid pink area without any menu (see picture). Same with the (existing?) command line option "--disable-gpu" Downgrading to chromium-browser_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb chromium-browser-l10n_79.0.3945.130-0ubuntu0.16.04.1_all.deb chromium-codecs-ffmpeg-extra_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb resolve the issue. Description: Ubuntu 16.04.6 LTS All packages are up to date on 2020-02-17 on xenial, xenial-updates and xenial-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862767] Re: gnome-control-center crashes when try to open it
Sure. The output is $ dpkg -l | grep gnome-control-center ii gnome-control-center 1:3.34.1-1ubuntu2 amd64utilities to configure the GNOME desktop ii gnome-control-center-data 1:3.34.1-1ubuntu2 all configuration applets for GNOME - data files ii gnome-control-center-faces1:3.34.1-1ubuntu2 all utilities to configure the GNOME desktop - faces images $ which gnome-control-center /usr/bin/gnome-control-center $ ldd -r $(which gnome-control-center) linux-vdso.so.1 (0x7ffd25b1f000) libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x7ff46de64000) libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7ff46de07000) libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7ff46dcdf000) libgtk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 (0x7ff46d5cc000) libgdk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 (0x7ff46d4c8000) libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x7ff46d4b7000) libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x7ff46d469000) libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x7ff46d43f000) libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x7ff46d31f000) libgdk_pixbuf-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7ff46d2f7000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7ff46d1a8000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7ff46d06a000) libcheese.so.8 => /usr/lib/x86_64-linux-gnu/libcheese.so.8 (0x7ff46d054000) libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x7ff46d042000) libcheese-gtk.so.25 => /usr/lib/x86_64-linux-gnu/libcheese-gtk.so.25 (0x7ff46d031000) libwacom.so.2 => /usr/lib/x86_64-linux-gnu/libwacom.so.2 (0x7ff46d023000) libsnapd-glib.so.1 => /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1 (0x7ff46cfd1000) libsoup-2.4.so.1 => /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1 (0x7ff46cf36000) libgnome-desktop-3.so.18 => /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.18 (0x7ff46cef1000) libgoa-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libgoa-1.0.so.0 (0x7ff46cea2000) libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x7ff46cce2000) libcolord.so.2 => /usr/lib/x86_64-linux-gnu/libcolord.so.2 (0x7ff46cc91000) libcolord-gtk.so.1 => /usr/lib/x86_64-linux-gnu/libcolord-gtk.so.1 (0x7ff46cc87000) libpolkit-gobject-1.so.0 => /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 (0x7ff46cc67000) libupower-glib.so.3 => /usr/lib/x86_64-linux-gnu/libupower-glib.so.3 (0x7ff46cc3a000) libudisks2.so.0 => /usr/lib/x86_64-linux-gnu/libudisks2.so.0 (0x7ff46cbc) libgtop-2.0.so.11 => /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11 (0x7ff46cba4000) libgudev-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0 (0x7ff46cb97000) libgoa-backend-1.0.so.1 => /usr/lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 (0x7ff46cb34000) libnm.so.0 => /usr/lib/x86_64-linux-gnu/libnm.so.0 (0x7ff46c9e4000) libnma.so.0 => /usr/lib/x86_64-linux-gnu/libnma.so.0 (0x7ff46c982000) libmm-glib.so.0 => /usr/lib/x86_64-linux-gnu/libmm-glib.so.0 (0x7ff46c8a6000) libgnome-bluetooth.so.13 => /usr/lib/x86_64-linux-gnu/libgnome-bluetooth.so.13 (0x7ff46c86) libcups.so.2 => /usr/lib/x86_64-linux-gnu/libcups.so.2 (0x7ff46c7cf000) libsmbclient.so.0 => /usr/lib/x86_64-linux-gnu/libsmbclient.so.0 (0x7ff46c7a5000) libwhoopsie-preferences.so.0 => /usr/lib/x86_64-linux-gnu/libwhoopsie-preferences.so.0 (0x7ff46c799000) libaccountsservice.so.0 => /usr/lib/x86_64-linux-gnu/libaccountsservice.so.0 (0x7ff46c748000) libibus-1.0.so.5 => /usr/lib/x86_64-linux-gnu/libibus-1.0.so.5 (0x7ff46c6cf000) libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x7ff46c689000) libsecret-1.so.0 => /usr/lib/x86_64-linux-gnu/libsecret-1.so.0 (0x7ff46c634000) libpulse.so.0 => /usr/lib/x86_64-linux-gnu/libpulse.so.0 (0x7ff46c5df000) libpulse-mainloop-glib.so.0 => /usr/lib/x86_64-linux-gnu/libpulse-mainloop-glib.so.0 (0x7ff46c5d9000) libgsound.so.0 => /usr/lib/x86_64-linux-gnu/libgsound.so.0 (0x7ff46c5d) libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x7ff46c4f3000) libpwquality.so.1 => /usr/lib/x86_64-linux-gnu/libpwquality.so.1 (0x7ff46c4ea000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7ff46c4c7000) libc.so.6 => /lib/x8
[Desktop-packages] [Bug 1863603] [NEW] Screen is scrambled/distored and flickers
Public bug reported: The screen is distorted/scrambled every now and then. That is, it's like a few lines of pixels are repeated (so it's a normally a blur). The screen also flickers at times. This happens a few times a few. I've noticed that if I close the lid and let the screen dim/blank/suspend then normally is goes back to normal when it wakes up. To my knowledge his happens irrespective of what programs I use at the time. Dell XPS 13 (7390). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Feb 17 12:32:42 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-29-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-12-24 (54 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=c325f61e-5f45-4a7a-ada7-71dd6d7d4b42 ro resume=UUID=c325f61e-5f45-4a7a-ada7-71dd6d7d4b42 resume_offset=67694592 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd10/03/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption eoan ubuntu ** Attachment added: "Example of bug." https://bugs.launchpad.net/bugs/1863603/+attachment/5328923/+files/IMG_0260.JPEG -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1863603 Title: Screen is scrambled/distored and flickers Status in xorg package in Ubuntu: New Bug description: The screen is distorted/scrambled every now and then. That is, it's like a few lines of pixels are repeated (so it's a normally a blur). The screen also flickers at times. This happens a few times a few. I've noticed that if I close the lid and let the screen dim/blank/suspend then normally is goes back to normal when it wakes up. To my knowledge his happens irrespective of what programs I use at the time. Dell XPS 13 (7390). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Feb 17 12:32:42 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-26-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-29-generic, x86_64: installed GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-12-24 (54 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=UUID=c325f61e-5f45-4a7a-ada7-71dd6d7d4b42 ro resume=UUID=c325f61e-5f45-4a7a-ada7-71dd6d7d4b42 resume_offset=67694592 quiet splash mem_sleep_default=deep vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.boa
[Desktop-packages] [Bug 1857703] Re: Dell Inspiron 15 3000 Touchpad (Synaptics TM3096-006) Stopped working with kernel 4.15.0-72-generic (Ubuntu 18.04.3 LTS))
it sarted working again as usueal with 4.15.0-76 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1857703 Title: Dell Inspiron 15 3000 Touchpad (Synaptics TM3096-006) Stopped working with kernel 4.15.0-72-generic (Ubuntu 18.04.3 LTS)) Status in xserver-xorg-input-synaptics package in Ubuntu: New Bug description: So touchpad suddenly stopped working on this laptop i tried booting with GRUB_CMDLINE_LINUX_DEFAULT="i8042.reset quiet splash" and installing sudo apt install xserver-xorg-input-synaptics i think i also tried installing some touchpad software but that didnt help as well. tried booting the 4.15.0-70-generic kernel (only one available) - worked fawlessly.. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu InstallationDate: Installed on 2018-12-26 (368 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 15-3567 Package: xserver-xorg-input-synaptics 1.9.0-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-72-generic root=/dev/mapper/username--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/17/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.0 dmi.board.name: 033HWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.0:bd07/17/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn033HWX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1857703/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated
I tested the live session with today's daily build of Ubuntu MATE and can confirm that LANGUAGE is no longer set. Thus translated strings in universe packages are always displayed in the selected language. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated Status in lightdm package in Ubuntu: Fix Released Bug description: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1861481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1307648] Re: chromium-browser does not accept keyboard input with iBus
Re comments #41 and #42,the issue affecting the snapped version of Chromium in Ubuntu 20.04 is bug 1863255 -- 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/1307648 Title: chromium-browser does not accept keyboard input with iBus Status in chromium-browser package in Ubuntu: Incomplete Bug description: To reproduce install chromium 34 from proposed with pepperflash. And find a site that you input some text into like indeed.com or some others. Then you hit the keys on the keyboard but no text is seen onscreen. I expected the text to be entering into chroumium like it is on any other browser. And for the text to be entered into the browser and transfered ot the webpage I am submitting it to. Instead it did not show up and indeed.com thought I did not enter anything even though I pressed several keys on my keyboard. Description: Ubuntu 14.04 LTS Release: 14.04 chromium-browser: Installed: 34.0.1847.116-0ubuntu1~pkg1006 Candidate: 34.0.1847.116-0ubuntu1~pkg1006 Version table: *** 34.0.1847.116-0ubuntu1~pkg1006 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 33.0.1750.152-0ubuntu1~pkg995.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 34.0.1847.116-0ubuntu1~pkg1006 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Apr 14 11:15:07 2014 Desktop-Session: DESKTOP_SESSION = Lubuntu XDG_CONFIG_DIRS = /etc/xdg/lubuntu:/etc/xdg/xdg-Lubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /etc/xdg/lubuntu:/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg:/usr/share/Lubuntu:/usr/local/share/:/usr/share/ DetectedPlugins: DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sdc4 ext4 641G 61G 549G 10% /\nnone tmpfs 4.0K 0 4.0K 0% /sys/fs/cgroup\nudev devtmpfs 1.9G 4.0K 1.9G 1% /dev\ntmpfs tmpfs 386M 1.3M 385M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 1.9G 17M 1.9G 1% /run/shm\nnone tmpfs 100M 16K 100M 1% /run/user\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sdc4 41M 565K 41M2% /\nnone 483K 2 483K1% /sys/fs/cgroup\nudev 480K 612 479K1% /dev\ntmpfs 483K 643 482K1% /run\nnone 483K 5 483K1% /run/lock\nnone 483K19 483K1% /run/shm\nnone 483K13 483K1% /run/user\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2014-01-02 (102 days ago) InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha amd64 (20140101) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-04-14T10:56:12.681598 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1307648/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1307648] Re: chromium-browser does not accept keyboard input with iBus
I've just experienced the same bug this morning with snapped Chromium, fixed with `ibus exit`: $ snap info chromium name: chromium summary: Chromium web browser, open-source version of Chrome publisher: Canonical✓ store-url: https://snapcraft.io/chromium contact: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap license: unset description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium.chromedriver - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: latest/stable refresh-date: 5 days ago, at 14:13 GMT channels: stable:80.0.3987.100 2020-02-12 (1026) 160MB - candidate: 80.0.3987.100 2020-02-12 (1026) 160MB - beta: 80.0.3987.85 2020-02-04 (1014) 160MB - edge: 81.0.4044.17 2020-02-14 (1028) 161MB - installed: 80.0.3987.100(1026) 160MB - $ env | grep IM_ CLUTTER_IM_MODULE=ibus GTK_IM_MODULE=ibus IM_CONFIG_PHASE=1 QT4_IM_MODULE=ibus QT_IM_MODULE=ibus $ uname -a Linux morwanneg 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal -- 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/1307648 Title: chromium-browser does not accept keyboard input with iBus Status in chromium-browser package in Ubuntu: Incomplete Bug description: To reproduce install chromium 34 from proposed with pepperflash. And find a site that you input some text into like indeed.com or some others. Then you hit the keys on the keyboard but no text is seen onscreen. I expected the text to be entering into chroumium like it is on any other browser. And for the text to be entered into the browser and transfered ot the webpage I am submitting it to. Instead it did not show up and indeed.com thought I did not enter anything even though I pressed several keys on my keyboard. Description: Ubuntu 14.04 LTS Release: 14.04 chromium-browser: Installed: 34.0.1847.116-0ubuntu1~pkg1006 Candidate: 34.0.1847.116-0ubuntu1~pkg1006 Version table: *** 34.0.1847.116-0ubuntu1~pkg1006 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 33.0.1750.152-0ubuntu1~pkg995.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 34.0.1847.116-0ubuntu1~pkg1006 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Mon Apr 14 11:15:07 2014 Desktop-Session: DESKTOP_SESSION = Lubuntu XDG_CONFIG_DIRS = /etc/xdg/lubuntu:/etc/xdg/xdg-Lubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /etc/xdg/lubuntu:/usr/local/share:/usr/share:/usr/share/gdm:/var/lib/menu-xdg:/usr/share/Lubuntu:/usr/local/share/:/usr/share/ DetectedPlugins: DiskUsage: b'Filesystem Type Size Used Avail Use% Mounted on\n/dev/sdc4 ext4 641G 61G 549G 10% /\nnone tmpfs 4.0K 0 4.0K 0% /sys/fs/cgroup\nudev devtmpfs 1.9G 4.0K 1.9G 1% /dev\ntmpfs tmpfs 386M 1.3M 385M 1% /run\nnone tmpfs 5.0M 0 5.0M 0% /run/lock\nnone tmpfs 1.9G 17M 1.9G 1% /run/shm\nnone tmpfs 100M 16K 100M 1% /run/user\n' Inodes: b'Filesystem Inodes IUsed IFree IUse% Mounted on\n/dev/sdc4 41M 565K 41M2% /\nnone 483K 2 483K1% /sys/fs/cgroup\nudev 480K 612 479K1% /dev\ntmpfs 483K 643 482K1% /run\nnone 483K 5 483K1% /run/lock\nnone 483K19 483K1% /run/shm\nnone 483K13 483K1% /run/user\n' Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2014-01-02 (102 days ago) InstallationMedia: Lubuntu 14.04 "Trusty Tahr" - Alpha amd64 (20140101) SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'sensible-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/i
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
@Bill (franksmcb) (franksmcb) This is a bit broader. VirtualBox is still affected. I use 5.1 because of 25 VMs inside it. As I already wrote - see https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1796437/comments/16 : > Norbert (nrbrtx) wrote on 2020-01-16 > >Still reproducible on 20200115 and 20200116 builds. > >--- > >Reproducible method 1: > >1. boot installation media >2. select [o] Normal installation, [x] Download updates, [x] Install >third-party software >3. Wait installation to finish >4. Boot the installed system, wait for Snappy unpacking/initialization/seeding >(check from tty1 with `snap list`) >5. Login to desktop session >6. Get crash of whole Xorg after login when of Ubuntu MATE Welcome window is >starting to appear. > >Reproducible method 2: > >1. boot installation media >2. select [o] Normal installation, [ ] Download updates, [ ] Install >third-party software >3. Wait installation to finish >4. Boot the installed system, wait for Snappy unpacking/initialization/seeding >(check from tty1 with `snap list`) >5. Install Ubuntu restricted extras with `sudo apt-get install >ubuntu-restricted-extras` and reboot >6. Login to desktop session >7. Get crash of whole Xorg after login when of Ubuntu MATE Welcome window is >starting to appear. > >Guest settings: choosing video acceleration disabled or 3d video acceleration >does not change >behavior. Increasing VRAM from default 16 Mb to 128 Mb (max >for my machine) does not help either. >VirtualBox versions tested: > >* 5.1.38-dfsg-0ubuntu1.16.04.3 (from multiverse) - crash, >* 5.0.40 (from Oracle) - crash, >* 5.1.38 (from Oracle) - crash, >* 5.2.36 (from Oracle) - crash, >* 6.0.16 (from Oracle) - crash, >* 6.1.2 (from Oracle) - crash. > >--- > >Removing `ubuntu-mate-welcome` from autostart with `sudo rm >/etc/xdg/autostart/ubuntu-mate-welcome-autostart.desktop` fixes the login >issue. But direct launch of it with `ubuntu-mate-welcome` ends with another >crash. and https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1796437/comments/17 : > Norbert (nrbrtx) wrote on 2020-01-18 > >With virt-manager the crashes occur with Cirrus, QXL, VGA video drivers. >But does not occur with VMVGA video driver. >Possibly kernel (drm) issue. and https://bugs.launchpad.net/ubuntu/+source/xorg- server/+bug/1796437/comments/19 : > Norbert (nrbrtx) wrote on 2020-01-18 > >I found the real reason for the crashes. The problematic package is the >`gstreamer1.0-vaapi` (see >https://packages.ubuntu.com/focal/gstreamer1.0-vaapi). >It is a dependency of `ubuntu-restricted-addons` (see >https://packages.ubuntu.com/focal/ubuntu-restricted-addons). > >So ubuntu-mate-welcome and for example Cheese may be fixed by removing this >package with > >``` >sudo apt-get purge gstreamer1.0-vaapi >sudo apt-get autoremove --purge # to remove libgstreamer-plugins-bad1.0-0 (is >not a problem) >``` > >So please carefully analyze the crash dumps for errors in `gstreamer1.0-vaapi` >and fix this package. End of quotes. I would recommend to test any modern VirtualBox (according to https://www.virtualbox.org/wiki/Download_Old_Builds this means >= 5.2) with non-VMVGA video driver to reproduce the issue. And report here the results. -- 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/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in X.Org X server: New Status in gstreamer-vaapi package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Syst
[Desktop-packages] [Bug 1863400] Re: gnome-shell reports problem on boot
Complied with comment #6 and step 2 in comment #3. A web page is produced with all the bugs I have raised from this device, and yes the latest gnome one is there. But clicking on it takes me to webpage which says I have not got permission to see it and asks me to complete a form, which I have done. The form asks me for my email address etc and once completed it says they will be in touch. That was over 1 hour ago - not heard a thing. I do have the URL of the bug I could click on. Would that be secure to paste here? -- 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/1863400 Title: gnome-shell reports problem on boot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Problem reported at boot but does not seem to collect data and send, just does nothing. See attached screenshot of window. Still able to use laptop. This file exists in /var/crash -rw-r- 1 gdm whoopsie 21900809 Feb 14 22:01 _usr_bin_gnome-shell.121.crash The time of this file must have been at last shutdown which did take a little longer than usual. Description: Ubuntu 18.04.4 LTS Release: 18.04 gnome-shell: Installed: 3.28.4-0ubuntu18.04.3 Candidate: 3.28.4-0ubuntu18.04.3 Version table: *** 3.28.4-0ubuntu18.04.3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.3+git20190124-0ubuntu18.04.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.28.1-0ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 15 06:21:53 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-17 (454 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/1863400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863514] Re: Red fill address bar if the website is insecure.
That's a request for the upstream project. Would you mind filing it at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1863514 Title: Red fill address bar if the website is insecure. Status in firefox package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) Firefox 72 3) When visiting an insecure website, the address bar should be red filled. 4) The lock icon with a red slash is not very noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1863514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863584] [NEW] Drop gnombg for background drawing
Public bug reported: Copy the code into unity-settings-daemon so that we can use it with other unity (unity & u-c-c) components. ** Affects: unity (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: unity-control-center (Ubuntu) Importance: Undecided Assignee: Khurshid Alam (khurshid-alam) Status: Confirmed ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Assignee: Khurshid Alam (khurshid-alam) Status: Confirmed ** Tags: focal ** Changed in: unity-settings-daemon (Ubuntu) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) ** Changed in: unity-settings-daemon (Ubuntu) Status: New => Confirmed ** Also affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~khurshid-alam/unity-settings-daemon/drop-gnomebg ** Branch linked: lp:~khurshid-alam/unity-control-center/drop-gnomebg ** Changed in: unity-control-center (Ubuntu) Status: New => Confirmed ** Changed in: unity (Ubuntu) Status: New => Confirmed ** Description changed: Copy the code into unity-settings-daemon so that we can use it with - other components. + other unity (unity & u-c-c) components. ** Changed in: unity-control-center (Ubuntu) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1863584 Title: Drop gnombg for background drawing Status in unity package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Bug description: Copy the code into unity-settings-daemon so that we can use it with other unity (unity & u-c-c) components. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838129] Re: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap
@sergiusens Fantastic findings! Thanks a lot for looking into this. This is also the underlying issue behind another issue I face when selfhosting VS Code: it simply crashes when opening a native Open dialog. Unsetting those env vars also fixes that issue! We got that bootstrapping code from Martin (@flexiondotorg): https://github.com/snapcrafters/vscode/commit/1477ff8a6b80d3e337ffabf75c2c9e3482b8ab74 Including a tiny review from you: https://github.com/snapcrafters/vscode/commit/1477ff8a6b80d3e337ffabf75c2c9e3482b8ab74#r32657237 I didn't really understand the original motive behind the `Gdk-pixbuf loaders` section. What do you think we can do here? What's the right way to move forward? Thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1838129 Title: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap Status in firefox package in Ubuntu: Confirmed Bug description: How the crash happened: 0) Firefox is already open with a few tabs. 1) Click on a link in VS Code. 2) Firefox crashes 3) The crashreporter of firefex pops up. 4) Click on "Send to Mozilla". 5) Crash. Here is the crashreport of Firefox: https://crash-stats.mozilla.org/report/index/b6952db2-9983-4f67-b51c-f03a60190727#tab-details I send it manually via about:crashes because the crashreporter is crashed. VS Code is installed as a snap by the way. $ snap list Name Version Rev Tracking Publisher Notes code 2213894e 11stablevscode✓ classic core 16-2.39.37270 stablecanonical✓core core18 20190709 1066 stablecanonical✓base gtk-common-themes 0.1-22-gab0a26b 1313 stablecanonical✓- telegram-desktop 1.7.13 836 stabletelegram.desktop - As you can see telegram is also installed as as snap. but open links from telegram just work. Auto generated data below --- ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: firefox 68.0.1+build1-0ubuntu2 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stefano1718 F pulseaudio BuildID: 20190719083815 Channel: Unavailable CrashCounter: 1 CurrentDesktop: Unity Date: Sat Jul 27 13:01:39 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:1141 DefaultProfilePrefSources: prefs.js DefaultProfilePrefs: extensions.lastAppVersion: "68.0.1" (prefs.js) security.sandbox.content.tempDirSuffix: "0b21b0ae-b91f-43b6-9458-bf92ba3df531" (prefs.js) security.sandbox.plugin.tempDirSuffix: "9a7729c3-823f-443e-95cb-6b41d9a61198" (prefs.js) DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/firefox/crashreporter ForcedLayersAccel: False InstallationDate: Installed on 2019-07-20 (7 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190715) IpRoute: default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.199 metric 600 LocalLibraries: /snap/code/11/usr/lib/x86_64-linux-gnu/librsvg-2.so.2.40.13 /snap/code/11/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-gif.so /snap/code/11/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so /snap/code/11/usr/lib/x86_64-linux-gnu/libcroco-0.6.so.3.0.1 /snap/code/11/usr/lib/x86_64-linux-gnu/libicudata.so.55.1 /snap/code/11/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so /snap/code/11/usr/lib/x86_64-linux-gnu/libxml2.so.2.9.4 /snap/code/11/usr/lib/x86_64-linux-gnu/libicuuc.so.55.1 MostRecentCrashID: bp-b6952db2-9983-4f67-b51c-f03a60190727 ProcCmdline: /usr/lib/firefox/crashreporter /home/username/.mozilla/firefox/7n8aku4a.default/minidumps/7eb59ca7-3107-9f59-9af7-7a6e321d6230.dmp Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr
[Desktop-packages] [Bug 1863472] Re: Switching keyboard layout with Ctrl+Shift in Ubuntu 19.10
** Tags added: bionic ** Tags removed: bionic ** Tags added: eoan ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1863472 Title: Switching keyboard layout with Ctrl+Shift in Ubuntu 19.10 Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: During using Ubuntu 18.04 i set switching keyboard layout combination to Ctrl+Shift by tweak-tool. The combination worked great - with Shift-Ctrl and Ctrl-Shift both, no matter in which order keys were being pressed. But after upgrade to 19.10 and setting the same combination through the same tweak-tool it seems like only Ctrl-Shift is working and Shift-Ctrl is not anymore. Ubuntu release: 19.10 gnome-tweak-tool: 3.34.0-2 Steps to reproduce: - Launch "Tweaks" tool - Choose Keyboard & Mouse - Press Additional Layout Options - Choose "Switching to another layout" - Pick "Ctrl+Shift" by setting the checkbox active What was expected: Shift-Ctrl combination doing the same as Ctrl-Shift What happened instead: Ctrl-Shift is working and Shift-Ctrl is not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863580] [NEW] package nvidia-prime (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 2
Public bug reported: Description:Ubuntu 16.04.6 LTS Release:16.04 Hi, I have decided to upgrade from 14.04 to 16.04. Previously no problems with NVIDIA graphics card Since upgrade the login often looped (logged me out again automatically) and would not allow a change to the TTYs (Alt-Ctrl-F1 etc) Attempt to install nvidia-prime and nvidia-430 both seem to go awry. It starts now but is using the "Intel Ivybridge Mobile" drivers. Lots of problems coming up around "com.ubuntu.apport.apport-gtk-root" Will attempt a complete re-install and see what happens. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-prime (not installed) ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Fri Feb 14 11:59:04 2020 Df: ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2014-12-25 (1876 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: nvidia-prime Title: package nvidia-prime (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2020-02-13 (0 days ago) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- 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/1863580 Title: package nvidia-prime (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 Status in nvidia-prime package in Ubuntu: New Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 Hi, I have decided to upgrade from 14.04 to 16.04. Previously no problems with NVIDIA graphics card Since upgrade the login often looped (logged me out again automatically) and would not allow a change to the TTYs (Alt-Ctrl-F1 etc) Attempt to install nvidia-prime and nvidia-430 both seem to go awry. It starts now but is using the "Intel Ivybridge Mobile" drivers. Lots of problems coming up around "com.ubuntu.apport.apport-gtk-root" Will attempt a complete re-install and see what happens. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-prime (not installed) ProcVersionSignature: Ubuntu 4.4.0-173.203-generic 4.4.208 Uname: Linux 4.4.0-173-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Fri Feb 14 11:59:04 2020 Df: ErrorMessage: subprocess installed post-removal script returned error exit status 2 InstallationDate: Installed on 2014-12-25 (1876 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: nvidia-prime Title: package nvidia-prime (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2020-02-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1863580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856516] Re: Excessive memory usage by gnome-shell in 19.10
A note for anyone finding this that if you have installed AppImageLauncher then see bug #1862910. -- 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/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 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/1856516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862945] Re: Change desktop - select color no longer possible
Thank you for your bug report, it's an upstream decision though, see bug #1850753 ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Opinion -- 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/1862945 Title: Change desktop - select color no longer possible Status in gnome-control-center package in Ubuntu: Opinion Bug description: Open control center - settings - set background - select a solid color is not possible also if stated in the help. Change the desktop and lock screen backgrounds You can change the image used for your backgrounds or set it to be a solid color. corrado@corrado-x5-ff-0104:~$ inxi -Fxx System:Host: corrado-x5-ff-0104 Kernel: 5.4.0-12-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.3 wm: gnome-shell dm: GDM3 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 803 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5912 Display: x11 server: X.Org 1.20.7 driver: i915 compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.6 Mesa 19.3.3 compat-v: 3.0 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 chip ID: 8086:a170 Device-2: Logitech QuickCam Pro 9000 type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-10:5 chip ID: 046d:0990 Sound Server: ALSA v: k5.4.0-12-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 chip ID: 8086:15b8 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 2.05 TiB used: 12.48 GiB (0.6%) ID-1: /dev/nvme0n1 vendor: Kingston model: SKC2000M8250G size: 232.89 GiB speed: 31.6 Gb/s lanes: 4 serial: 50026B72823D1475 ID-2: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB speed: 6.0 Gb/s serial: 37PYNGAFS ID-3: /dev/sdb vendor: Hitachi model: HDS721010CLA332 size: 931.51 GiB speed: 3.0 Gb/s serial: JP2940J80Z3D3V Partition: ID-1: / size: 31.25 GiB used: 12.48 GiB (39.9%) fs: ext4 dev: /dev/nvme0n1p5 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 27.0 C mobo: 29.5 C Fan Speeds (RPM): fan-1: 0 fan-2: 2343 fan-3: 0 fan-4: 2268 fan-5: 0 fan-6: 0 Voltages: 12v: N/A 5v: N/A 3.3v: 3.49 vbat: 3.15 Info: Processes: 219 Uptime: 24m Memory: 7.49 GiB used: 1.24 GiB (16.6%) Init: systemd v: 244 runlevel: 5 Compilers: gcc: 9.2.1 alt: 9 Shell: bash v: 5.0.11 running in: gnome-terminal inxi: 3.0.37 corrado@corrado-x5-ff-0104:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 12 14:30:09 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-01-04 (39 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) 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/1862945/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863472] Re: Switching keyboard layout with Ctrl+Shift in Ubuntu 19.10
** Package changed: gnome-control-center (Ubuntu) => 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/1863472 Title: Switching keyboard layout with Ctrl+Shift in Ubuntu 19.10 Status in gnome-shell package in Ubuntu: New Bug description: During using Ubuntu 18.04 i set switching keyboard layout combination to Ctrl+Shift by tweak-tool. The combination worked great - with Shift-Ctrl and Ctrl-Shift both, no matter in which order keys were being pressed. But after upgrade to 19.10 and setting the same combination through the same tweak-tool it seems like only Ctrl-Shift is working and Shift-Ctrl is not anymore. Ubuntu release: 19.10 gnome-tweak-tool: 3.34.0-2 Steps to reproduce: - Launch "Tweaks" tool - Choose Keyboard & Mouse - Press Additional Layout Options - Choose "Switching to another layout" - Pick "Ctrl+Shift" by setting the checkbox active What was expected: Shift-Ctrl combination doing the same as Ctrl-Shift What happened instead: Ctrl-Shift is working and Shift-Ctrl is not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1863472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862767] Re: gnome-control-center crashes when try to open it
Thank you for your bug report Can you provide the output of those commands? $ dpkg -l | grep gnome-control-center $ which gnome-control-center $ ldd -r $(which gnome-control-center) ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862767 Title: gnome-control-center crashes when try to open it Status in gnome-control-center package in Ubuntu: Incomplete Bug description: gnome-control center crashes when trying to open it. Tested as following $ gnome-control-center --verbose ** cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object)) Aborted (core dumped) When trying to open it through the graphical interface it dies silently. A message of error would help too. Additional information: $ lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 09:24:49 2020 InstallationDate: Installed on 2018-05-07 (644 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863376] Re: Seg Fault during version check
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- 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/1863376 Title: Seg Fault during version check Status in nautilus package in Ubuntu: Invalid Bug description: 1) Ubuntu 19.10 2) 3.34.1 3) No seg fault. 4) Seg fault occurred when checking nautilus version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1863376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1527837] Re: "Make Link" operation missing from context menu
The issue there was resolved, if it's back in newer version best to open a new fresh report describing the problem as it exists today ** Changed in: nautilus (Ubuntu) Status: Confirmed => Fix Released -- 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/1527837 Title: "Make Link" operation missing from context menu Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Bug description: In Nautilus 3.15.x create symbolic links ("make link") was removed from the context menu (not sure why?). The alternate method with middle-click/drag does not work with mouse-less device (laptops/netbooks) and the other alternate method, which involves mouse, keyboard and three fingers simultaneously, is very inconvenient for normal users and has bugs. And It doesn't look like upstream is keen to get back this option very soon. For LTS, its a major regression and Ubuntu should patch it until they do. https://bugzilla.gnome.org/show_bug.cgi?id=745575 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1527837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792424] Re: Left panel flickers like crazy during several seconds after deleting a bunch of files
Reporting upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/ would be more useful than arguing over bug settings on this ticket... -- 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/1792424 Title: Left panel flickers like crazy during several seconds after deleting a bunch of files Status in nautilus package in Ubuntu: Confirmed Bug description: I have no idea if there are some requirements to trigger this issue, so I don't know whether you'll be able to reproduce it by just following my steps. Anyway, I can reproduce it 100% of the times: 1. Open some folder in Nautilus 2. Select a few files. Make sure you select quite a few 3. Delete them by pressing the DEL key Expected: Nothing, a part from the files being deleted and disappearing from the displayed folder contents. Observed: During a few seconds after you hit Delete (I guess the time it takes to move the files to Trash and do some associated action, which by the way I don't know what it is that can take so long when deleting just a handful of files), the items in the list of shortcuts in the left panel (see screenshot) start flickering frantically, like crazy. It's pathetic. It looks like the item called "Networks", just below "Trash", disappears and reappears several times very quickly, causing all the items below it to move down and up, hence the flickering. Obviously it makes no sense. Note: there's nothing wrong to be appreciated in my screenshot, it just indicates where the flickering happens. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140 Uname: Linux 4.4.0-135-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 13 19:24:36 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'190' b'org.gnome.nautilus.window-state' b'geometry' b"'1044x767+374+165'" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2013-10-11 (1797 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1792424/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1857869] Re: Red fill the search stop icon
Thanks ** Changed in: nautilus (Ubuntu) Status: New => Triaged ** Also affects: nautilus via https://gitlab.gnome.org/GNOME/nautilus/issues/1375 Importance: Unknown Status: Unknown -- 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/1857869 Title: Red fill the search stop icon Status in Nautilus: Unknown Status in nautilus package in Ubuntu: Triaged Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu1 3) It might be better if the search stop icon was red filled. Similar to a stop sign. 4) The search stop icon is white filled. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1857869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862553] Re: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget()
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: gnome-control-center (Ubuntu) Importance: Medium => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862553 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() Status in gnome-control-center package in Ubuntu: Incomplete Bug description: problem with Ubuntu software centre ver.3.35.2 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.90-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 00:28:42 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-02-06 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x55db27c2df87 : mov 0x3f8(%rax),%rax PC (0x55db27c2df87) ok source "0x3f8(%rax)" (0x03f8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: cc_panel_get_title_widget () ?? () ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-control-center crashed with SIGSEGV in cc_panel_get_title_widget() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862553/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1838948] Re: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.
*** This bug is a duplicate of bug 1671487 *** https://bugs.launchpad.net/bugs/1671487 ** This bug has been marked a duplicate of private bug 1671487 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1838948 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. Status in eog package in Ubuntu: Confirmed Bug description: I opened an image. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: eog 3.28.1-1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AssertionMessage: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. CurrentDesktop: ubuntu:GNOME Date: Mon Jul 29 16:22:00 2019 ExecutablePath: /usr/bin/eog ExecutableTimestamp: 1523677004 InstallationDate: Installed on 2017-03-13 (874 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcCmdline: eog /home/mircea/Downloads/IMG_20190410_143513.jpg ProcCwd: /home/mircea Signal: 6 SourcePackage: eog StacktraceTop: __assert_fail_base (fmt=0x7fac8c9d47d8 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fac8c0ce9a9 "*ptr != NULL", file=file@entry=0x7fac8c0ce980 "../../../../src/cairo-xlib-surface-shm.c", line=line@entry=619, function=function@entry=0x7fac8c0cead0 "_cairo_xlib_shm_pool_create") at assert.c:92 __GI___assert_fail (assertion=0x7fac8c0ce9a9 "*ptr != NULL", file=0x7fac8c0ce980 "../../../../src/cairo-xlib-surface-shm.c", line=619, function=0x7fac8c0cead0 "_cairo_xlib_shm_pool_create") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. UpgradeStatus: Upgraded to bionic on 2018-08-24 (345 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1838948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1671487] Re: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed.
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1671487 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. Status in eog package in Ubuntu: Confirmed Bug description: Tried to open a tiff file, eog crashed on opening. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: eog 3.23.91-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AssertionMessage: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. CurrentDesktop: GNOME Date: Thu Mar 9 14:47:55 2017 ExecutablePath: /usr/bin/eog InstallationDate: Installed on 2017-03-05 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219) ProcCmdline: eog /data/username/RuG_GDrive/5902O_park/5902O\ data/Vector\ comparison/batch3_pilot-direct-injection_march2017/rat_30_ink-injection_2017-03-08tif Signal: 6 SourcePackage: eog StacktraceTop: __assert_fail_base (fmt=, assertion=assertion@entry=0x7fbbdbada449 "*ptr != NULL", file=file@entry=0x7fbbdbada420 "../../../../src/cairo-xlib-surface-shm.c", line=line@entry=619, function=function@entry=0x7fbbdbada570 "_cairo_xlib_shm_pool_create") at assert.c:92 __GI___assert_fail (assertion=0x7fbbdbada449 "*ptr != NULL", file=0x7fbbdbada420 "../../../../src/cairo-xlib-surface-shm.c", line=619, function=0x7fbbdbada570 "_cairo_xlib_shm_pool_create") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 Title: eog assert failure: eog: ../../../../src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != NULL' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1671487/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862478] Re: gnome-system-monitor can't measure network transfer rate
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/1862478 Title: gnome-system-monitor can't measure network transfer rate Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: It started happening since I updated today and version 3.35.90 got installed. It had been working normally before that. The total number of bytes received seems to be accurate (I really downloaded a bit over 1GB of data when the screenshot was taken), but the transfer rate is not being measured accurately. The real transfer rate when the screenshot was taken was around 10 MB/s while it shows just a few bytes/second. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.35.90-1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 8 22:29:41 2020 InstallationDate: Installed on 2019-05-15 (269 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to focal on 2020-01-20 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1862478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862541] Re: Ctrl+A does not always select all contents of the visited folder (can lead to permanently lost work!)
Thank you for your bug report. That looks like an upstream issue, could you report it there? https://gitlab.gnome.org/GNOME/nautilus/issues ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1862541 Title: Ctrl+A does not always select all contents of the visited folder (can lead to permanently lost work!) Status in nautilus package in Ubuntu: New Bug description: The other day I wanted to move all the files in one folder over to another folder using the cut + paste method. I visited the source folder, pressed Ctrl+A (select all) followed by Ctrl+X (cut), and then browsed to the target folder and pressed Ctrl+V (paste). Then I went and deleted the source folder, which I reasonably assumed to now be empty. However, it turned out that not all the files had been moved, and that the remaining files had been deleted along with the original folder (which I deleted permanently with Shift+Del, I might add). After some troubleshooting I've been able to determine the most likely cause. When visiting a folder, there is usually some delay during which the contents of the folder are read from disk and the thumbnails are being updated (for large folders this delay can be on the order of seconds). If Ctrl+A is pressed before this process has finished, only a subset of the files/folders are selected. Thus, I probably only cut/moved some of the files, and left the remaining files behind. This is a very serious bug, as it can lead to permanent loss of work (as it did for me). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 21:22:24 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2020-02-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1862541/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862264] Re: Browsing smb share is painfully slow when mounted via "gio" (compared with "mount")
Thank you for your bug report, that's likely an upstream issue, could you report it to them on https://gitlab.gnome.org/GNOME/glib/issues ? ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Low -- 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/1862264 Title: Browsing smb share is painfully slow when mounted via "gio" (compared with "mount") Status in glib2.0 package in Ubuntu: New Bug description: Ubuntu 18.04 LTS here, fully updated (as of late Jan 2020). TEST #1: To establish a baseline/expected behavior, we first mount an SMB share via mount.cifs and time an ls command: $ sudo mount -t cifs -o username=pablo //myserver.example.com/share ~/mnt/share $ cd ~/mnt/share/some/dir $ time ls ... approx 320 files ... real 0m1,080s user 0m0,008s sys 0m0,005s $ sudo umount ~/mnt/share TEST #2 Now we do the same via gio mount: $ gio mount smb://myserver.example.com/share cd /run/user/1000/gvfs/smb-share\:server\=myserver.example.com\,share\=share/some/dir $ time ls ... same 320 files ... real 0m28,999s user 0m0,013s sys 0m0,032s Enumeration of files is about 29 times slower when mounted via gio mount than via mount -t cifs. TEST #3 Now for the real weird: while using the gio-mounted folder, we now time ls IN COMBINATION WITH SOMETHING ELSE (can be strace ls, ls|wc etc...): $ time ls | wc 321 3239804 real 0m0,546s user 0m0,006s sys 0m0,004s Note that this is almost TWICE AS FAST than the "fast" mount of test #1 and about 53 times faster than "slow" test #2 ! The expectation is that Tests 1 and 2 should have similar timings, not differing by a factor of 30 or so. More disturbing, there is no good reason why tests 2 and 3 differ by an even bigger factor of 53: They use the same underlying infrastructure which test 3 proves is adequately fast. And yet, we get this slow down in test 2. As a final note, these benchmarks are a distilled version of the original real-life motivating scenario where a Java-based program would simply take tens of minutes to display the same list of 320 files when mounted via gio mount and a second or so when mounted via mount -t cifs. The same timing difference is of course visible in any file manager. Hope this helps PS: several old/ancient bug reports exist for a similar issue and I deliberately copied the title from one of them (#259771) PS2: may or may not be relevant: The remote server is a VM running Windows 7 (yes, I know...) and the connection was made via VPN (Ubuntu stock SSTP). PS3: Another data point (server is now a Synolgy NAS, not a Win7 VM) $ gio mount smb://nas.example.com/share2 $ cd /run/user/1000/gvfs/smb- share\:server\=nas.example.com\,share\=share2/another/path $ time ls ... 528 subdirs approximately ... real 0m45,075s user 0m0,013s sys 0m0,058s $ time ls | wc 5281631 10893 real 0m0,911s user 0m0,003s sys 0m0,005s Factor is about 50. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1862264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862544] Re: Double-clicking a folder sometimes opens another, recently visited folder
Thank you for your bug report. That looks like an upstream issue, could you report it to them on https://gitlab.gnome.org/GNOME/nautilus/issues ? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1862544 Title: Double-clicking a folder sometimes opens another, recently visited folder Status in nautilus package in Ubuntu: New Bug description: The following happens for me very frequently. Say I have the following folder structure: A |- B |- C |- some other files/folders... I'm currently browsing the folder B. Then I go up one level, to A, by pressing backspace. I then immediately double-click on the icon for folder C to enter into it. Very frequently, this instead takes me back into folder B. What appears to be happening is that when I go up from B to A, if I double-click the icon for C while the contents of A are being read from disk and the thumbnails are being refreshed, the program registers that I have double-clicked something, but after the thumbnail refresh has finished, the "selected folder" reverts back to B. Hence, the program thinks I double-clicked the icon for B instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 9 21:42:19 2020 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2020-02-09 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1862544/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863473] Re: Network History graph not showing actual network throughput.
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/1863473 Title: Network History graph not showing actual network throughput. Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: Network History graph not showing actual network throughput. Probably not scaled. nmon shows current throughput correctly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-system-monitor 3.35.90-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 16 15:51:48 2020 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2020-02-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1863473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862359] Re: Gnome Control Center doesn't open
Thank you for your bug report, that library is from pipewire that we don't use/enable by default. Did you install some pulseaudio plugin for it or tried to replace pulseaudio on your system? Can you provide the output of those commands? $ dpkg -l | grep gnome-control-center $ which gnome-control-center $ ldd -r $(which gnome-control-center) ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1862359 Title: Gnome Control Center doesn't open Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When I try to open the Gnome Control Center application, it dies silently. When I try to open it on the terminal, this error is displayed on the terminal: $ gnome-control-center --verbose can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: cannot open shared object file: No such file or directory Segmentation fault (core dumped) I believe it is a problem with outdated dependencies (libspa-support). Could you fix this bug, please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1862359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1849859] Re: smb printing fails
Thank you...It works -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1849859 Title: smb printing fails Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed
Launchpad has imported 13 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=692666. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2013-01-28T00:55:11+00:00 Yorick Henning wrote: Fairly straightforward. This needs to be fixed. I have mice that scroll pages at the barest touch (and are therefore unusable without xinput hackery) and other mice that require four or five turns of the wheel to scroll down a paragraph (and are therefore equally as unusable). This has been a problem in Gnome for *over a decade*. https://bugzilla.gnome.org/show_bug.cgi?id=89259 Somebody *please* just implement it. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/124440/comments/32 On 2013-03-05T08:31:48+00:00 Adam Niedling wrote: This bug is recently getting lots of attention at the downstream bug report: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/124440 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/124440/comments/52 On 2013-04-11T12:45:00+00:00 Ondrej Holy wrote: *** Bug 697404 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/124440/comments/55 On 2014-10-19T05:24:10+00:00 teppot wrote: Confirmed with gnome-control-center 3.14.1 on Fedora 21. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/124440/comments/69 On 2015-03-31T14:01:32+00:00 Theo-dev-5 wrote: Confirmend with gnome-control-center 3.16. on Arch. Is there a reason why this hasn't been implemented in gnome (e.g. conflicts with guidelines) or did just nobody implement this? I there is a chance to get a patch into upstream I would do some work in this regards. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/124440/comments/72 On 2015-03-31T20:07:21+00:00 Andre Klapper wrote: Silence means that nobody works on this. :) More info if you're interested to contribute code: https://wiki.gnome.org/Git/Developers Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/124440/comments/73 On 2015-04-10T13:14:49+00:00 Bugzilla-x wrote: This needs implementing in libinput first if it's going to be added to the UI. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/124440/comments/76 On 2015-04-14T13:21:55+00:00 Bugzilla-x wrote: It doesn't actually need to be a configuration option, but it's a property of the hardware. You'll need to file a bug against systemd or libinput at bugzilla.freedesktop.org for the angle of the scroll wheel to be tagged properly. See those articles for details: http://who-t.blogspot.com.au/2015/01/providing-physical-movement-of-wheel.html http://cgit.freedesktop.org/systemd/systemd/commit/?id=011c703495fb564a49dea44b424445241cd58634 Feel free to post the bug URL here for others to follow. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/124440/comments/77 On 2015-08-26T17:40:03+00:00 Yorick Henning wrote: Hardware support for 15 degrees v. 20 degrees is not the same thing as a user-configurable sensitivity multiplier and/or acceleration factor. KDE, Windows, and Mac OS all support this as an option. Add another two years onto this being a basic, unsupported feature I guess. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/124440/comments/80 On 2015-08-26T21:21:28+00:00 Andre Klapper wrote: @steppres: For random offtopic operating system comments please use some forum or blog instead of GNOME Bugzilla. Thanks! Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/124440/comments/81 On 2015-10-27T10:50:07+00:00 Andre Klapper wrote: *** Bug 757100 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-control- center/+bug/124440/comments/84 On 2016-09-23T11
[Desktop-packages] [Bug 1863400] Re: gnome-shell reports problem on boot
Please go to step 2 in comment #3. -- 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/1863400 Title: gnome-shell reports problem on boot Status in gnome-shell package in Ubuntu: Incomplete Bug description: Problem reported at boot but does not seem to collect data and send, just does nothing. See attached screenshot of window. Still able to use laptop. This file exists in /var/crash -rw-r- 1 gdm whoopsie 21900809 Feb 14 22:01 _usr_bin_gnome-shell.121.crash The time of this file must have been at last shutdown which did take a little longer than usual. Description: Ubuntu 18.04.4 LTS Release: 18.04 gnome-shell: Installed: 3.28.4-0ubuntu18.04.3 Candidate: 3.28.4-0ubuntu18.04.3 Version table: *** 3.28.4-0ubuntu18.04.3 500 500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.3+git20190124-0ubuntu18.04.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 3.28.1-0ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Feb 15 06:21:53 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-11-17 (454 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/1863400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863570] [NEW] Update GameMode to 1.5 stable (includes perf regression fix for Intel iGPUs)
Public bug reported: The current GameMode package version is from an outdated git revision. Stable version 1.5 was released last month. Notably, the new version includes changes to avoid causing performance regressions on Intel integrated GPUs: https://github.com/FeralInteractive/gamemode/pull/179 It would be great if this could be upgraded in 20.04 LTS so that those changes are available. ** Affects: gamemode (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gamemode in Ubuntu. https://bugs.launchpad.net/bugs/1863570 Title: Update GameMode to 1.5 stable (includes perf regression fix for Intel iGPUs) Status in gamemode package in Ubuntu: New Bug description: The current GameMode package version is from an outdated git revision. Stable version 1.5 was released last month. Notably, the new version includes changes to avoid causing performance regressions on Intel integrated GPUs: https://github.com/FeralInteractive/gamemode/pull/179 It would be great if this could be upgraded in 20.04 LTS so that those changes are available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/1863570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp