[Desktop-packages] [Bug 1781647] Re: gnome-shell crashed with SIGABRT in __GI___poll() from g_main_context_poll() from g_main_context_iterate() from g_main_loop_run() from g_dbus_connection_send_messa
So far there have been no lockups since I disabled those two, so I've re-enabled Removable Drive Menu to see if that causes the lockups to return. -- 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/1781647 Title: gnome-shell crashed with SIGABRT in __GI___poll() from g_main_context_poll() from g_main_context_iterate() from g_main_loop_run() from g_dbus_connection_send_message_with_reply_sync() from g_dbus_connection_call_sync_internal() Status in gnome-shell package in Ubuntu: Incomplete Bug description: The computer hard-locked up after I did a suspend/resume cycle and entered my password. I generated this via ssh'ing in from a phone and issuing a kill -ABRT command on my gnome-shell session pid. This happens randomly but with annoying frequency and it happens whether I run gnome-shell in X or Wayland. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 Uname: Linux 4.17.5-041705-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jul 13 18:57:15 2018 DisplayManager: gdm3 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1529538342 InstallationDate: Installed on 2017-08-16 (331 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/rocko ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: gnome-shell StacktraceTop: raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:51 () () at /lib/x86_64-linux-gnu/libpthread.so.0 __GI___poll (fds=0x55ddc16f8270, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with SIGABRT in raise() UpgradeStatus: Upgraded to bionic on 2017-11-17 (238 days ago) UserGroups: adm bumblebee cdrom dip kvm lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781647/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784107] [NEW] package python3-update-manager 1:18.04.11.4 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
You have been subscribed to a public bug: Ubuntu 18.04.1 LTS ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-update-manager 1:18.04.11.4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: linux-headers-4.15.0-23:amd64: Remove NULL: ConfigurePending Architecture: amd64 Date: Fri Jul 27 06:02:05 2018 ErrorMessage: vereistenproblemen - blijft ongeconfigureerd GsettingsChanges: InstallationDate: Installed on 2018-06-12 (45 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: update-manager Title: package python3-update-manager 1:18.04.11.4 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: hplip (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- package python3-update-manager 1:18.04.11.4 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd https://bugs.launchpad.net/bugs/1784107 You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip 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 1784940] Re: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: '/usr/share/doc/libgtkmm-2.4-dev/examples/README' を上書きしようとしています。これはパッケージ libgtkmm-2.4-dev:amd64
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtkmm2.4 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtkmm2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1784940 Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: '/usr/share/doc/libgtkmm-2.4-dev/examples/README' を上書きしようとしています。これはパッケージ libgtkmm-2.4-dev:amd64 1:2.24.5-2 にも存在します Status in gtkmm2.4 package in Ubuntu: Confirmed Bug description: 20180801 install gtkmm3.0<-- Is this influenced? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgtkmm-2.4-doc (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 1 17:32:12 2018 ErrorMessage: '/usr/share/doc/libgtkmm-2.4-dev/examples/README' を上書きしようとしています。これはパッケージ libgtkmm-2.4-dev:amd64 1:2.24.5-2 にも存在します InstallationDate: Installed on 2018-04-15 (107 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: gtkmm2.4 Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: '/usr/share/doc/libgtkmm-2.4-dev/examples/README' を上書きしようとしています。これはパッケージ libgtkmm-2.4-dev:amd64 1:2.24.5-2 にも存在します UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtkmm2.4/+bug/1784940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
** Attachment added: "Screenshot from 2018-08-02 14-11-37.png" https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+attachment/5170643/+files/Screenshot%20from%202018-08-02%2014-11-37.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
I've tried replicating your setup in a fresh bionic VM (ie. using tmux as default shell which then launches bash) and I can't replicate this: amurray@sec-bionic-amd64:~$ grep amurray /etc/passwd amurray:x:1000:1000:Ubuntu,,,:/home/amurray:/usr/bin/tmux amurray@sec-bionic-amd64:~$ echo $SHELL /bin/bash amurray@sec-bionic-amd64:~$ cat /etc/tmux.conf set -g default-shell /bin/bash amurray@sec-bionic-amd64:~$ groups amurray adm cdrom sudo dip plugdev lpadmin sambashare This is all from within a graphic gnome-terminal launched after logging into the desktop (see picture which I will attach separately). Can you perhaps try and provide more details on how I could try and replicate this? A couple things to try 1. I've rebuilt polkit-1 with some extra debugging to try and flag when UIDs mismatch - this should end up in the following PPA https://launchpad.net/~alexmurray/+archive/ubuntu/lp1784964 which you could try installing from and seeing if journalctl shows anything? 2. Can you try downgrading polkit-1 and see if that resolves the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302192] Re: capabilities not preserved on installation
** Branch linked: lp:~vorlon/livecd-rootfs/lp.1302192-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1302192 Title: capabilities not preserved on installation Status in attr package in Ubuntu: Fix Released Status in iputils package in Ubuntu: Confirmed Status in live-installer package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: New Status in ubiquity package in Ubuntu: Fix Released Status in attr source package in Trusty: Fix Released Status in iputils source package in Trusty: Confirmed Status in live-installer source package in Trusty: Fix Released Status in ubiquity source package in Trusty: Fix Released Bug description: Ping is not longer setuid root and I have to ping as root: [~]$ ping kubuntu.org ping: icmp open socket: Operation not permitted [~]$ sudo ping kubuntu.org PING kubuntu.org (91.189.94.156) 56(84) bytes of data. 64 bytes from vostok.canonical.com (91.189.94.156): icmp_seq=1 ttl=51 time=52.2 ms --- kubuntu.org ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 52.231/52.231/52.231/0.000 ms [~]$ Related bugs: bug 1313550: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/attr/+bug/1302192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Hello Adam, or anyone else affected, Accepted console-setup into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/console- setup/1.178ubuntu2.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: console-setup (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic ** Tags removed: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Fix Committed Status in gnome-control-center source package in Bionic: Invalid Bug description: [Impact] The keyboard-configuration package provides a tool for configuring the keyboard via /etc/default/keyboard. However, there are desktop GUIs which provide such tools as well, and in the case of gnome-control- center it has another idea of what /etc/default/keyboard should contain. In short: The different tools don't play well together. The proposed upload does not claim to fix all issues with this incompatibility. But one of the annoyances is that a pure upgrade of the keyboard-configuration package may result in a changed keyboard configuration without the user asking for it. The proposed upload does address that particular issue on desktop systems. [Test Case] 1. On an Ubuntu 18.04 system, make sure that the contents of /etc/default/keyboard is 'the g-c-c style', for instance: XKBLAYOUT=se,us BACKSPACE=guess XKBVARIANT=, 2. Reboot. 3. Upgrade to the version of the keyboard-configuration package in bionic-proposed. => Find that /etc/default/keyboard was not changed through the upgrade. 4. Run the command sudo dpkg-reconfigure keyboard-configuration => Find that you are now offered to change your keyboard configuration. [Regression Potential] As a result of this upload, and unlike before, no keyboard configuration will happen behind the scenes on a desktop system due to an upgrade of the keyboard-configuration package. This is the desired change, and I can't think of a case when a user would want the configuration to be changed without having asked for it. [Original description] Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1302192] Re: capabilities not preserved on installation
** Branch linked: lp:~vorlon/livecd-rootfs/lp.1302192 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1302192 Title: capabilities not preserved on installation Status in attr package in Ubuntu: Fix Released Status in iputils package in Ubuntu: Confirmed Status in live-installer package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: New Status in ubiquity package in Ubuntu: Fix Released Status in attr source package in Trusty: Fix Released Status in iputils source package in Trusty: Confirmed Status in live-installer source package in Trusty: Fix Released Status in ubiquity source package in Trusty: Fix Released Bug description: Ping is not longer setuid root and I have to ping as root: [~]$ ping kubuntu.org ping: icmp open socket: Operation not permitted [~]$ sudo ping kubuntu.org PING kubuntu.org (91.189.94.156) 56(84) bytes of data. 64 bytes from vostok.canonical.com (91.189.94.156): icmp_seq=1 ttl=51 time=52.2 ms --- kubuntu.org ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 52.231/52.231/52.231/0.000 ms [~]$ Related bugs: bug 1313550: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/attr/+bug/1302192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302192] Re: capabilities not preserved on installation
** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** No longer affects: livecd-rootfs (Ubuntu Trusty) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/1302192 Title: capabilities not preserved on installation Status in attr package in Ubuntu: Fix Released Status in iputils package in Ubuntu: Confirmed Status in live-installer package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: New Status in ubiquity package in Ubuntu: Fix Released Status in attr source package in Trusty: Fix Released Status in iputils source package in Trusty: Confirmed Status in live-installer source package in Trusty: Fix Released Status in ubiquity source package in Trusty: Fix Released Bug description: Ping is not longer setuid root and I have to ping as root: [~]$ ping kubuntu.org ping: icmp open socket: Operation not permitted [~]$ sudo ping kubuntu.org PING kubuntu.org (91.189.94.156) 56(84) bytes of data. 64 bytes from vostok.canonical.com (91.189.94.156): icmp_seq=1 ttl=51 time=52.2 ms --- kubuntu.org ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 52.231/52.231/52.231/0.000 ms [~]$ Related bugs: bug 1313550: ping does not work as a normal user on trusty tarball cloud images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/attr/+bug/1302192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
@vanvugt, new GDM bug has been created here: https://gitlab.gnome.org/GNOME/gdm/issues/408 -- 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/1767918 Title: Login password from GDM is shown in plain text on the VT1 console Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/408 --- I don't which package this applies to, but I believe the best bet is GDM. Steps to reproduce: 1) Log-in using X11 login via GDM. 2) Use the desktop for a while. (For some reason I cannot reproduce if I login and then restart after a short while). 3) In Gnome click System menu -> Power Button -> Restart 4) Quickly press CTRL-ALT-F1 5) I see my login password in plain text in the console. Once I saw the login password repeated twice. See attached photo with the login password blanked out. Below the password is the console cursor. ## lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ## apt-cache policy gdm3 gdm3: Installed: 3.28.0-0ubuntu1 Candidate: 3.28.0-0ubuntu1 Version table: *** 3.28.0-0ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-18.19-generic 4.15.17 Uname: Linux 4.15.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:54:07 2018 InstallationDate: Installed on 2018-04-13 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
** Description changed: + https://gitlab.gnome.org/GNOME/gdm/issues/408 + + --- + I don't which package this applies to, but I believe the best bet is GDM. Steps to reproduce: 1) Log-in using X11 login via GDM. 2) Use the desktop for a while. (For some reason I cannot reproduce if I login and then restart after a short while). 3) In Gnome click System menu -> Power Button -> Restart 4) Quickly press CTRL-ALT-F1 5) I see my login password in plain text in the console. Once I saw the login password repeated twice. See attached photo with the login password blanked out. Below the password is the console cursor. ## lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ## apt-cache policy gdm3 gdm3: - Installed: 3.28.0-0ubuntu1 - Candidate: 3.28.0-0ubuntu1 - Version table: - *** 3.28.0-0ubuntu1 500 - 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 3.28.0-0ubuntu1 + Candidate: 3.28.0-0ubuntu1 + Version table: + *** 3.28.0-0ubuntu1 500 + 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-18.19-generic 4.15.17 Uname: Linux 4.15.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:54:07 2018 InstallationDate: Installed on 2018-04-13 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767918 Title: Login password from GDM is shown in plain text on the VT1 console Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/408 --- I don't which package this applies to, but I believe the best bet is GDM. Steps to reproduce: 1) Log-in using X11 login via GDM. 2) Use the desktop for a while. (For some reason I cannot reproduce if I login and then restart after a short while). 3) In Gnome click System menu -> Power Button -> Restart 4) Quickly press CTRL-ALT-F1 5) I see my login password in plain text in the console. Once I saw the login password repeated twice. See attached photo with the login password blanked out. Below the password is the console cursor. ## lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ## apt-cache policy gdm3 gdm3: Installed: 3.28.0-0ubuntu1 Candidate: 3.28.0-0ubuntu1 Version table: *** 3.28.0-0ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-18.19-generic 4.15.17 Uname: Linux 4.15.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:54:07 2018 InstallationDate: Installed on 2018-04-13 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS
Workaround: 1. Add a line to /etc/environment like: CLUTTER_DEFAULT_FPS=144 or whatever your monitor's real refresh rate is. 2. Reboot. -- 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/1763892 Title: 144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS Status in Mutter: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: Monitor is set to 144hz, but on Wayland it visually fails to go above 60Hz. On XOrg it runs higher and feels much smoother. I have confirmed the monitor is running at 144Hz during the Wayland session, and that is also the setting in the Settings control panel. Using the additional NVidia drivers installed using the Ubuntu software control panel. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libwayland-bin (not installed) ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 14 08:43:29 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 1070] [1462:3301] InstallationDate: Installed on 2018-03-30 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0610 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z370-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 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/mutter/+bug/1763892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784974] Re: Update mozjs52 to 52.1.9
** Description changed: Impact -- mozjs is Firefox's Spidermonkey JavaScript engine. mozjs52 is derived from Firefox 52 ESR. 52.9 is the final scheduled release in the 52 series. (mozjs itself never got "official releases" from Mozilla.) By comparing the bug numbers in the release notes with the bug numbers mentioned at https://github.com/mozilla/gecko-dev/commits/esr52/js/src/ - it looks like the new release includes fixes for one or more memory - safety bugs identified as CVE-2018-5188. + it looks like the new release includes one or more memory safety bugs + identified as CVE-2018-5188. GNOME Shell (Ubuntu's default interface in Ubuntu 18.04 LTS) requires mozjs52. Nothing else in Ubuntu 18.04 LTS uses mozjs52. References -- https://www.mozilla.org/en-US/firefox/52.9.0/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2018-17/ https://wiki.ubuntu.com/SecurityTeam/FAQ#mozjs Test Case - Install the update. Restart your computer. Log in and make sure the default desktop still works. Regression Potential This is a minor release in the long-term support series. I count about 6 cherry-picked targeted commits. Other Info -- - I believe the version in Ubuntu 18.10 (synced with Debian) goes back to building with the distro's ICU library instead of the bundled version. Maybe we should backport from 18.10 instead of a more minimal diff against the Ubuntu version. + I believe the version in Ubuntu 18.10 (synced with Debian) goes back to building with the distro's ICU library instead of the bundled version. Maybe we should backport from 18.10 instead of a more minimal diff against the Ubuntu version. I did verify that a backport builds on Ubuntu 18.04 LTS. A diff of the 18.10 version is at https://launchpad.net/ubuntu/+source/mozjs52/52.9.1-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs52 in Ubuntu. https://bugs.launchpad.net/bugs/1784974 Title: Update mozjs52 to 52.1.9 Status in mozjs52 package in Ubuntu: Fix Released Status in mozjs52 source package in Bionic: Triaged Bug description: Impact -- mozjs is Firefox's Spidermonkey JavaScript engine. mozjs52 is derived from Firefox 52 ESR. 52.9 is the final scheduled release in the 52 series. (mozjs itself never got "official releases" from Mozilla.) By comparing the bug numbers in the release notes with the bug numbers mentioned at https://github.com/mozilla/gecko- dev/commits/esr52/js/src/ it looks like the new release includes one or more memory safety bugs identified as CVE-2018-5188. GNOME Shell (Ubuntu's default interface in Ubuntu 18.04 LTS) requires mozjs52. Nothing else in Ubuntu 18.04 LTS uses mozjs52. References -- https://www.mozilla.org/en-US/firefox/52.9.0/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2018-17/ https://wiki.ubuntu.com/SecurityTeam/FAQ#mozjs Test Case - Install the update. Restart your computer. Log in and make sure the default desktop still works. Regression Potential This is a minor release in the long-term support series. I count about 6 cherry-picked targeted commits. Other Info -- I believe the version in Ubuntu 18.10 (synced with Debian) goes back to building with the distro's ICU library instead of the bundled version. Maybe we should backport from 18.10 instead of a more minimal diff against the Ubuntu version. I did verify that a backport builds on Ubuntu 18.04 LTS. A diff of the 18.10 version is at https://launchpad.net/ubuntu/+source/mozjs52/52.9.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs52/+bug/1784974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772791] Re: Lock/login screen displays password in clear text occasionally
** Summary changed: - Lock Screen displayed password in clear text on one occasion + Lock/login screen displays password in clear text occasionally -- 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/1772791 Title: Lock/login screen displays password in clear text occasionally Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/305 --- Hello, folks, Today when I returned to my computer (which I locked with Super+L) and attempted to unlock it, it displayed my passphrase in cleartext in the 'Password' box. I noticed as soon as I got the first character in, then typed in the second character and it stayed clear. I then picked up my phone to record the attached video and while I was fiddling with it to get a good camera shot, the screen locked (for inactivity perhaps?) and when I unlocked this time, the password only displayed as dots (as expected). So unfortunately, I don't know how to replicate. It _did_ occur though, as the attached video will show if you go slowly (look for "hu", the first characters of legendary password "hunter2"). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 22 20:27:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:07a1] Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Dell Oland [Radeon HD 8570 / R7 240/340 OEM] [1028:1002] InstallationDate: Installed on 2018-05-02 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04d9:a0d5 Holtek Semiconductor, Inc. Bus 001 Device 002: ID 046d:c338 Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7050 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=9d600b65-ce52-4147-aace-2de5ac8c3c34 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.9 dmi.board.name: 0NW6H5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.9:bd01/30/2018:svnDellInc.:pnOptiPlex7050:pvr:rvnDellInc.:rn0NW6H5:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7050 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1772791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772791] Re: Lock Screen displayed password in clear text on one occasion
Upstream: https://gitlab.gnome.org/GNOME/gdm/issues/305 ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Description changed: + https://gitlab.gnome.org/GNOME/gdm/issues/305 + + --- + Hello, folks, Today when I returned to my computer (which I locked with Super+L) and attempted to unlock it, it displayed my passphrase in cleartext in the 'Password' box. I noticed as soon as I got the first character in, then typed in the second character and it stayed clear. I then picked up my phone to record the attached video and while I was fiddling with it to get a good camera shot, the screen locked (for inactivity perhaps?) and when I unlocked this time, the password only displayed as dots (as expected). So unfortunately, I don't know how to replicate. It _did_ occur though, as the attached video will show if you go slowly (look for "hu", the first characters of legendary password "hunter2"). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 22 20:27:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Subsystem: Dell HD Graphics 630 [1028:07a1] - Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) -Subsystem: Dell Oland [Radeon HD 8570 / R7 240/340 OEM] [1028:1002] + Subsystem: Dell HD Graphics 630 [1028:07a1] + Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) + Subsystem: Dell Oland [Radeon HD 8570 / R7 240/340 OEM] [1028:1002] InstallationDate: Installed on 2018-05-02 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 04d9:a0d5 Holtek Semiconductor, Inc. - Bus 001 Device 002: ID 046d:c338 Logitech, Inc. - Bus 001 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 003: ID 04d9:a0d5 Holtek Semiconductor, Inc. + Bus 001 Device 002: ID 046d:c338 Logitech, Inc. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7050 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=9d600b65-ce52-4147-aace-2de5ac8c3c34 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.9 dmi.board.name: 0NW6H5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.9:bd01/30/2018:svnDellInc.:pnOptiPlex7050:pvr:rvnDellInc.:rn0NW6H5:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7050 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: gdm3 (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1772791 Title: Lock Screen displayed password in clear text on one occasion Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/305 --- Hello, folks, Today when I returned to my computer (which I locked with Super+L) and attempted to unlock it, it displayed my passphrase in cleartext in the 'Password' box. I noticed as soon as I got the first character in, then typed in the second character and it stayed
[Desktop-packages] [Bug 1772791] Re: Lock Screen displayed password in clear text on one occasion
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772791 Title: Lock Screen displayed password in clear text on one occasion Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/305 --- Hello, folks, Today when I returned to my computer (which I locked with Super+L) and attempted to unlock it, it displayed my passphrase in cleartext in the 'Password' box. I noticed as soon as I got the first character in, then typed in the second character and it stayed clear. I then picked up my phone to record the attached video and while I was fiddling with it to get a good camera shot, the screen locked (for inactivity perhaps?) and when I unlocked this time, the password only displayed as dots (as expected). So unfortunately, I don't know how to replicate. It _did_ occur though, as the attached video will show if you go slowly (look for "hu", the first characters of legendary password "hunter2"). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 22 20:27:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:07a1] Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Dell Oland [Radeon HD 8570 / R7 240/340 OEM] [1028:1002] InstallationDate: Installed on 2018-05-02 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04d9:a0d5 Holtek Semiconductor, Inc. Bus 001 Device 002: ID 046d:c338 Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7050 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=9d600b65-ce52-4147-aace-2de5ac8c3c34 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.9 dmi.board.name: 0NW6H5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.9:bd01/30/2018:svnDellInc.:pnOptiPlex7050:pvr:rvnDellInc.:rn0NW6H5:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7050 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1772791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
Could someone experiencing the bug please report it to the Gnome developers here: https://gitlab.gnome.org/GNOME/gdm/issues (I'm not sure if it's going to be in "gdm", "mutter" or "gnome-shell" yet) -- 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/1767918 Title: Login password from GDM is shown in plain text on the VT1 console Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I don't which package this applies to, but I believe the best bet is GDM. Steps to reproduce: 1) Log-in using X11 login via GDM. 2) Use the desktop for a while. (For some reason I cannot reproduce if I login and then restart after a short while). 3) In Gnome click System menu -> Power Button -> Restart 4) Quickly press CTRL-ALT-F1 5) I see my login password in plain text in the console. Once I saw the login password repeated twice. See attached photo with the login password blanked out. Below the password is the console cursor. ## lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ## apt-cache policy gdm3 gdm3: Installed: 3.28.0-0ubuntu1 Candidate: 3.28.0-0ubuntu1 Version table: *** 3.28.0-0ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-18.19-generic 4.15.17 Uname: Linux 4.15.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:54:07 2018 InstallationDate: Installed on 2018-04-13 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772791] Re: Lock Screen displayed password in clear text on one occasion
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772791 Title: Lock Screen displayed password in clear text on one occasion Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/305 --- Hello, folks, Today when I returned to my computer (which I locked with Super+L) and attempted to unlock it, it displayed my passphrase in cleartext in the 'Password' box. I noticed as soon as I got the first character in, then typed in the second character and it stayed clear. I then picked up my phone to record the attached video and while I was fiddling with it to get a good camera shot, the screen locked (for inactivity perhaps?) and when I unlocked this time, the password only displayed as dots (as expected). So unfortunately, I don't know how to replicate. It _did_ occur though, as the attached video will show if you go slowly (look for "hu", the first characters of legendary password "hunter2"). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue May 22 20:27:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:07a1] Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Dell Oland [Radeon HD 8570 / R7 240/340 OEM] [1028:1002] InstallationDate: Installed on 2018-05-02 (21 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04d9:a0d5 Holtek Semiconductor, Inc. Bus 001 Device 002: ID 046d:c338 Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7050 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=9d600b65-ce52-4147-aace-2de5ac8c3c34 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.9 dmi.board.name: 0NW6H5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.9:bd01/30/2018:svnDellInc.:pnOptiPlex7050:pvr:rvnDellInc.:rn0NW6H5:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7050 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1772791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
No, because multiple people experience this bug and they wouldn't be able to share the same bug if it was private. -- 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/1767918 Title: Login password from GDM is shown in plain text on the VT1 console Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I don't which package this applies to, but I believe the best bet is GDM. Steps to reproduce: 1) Log-in using X11 login via GDM. 2) Use the desktop for a while. (For some reason I cannot reproduce if I login and then restart after a short while). 3) In Gnome click System menu -> Power Button -> Restart 4) Quickly press CTRL-ALT-F1 5) I see my login password in plain text in the console. Once I saw the login password repeated twice. See attached photo with the login password blanked out. Below the password is the console cursor. ## lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ## apt-cache policy gdm3 gdm3: Installed: 3.28.0-0ubuntu1 Candidate: 3.28.0-0ubuntu1 Version table: *** 3.28.0-0ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-18.19-generic 4.15.17 Uname: Linux 4.15.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:54:07 2018 InstallationDate: Installed on 2018-04-13 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779637] Re: Password visible at login screen
*** This bug is a duplicate of bug 1772791 *** https://bugs.launchpad.net/bugs/1772791 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1772791, so it 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. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1772791 Lock Screen displayed password in clear text on one occasion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1779637 Title: Password visible at login screen Status in gnome-screensaver package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: We have a shared computer (2 user accounts) and I was surprised to find after screen lock that my password was visible when entering it to log back in. * Ubuntu 18.04 LTS / 18.04 * gdm 3.28.2-0ubuntu1.2 (I don't seem to have any packages matching screensaver, so GDM?) I expected: to see masked characters when entering my password I saw: my password visible on screen! I was not able to repeat the issue after a reboot. Checking "security" because that way security team gets to decide if this is really a vulnerability - sorry if that's turning the volume up a bit high, I won't be offended if you make it public straight away, but I'd rather you had the option than that I got it wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1779637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1499113]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/401. -- 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/1499113 Title: pulseaudio crashed with SIGSEGV in set_profile_cb() from pa_card_set_profile() from command_set_card_profile() from pa_pdispatch_run() from pstream_packet_callback() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/7ccf872ad0cc36d20cf02cc1c1ba6f0d881287cd --- Connect two devices, celu movil samsung and headphone ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu12 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 26880 F...m pulseaudio /dev/snd/controlC0: caravena 26880 F pulseaudio CurrentDesktop: GNOME Date: Wed Sep 23 20:52:31 2015 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2015-07-26 (59 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog SegvAnalysis: Segfault happened at: 0x7f1042baad12:mov0x34(%rax),%eax PC (0x7f1042baad12) ok source "0x34(%rax)" (0x0055) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/pulse-6.0/modules/module-bluez5-device.so pa_card_set_profile () from /usr/lib/libpulsecore-6.0.so ?? () from /usr/lib/pulse-6.0/modules/libprotocol-native.so pa_pdispatch_run () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-6.0.so ?? () from /usr/lib/pulse-6.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGSEGV in pa_card_set_profile() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1499113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1499113] Re: pulseaudio crashed with SIGSEGV in set_profile_cb() from pa_card_set_profile() from command_set_card_profile() from pa_pdispatch_run() from pstream_packet_callback
** Changed in: pulseaudio Status: Confirmed => Unknown -- 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/1499113 Title: pulseaudio crashed with SIGSEGV in set_profile_cb() from pa_card_set_profile() from command_set_card_profile() from pa_pdispatch_run() from pstream_packet_callback() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/7ccf872ad0cc36d20cf02cc1c1ba6f0d881287cd --- Connect two devices, celu movil samsung and headphone ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: pulseaudio 1:6.0-0ubuntu12 ProcVersionSignature: Ubuntu 4.2.0-10.12-generic 4.2.0 Uname: Linux 4.2.0-10-generic x86_64 ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 26880 F...m pulseaudio /dev/snd/controlC0: caravena 26880 F pulseaudio CurrentDesktop: GNOME Date: Wed Sep 23 20:52:31 2015 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2015-07-26 (59 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog SegvAnalysis: Segfault happened at: 0x7f1042baad12:mov0x34(%rax),%eax PC (0x7f1042baad12) ok source "0x34(%rax)" (0x0055) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/pulse-6.0/modules/module-bluez5-device.so pa_card_set_profile () from /usr/lib/libpulsecore-6.0.so ?? () from /usr/lib/pulse-6.0/modules/libprotocol-native.so pa_pdispatch_run () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-6.0.so ?? () from /usr/lib/pulse-6.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGSEGV in pa_card_set_profile() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1499113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767918] Re: Login password from GDM is shown in plain text on the VT1 console
Yikes, shouldn't this bug be marked private? -- 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/1767918 Title: Login password from GDM is shown in plain text on the VT1 console Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I don't which package this applies to, but I believe the best bet is GDM. Steps to reproduce: 1) Log-in using X11 login via GDM. 2) Use the desktop for a while. (For some reason I cannot reproduce if I login and then restart after a short while). 3) In Gnome click System menu -> Power Button -> Restart 4) Quickly press CTRL-ALT-F1 5) I see my login password in plain text in the console. Once I saw the login password repeated twice. See attached photo with the login password blanked out. Below the password is the console cursor. ## lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ## apt-cache policy gdm3 gdm3: Installed: 3.28.0-0ubuntu1 Candidate: 3.28.0-0ubuntu1 Version table: *** 3.28.0-0ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-18.19-generic 4.15.17 Uname: Linux 4.15.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:54:07 2018 InstallationDate: Installed on 2018-04-13 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
It seems that /var/run/ConsoleKit directory and its database is only created by console tty log-ins but not the GUI. There was no directory after GUI Terminal shell started; only after switching to TTY1. So it would seem this isn't the cause since PCs without ConsoleKit work fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
Looking at the diff between upstream 0.105 and Ubuntu's I happened to notice the CKDB_PATH (ConsoleKit database path) /var/run/ConsoleKit/database which seems to be consulted on some occasions. On the affected PC which was d-r-u-ed from 16.04 ConsoleKit 0.4.6-5 is still installed and that database is present. On another PC that has a clean 18.04 install that doesn't exist because consolekit is purely virtual now. I'm not sure if this is relevant or not but worth reporting. The database contains (for the *good* session) : [Seat /org/freedesktop/ConsoleKit/Seat1] kind=0 sessions=/org/freedesktop/ConsoleKit/Session1 devices= [Session /org/freedesktop/ConsoleKit/Session1] uid=1000 seat=/org/freedesktop/ConsoleKit/Seat1 login_session_id=3 display_device=/dev/tty1 remote_host_name= is_active=false is_local=true creation_time=2018-08-02T01:18:34.707417Z [SessionLeader /org/freedesktop/ConsoleKit/Session1] session=/org/freedesktop/ConsoleKit/Session1 uid=0 pid=2494 service_name=:1.73 Note it references "display_device=/dev/tty1" That is, I think, a reference to the TTY1 console login I did first. I'm going to restart after writing this and check what is in the file if I open the GUI Terminal shell first. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755779] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_writer_default() from g_log_structured_array() from g_log_structured_standard() from _gdk_x11_display
Now https://gitlab.gnome.org/GNOME/mutter/issues/253 ** Description changed: https://errors.ubuntu.com/problem/37a88e96048de35d02939c3dd8fe220f716448ee + https://gitlab.gnome.org/GNOME/mutter/issues/253 --- don't know why, maybe related to printer ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 14 10:02:43 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'libreoffice-calc.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 'libreoffice-writer.desktop', 'yelp.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-02-12 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo -- 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/1755779 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_writer_default() from g_log_structured_array() from g_log_structured_standard() from _gdk_x11_display_error_event() ["BadPixmap (invalid Pixmap parameter)"] from ... meta_pre_paint_func() Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/37a88e96048de35d02939c3dd8fe220f716448ee https://gitlab.gnome.org/GNOME/mutter/issues/253 --- don't know why, maybe related to printer ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 14 10:02:43 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['firefox.desktop', 'thunderbird.desktop', 'libreoffice-calc.desktop', 'org.gnome.Nautilus.desktop', 'rhythmbox.desktop', 'libreoffice-writer.desktop', 'yelp.desktop', 'gnome-control-center.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-02-12 (29 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XSync () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 Title: gnome-shell crashed with signal 5 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/gnome-shell/+bug/1755779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782614] Re: Upgrade to 3.28.3 and SRU it
I had tagged .1 - in error since it wasn't accepted - when uploading it, so it was easier on our side to upload a new revision with -v. I guess you would prefer us to remove references to bugs that aren't directly being SRUed. In this case it was a change between .1 and .2 so I left it in. The bug is not nominated, which I intended to be an indication of its status. I've done that before with other SRUs without any problems, but if it is an issue then I will remove it when re- uploading. Sorry about the LP-Bugs-Fixed. I uploaded from a Debian packaging directory on Ubuntu and I'd set DEB_VENDOR=Debian. I'll take a look at the 3.28.3 proposal and probably upload that. -- 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/1782614 Title: Upgrade to 3.28.3 and SRU it Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Bug description: [ Description ] The third stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been fixed, VPN fixes so network related featurs should be checked more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1782614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784954] Re: Intel hd 620 graphics driver not working
Please explain in more detail what's not working. Would taking a photo of the screen help to show the problem? ** 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/1784954 Title: Intel hd 620 graphics driver not working Status in Ubuntu: Incomplete Bug description: the graphics driver for intel HD 620 is not working. Very poor graphics from what I had in windows.My processor is i5 7200u. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 04:05:32 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1094] InstallationDate: Installed on 2018-08-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b573 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=6078e205-6c45-4def-8d68-f24e9f29b526 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.20:bd12/13/2016:svnAcer:pnAspireE5-575:pvrV1.20:rvnAcer:rnIronman_SK:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575 dmi.product.version: V1.20 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1784954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784914] Re: bad graphics
Can you please take a photo of the problem so that we can understand what's not working? ** 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/1784914 Title: bad graphics Status in Ubuntu: Incomplete Bug description: Bad graphics.no background for lock screen displayed.no notifications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 1 23:04:28 2018 DistUpgraded: 2018-05-17 18:51:57,274 DEBUG icon theme changed, re-reading DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1: added oem-wifi-qualcomm-ath10k-lp1734600-4.4, 4.1: added ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:07b7] InstallationDate: Installed on 2018-03-16 (138 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e007 Atheros Communications, Inc. Bus 001 Device 002: ID 1bcf:28c0 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3480 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=432f4987-63c1-4b9f-9e85-7e968884f145 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-17 (76 days ago) dmi.bios.date: 07/21/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 00T9J8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd07/21/2017:svnDellInc.:pnLatitude3480:pvr:rvnDellInc.:rn00T9J8:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3480 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Apr 19 01:19:56 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 11836 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1784914/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767918] Re: Login password is shown in plain text on VT1 when shutting down
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Summary changed: - Login password is shown in plain text on VT1 when shutting down + Login password from GDM is shown in plain text on the VT1 console -- 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/1767918 Title: Login password from GDM is shown in plain text on the VT1 console Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I don't which package this applies to, but I believe the best bet is GDM. Steps to reproduce: 1) Log-in using X11 login via GDM. 2) Use the desktop for a while. (For some reason I cannot reproduce if I login and then restart after a short while). 3) In Gnome click System menu -> Power Button -> Restart 4) Quickly press CTRL-ALT-F1 5) I see my login password in plain text in the console. Once I saw the login password repeated twice. See attached photo with the login password blanked out. Below the password is the console cursor. ## lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ## apt-cache policy gdm3 gdm3: Installed: 3.28.0-0ubuntu1 Candidate: 3.28.0-0ubuntu1 Version table: *** 3.28.0-0ubuntu1 500 500 http://nz.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-18.19-generic 4.15.17 Uname: Linux 4.15.0-18-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 14:54:07 2018 InstallationDate: Installed on 2018-04-13 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1767918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784888] Re: password appears in clear after login with gdm3
*** This bug is a duplicate of bug 1767918 *** https://bugs.launchpad.net/bugs/1767918 ** This bug is no longer a duplicate of bug 1784852 Login / switch user passwords visible on screen! ** This bug has been marked a duplicate of bug 1767918 Login password is shown in plain text on VT1 when shutting down -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1784888 Title: password appears in clear after login with gdm3 Status in gdm3 package in Ubuntu: Confirmed Bug description: After having entered my password and logged in with gdm3 greeter, if I type "Ctl-Alt-F1" to switch to the console I can see my password not encrypted in the console. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 1 17:30:51 2018 InstallationDate: Installed on 2018-01-20 (193 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1784888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780616] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1780616 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: Confirmed Bug description: Upgrading from 16.04 to 18.04. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Jul 8 05:09:36 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2017-01-23 (531 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.2.27 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-07-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1780616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784852] Re: Login / switch user passwords visible on screen!
*** This bug is a duplicate of bug 1767918 *** https://bugs.launchpad.net/bugs/1767918 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1767918, so it 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. Feel free to continue to report any other bugs you may find. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1767918 Login password is shown in plain text on VT1 when shutting down -- 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/1784852 Title: Login / switch user passwords visible on screen! Status in gdm package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: I suspect many of the details I'm providing in this bug report are irrelevant, but as I don't know exactly what is causing this issue I'm trying to provide more information rather than less. I recently installed Ubuntu 18.04.1 on two relatively old computers (mentioning their age because the installer may have chosen to configure them differently based on their hardware). Ubuntu was installed on an unencrypted partition next to Windows (Windows 7 on one computers, Windows 10 on the other). After doing this, I added two additional non-admin users through the Users control panel, in addition to the admin user that was created when Ubuntu was installed. After doing this, I was regularly using "Switch User" to switch between the various user accounts. Whenever I selected the "Switch User menu command, before the graphical user-switching screen came up, I briefly saw a screen with some kernel messages on it, and BELOW THE KERNEL MESSAGES WERE THE PASSWORDS THAT HAD BEEN USED TO LOG INTO THE VARIOUS ACCOUNTS, visible right there in plaintext. I am not sure whether these passwords were printed as a result of an initial login, a "Switch User", or both. All I can tell you is that I was able to see other users' passwords briefly whenever I executed the "Switch User" menu command. I am not able to reproduce this on a third laptop. On this laptop, when I execute "Switch User", the screen goes blank briefly, rather than showing a screen with kernel messages and passwords on it. I wonder if this has something to do with the graphics card or capabilities or something. I have attached a photo of what I saw before the user-switching screen came up, with the passwords blurred out of course. Please let me know if there's any other information I can gather to make this report more useful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1784852/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784671] Re: Keeping Alt+Space pressed shows the window menu and then minimizes the window
Thanks! Marco or Andrea: Please could you make this bug SRU compliant since it's included in ubuntu/bionic? ** Also affects: gnome-shell (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu Bionic) Status: New => In Progress ** Changed in: gnome-shell (Ubuntu Bionic) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1784671 Title: Keeping Alt+Space pressed shows the window menu and then minimizes the window Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: In Progress Bug description: To reproduce: Open a couple of windows Press Alt+Space and keep it pressed Expected results: The window menu opens and nothing else happens Current behavior: The window menu opens The window is minimized The window menu of the following window is open The window is minized ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
@TJ re comment:6 that fix is already in for both xenial and bionic as far as I can see. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781826] Re: System logout when turn off the screen or suspend Ubuntu 18.04
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: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: Incomplete Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779637] Re: Password visible at login screen
The lock GUI is provided by 'gnome-shell' ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-screensaver (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-screensaver (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1779637 Title: Password visible at login screen Status in gnome-screensaver package in Ubuntu: New Status in gnome-shell package in Ubuntu: New Bug description: We have a shared computer (2 user accounts) and I was surprised to find after screen lock that my password was visible when entering it to log back in. * Ubuntu 18.04 LTS / 18.04 * gdm 3.28.2-0ubuntu1.2 (I don't seem to have any packages matching screensaver, so GDM?) I expected: to see masked characters when entering my password I saw: my password visible on screen! I was not able to repeat the issue after a reboot. Checking "security" because that way security team gets to decide if this is really a vulnerability - sorry if that's turning the volume up a bit high, I won't be offended if you make it public straight away, but I'd rather you had the option than that I got it wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1779637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784974] [NEW] Update mozjs52 to 52.1.9
*** This bug is a security vulnerability *** Public security bug reported: Impact -- mozjs is Firefox's Spidermonkey JavaScript engine. mozjs52 is derived from Firefox 52 ESR. 52.9 is the final scheduled release in the 52 series. (mozjs itself never got "official releases" from Mozilla.) By comparing the bug numbers in the release notes with the bug numbers mentioned at https://github.com/mozilla/gecko-dev/commits/esr52/js/src/ it looks like the new release includes fixes for one or more memory safety bugs identified as CVE-2018-5188. GNOME Shell (Ubuntu's default interface in Ubuntu 18.04 LTS) requires mozjs52. Nothing else in Ubuntu 18.04 LTS uses mozjs52. References -- https://www.mozilla.org/en-US/firefox/52.9.0/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2018-17/ https://wiki.ubuntu.com/SecurityTeam/FAQ#mozjs Test Case - Install the update. Restart your computer. Log in and make sure the default desktop still works. Regression Potential This is a minor release in the long-term support series. I count about 6 cherry-picked targeted commits. Other Info -- I believe the version in Ubuntu 18.10 (synced with Debian) goes back to building with the distro's ICU library instead of the bundled version. Maybe we should backport from 18.10 instead of a more minimal diff against the Ubuntu version. A diff of the 18.10 version is at https://launchpad.net/ubuntu/+source/mozjs52/52.9.1-1 ** Affects: mozjs52 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mozjs52 (Ubuntu Bionic) Importance: Undecided Status: Triaged ** Tags: bionic ** Also affects: mozjs52 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: mozjs52 (Ubuntu Bionic) Status: New => Triaged ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-5188 ** Description changed: Impact -- mozjs is Firefox's Spidermonkey JavaScript engine. mozjs52 is derived from Firefox 52 ESR. 52.9 is the final scheduled release in the 52 series. (mozjs itself never got "official releases" from Mozilla.) By comparing the bug numbers in the release notes with the bug numbers mentioned at https://github.com/mozilla/gecko-dev/commits/esr52/js/src/ - it looks like the new release includes one or more memory safety bugs - identified as CVE-2018-5188. + it looks like the new release includes fixes for one or more memory + safety bugs identified as CVE-2018-5188. GNOME Shell (Ubuntu's default interface in Ubuntu 18.04 LTS) requires mozjs52. Nothing else in Ubuntu 18.04 LTS uses mozjs52. References -- https://www.mozilla.org/en-US/firefox/52.9.0/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2018-17/ https://wiki.ubuntu.com/SecurityTeam/FAQ#mozjs Test Case - Install the update. Restart your computer. Log in and make sure the default desktop still works. Regression Potential This is a minor release in the long-term support series. I count about 6 cherry-picked targeted commits. Other Info -- I believe the version in Ubuntu 18.10 (synced with Debian) goes back to building with the distro's ICU library instead of the bundled version. Maybe we should backport from 18.10 instead of a more minimal diff against the Ubuntu version. A diff of the 18.10 version is at https://launchpad.net/ubuntu/+source/mozjs52/52.9.1-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs52 in Ubuntu. https://bugs.launchpad.net/bugs/1784974 Title: Update mozjs52 to 52.1.9 Status in mozjs52 package in Ubuntu: Fix Released Status in mozjs52 source package in Bionic: Triaged Bug description: Impact -- mozjs is Firefox's Spidermonkey JavaScript engine. mozjs52 is derived from Firefox 52 ESR. 52.9 is the final scheduled release in the 52 series. (mozjs itself never got "official releases" from Mozilla.) By comparing the bug numbers in the release notes with the bug numbers mentioned at https://github.com/mozilla/gecko- dev/commits/esr52/js/src/ it looks like the new release includes fixes for one or more memory safety bugs identified as CVE-2018-5188. GNOME Shell (Ubuntu's default interface in Ubuntu 18.04 LTS) requires mozjs52. Nothing else in Ubuntu 18.04 LTS uses mozjs52. References -- https://www.mozilla.org/en-US/firefox/52.9.0/releasenotes/ https://www.mozilla.org/en-US/security/advisories/mfsa2018-17/ https://wiki.ubuntu.com/SecurityTeam/FAQ#mozjs Test Case - Install the update. Restart your computer. Log in and make sure the default desktop still works. Regression Potential This is a minor release in the long-term support series. I count about 6 cherry-picked targeted commits. Other Info -- I believe the version
[Desktop-packages] [Bug 1784633] Re: workspace side selector not properly rendered
** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/issues/457 + + --- + After upgrading Ubuntu to 18.04 the workspace selector, show on the side of the shell is not properly rendered. The panel takes the whole right side, independent from the number of workspaces I chose and the colored border around the active one is offset. The first time I open the shell the border highlight the proper box, the is set to the top left corner of the panel. I am attaching a picture showing the issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 31 09:57:01 2018 DisplayManager: gdm3 GsettingsChanges: - + InstallationDate: Installed on 2016-07-02 (758 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-07-24 (6 days ago) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1784633 Title: workspace side selector not properly rendered Status in gnome-shell package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/457 --- After upgrading Ubuntu to 18.04 the workspace selector, show on the side of the shell is not properly rendered. The panel takes the whole right side, independent from the number of workspaces I chose and the colored border around the active one is offset. The first time I open the shell the border highlight the proper box, the is set to the top left corner of the panel. I am attaching a picture showing the issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 31 09:57:01 2018 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2016-07-02 (758 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-07-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784850] Re: Xorg crashed with SIGABRT in Osabort
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: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => xorg-server (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/1784850 Title: Xorg crashed with SIGABRT in Osabort Status in xorg-server package in Ubuntu: Incomplete Bug description: Loading problem may be running since last upgrade ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 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: Wed Aug 1 14:43:42 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2018-01-25 (187 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. GA-MA78LMT-US2H ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=7658499f-b118-4175-baa0-7d52bfd45a1c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F9 dmi.board.name: GA-MA78LMT-US2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd08/09/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA78LMT-US2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA78LMT-US2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA78LMT-US2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Aug 1 14:10:00 2018 xserver.configfile: default xserver.errors: Wacom Graphire Pen stylus: Invalid type 'touch' for this device. Wacom Graphire Pen stylus: Invalid type 'pad' for this device. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1784850/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1774498] Re: Windows flash by external screen on workspace change
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-shell/issues/455 + + --- + gnome-shell has the very interesting default of only doing virtual desktops on the internal screen. This works fine but has a strange visual glitch when changing virtual desktops where the contents of the internal screen flash through the external one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:06:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1774498 Title: Windows flash by external screen on workspace change Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/455 --- gnome-shell has the very interesting default of only doing virtual desktops on the internal screen. This works fine but has a strange visual glitch when changing virtual desktops where the contents of the internal screen flash through the external one. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu May 31 21:06:47 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-31 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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/1774498/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
I can't reproduce this myself but I am using the default shell (bash provided by dash) and gnome-terminal. My understanding of the change to policykit-1 https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 is that previously the UID was supplied by the caller and used without validation - instead now policykit tries to validate the supplied UID against the actual UID of the subject - however this could change over time and is racy - so there are a bunch of failure modes which this change to policykit introduces which would previously have worked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
Looking at the diff between Ubuntu and upstream I noticed Ubuntu 0.105 code isn't adapted for "systemd --user" as described in https://bugs.freedesktop.org/show_bug.cgi?id=76358 and in the source for the function: polkit_backend_session_monitor_is_session_active() ** Bug watch added: freedesktop.org Bugzilla #76358 https://bugs.freedesktop.org/show_bug.cgi?id=76358 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial
This bug has been closed for over 2 years. If you have any ongoing problem then please open a new bug for it. -- 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/1549163 Title: Bluetooth headset HSP/HFP mode not working in Xenial Status in HWE Next: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: Using the 2/14 Xenial daily build, paired bluetooth headsets' do not work in HSP/HFP mode. [Steps to reproduce] 1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build 2. In the laptop, go to sound settings > output tab > try switching mode to HSP/HFP mode 3. Press the "test sound" button and try playing sound 4. Go to the input tab and check if bluetooth headset mic is listed [Expected result] After step 3, a window for mono audio test should pop up After step 4, the input tab should list a bluetooth headset mic device [Actual result] After step 3, the window that pops up is for stereo (A2DP) audio test After step 4, the input tab does not list any bluetooth headset mic [Details] BT wireless module: * Intel 3160 BT headset: * Jabra CLI Xenial: 2/14 daily build: * Kernel: 4.4.0-6 * bluez: 5.36-0ubuntu1 * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1 * pulseaudio: 1:8.0-0ubuntu2 * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2 [Note] Also double checked with same set of hardware, but with 15.10 installed. Bluetooth headset HSP/HFP mode worked correctly in 15.10. 15.10 details: * kernel: 4.2.0-19 * bluez: 5.35-0ubuntu2 * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1 * pulseaudio: 1:6.0-0ubuntu13 * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720820] Re: [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes.
Uninstalling gstreamer1.0-vaapi does not solve the issue for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1720820 Title: [radeon] Totem with gstreamer1.0-vaapi and Wayland is just a black screen, then crashes. Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: WORKAROUNDS Just for totem: sudo apt remove gstreamer1.0-vaapi Or to workaround in all players: sudo apt remove mesa-va-drivers ORIGINAL DESCRIPTION Totem with gstreamer1.0-vaapi and Wayland crashes on my machine with AMD Fury graphics card and open source drivers. Video output is just a black frame and crash happens within just a few seconds after video playback starts. Could not reproduce bug on two older Intel laptops with iGPU's where hardware acceleration seemed to work fine under Wayland. Issue is only present on Wayland, not x. I can get hardware accelerated video playback working on Wayland with 'mpv --hwdec=vaapi-copy --opengl-backend=wayland' but this is the only way I have found so far. Even in mpv, no other option than vaapi-copy works. gst-play-1.0 outputs the following error: ERROR Internal error: could not render surface for file:///*** ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1483): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 totem 3.25.90.1-0ubuntu3 gstreamer1.0-vaapi:amd641.12.3-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1720820/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
The quirk is more nuanced than I reported above. This reports groups correctly: 1. GUI login 2. Switch to TTY, login 3. "groups" 4. Switch to GUI 5. Launch Terminal 6. "groups" This only reports the username: 1. GUI Login 2. Launch Terminal 3. "groups" 4. Switch to TTY, login 5. "groups" Tests done with /usr/bin/tmux as the user's shell and tmux default-shell = /bin/bash which has been my standard configuration for several years now with no problems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
I've discovered another quirk: If my first log-in after booting is at the TTY console (not GUI) the groups show up correctly there *and* in a terminal in the Xorg GUI session afterwards. But if I first log-in to the GUI then log-in to the TTY console both show only the user group. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 399696] Re: default printer status as switched off in CUPS
Hello Krzysztof, Thank you for submitting this bug and reporting a problem with cups and printing. You made this bug report some time ago and Ubuntu has been updated since then. Could you confirm that this is no longer a problem and that we can close the ticket? If it is still a problem, are you still interested in finding a solution to this bug? If you are, could you let us know, and in the current version, run the following (only once): apport-collect BUGNUMBER and upload the updated logs and and any other logs that are relevant for this particular issue. Thank you again for helping make Ubuntu better. G ** Changed in: cups (Ubuntu) Status: New => Incomplete -- 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/399696 Title: default printer status as switched off in CUPS Status in cups package in Ubuntu: Incomplete Bug description: After turning on my printer its default status in CUPS is set to off and it doesn't print. The status is setting in context menu of the printer in 'system-config-printer'. If I manually switch this setting to on then all queued jobs are printed. Next, when I turn the printer off and on again the problem occurs - it has automatically 'switched off' status again. I'm not sure what is name for that setting in English, because I use another language. I've noticed after restarting CUPS server the problem doesn't occur. Printer: HP LaserJet P1005 Ubuntu version: 8.10 Intrepid up-to date (20090714) CUPS version: 1.3.9-2ubuntu9.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/399696/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784969] [NEW] upowerd segfaults over and over again.
Public bug reported: [392516.984355] upowerd[29614]: segfault at 8 ip 55e142176d50 sp 7ffe615a51e0 error 4 in upowerd[55e142156000+39000] [392542.249963] upowerd[29775]: segfault at 8 ip 55a107c1bd50 sp 7ffd1d444f80 error 4 in upowerd[55a107bfb000+39000] [392567.755465] upowerd[29946]: segfault at 8 ip 561edaf8cd50 sp 7ffe03101330 error 4 in upowerd[561edaf6c000+39000] [392592.998110] upowerd[30107]: segfault at 8 ip 558da7db8d50 sp 7fffbcfece90 error 4 in upowerd[558da7d98000+39000] [392618.233396] upowerd[30291]: segfault at 8 ip 5652ae549d50 sp 7ffdddb529b0 error 4 in upowerd[5652ae529000+39000] [392643.491371] upowerd[30732]: segfault at 8 ip 559c184dcd50 sp 7fffac9cd460 error 4 in upowerd[559c184bc000+39000] [392668.986076] upowerd[30945]: segfault at 8 ip 5569d2f0ad50 sp 7ffc0b9c03d0 error 4 in upowerd[5569d2eea000+39000] [392694.258076] upowerd[31245]: segfault at 8 ip 561c77151d50 sp 7fff74956fa0 error 4 in upowerd[561c77131000+39000] [392719.508055] upowerd[31409]: segfault at 8 ip 55d251c39d50 sp 7ffe514025c0 error 4 in upowerd[55d251c19000+39000] [392744.757247] upowerd[31569]: segfault at 8 ip 55fadf695d50 sp 7ffe581d4d10 error 4 in upowerd[55fadf675000+39000] [392770.004408] upowerd[31739]: segfault at 8 ip 55dce3cc1d50 sp 7ffe812efda0 error 4 in upowerd[55dce3ca1000+39000] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2 ProcVersionSignature: Ubuntu 4.15.0-26.28-lowlatency 4.15.18 Uname: Linux 4.15.0-26-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: MATE Date: Wed Aug 1 01:55:16 2018 SourcePackage: upower UpgradeStatus: Upgraded to bionic on 2018-07-04 (27 days ago) ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1784969 Title: upowerd segfaults over and over again. Status in upower package in Ubuntu: New Bug description: [392516.984355] upowerd[29614]: segfault at 8 ip 55e142176d50 sp 7ffe615a51e0 error 4 in upowerd[55e142156000+39000] [392542.249963] upowerd[29775]: segfault at 8 ip 55a107c1bd50 sp 7ffd1d444f80 error 4 in upowerd[55a107bfb000+39000] [392567.755465] upowerd[29946]: segfault at 8 ip 561edaf8cd50 sp 7ffe03101330 error 4 in upowerd[561edaf6c000+39000] [392592.998110] upowerd[30107]: segfault at 8 ip 558da7db8d50 sp 7fffbcfece90 error 4 in upowerd[558da7d98000+39000] [392618.233396] upowerd[30291]: segfault at 8 ip 5652ae549d50 sp 7ffdddb529b0 error 4 in upowerd[5652ae529000+39000] [392643.491371] upowerd[30732]: segfault at 8 ip 559c184dcd50 sp 7fffac9cd460 error 4 in upowerd[559c184bc000+39000] [392668.986076] upowerd[30945]: segfault at 8 ip 5569d2f0ad50 sp 7ffc0b9c03d0 error 4 in upowerd[5569d2eea000+39000] [392694.258076] upowerd[31245]: segfault at 8 ip 561c77151d50 sp 7fff74956fa0 error 4 in upowerd[561c77131000+39000] [392719.508055] upowerd[31409]: segfault at 8 ip 55d251c39d50 sp 7ffe514025c0 error 4 in upowerd[55d251c19000+39000] [392744.757247] upowerd[31569]: segfault at 8 ip 55fadf695d50 sp 7ffe581d4d10 error 4 in upowerd[55fadf675000+39000] [392770.004408] upowerd[31739]: segfault at 8 ip 55dce3cc1d50 sp 7ffe812efda0 error 4 in upowerd[55dce3ca1000+39000] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: upower 0.99.7-2 ProcVersionSignature: Ubuntu 4.15.0-26.28-lowlatency 4.15.18 Uname: Linux 4.15.0-26-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: MATE Date: Wed Aug 1 01:55:16 2018 SourcePackage: upower UpgradeStatus: Upgraded to bionic on 2018-07-04 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1784969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784894] Re: crashes
*** This bug is a duplicate of bug 1784883 *** https://bugs.launchpad.net/bugs/1784883 Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1784894 Title: crashes Status in xorg package in Ubuntu: Confirmed Bug description: Downloaded ubuntu more than a couple of times, still running into errors.When time is available please fix errors. Ubuntu team is very skilled and appreciated, you guys always get the work done. Thank you, hope to hear from you guys soon,have a great day, goodbye. -Richard Rios ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Wed Aug 1 09:05:17 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0763] Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X600/X600 SE] [1002:5b62] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X600/X600 SE] [1002:0602] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RV380 [Radeon X300/X550/X1050 Series] (Secondary) [1002:0603] InstallationDate: Installed on 2018-06-23 (39 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3668 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.4 dmi.board.name: 07KY25 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.4:bd06/20/2017:svnDellInc.:pnInspiron3668:pvr:rvnDellInc.:rn07KY25:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3668 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1784894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784894] Re: crashes
*** This bug is a duplicate of bug 1784883 *** https://bugs.launchpad.net/bugs/1784883 Please try to avoid creating duplicate bug reports for the same issue. -- 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/1784894 Title: crashes Status in xorg package in Ubuntu: Confirmed Bug description: Downloaded ubuntu more than a couple of times, still running into errors.When time is available please fix errors. Ubuntu team is very skilled and appreciated, you guys always get the work done. Thank you, hope to hear from you guys soon,have a great day, goodbye. -Richard Rios ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Wed Aug 1 09:05:17 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0763] Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X600/X600 SE] [1002:5b62] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X600/X600 SE] [1002:0602] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RV380 [Radeon X300/X550/X1050 Series] (Secondary) [1002:0603] InstallationDate: Installed on 2018-06-23 (39 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3668 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.4 dmi.board.name: 07KY25 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.4:bd06/20/2017:svnDellInc.:pnInspiron3668:pvr:rvnDellInc.:rn07KY25:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3668 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1784894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784894]
*** This bug is a duplicate of bug 1784883 *** https://bugs.launchpad.net/bugs/1784883 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1784883, so it 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. ** This bug has been marked a duplicate of bug 1784883 crashing -- 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/1784894 Title: crashes Status in xorg package in Ubuntu: Confirmed Bug description: Downloaded ubuntu more than a couple of times, still running into errors.When time is available please fix errors. Ubuntu team is very skilled and appreciated, you guys always get the work done. Thank you, hope to hear from you guys soon,have a great day, goodbye. -Richard Rios ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Wed Aug 1 09:05:17 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0763] Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X600/X600 SE] [1002:5b62] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X600/X600 SE] [1002:0602] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RV380 [Radeon X300/X550/X1050 Series] (Secondary) [1002:0603] InstallationDate: Installed on 2018-06-23 (39 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3668 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/20/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.4 dmi.board.name: 07KY25 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.4:bd06/20/2017:svnDellInc.:pnInspiron3668:pvr:rvnDellInc.:rn07KY25:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3668 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1784894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
journalctl shows the problem with the auid and session values being 0x (-1) when calling a sudo command: Aug 02 01:18:20 hephaestion.lan.iam.tj audit[5094]: USER_AUTH pid=5094 uid=1000 auid=4294967295 ses=4294967295 msg='op=PAM:authentication acct="tj" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/1 res=success' and trying to tail syslog: tj ~ tail -f /var/log/syslog tail: cannot open '/var/log/syslog' for reading: Permission denied tail: no files remaining tj ~ ls -ld /var /var/log /var/log/syslog drwxr-xr-x 16 root root 4096 Apr 2 13:02 /var drwxrwxr-x 25 root syslog 4096 Aug 2 01:16 /var/log -rw-r- 1 syslog adm235432 Aug 2 01:31 /var/log/syslog tj ~ groups $USER tj : tj root adm disk lp dialout cdrom floppy sudo audio video plugdev users netdev lpadmin kvm libvirtd wireshark lxd libvirtd tj ~ groups tj -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: policykit-1 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784892] Re: package tracker-extract 1.6.2-0ubuntu1.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo
Thank you for taking the time to file a bug report. This looks like a local issue that occurred during the time of upgrade. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: tracker (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1784892 Title: package tracker-extract 1.6.2-0ubuntu1.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in tracker package in Ubuntu: Incomplete Bug description: help ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tracker-extract 1.6.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Aug 1 12:00:52 2018 DpkgHistoryLog: Start-Date: 2018-08-01 12:00:30 Commandline: /usr/sbin/synaptic Requested-By: bruno (1000) Remove: gedit:amd64 (3.20.2-2ubuntu1~ubuntu16.04.1), eog:amd64 (3.18.2-1ubuntu2.1), rhythmbox-plugins:amd64 (3.3-1ubuntu7), rhythmbox-plugin-zeitgeist:amd64 (3.3-1ubuntu7), ubuntu-gnome-desktop:amd64 (0.58.3), rhythmbox-plugin-magnatune:amd64 (3.3-1ubuntu7) Purge: tracker-miner-fs:amd64 (1.8.3+really1.8.0-2ubuntu1~xenial4), gir1.2-peas-1.0:amd64 (1.18.0-3~ubuntu16.04.1), totem-plugins:amd64 (3.20.1-3ubuntu0~xenial2), gir1.2-totem-1.0:amd64 (3.20.1-3ubuntu0~xenial2) ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: tracker Title: package tracker-extract 1.6.2-0ubuntu1.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1784892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784892] Re: package tracker-extract 1.6.2-0ubuntu1.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1784892 Title: package tracker-extract 1.6.2-0ubuntu1.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in tracker package in Ubuntu: Incomplete Bug description: help ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tracker-extract 1.6.2-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Aug 1 12:00:52 2018 DpkgHistoryLog: Start-Date: 2018-08-01 12:00:30 Commandline: /usr/sbin/synaptic Requested-By: bruno (1000) Remove: gedit:amd64 (3.20.2-2ubuntu1~ubuntu16.04.1), eog:amd64 (3.18.2-1ubuntu2.1), rhythmbox-plugins:amd64 (3.3-1ubuntu7), rhythmbox-plugin-zeitgeist:amd64 (3.3-1ubuntu7), ubuntu-gnome-desktop:amd64 (0.58.3), rhythmbox-plugin-magnatune:amd64 (3.3-1ubuntu7) Purge: tracker-miner-fs:amd64 (1.8.3+really1.8.0-2ubuntu1~xenial4), gir1.2-peas-1.0:amd64 (1.18.0-3~ubuntu16.04.1), totem-plugins:amd64 (3.20.1-3ubuntu0~xenial2), gir1.2-totem-1.0:amd64 (3.20.1-3ubuntu0~xenial2) ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: tracker Title: package tracker-extract 1.6.2-0ubuntu1.1 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1784892/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
I observe what is likely the same problem on XUbuntu 16.04.5, running these commands in xfce4-terminal: user1@mysystem:~$ lsb_release -ds;cat /proc/version;echo $SHELL;groups;groups $(whoami) Ubuntu 16.04.5 LTS Linux version 4.15.0-29-generic (buildd@lcy01-amd64-024) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.10)) #31~16.04.1-Ubuntu SMP Wed Jul 18 08:54:04 UTC 2018 /bin/bash user1 user1 : user1 adm disk fax cdrom sudo dip plugdev users lxd lpadmin sambashare libvirtd vboxusers user1@mysystem:~$ ps f PID TTY STAT TIME COMMAND 3544 pts/2Ss 0:00 bash 3582 pts/2R+ 0:00 \_ ps f user1@mysystem:~$ cat /proc/3544/loginuid;echo 4294967295 Everything behaves correctly on tty1 or after sudo login + login as user1 on the terminal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784883]
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, 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, and 3. the behavior you actually encountered (in as much detail as possible). Thanks! -- 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/1784883 Title: crashing Status in xorg package in Ubuntu: Incomplete Bug description: the system keeps crashing i might not be downloading ubuntu right but i already reloaded like 10 times ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Wed Aug 1 07:46:20 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 405] [10de:10c5] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GT218 [GeForce 405] [1462:2298] InstallationDate: Installed on 2018-07-22 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pro 3500 Series ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.12 dmi.board.name: 2ABF dmi.board.vendor: Foxconn dmi.board.version: 3.10 dmi.chassis.asset.tag: MXL3010XFS dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.12:bd12/14/2012:svnHewlett-Packard:pnHPPro3500Series:pvr:rvnFoxconn:rn2ABF:rvr3.10:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Pro 3500 Series dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/xorg/+bug/1784883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784883] Re: crashing
I can see from the attached logs there are file-system errors (likely due to incomplete shutdowns in the past) but I am surprised by the presence of XFS and QNX file-system drivers both being loaded - can you describe this system in more details - also any details you can provide about the crash would be good - what do you see when it crashes? ** Changed in: xorg (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/1784883 Title: crashing Status in xorg package in Ubuntu: Incomplete Bug description: the system keeps crashing i might not be downloading ubuntu right but i already reloaded like 10 times ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Wed Aug 1 07:46:20 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 405] [10de:10c5] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GT218 [GeForce 405] [1462:2298] InstallationDate: Installed on 2018-07-22 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pro 3500 Series ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.12 dmi.board.name: 2ABF dmi.board.vendor: Foxconn dmi.board.version: 3.10 dmi.chassis.asset.tag: MXL3010XFS dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.12:bd12/14/2012:svnHewlett-Packard:pnHPPro3500Series:pvr:rvnFoxconn:rn2ABF:rvr3.10:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Pro 3500 Series dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/xorg/+bug/1784883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784883] Re: crashing
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1784883 Title: crashing Status in xorg package in Ubuntu: Incomplete Bug description: the system keeps crashing i might not be downloading ubuntu right but i already reloaded like 10 times ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None Date: Wed Aug 1 07:46:20 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 405] [10de:10c5] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GT218 [GeForce 405] [1462:2298] InstallationDate: Installed on 2018-07-22 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pro 3500 Series ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2012 dmi.bios.vendor: AMI dmi.bios.version: 8.12 dmi.board.name: 2ABF dmi.board.vendor: Foxconn dmi.board.version: 3.10 dmi.chassis.asset.tag: MXL3010XFS dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.12:bd12/14/2012:svnHewlett-Packard:pnHPPro3500Series:pvr:rvnFoxconn:rn2ABF:rvr3.10:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Pro 3500 Series dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A 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/xorg/+bug/1784883/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] Re: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
** Description changed: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. + + I also noticed Ubuntu is still based on version 0.105 which was released + in 2012 - upstream released 0.115 with the CVE patch. + + I suspect the backporting has missed something. + + The Ubuntu backport patch is: + + https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu + /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: Confirmed Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. I also noticed Ubuntu is still based on version 0.105 which was released in 2012 - upstream released 0.115 with the CVE patch. I suspect the backporting has missed something. The Ubuntu backport patch is: https://git.launchpad.net/ubuntu/+source/policykit-1/commit/?h=applied/ubuntu /bionic-devel=840c50182f5ab1ba28c1d20cce4c207364852935 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779637] Re: Password visible at login screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-screensaver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1779637 Title: Password visible at login screen Status in gnome-screensaver package in Ubuntu: Confirmed Bug description: We have a shared computer (2 user accounts) and I was surprised to find after screen lock that my password was visible when entering it to log back in. * Ubuntu 18.04 LTS / 18.04 * gdm 3.28.2-0ubuntu1.2 (I don't seem to have any packages matching screensaver, so GDM?) I expected: to see masked characters when entering my password I saw: my password visible on screen! I was not able to repeat the issue after a reboot. Checking "security" because that way security team gets to decide if this is really a vulnerability - sorry if that's turning the volume up a bit high, I won't be offended if you make it public straight away, but I'd rather you had the option than that I got it wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1779637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780501] Re: Traceback calling Vte.Terminal.feed_child()
This bug was fixed in the package ubuntu-release-upgrader - 1:18.10.6
---
ubuntu-release-upgrader (1:18.10.6) cosmic; urgency=medium
* DistUpgradeQuirks.py:
- make sure that snapd is installed before trying to use it.
(LP: #1783589)
- update the view with information regarding the progress of snaps being
installed. (LP: #1783593)
- when checking for connectivity to the snap store use C.UTF-8 for the
language so error message matching works. (LP: #1783738)
* DistUpgradeController.py:
- Remove debs from apt's "Dir::Cache::archives" folder after the upgrade
has completed successfully.
- Add a telemetry marker to report the time to process migration from deb
to snaps.
* DistUpgrade/DistUpgradeViewGtk3.py: call vte's terminal.feed_child() with
the correct parameters thereby fixing a crash. (LP: #1780501)
-- Brian Murray Wed, 01 Aug 2018 15:06:53 -0700
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1780501
Title:
Traceback calling Vte.Terminal.feed_child()
Status in ubuntu-release-upgrader package in Ubuntu:
Fix Released
Status in vte2.91 package in Ubuntu:
Won't Fix
Status in ubuntu-release-upgrader source package in Bionic:
Invalid
Status in vte2.91 source package in Bionic:
Fix Committed
Bug description:
[Test Case]
1) Ensure the following packages from -updates (version
0.52.2-1ubuntu1~18.04.1) are installed on an Ubuntu 18.04 system:
gir1.2-vte-2.91 libvte-2.91-0 libvte-2.91-common
2) Modify /etc/issue e.g. I changed 18.04 to 18.04.2
3) Ensure /etc/update-manager/release-upgrades contains "Prompt=normal"
4) Run /usr/lib/ubuntu-release-upgrader/check-new-release-gtk -d
5) When prompted about replacing "the customized configuration file
'/etc/issue'" click Keep
6) Observe a traceback in Vte.Terminal.feed_child()
After installing the new version of vte2.91 in -proposed you should no
longer receive a Traceback when clicking keep during the upgrade
process.
[Regression Potential]
Per laney: "The regression potential is that I messed up the upload and
everything using feed* breaks."
It'd probably be good to test guake too since it uses feed_child().
[Original Description]
I was upgrading from Bionic to Cosmic when I received a conffile prompt
regarding /etc/update-initramfs/initramfs.conf, I clicked keep and then saw
this Traceback:
Original exception was:
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-filpk342/cosmic", line 8, in
sys.exit(main())
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeMain.py", line
238, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py",
line 1949, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py",
line 1912, in fullUpgrade
if not self.doDistUpgrade():
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py",
line 1248, in doDistUpgrade
res = self.cache.commit(fprogress,iprogress)
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeCache.py", line
293, in commit
apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 606, in commit
pm = apt_pkg.PackageManager(self._depcache)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 569, in
install_archives
# compat with older API
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeView.py", line
229, in run
res = os.WEXITSTATUS(self.wait_child())
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py",
line 340, in wait_child
self.update_interface()
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py",
line 347, in update_interface
InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 252, in
update_interface
if err.errno != errno.EAGAIN and err.errno != errno.EWOULDBLOCK:
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py",
line 276, in conffile
self.term.feed_child("n\n", -1)
TypeError: Vte.Terminal.feed_child() takes exactly 2 arguments (3 given)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780501/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784965] [NEW] EOG hangs when loading a (possibly corrupted) jpg file
Public bug reported: When I load the attached image in EOG, it uses gigs of memory, gets corrupted window decorations, and makes some mouse input in gnome-shell not work. Chrome and the Mac photo viewer load the image and don't bring the system to its knees. ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Testing border/crop tool in new Polarr" https://bugs.launchpad.net/bugs/1784965/+attachment/5170604/+files/ales-krivec-107499.jpg -- 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/1784965 Title: EOG hangs when loading a (possibly corrupted) jpg file Status in eog package in Ubuntu: New Bug description: When I load the attached image in EOG, it uses gigs of memory, gets corrupted window decorations, and makes some mouse input in gnome- shell not work. Chrome and the Mac photo viewer load the image and don't bring the system to its knees. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1784965/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784964] [NEW] Regression due to CVE-2018-1116 (processes not inheriting user ID or groups )
Public bug reported: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1784964 Title: Regression due to CVE-2018-1116 (processes not inheriting user ID or groups ) Status in policykit-1 package in Ubuntu: New Bug description: This report is tracking a possible regression caused by the recent CVE-2018-1116 patches to policykit-1. On 18.04, since package upgrades on July 23rd, and after the first reboot since then on Aug 1st, I hit an issue with the primary (sudo, adm, etc...) user getting Permission Denied trying to do: tail -f /var/log/syslog when that file is owned by syslog:adm and is g=r. I then found that "groups" reports only the $USER and not the entire list, but "groups $USER" reports all the groups correctly. The user shell is set to /usr/bin/tmux and /etc/tmux.conf has "set -g default-shell /bin/bash" After changing the user's shell back to /bin/bash and logging in on tty1 the list of groups shows correctly for the /bin/bash process running on tty1. I investigated and found that for the affected processes, such as the tmux process, /proc/$PID/loginuid = 4294967295 whereas the /bin/bash process on tty1 correctly reported 1000. The same with the respective gid_map and uid_map. 4294967295 == -1 == 0x The recent CVE patch to policykit has several functions where it does "uid = -1" which seems to tie in to my findings so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1784964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782614] Re: Upgrade to 3.28.3 and SRU it
Robie, Yes, I'd go directly with 3.28.3-0ubuntu0.18.04.2, actually we've also a .3 ready, so probably we could go with that too. Bug #1783363 never hit bionic, the fix was just applied to cosmic, so no need to SRU it. debian/patches/workspace-fix-repositioned-windows-in-activities.patch was already present in ubuntu, we just refreshed it with some minor changes as per upstream review. But nothing changed in behavior. -- 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/1782614 Title: Upgrade to 3.28.3 and SRU it Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Bug description: [ Description ] The third stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been fixed, VPN fixes so network related featurs should be checked more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1782614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1784690] Re: package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
This issue goes back to when you could use guest mode, but guest mode developed this issue so you have these large number of groups causing this error message. Can't you test and package the following solution into the operating system and de-bug it: https://askubuntu.com/questions/979467/esoteric-error-logs-in- ubuntu-17-10 On 8/1/18, Alex Murray wrote: > It failed to install since there was no available group ID to create: > > addgroup: No GID is available in the range 100-999 (FIRST_SYS_GID - > LAST_SYS_GID). > addgroup: The group `geoclue' was not created. > > Have you got a large number of groups in your system? > > ** Information type changed from Private Security to Public > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1784690 > > Title: > package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: > subprocess installed post-installation script returned error exit > status 1 > > Status in geoclue-2.0 package in Ubuntu: > New > > Bug description: > Crash report generated > > ProblemType: Package > DistroRelease: Ubuntu 17.10 > Package: geoclue-2.0 2.4.7-1ubuntu1 > ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16 > Uname: Linux 4.13.0-46-generic i686 > ApportVersion: 2.20.7-0ubuntu3.9 > Architecture: i386 > Date: Wed Jul 25 07:45:26 2018 > ErrorMessage: subprocess installed post-installation script returned error > exit status 1 > InstallationDate: Installed on 2015-10-19 (1016 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 > (20140417) > Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, > 3.6.3-0ubuntu3 > PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, > 2.7.14-2ubuntu1 > RelatedPackageVersions: >dpkg 1.18.24ubuntu1 >apt 1.5.2 > SourcePackage: geoclue-2.0 > Title: package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: > subprocess installed post-installation script returned error exit status 1 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1784690/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1784690 Title: package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in geoclue-2.0 package in Ubuntu: New Bug description: Crash report generated ProblemType: Package DistroRelease: Ubuntu 17.10 Package: geoclue-2.0 2.4.7-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16 Uname: Linux 4.13.0-46-generic i686 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 Date: Wed Jul 25 07:45:26 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-10-19 (1016 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu3 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.2 SourcePackage: geoclue-2.0 Title: package geoclue-2.0 2.4.7-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1784690/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial
Same issue on 18.04 Kubuntu, Gnome and KDE Neon -- 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/1549163 Title: Bluetooth headset HSP/HFP mode not working in Xenial Status in HWE Next: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: Using the 2/14 Xenial daily build, paired bluetooth headsets' do not work in HSP/HFP mode. [Steps to reproduce] 1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build 2. In the laptop, go to sound settings > output tab > try switching mode to HSP/HFP mode 3. Press the "test sound" button and try playing sound 4. Go to the input tab and check if bluetooth headset mic is listed [Expected result] After step 3, a window for mono audio test should pop up After step 4, the input tab should list a bluetooth headset mic device [Actual result] After step 3, the window that pops up is for stereo (A2DP) audio test After step 4, the input tab does not list any bluetooth headset mic [Details] BT wireless module: * Intel 3160 BT headset: * Jabra CLI Xenial: 2/14 daily build: * Kernel: 4.4.0-6 * bluez: 5.36-0ubuntu1 * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1 * pulseaudio: 1:8.0-0ubuntu2 * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2 [Note] Also double checked with same set of hardware, but with 15.10 installed. Bluetooth headset HSP/HFP mode worked correctly in 15.10. 15.10 details: * kernel: 4.2.0-19 * bluez: 5.35-0ubuntu2 * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1 * pulseaudio: 1:6.0-0ubuntu13 * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782614] Re: Upgrade to 3.28.3 and SRU it
For Bionic: Shouldn't this be 3.28.3-0ubuntu0.18.04.1 directly, rather than 3.28.3-0ubuntu0.18.04.1 then 3.28.3-0ubuntu0.18.04.2? Missing Launchpad-Bugs-Fixed field in changes file. Did you use Ubuntu or set vendor to Ubuntu if on Debian? Please re-upload with that. Bugs like bug 1783363 appear to be missing SRU paperwork. Please fix (or tell me why not necessary) before re-uploading. Doesn't debian/patches/workspace-fix-repositioned-windows-in- activities.patch need a bug and SRU paperwork? AIUI, GNOME packages in Ubuntu have an exception for upstream microreleases (as QA'd by upstream) and not for cherry-picks. -- 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/1782614 Title: Upgrade to 3.28.3 and SRU it Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: In Progress Bug description: [ Description ] The third stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been fixed, VPN fixes so network related featurs should be checked more To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1782614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1783311] Re: Upgrade to 3.28.3 and SRU it
Hello Marco, or anyone else affected, Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3-1~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: mutter (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1783311 Title: Upgrade to 3.28.3 and SRU it Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Committed Bug description: [ Description ] The third stable release in the 3.28 series. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been fixed, some changes to the monitor management, so changing settings there should be tested deeply. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1783311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784954] [NEW] Intel hd 620 graphics driver not working
Public bug reported: the graphics driver for intel HD 620 is not working. Very poor graphics from what I had in windows.My processor is i5 7200u. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 04:05:32 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1094] InstallationDate: Installed on 2018-08-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b573 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=6078e205-6c45-4def-8d68-f24e9f29b526 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.20:bd12/13/2016:svnAcer:pnAspireE5-575:pvrV1.20:rvnAcer:rnIronman_SK:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575 dmi.product.version: V1.20 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1784954 Title: Intel hd 620 graphics driver not working Status in xorg package in Ubuntu: New Bug description: the graphics driver for intel HD 620 is not working. Very poor graphics from what I had in windows.My processor is i5 7200u. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 2 04:05:32 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1094] InstallationDate: Installed on 2018-08-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b573 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=6078e205-6c45-4def-8d68-f24e9f29b526 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.20:bd12/13/2016:svnAcer:pnAspireE5-575:pvrV1.20:rvnAcer:rnIronman_SK:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: KBL dmi.product.name: Aspire E5-575 dmi.product.version: V1.20
[Desktop-packages] [Bug 955011] Re: HTML bookmarks file from other browser is not shown in file dialog
Thanks. Closing as "Invalid" as bug was never confirmed. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Invalid -- 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/955011 Title: HTML bookmarks file from other browser is not shown in file dialog Status in chromium-browser package in Ubuntu: Invalid Bug description: I tried importing my bookmarks from Firefox. I export the bookmarks into an HTML file through the firefox dialog and place it in a folder. In Chrome/Chromium I navigate to the bookmark manager and choose "Import from HTML file" in the resulting file dialog the dropdown menu is restricted to "application/x-extension-html". This will not allow me to select any files at all let alone the desired html file. Expected behavior: I should be able to select the html file generated by another piece of software and have the contained bookmarks imported into Chrome/Chromium Actual behavior: Can not select any html file to import at all. Impossible to import bookmarks any way since the import browser data function is broken as well. Steps to reproduce: 1. Export bookmarks to HTML file from another browser 2. Open Bookmarks Manager 3. Select "Import from HTML file" in the Organize menu 4. Can not select html file in the file dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/955011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780442] Re: Please backport fix for & in attributes
It needs to go through the SRU process (https://wiki.ubuntu.com/StableReleaseUpdates) which can take a few weeks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1780442 Title: Please backport fix for & in attributes Status in Fwupd: New Status in appstream-glib package in Ubuntu: Fix Released Status in appstream-glib source package in Xenial: Fix Committed Bug description: [Impact] There are instances of fwupd being unable to run updates on certain devices on Ubuntu 16.04. due to a "&" in metadata. [Test Case] * Try to perform an update on a 8bitdo affected device. [Regression Potential] * Regressions would occur in metadata processing where the fwupd daemon wouldn't be able to process it. [Other Info] This was discussed here: https://github.com/hughsie/fwupd/issues/565#issuecomment-402534337 This has been fixed in appstream-glib to prevent & in the metadata. This fix is already in 18.04 and just needs to be backported to 16.04. https://github.com/hughsie/appstream-glib/commit/6048520484101df5d33f3c852c10640e630d20cf To manage notifications about this bug go to: https://bugs.launchpad.net/fwupd/+bug/1780442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781826] Re: System logout when turn off the screen or suspend Ubuntu 18.04
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1781826 Title: System logout when turn off the screen or suspend Ubuntu 18.04 Status in gnome-shell package in Ubuntu: New Bug description: When turn off the screen or suspend, and resume the system is logged out, this mostly happens with nvidia driver (390 or 396). I noticed that when close the lid and reopen the system is still working and all of a sudden it appears a login screen and when login all programs as killed as it was logged out. And most of times after login it locks and prompts an unlock screen. I tried to switch to nouveau driver and the problem seems not to happen, but that leaves me with a poor performance in terms of graphics. I tried to reset the setting in dconf using dconf-editor to reset the system recursively, at the beginning seems to be solved but it gets back. I need to mention that I faced the same problem when using budgie flavor, I thought that it might be a budgie problem but it appears to be a gnome problem since budgie is based on gnome and on both the problem happens when using Nvidia drivers. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 955011] Re: HTML bookmarks file from other browser is not shown in file dialog
Just close this. Six years and a complete Firefox rebuild later I have no way to verify if this still applies. -- 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/955011 Title: HTML bookmarks file from other browser is not shown in file dialog Status in chromium-browser package in Ubuntu: Incomplete Bug description: I tried importing my bookmarks from Firefox. I export the bookmarks into an HTML file through the firefox dialog and place it in a folder. In Chrome/Chromium I navigate to the bookmark manager and choose "Import from HTML file" in the resulting file dialog the dropdown menu is restricted to "application/x-extension-html". This will not allow me to select any files at all let alone the desired html file. Expected behavior: I should be able to select the html file generated by another piece of software and have the contained bookmarks imported into Chrome/Chromium Actual behavior: Can not select any html file to import at all. Impossible to import bookmarks any way since the import browser data function is broken as well. Steps to reproduce: 1. Export bookmarks to HTML file from another browser 2. Open Bookmarks Manager 3. Select "Import from HTML file" in the Organize menu 4. Can not select html file in the file dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/955011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765799] Please test proposed package
Hello João, or anyone else affected, Accepted gnome-menus into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- menus/3.13.3-11ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1765799 Title: Applications menu does not get populated with recently installed apps using apt Status in gnome-menus package in Ubuntu: Fix Released Status in gnome-menus source package in Bionic: Fix Committed Bug description: [Impact] Applications menu for GNOME3 based desktop environments doesn't get populated with recently installed app using apt or GUI apps like gnome-software, budgie-welcome (Ubuntu Budgie) Users need to physically logout and login again before they see the application appear in their menu. This is an intermittent issue - some installs work correctly, some installs dont display in the menu. After logging out and logging in, those installs that didnt display, now appear in the menu. This affects all desktop environments that use gnome-menus to recognise new/changed/deleted applications. Primarily this would be Unity and Budgie Desktop. Not sure about GNOME Shell or other desktop environments [Test Case] Install an application using apt (command line), GNOME Software or through budgie-welcome (Ubuntu Budgie only) - The application icon should appear in the menu of the desktop environment being used. Remove an application through apt, GNOME Software and/or budgie- welcome (ubuntu budgie) - The application icon should disappear from the menu of the desktop environment being used Repeat the above two test cases several times (e.g. 10x) with different applications [Regression Potential] Arguably the risk is that the patch introduces potential instability into the installation sequence that could cause crashes. That's the worst case scenario. The mitigation here is that the patch is the exact same patch used in 17.04 and 17.10. It was also used in 16.04 and 16.10 - in these two cases the patch did not contain a one line fix introduced in 17.04 that fixed a crashing race issue in budgie-desktop. [Other Info] Consultation with the uploader to 18.04 (Jeremy) is a must here to discuss possibly reasons why when merging with Debian, the ubuntu specific patch was not readded. Below is the original description Applications menu doesn't get populated with recently installed app using apt. For example, after installing Firefox using apt, its shortcut does not appear immediately in the applications main menu. It only appeared there after I rebooted (maybe logging off also does the job). A “refresh menu” action has to be triggered somehow after installations. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Apr 20 18:39:49 2018 Dependencies: InstallationDate: Installed on 2018-04-20 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180418) SourcePackage: gnome-menus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1765799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765799] Re: Applications menu does not get populated with recently installed apps using apt
Unsubscribing ~ubuntu-sponsors. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1765799 Title: Applications menu does not get populated with recently installed apps using apt Status in gnome-menus package in Ubuntu: Fix Released Status in gnome-menus source package in Bionic: Fix Committed Bug description: [Impact] Applications menu for GNOME3 based desktop environments doesn't get populated with recently installed app using apt or GUI apps like gnome-software, budgie-welcome (Ubuntu Budgie) Users need to physically logout and login again before they see the application appear in their menu. This is an intermittent issue - some installs work correctly, some installs dont display in the menu. After logging out and logging in, those installs that didnt display, now appear in the menu. This affects all desktop environments that use gnome-menus to recognise new/changed/deleted applications. Primarily this would be Unity and Budgie Desktop. Not sure about GNOME Shell or other desktop environments [Test Case] Install an application using apt (command line), GNOME Software or through budgie-welcome (Ubuntu Budgie only) - The application icon should appear in the menu of the desktop environment being used. Remove an application through apt, GNOME Software and/or budgie- welcome (ubuntu budgie) - The application icon should disappear from the menu of the desktop environment being used Repeat the above two test cases several times (e.g. 10x) with different applications [Regression Potential] Arguably the risk is that the patch introduces potential instability into the installation sequence that could cause crashes. That's the worst case scenario. The mitigation here is that the patch is the exact same patch used in 17.04 and 17.10. It was also used in 16.04 and 16.10 - in these two cases the patch did not contain a one line fix introduced in 17.04 that fixed a crashing race issue in budgie-desktop. [Other Info] Consultation with the uploader to 18.04 (Jeremy) is a must here to discuss possibly reasons why when merging with Debian, the ubuntu specific patch was not readded. Below is the original description Applications menu doesn't get populated with recently installed app using apt. For example, after installing Firefox using apt, its shortcut does not appear immediately in the applications main menu. It only appeared there after I rebooted (maybe logging off also does the job). A “refresh menu” action has to be triggered somehow after installations. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Apr 20 18:39:49 2018 Dependencies: InstallationDate: Installed on 2018-04-20 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180418) SourcePackage: gnome-menus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1765799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765799] Re: Applications menu does not get populated with recently installed apps using apt
> Tested this extensively in budgie - installing/removing repeatedly via gnome-software, budgie-welcome, command line. Works everytime. Thank you for treating this carefully. ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1765799 Title: Applications menu does not get populated with recently installed apps using apt Status in gnome-menus package in Ubuntu: Fix Released Status in gnome-menus source package in Bionic: Fix Committed Bug description: [Impact] Applications menu for GNOME3 based desktop environments doesn't get populated with recently installed app using apt or GUI apps like gnome-software, budgie-welcome (Ubuntu Budgie) Users need to physically logout and login again before they see the application appear in their menu. This is an intermittent issue - some installs work correctly, some installs dont display in the menu. After logging out and logging in, those installs that didnt display, now appear in the menu. This affects all desktop environments that use gnome-menus to recognise new/changed/deleted applications. Primarily this would be Unity and Budgie Desktop. Not sure about GNOME Shell or other desktop environments [Test Case] Install an application using apt (command line), GNOME Software or through budgie-welcome (Ubuntu Budgie only) - The application icon should appear in the menu of the desktop environment being used. Remove an application through apt, GNOME Software and/or budgie- welcome (ubuntu budgie) - The application icon should disappear from the menu of the desktop environment being used Repeat the above two test cases several times (e.g. 10x) with different applications [Regression Potential] Arguably the risk is that the patch introduces potential instability into the installation sequence that could cause crashes. That's the worst case scenario. The mitigation here is that the patch is the exact same patch used in 17.04 and 17.10. It was also used in 16.04 and 16.10 - in these two cases the patch did not contain a one line fix introduced in 17.04 that fixed a crashing race issue in budgie-desktop. [Other Info] Consultation with the uploader to 18.04 (Jeremy) is a must here to discuss possibly reasons why when merging with Debian, the ubuntu specific patch was not readded. Below is the original description Applications menu doesn't get populated with recently installed app using apt. For example, after installing Firefox using apt, its shortcut does not appear immediately in the applications main menu. It only appeared there after I rebooted (maybe logging off also does the job). A “refresh menu” action has to be triggered somehow after installations. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-menus 3.13.3-11ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Apr 20 18:39:49 2018 Dependencies: InstallationDate: Installed on 2018-04-20 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180418) SourcePackage: gnome-menus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1765799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1780501] Re: Traceback calling Vte.Terminal.feed_child()
** Branch linked: lp:ubuntu-release-upgrader
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1780501
Title:
Traceback calling Vte.Terminal.feed_child()
Status in ubuntu-release-upgrader package in Ubuntu:
In Progress
Status in vte2.91 package in Ubuntu:
Won't Fix
Status in ubuntu-release-upgrader source package in Bionic:
Invalid
Status in vte2.91 source package in Bionic:
Fix Committed
Bug description:
[Test Case]
1) Ensure the following packages from -updates (version
0.52.2-1ubuntu1~18.04.1) are installed on an Ubuntu 18.04 system:
gir1.2-vte-2.91 libvte-2.91-0 libvte-2.91-common
2) Modify /etc/issue e.g. I changed 18.04 to 18.04.2
3) Ensure /etc/update-manager/release-upgrades contains "Prompt=normal"
4) Run /usr/lib/ubuntu-release-upgrader/check-new-release-gtk -d
5) When prompted about replacing "the customized configuration file
'/etc/issue'" click Keep
6) Observe a traceback in Vte.Terminal.feed_child()
After installing the new version of vte2.91 in -proposed you should no
longer receive a Traceback when clicking keep during the upgrade
process.
[Regression Potential]
Per laney: "The regression potential is that I messed up the upload and
everything using feed* breaks."
It'd probably be good to test guake too since it uses feed_child().
[Original Description]
I was upgrading from Bionic to Cosmic when I received a conffile prompt
regarding /etc/update-initramfs/initramfs.conf, I clicked keep and then saw
this Traceback:
Original exception was:
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-filpk342/cosmic", line 8, in
sys.exit(main())
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeMain.py", line
238, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py",
line 1949, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py",
line 1912, in fullUpgrade
if not self.doDistUpgrade():
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py",
line 1248, in doDistUpgrade
res = self.cache.commit(fprogress,iprogress)
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeCache.py", line
293, in commit
apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 606, in commit
pm = apt_pkg.PackageManager(self._depcache)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 569, in
install_archives
# compat with older API
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeView.py", line
229, in run
res = os.WEXITSTATUS(self.wait_child())
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py",
line 340, in wait_child
self.update_interface()
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py",
line 347, in update_interface
InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 252, in
update_interface
if err.errno != errno.EAGAIN and err.errno != errno.EWOULDBLOCK:
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py",
line 276, in conffile
self.term.feed_child("n\n", -1)
TypeError: Vte.Terminal.feed_child() takes exactly 2 arguments (3 given)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780501/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778160] Re: /usr/bin/gnome-software:11:g_type_check_instance:g_signal_emit_valist:g_signal_emit:g_closure_invoke:signal_emit_unlocked_R
> Asked on forum if anyone knows a suitable snap to test this: https://forum.snapcraft.io/t/searching-for-a-snap-that-has-a-plug-with-multiple-slots Looks like you got an answer there on how to reproduce? Accepting for now, but please verify using that method (or by finding the culprit snap that causes user crashes) for SRU verification. ** Tags added: verification-needed verification-needed-bionic -- 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/1778160 Title: /usr/bin/gnome- software:11:g_type_check_instance:g_signal_emit_valist:g_signal_emit:g_closure_invoke:signal_emit_unlocked_R Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Configuring the permissions for a snap that has a plug that can connect to multiple slots causes a crash: https://errors.ubuntu.com/problem/46232e57fbbc469ce3e5f5c0f12bc24f95cd27c6 [Test Case] 1. Open GNOME Software 2. Search for and install TBD snap 3. Open Permissions dialog 4. Toggle TBD permission that uses a combo box Expected result: Permission is changed Observed result: GNOME Software crashes [Regression Potential] Fix is to rename a signal to avoid a name collision, low chance of introducing new bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1778160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778160] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1778160 Title: /usr/bin/gnome- software:11:g_type_check_instance:g_signal_emit_valist:g_signal_emit:g_closure_invoke:signal_emit_unlocked_R Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Configuring the permissions for a snap that has a plug that can connect to multiple slots causes a crash: https://errors.ubuntu.com/problem/46232e57fbbc469ce3e5f5c0f12bc24f95cd27c6 [Test Case] 1. Open GNOME Software 2. Search for and install TBD snap 3. Open Permissions dialog 4. Toggle TBD permission that uses a combo box Expected result: Permission is changed Observed result: GNOME Software crashes [Regression Potential] Fix is to rename a signal to avoid a name collision, low chance of introducing new bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1778160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778160] Re: /usr/bin/gnome-software:11:g_type_check_instance:g_signal_emit_valist:g_signal_emit:g_closure_invoke:signal_emit_unlocked_R
> [Regression Potential] Fix is to rename a signal to avoid a name collision, low chance of introducing new bugs. Please update that to inform testers where to look for new bugs if the change does happen to introduce any. -- 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/1778160 Title: /usr/bin/gnome- software:11:g_type_check_instance:g_signal_emit_valist:g_signal_emit:g_closure_invoke:signal_emit_unlocked_R Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Configuring the permissions for a snap that has a plug that can connect to multiple slots causes a crash: https://errors.ubuntu.com/problem/46232e57fbbc469ce3e5f5c0f12bc24f95cd27c6 [Test Case] 1. Open GNOME Software 2. Search for and install TBD snap 3. Open Permissions dialog 4. Toggle TBD permission that uses a combo box Expected result: Permission is changed Observed result: GNOME Software crashes [Regression Potential] Fix is to rename a signal to avoid a name collision, low chance of introducing new bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1778160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1781996] Re: /usr/bin/gnome-software:11:g_date_time_to_instant:g_date_time_to_unix:gs_plugin_refine_app:gs_plugin_loader_call_vfunc:gs_plugin_loader_run_refine_filter
Hello errors.ubuntu.com, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Also affects: gnome-software (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: gnome-software (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- 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/1781996 Title: /usr/bin/gnome- software:11:g_date_time_to_instant:g_date_time_to_unix:gs_plugin_refine_app:gs_plugin_loader_call_vfunc:gs_plugin_loader_run_refine_filter Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Fix Committed Bug description: * Impact gnome-software segfaults in the snap handling code in some cases * Test case No specific steps to test but look at the error reports, there should be no entry for the next version * Regression potential The code is just changing the installation date info, check that this one is still rightly displayed for most snaps -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.29.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/736dd4ead394ce3227125f661809e20472d3444c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1781996/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1024129] Re: I have no cursor...again
Thanks. Closing as "Invalid" as cause of issue was never confirmed. ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- 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/1024129 Title: I have no cursor...again Status in firefox package in Ubuntu: Invalid Bug description: I have no cursor...again. I was able to copy and paste from a word document. This happens every time there is an update. Isn't there something you guys can do about this? It is extremely annoying and frustrating. I may have to give up using Linux because doing school work has become a nightmare using your system. As much as I love Linux the frustrations is beginning to become unbearable. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: firefox 13.0.1+build1-0ubuntu0.11.10.1 ProcVersionSignature: Ubuntu 3.0.0-22.36-generic 3.0.33 Uname: Linux 3.0.0-22-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wanda 1598 F pulseaudio /dev/snd/controlC1: wanda 1598 F pulseaudio BuildID: 20120615085229 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'VT82xx'/'HDA VIA VT82xx at 0xbfffc000 irq 17' Mixer name : 'Realtek ALC883' Components : 'HDA:10ec0883,14627253,0012' Controls : 34 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'U0x46d0x9a1'/'USB Device 0x46d:0x9a1 at usb-:00:10.4-1, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:09a1' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 3072 Mono: Capture 870 [28%] [21.39dB] [on] Channel: release Date: Thu Jul 12 18:11:57 2012 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 192.168.1.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=13.0.1/20120615085229 (In use) RelatedPackageVersions: rhythmbox-plugins 2.90.1~20110908-0ubuntu1.4 google-talkplugin 3.1.4.0-1 icedtea-plugin1.1.3-1ubuntu1.1 totem-mozilla 3.0.1-0ubuntu7.1 RfKill: RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to oneiric on 2011-11-28 (227 days ago) dmi.bios.date: 03/06/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: V1.8 dmi.board.name: MS-7253 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrV1.8:bd03/06/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7253:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7253:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr: dmi.product.name: MS-7253 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1024129/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 881016] Re: Computer running very "choppy" since the last update.
Thanks. Closing as "Invalid" as bug was never in confirmed status. ** Changed in: firefox (Ubuntu) Status: Incomplete => Invalid -- 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/881016 Title: Computer running very "choppy" since the last update. Status in firefox package in Ubuntu: Invalid Bug description: Since the last update, my computer has been running very sluggish. There is a delay when I type, pages don't scroll, pages are taking longer to load, links click and open right away, and the processor sounds like it's racing. There is sometimes a delay when switching between windows. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 7.0.1+build1+nobinonly-0ubuntu0.11.04.1 ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 Uname: Linux 2.6.38-11-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wanda 1293 F pulseaudio /dev/snd/controlC1: wanda 1293 F pulseaudio BuildID: 20110928224508 CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'VT82xx'/'HDA VIA VT82xx at 0xbfffc000 irq 17' Mixer name : 'Realtek ALC883' Components : 'HDA:10ec0883,14627253,0012' Controls : 33 Simple ctrls : 19 Card1.Amixer.info: Card hw:1 'U0x46d0x9a1'/'USB Device 0x46d:0x9a1 at usb-:00:10.4-4, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:09a1' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 3072 Mono: Capture 870 [28%] [21.39dB] [on] Channel: release Date: Mon Oct 24 14:10:51 2011 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.27 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 default via 192.168.1.1 dev eth0 proto static IwConfig: lono wireless extensions. eth0 no wireless extensions. ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=7.0.1/20110928224508 (Running) RfKill: RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: V1.8 dmi.board.name: MS-7253 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrV1.8:bd03/06/2008:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7253:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7253:rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr: dmi.product.name: MS-7253 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/881016/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()
Anyone affected here who can provide a full jouralctl log? -- 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/1702151 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/ada10af9bce533d2cce9447f055123b325fd6c1d --- Todays update had a kernal and my gnome shell update. Happened when I rebooted. I now have a black screen and no panel. Icons are all that shows up on desktop. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu7 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 3 12:46:31 2017 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: gnome-shell --sm-client-id 102c52716a25d9b2dd1495780366603150001329 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9bec254d5c : movzbl 0x14(%rax),%edx PC (0x7f9bec254d5c) ok source "0x14(%rax)" (0x20706f746b736558) not located in a known VMA region (needed readable region)! destination "%edx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 st_theme_get_custom_stylesheets () from /usr/lib/gnome-shell/libgnome-shell.so ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() 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/gnome-shell/+bug/1702151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 881016] Re: Computer running very "choppy" since the last update.
I no longer have this issue. This bug can be closed. Thank you. On Mon, Jul 30, 2018 at 10:31 AM, Paul White <881...@bugs.launchpad.net> wrote: > WLB, > > We are sorry that we do not always have the capacity to review all > reported bugs in a timely manner. You reported this bug some time ago > and there have been many changes in Ubuntu since that time. > > Presumably this problem was a one time occurrence and/or is no longer an > issue? Can this bug report now be closed? > > If we do not hear from you the bug report will close itself in > approximately 60 days time. > > Thank you for helping make Ubuntu better. > > Paul White > [Ubuntu Bug Squad] > > ** Changed in: firefox (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/881016 > > Title: > Computer running very "choppy" since the last update. > > Status in firefox package in Ubuntu: > Incomplete > > Bug description: > Since the last update, my computer has been running very sluggish. > There is a delay when I type, pages don't scroll, pages are taking > longer to load, links click and open right away, and the processor > sounds like it's racing. There is sometimes a delay when switching > between windows. > > ProblemType: Bug > DistroRelease: Ubuntu 11.04 > Package: firefox 7.0.1+build1+nobinonly-0ubuntu0.11.04.1 > ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8 > Uname: Linux 2.6.38-11-generic x86_64 > NonfreeKernelModules: nvidia > AddonCompatCheckDisabled: False > AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: wanda 1293 F pulseaudio >/dev/snd/controlC1: wanda 1293 F pulseaudio > BuildID: 20110928224508 > CRDA: Error: [Errno 2] No such file or directory > Card0.Amixer.info: >Card hw:0 'VT82xx'/'HDA VIA VT82xx at 0xbfffc000 irq 17' > Mixer name : 'Realtek ALC883' > Components : 'HDA:10ec0883,14627253,0012' > Controls : 33 > Simple ctrls : 19 > Card1.Amixer.info: >Card hw:1 'U0x46d0x9a1'/'USB Device 0x46d:0x9a1 at usb-:00:10.4-4, > high speed' > Mixer name : 'USB Mixer' > Components : 'USB046d:09a1' > Controls : 2 > Simple ctrls : 1 > Card1.Amixer.values: >Simple mixer control 'Mic',0 > Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum > Capture channels: Mono > Limits: Capture 0 - 3072 > Mono: Capture 870 [28%] [21.39dB] [on] > Channel: release > Date: Mon Oct 24 14:10:51 2011 > ForcedLayersAccel: False > IfupdownConfig: >auto lo >iface lo inet loopback > InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 > (20110427.1) > IpRoute: >192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.27 > metric 1 >169.254.0.0/16 dev eth0 scope link metric 1000 >default via 192.168.1.1 dev eth0 proto static > IwConfig: >lono wireless extensions. > >eth0 no wireless extensions. > ProcEnviron: >LANGUAGE=en_US:en >LANG=en_US.UTF-8 >SHELL=/bin/bash > Profiles: Profile0 (Default) - LastVersion=7.0.1/20110928224508 > (Running) > RfKill: > > RunningIncompatibleAddons: False > SourcePackage: firefox > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 03/06/2008 > dmi.bios.vendor: Phoenix Technologies, LTD > dmi.bios.version: V1.8 > dmi.board.name: MS-7253 > dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD > dmi.board.version: 1.0 > dmi.chassis.type: 3 > dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD > dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrV1.8:bd03/06/2008: > svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7253:pvr1.0:rvnMICRO- > STARINTERNATIONALCO.,LTD:rnMS-7253:rvr1.0:cvnMICRO- > STARINTERNATIONALCO.,LTD:ct3:cvr: > dmi.product.name: MS-7253 > dmi.product.version: 1.0 > dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/ > 881016/+subscriptions > -- -- 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/881016 Title: Computer running very "choppy" since the last update. Status in firefox package in Ubuntu: Incomplete Bug description: Since the last update, my computer has been running very sluggish. There is a delay when I type, pages don't scroll, pages are taking longer to load, links click and open right away, and the processor sounds like it's racing. There is sometimes a delay when switching between windows. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 7.0.1+build1+nobinonly-0ubuntu0.11.04.1 ProcVersionSignature:
Re: [Desktop-packages] [Bug 1024129] Re: I have no cursor...again
I no longer have the issue. This bug can be closed. Thank you. On Wed, Aug 1, 2018 at 12:46 PM, Paul White <1024...@bugs.launchpad.net> wrote: > WLB, > > We are sorry that we do not always have the capacity to review all > reported bugs in a timely manner. You reported this bug some time ago > and there have been many changes in Ubuntu since that time. > > Presumably this problem was a one time occurrence and/or is no longer an > issue? Can this bug report now be closed? > > If we do not hear from you the bug report will close itself in > approximately 60 days time. > > Thank you for helping make Ubuntu better. > > Paul White > [Ubuntu Bug Squad] > > ** Changed in: firefox (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1024129 > > Title: > I have no cursor...again > > Status in firefox package in Ubuntu: > Incomplete > > Bug description: > I have no cursor...again. I was able to copy and paste from a word > document. This happens every time there is an update. Isn't there > something you guys can do about this? It is extremely annoying and > frustrating. I may have to give up using Linux because doing school > work has become a nightmare using your system. As much as I love > Linux the frustrations is beginning to become unbearable. > > ProblemType: Bug > DistroRelease: Ubuntu 11.10 > Package: firefox 13.0.1+build1-0ubuntu0.11.10.1 > ProcVersionSignature: Ubuntu 3.0.0-22.36-generic 3.0.33 > Uname: Linux 3.0.0-22-generic x86_64 > NonfreeKernelModules: nvidia > AddonCompatCheckDisabled: False > AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. > ApportVersion: 1.23-0ubuntu4 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: wanda 1598 F pulseaudio >/dev/snd/controlC1: wanda 1598 F pulseaudio > BuildID: 20120615085229 > CRDA: Error: [Errno 2] No such file or directory > Card0.Amixer.info: >Card hw:0 'VT82xx'/'HDA VIA VT82xx at 0xbfffc000 irq 17' > Mixer name : 'Realtek ALC883' > Components : 'HDA:10ec0883,14627253,0012' > Controls : 34 > Simple ctrls : 20 > Card1.Amixer.info: >Card hw:1 'U0x46d0x9a1'/'USB Device 0x46d:0x9a1 at usb-:00:10.4-1, > high speed' > Mixer name : 'USB Mixer' > Components : 'USB046d:09a1' > Controls : 2 > Simple ctrls : 1 > Card1.Amixer.values: >Simple mixer control 'Mic',0 > Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum > Capture channels: Mono > Limits: Capture 0 - 3072 > Mono: Capture 870 [28%] [21.39dB] [on] > Channel: release > Date: Thu Jul 12 18:11:57 2012 > ForcedLayersAccel: False > IfupdownConfig: >auto lo >iface lo inet loopback > InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 > (20110427.1) > IpRoute: >default via 192.168.1.1 dev eth0 proto static >169.254.0.0/16 dev eth0 scope link metric 1000 >192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2 > metric 1 > IwConfig: >lono wireless extensions. > >eth0 no wireless extensions. > ProcEnviron: >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > Profiles: Profile0 (Default) - LastVersion=13.0.1/20120615085229 (In > use) > RelatedPackageVersions: >rhythmbox-plugins 2.90.1~20110908-0ubuntu1.4 >google-talkplugin 3.1.4.0-1 >icedtea-plugin1.1.3-1ubuntu1.1 >totem-mozilla 3.0.1-0ubuntu7.1 > RfKill: > > RunningIncompatibleAddons: False > SourcePackage: firefox > UpgradeStatus: Upgraded to oneiric on 2011-11-28 (227 days ago) > dmi.bios.date: 03/06/2008 > dmi.bios.vendor: Phoenix Technologies, LTD > dmi.bios.version: V1.8 > dmi.board.name: MS-7253 > dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD > dmi.board.version: 1.0 > dmi.chassis.type: 3 > dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD > dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrV1.8:bd03/06/2008: > svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7253:pvr1.0:rvnMICRO- > STARINTERNATIONALCO.,LTD:rnMS-7253:rvr1.0:cvnMICRO- > STARINTERNATIONALCO.,LTD:ct3:cvr: > dmi.product.name: MS-7253 > dmi.product.version: 1.0 > dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/ > 1024129/+subscriptions > -- -- 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/1024129 Title: I have no cursor...again Status in firefox package in Ubuntu: Incomplete Bug description: I have no cursor...again. I was able to copy and paste from a word document. This happens every time there is an update. Isn't there something
[Desktop-packages] [Bug 1784941] [NEW] PCI/internal sound card not detected
Public bug reported: after working fine, at some stage ubuntu stopped playing sounds - seems that sound card is not detected by os tried https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS with both xenial packages, didn't work either (packages were not displayed in software center after reboot although they were completely installed) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Aug 1 23:08:49 2018 InstallationDate: Installed on 2017-08-21 (345 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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: 01/16/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.23 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd01/16/2017:svnAcer:pnAspireE5-575G:pvrV1.23:rvnAcer:rnIronman_SK:rvrV1.23:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-575G dmi.product.version: V1.23 dmi.sys.vendor: Acer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1784941 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: after working fine, at some stage ubuntu stopped playing sounds - seems that sound card is not detected by os tried https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS with both xenial packages, didn't work either (packages were not displayed in software center after reboot although they were completely installed) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Wed Aug 1 23:08:49 2018 InstallationDate: Installed on 2017-08-21 (345 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) 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: 01/16/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.23 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd01/16/2017:svnAcer:pnAspireE5-575G:pvrV1.23:rvnAcer:rnIronman_SK:rvrV1.23:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E5-575G dmi.product.version: V1.23 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784940] [NEW] package libgtkmm-2.4-doc (not installed) failed to install/upgrade: '/usr/share/doc/libgtkmm-2.4-dev/examples/README' を上書きしようとしています。これはパッケージ libgtkmm-2.4-dev:amd
Public bug reported: 20180801 install gtkmm3.0<-- Is this influenced? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgtkmm-2.4-doc (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 1 17:32:12 2018 ErrorMessage: '/usr/share/doc/libgtkmm-2.4-dev/examples/README' を上書きしようとしています。これはパッケージ libgtkmm-2.4-dev:amd64 1:2.24.5-2 にも存在します InstallationDate: Installed on 2018-04-15 (107 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: gtkmm2.4 Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: '/usr/share/doc/libgtkmm-2.4-dev/examples/README' を上書きしようとしています。これはパッケージ libgtkmm-2.4-dev:amd64 1:2.24.5-2 にも存在します UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtkmm2.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtkmm2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1784940 Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: '/usr/share/doc/libgtkmm-2.4-dev/examples/README' を上書きしようとしています。これはパッケージ libgtkmm-2.4-dev:amd64 1:2.24.5-2 にも存在します Status in gtkmm2.4 package in Ubuntu: New Bug description: 20180801 install gtkmm3.0<-- Is this influenced? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgtkmm-2.4-doc (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 1 17:32:12 2018 ErrorMessage: '/usr/share/doc/libgtkmm-2.4-dev/examples/README' を上書きしようとしています。これはパッケージ libgtkmm-2.4-dev:amd64 1:2.24.5-2 にも存在します InstallationDate: Installed on 2018-04-15 (107 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: gtkmm2.4 Title: package libgtkmm-2.4-doc (not installed) failed to install/upgrade: '/usr/share/doc/libgtkmm-2.4-dev/examples/README' を上書きしようとしています。これはパッケージ libgtkmm-2.4-dev:amd64 1:2.24.5-2 にも存在します UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtkmm2.4/+bug/1784940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1707006] Re: No Sound (dummy output)
It's working now. I guess the fix came with Kernel release 4.4.0-130.
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => New
** Changed in: alsa-driver (Ubuntu)
Status: New => Fix Released
--
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/1707006
Title:
No Sound (dummy output)
Status in alsa-driver package in Ubuntu:
Fix Released
Bug description:
No sound after update.
For your information:
It's OK for Kernel release 4.4.0-81-generic and older.
It's not OK for Kernel release 4.4.0-87-generic and 4.4.0-83-generic.
I have not installed releases 4.4.0-82, 4.4.0-84, 4.4.0-85 and 4.4.0-86, so I
don't know about these versions.
!!
!!ALSA Information Script v 0.4.64
!!
!!Script ran on: Thu Jul 27 02:21:13 UTC 2017
!!Linux Distribution
!!--
Ubuntu 16.04.2 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
16.04.2 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS" HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
UBUNTU_CODENAME=xenial
!!DMI Information
!!---
Manufacturer: Hewlett-Packard
Product Name: HP 1000 Notebook PC
Product Version: 088311305B1610100
Firmware Version: F.26
Board Vendor: Hewlett-Packard
Board Name:1854
!!ACPI Device Status Information
!!---
/sys/bus/acpi/devices/HPQ6001:00/status15
/sys/bus/acpi/devices/HPQ8001:00/status15
/sys/bus/acpi/devices/INT340E:00/status15
/sys/bus/acpi/devices/INT3F0D:00/status15
/sys/bus/acpi/devices/LNXPOWER:00/status 1
/sys/bus/acpi/devices/PNP0103:00/status15
/sys/bus/acpi/devices/PNP0C01:00/status15
/sys/bus/acpi/devices/PNP0C09:00/status15
/sys/bus/acpi/devices/PNP0C0A:00/status31
/sys/bus/acpi/devices/PNP0C0F:00/status9
/sys/bus/acpi/devices/PNP0C0F:01/status9
/sys/bus/acpi/devices/PNP0C0F:02/status9
/sys/bus/acpi/devices/PNP0C0F:03/status9
/sys/bus/acpi/devices/PNP0C0F:04/status9
/sys/bus/acpi/devices/PNP0C0F:05/status9
/sys/bus/acpi/devices/PNP0C0F:06/status9
/sys/bus/acpi/devices/PNP0C0F:07/status9
/sys/bus/acpi/devices/SYN1E6A:00/status15
!!Kernel Information
!!--
Kernel release:4.4.0-87-generic
Operating System: GNU/Linux
Architecture: x86_64
Processor: x86_64
SMP Enabled: Yes
!!ALSA Version
!!
Driver version: k4.4.0-87-generic
Library version:1.1.0
Utilities version: 1.1.0
!!Loaded ALSA modules
!!---
!!Sound Servers on this system
!!
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes
ESound Daemon:
Installed - Yes (/usr/bin/esd)
Running - No
Jack:
Installed - Yes (/usr/bin/jackd)
Running - No
!!Soundcards recognised by ALSA
!!-
--- no soundcards ---
!!PCI Soundcards installed in the system
!!--
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset
Family High Definition Audio Controller (rev 04)
!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!---
00:1b.0 0403: 8086:1e20 (rev 04)
Subsystem: 103c:1854
!!Modprobe options (Sound related)
!!
snd_pcsp: index=-2
snd_usb_audio: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_usb_audio: index=-2
snd_usb_caiaq: index=-2
snd_usb_ua101: index=-2
snd_usb_us122l: index=-2
snd_usb_usx2y: index=-2
snd_cmipci: mpu_port=0x330 fm_port=0x388
snd_pcsp: index=-2
snd_usb_audio: index=-2
snd_aloop: index=-2
!!Loaded sound module options
!!---
!!ALSA Device nodes
!!-
crw-rw 1 root audio 116, 1 Jul 26 23:06 /dev/snd/seq
crw-rw 1 root audio 116, 33 Jul 26 23:06 /dev/snd/timer
!!ALSA configuration files
!!
!!User specific config file (~/.asoundrc)
pcm.!default {
type plug
slave { pcm "jack" }
}
pcm.jack {
type jack
playback_ports {
0 system:playback_1
1 system:playback_2
}
capture_ports {
0 system:capture_1
1 system:capture_2
}
}
ctl.mixer0 {
type hw
card 0
}
!!Aplay/Arecord output
[Desktop-packages] [Bug 1707006] Re: No Sound (dummy output)
It's working now. I guess the fix came with Kernel release 4.4.0-130.
--
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/1707006
Title:
No Sound (dummy output)
Status in alsa-driver package in Ubuntu:
Fix Released
Bug description:
No sound after update.
For your information:
It's OK for Kernel release 4.4.0-81-generic and older.
It's not OK for Kernel release 4.4.0-87-generic and 4.4.0-83-generic.
I have not installed releases 4.4.0-82, 4.4.0-84, 4.4.0-85 and 4.4.0-86, so I
don't know about these versions.
!!
!!ALSA Information Script v 0.4.64
!!
!!Script ran on: Thu Jul 27 02:21:13 UTC 2017
!!Linux Distribution
!!--
Ubuntu 16.04.2 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
16.04.2 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.2 LTS" HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
UBUNTU_CODENAME=xenial
!!DMI Information
!!---
Manufacturer: Hewlett-Packard
Product Name: HP 1000 Notebook PC
Product Version: 088311305B1610100
Firmware Version: F.26
Board Vendor: Hewlett-Packard
Board Name:1854
!!ACPI Device Status Information
!!---
/sys/bus/acpi/devices/HPQ6001:00/status15
/sys/bus/acpi/devices/HPQ8001:00/status15
/sys/bus/acpi/devices/INT340E:00/status15
/sys/bus/acpi/devices/INT3F0D:00/status15
/sys/bus/acpi/devices/LNXPOWER:00/status 1
/sys/bus/acpi/devices/PNP0103:00/status15
/sys/bus/acpi/devices/PNP0C01:00/status15
/sys/bus/acpi/devices/PNP0C09:00/status15
/sys/bus/acpi/devices/PNP0C0A:00/status31
/sys/bus/acpi/devices/PNP0C0F:00/status9
/sys/bus/acpi/devices/PNP0C0F:01/status9
/sys/bus/acpi/devices/PNP0C0F:02/status9
/sys/bus/acpi/devices/PNP0C0F:03/status9
/sys/bus/acpi/devices/PNP0C0F:04/status9
/sys/bus/acpi/devices/PNP0C0F:05/status9
/sys/bus/acpi/devices/PNP0C0F:06/status9
/sys/bus/acpi/devices/PNP0C0F:07/status9
/sys/bus/acpi/devices/SYN1E6A:00/status15
!!Kernel Information
!!--
Kernel release:4.4.0-87-generic
Operating System: GNU/Linux
Architecture: x86_64
Processor: x86_64
SMP Enabled: Yes
!!ALSA Version
!!
Driver version: k4.4.0-87-generic
Library version:1.1.0
Utilities version: 1.1.0
!!Loaded ALSA modules
!!---
!!Sound Servers on this system
!!
Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes
ESound Daemon:
Installed - Yes (/usr/bin/esd)
Running - No
Jack:
Installed - Yes (/usr/bin/jackd)
Running - No
!!Soundcards recognised by ALSA
!!-
--- no soundcards ---
!!PCI Soundcards installed in the system
!!--
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset
Family High Definition Audio Controller (rev 04)
!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!---
00:1b.0 0403: 8086:1e20 (rev 04)
Subsystem: 103c:1854
!!Modprobe options (Sound related)
!!
snd_pcsp: index=-2
snd_usb_audio: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_usb_audio: index=-2
snd_usb_caiaq: index=-2
snd_usb_ua101: index=-2
snd_usb_us122l: index=-2
snd_usb_usx2y: index=-2
snd_cmipci: mpu_port=0x330 fm_port=0x388
snd_pcsp: index=-2
snd_usb_audio: index=-2
snd_aloop: index=-2
!!Loaded sound module options
!!---
!!ALSA Device nodes
!!-
crw-rw 1 root audio 116, 1 Jul 26 23:06 /dev/snd/seq
crw-rw 1 root audio 116, 33 Jul 26 23:06 /dev/snd/timer
!!ALSA configuration files
!!
!!User specific config file (~/.asoundrc)
pcm.!default {
type plug
slave { pcm "jack" }
}
pcm.jack {
type jack
playback_ports {
0 system:playback_1
1 system:playback_2
}
capture_ports {
0 system:capture_1
1 system:capture_2
}
}
ctl.mixer0 {
type hw
card 0
}
!!Aplay/Arecord output
!!
APLAY
aplay: device_list:268: no soundcards found...
ARECORD
arecord: device_list:268: no soundcards found...
[Desktop-packages] [Bug 1780501] Re: Traceback calling Vte.Terminal.feed_child()
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Triaged => In Progress
** Changed in: ubuntu-release-upgrader (Ubuntu)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte2.91 in Ubuntu.
https://bugs.launchpad.net/bugs/1780501
Title:
Traceback calling Vte.Terminal.feed_child()
Status in ubuntu-release-upgrader package in Ubuntu:
In Progress
Status in vte2.91 package in Ubuntu:
Won't Fix
Status in ubuntu-release-upgrader source package in Bionic:
Invalid
Status in vte2.91 source package in Bionic:
Fix Committed
Bug description:
[Test Case]
1) Ensure the following packages from -updates (version
0.52.2-1ubuntu1~18.04.1) are installed on an Ubuntu 18.04 system:
gir1.2-vte-2.91 libvte-2.91-0 libvte-2.91-common
2) Modify /etc/issue e.g. I changed 18.04 to 18.04.2
3) Ensure /etc/update-manager/release-upgrades contains "Prompt=normal"
4) Run /usr/lib/ubuntu-release-upgrader/check-new-release-gtk -d
5) When prompted about replacing "the customized configuration file
'/etc/issue'" click Keep
6) Observe a traceback in Vte.Terminal.feed_child()
After installing the new version of vte2.91 in -proposed you should no
longer receive a Traceback when clicking keep during the upgrade
process.
[Regression Potential]
Per laney: "The regression potential is that I messed up the upload and
everything using feed* breaks."
It'd probably be good to test guake too since it uses feed_child().
[Original Description]
I was upgrading from Bionic to Cosmic when I received a conffile prompt
regarding /etc/update-initramfs/initramfs.conf, I clicked keep and then saw
this Traceback:
Original exception was:
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-filpk342/cosmic", line 8, in
sys.exit(main())
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeMain.py", line
238, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py",
line 1949, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py",
line 1912, in fullUpgrade
if not self.doDistUpgrade():
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeController.py",
line 1248, in doDistUpgrade
res = self.cache.commit(fprogress,iprogress)
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeCache.py", line
293, in commit
apt.Cache.commit(self, fprogress, iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 606, in commit
pm = apt_pkg.PackageManager(self._depcache)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 569, in
install_archives
# compat with older API
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeView.py", line
229, in run
res = os.WEXITSTATUS(self.wait_child())
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py",
line 340, in wait_child
self.update_interface()
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py",
line 347, in update_interface
InstallProgress.update_interface(self)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 252, in
update_interface
if err.errno != errno.EAGAIN and err.errno != errno.EWOULDBLOCK:
File
"/tmp/ubuntu-release-upgrader-filpk342/DistUpgrade/DistUpgradeViewGtk3.py",
line 276, in conffile
self.term.feed_child("n\n", -1)
TypeError: Vte.Terminal.feed_child() takes exactly 2 arguments (3 given)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1780501/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1784633] Re: workspace side selector not properly rendered
I did check the shell behavior without the extensions, and it is very similar. The only difference is that natively the workspaces are stacked, so there is no more the issue with the size of the panel, but the one with the border is still there. I submitted the bug to the shell developers as this address (#457): https://gitlab.gnome.org/GNOME/gnome-shell/issues/457 -- 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/1784633 Title: workspace side selector not properly rendered Status in gnome-shell package in Ubuntu: Incomplete Bug description: After upgrading Ubuntu to 18.04 the workspace selector, show on the side of the shell is not properly rendered. The panel takes the whole right side, independent from the number of workspaces I chose and the colored border around the active one is offset. The first time I open the shell the border highlight the proper box, the is set to the top left corner of the panel. I am attaching a picture showing the issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 31 09:57:01 2018 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2016-07-02 (758 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-07-24 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1784633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1764779] Re: Nautilus crashed open Windows-partition
This bug was fixed in the package nautilus - 1:3.26.4-0ubuntu2 --- nautilus (1:3.26.4-0ubuntu2) cosmic; urgency=medium * debian/patches/nautilusgtkplacesview-show-error-if-volume-is-not-mo.patch: - don't crash if selecting a volume that is not mounted (LP: #1764779) + patch re-added after gbp deleted on importing new upstream release * debian/patches/file-view-Always-unset-pending_selection-after-freeing-it.patch: - don't crash when try to select a file multiple times in a single run (LP: #1713581) * debian/patches/query-add-recursive-flags-and-use-it-in-search-engines.patch: - Apply the upstream version of it (with 3.26 changes) * debian/patches/0015-tracker-search-engine-don-t-start-it-if-not-availabl.patch, debian/patches/0018-search-engine-add-locate-based-search-engine.patch, debian/patches/file-view-Always-unset-pending_selection-after-freeing-it.patch, - Refresh as per recursive-query patch update * 0016-search-engine-add-a-recent-search-engine-listing-Gtk.patch: - Refresh with upstream merged-description -- Marco Trevisan (Treviño) Wed, 01 Aug 2018 20:58:52 +0200 ** Changed in: nautilus (Ubuntu) Status: In Progress => 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/1764779 Title: Nautilus crashed open Windows-partition Status in glib package in Ubuntu: Triaged Status in nautilus package in Ubuntu: Fix Released Bug description: [ Description ] if I open a new partition from the Hard-drive (Windows in this case) Nautilus crash, report him self and after reopen it, the partition is normal available as nothing would be [ Test case ] * Open nautilus and select an external hd that is not mounted from the sidebar * Nautilus sould not crash (in case showing an error message) [ Regression potential ] Partitions that have been actually mounted, are not shown or an error is prompted. - Issue from the log: Apr 17 16:45:29 hostname udisksd[1014]: Failed to setup systemd-based mount point cleanup: Process reported exit code 5: Failed to start clean-mount-point@media-username-12F6CC77F6CC5D1B.service: Unit media-username-12F6CC77F6CC5D1B.mount not found. Apr 17 16:45:29 hostname nautilus[11486]: g_mount_get_default_location: assertion 'G_IS_MOUNT (mount)' failed Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: ** Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: ERROR:../src/nautilus-file.c:721:nautilus_file_get_internal: assertion failed: (location != NULL) - ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 16:45:30 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-move-to-trash-shortcut-changed-dialog' b'false' b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' b'org.gnome.nautilus.window-state' b'geometry' b"'927x1011+926+27'" InstallationDate: Installed on 2018-03-16 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180315) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8Signal: 6SourcePackage: nautilus StacktraceTop: g_assertion_message () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib/+bug/1764779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1713581] Re: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
This bug was fixed in the package nautilus - 1:3.26.4-0ubuntu2 --- nautilus (1:3.26.4-0ubuntu2) cosmic; urgency=medium * debian/patches/nautilusgtkplacesview-show-error-if-volume-is-not-mo.patch: - don't crash if selecting a volume that is not mounted (LP: #1764779) + patch re-added after gbp deleted on importing new upstream release * debian/patches/file-view-Always-unset-pending_selection-after-freeing-it.patch: - don't crash when try to select a file multiple times in a single run (LP: #1713581) * debian/patches/query-add-recursive-flags-and-use-it-in-search-engines.patch: - Apply the upstream version of it (with 3.26 changes) * debian/patches/0015-tracker-search-engine-don-t-start-it-if-not-availabl.patch, debian/patches/0018-search-engine-add-locate-based-search-engine.patch, debian/patches/file-view-Always-unset-pending_selection-after-freeing-it.patch, - Refresh as per recursive-query patch update * 0016-search-engine-add-a-recent-search-engine-listing-Gtk.patch: - Refresh with upstream merged-description -- Marco Trevisan (Treviño) Wed, 01 Aug 2018 20:58:52 +0200 ** Changed in: nautilus (Ubuntu) Status: In Progress => 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/1713581 Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in nautilus package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/ef1ce30f6325c683b207fd96a3be93eda5384054 Fixed in https://gitlab.gnome.org/GNOME/nautilus/commit/b6691821b86460bf9d4caa6391666ae506a743c5 no idea,sorry ProblemType: CrashDistroRelease: Ubuntu 17.10 Package: nautilus 1:3.25.90-0ubuntu1 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 29 00:07:44 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-08-09 (19 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170807) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=de_DE.UTF-8 SegvAnalysis: Segfault happened at: 0x7f8b19a60d27 : mov(%rdi),%rdx PC (0x7f8b19a60d27) ok source "(%rdi)" (0x0002) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: nautilus StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_list_copy_deep () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () Title: nautilus crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1713581/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 839110] Re: the "History" item is flashing up 2x
zsolt.ruszinyák We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Presumably this problem was a one time occurrence and/or is no longer an issue? Can this bug report now be closed? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/839110 Title: the "History" item is flashing up 2x Status in firefox package in Ubuntu: Incomplete Bug description: when I clock on History, at first, old results show up, then they disappear and, subsequently, the latest history appears. this flashing is very annoying. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: firefox-globalmenu 7.0~b3+build1+nobinonly-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic i686 Architecture: i386 CasperVersion: 1.280 Date: Thu Sep 1 21:17:54 2011 LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/839110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 908929] Re: More than a dozen browser windows open after suspended animation
sysf1, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Presumably this problem was a one time occurrence and/or is no longer an issue? Can this bug report now be closed? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/908929 Title: More than a dozen browser windows open after suspended animation Status in firefox package in Ubuntu: Incomplete Bug description: More than a dozen browser windows open after suspended animation, waiting to restore the normal window is very slow, and twenty-three minutes recovery ubuntu system version: ubuntu 10.10 2.6.35-31-generic ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.24+build2+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-31.63-generic 2.6.35.13 Uname: Linux 2.6.35-31-generic i686 Architecture: i386 Date: Tue Dec 27 10:26:41 2011 EcryptfsInUse: Yes FirefoxPackages: firefox 3.6.24+build2+nobinonly-0ubuntu0.10.10.1 firefox-gnome-support 3.6.24+build2+nobinonly-0ubuntu0.10.10.1 firefox-branding 3.6.24+build2+nobinonly-0ubuntu0.10.10.1 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANGUAGE=zh_CN:zh LANG=zh_CN.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/908929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1087154] Re: tooltips pop up underneath menu
fj4, Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Your problem may have been fixed with some of the updates. It would help us a lot if you could test on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once in a terminal: apport-collect 1087154 and add any additional information that you think relevant. Alternatively, please confirm that this is no longer a problem and that we can close the report. If we do not hear from you the bug report will close itself in approximately two months time. Thank you again for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1087154 Title: tooltips pop up underneath menu Status in firefox package in Ubuntu: Incomplete Bug description: I use RSS feeds in my Bookmarks toolbar. Each feed is a dropdown menu, so I can preview the headlines. Headlines that are too long get cut off with an ellipsis, so I typically hover the cursor on them so that a tooltip pops up and I can read them in their entirety. In Firefox 17 for Windows, there is no issue. In Firefox 17 for Linux, the tooltip pops UNDER the dropdown menu, hiding the full headline. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1087154/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 809988] Re: Recent intermittent issues
Brian, We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Presumably this problem was a one time occurrence and/or is no longer an issue? Can this bug report now be closed? If we do not hear from you the bug report will close itself in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/809988 Title: Recent intermittent issues Status in firefox package in Ubuntu: Incomplete Bug description: Firefox works fine. Sometimes...when I close the browser, it closes with no problems. The icon on the launcher doesn't have the little arrow that shows that it's still open. Yet, if I try to run Firefox again later...I receive an error message that says something like: "Firefox is currently running. Please close the open window or re-boot your computer." Since I can find no open Firefox session, re-booting the PC is my only option. After the boot, the browser works fine...but eventually the problem will come back up. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 5.0+build1+nobinonly-0ubuntu0.11.04.2 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Wed Jul 13 11:07:06 2011 FirefoxPackages: firefox 5.0+build1+nobinonly-0ubuntu0.11.04.2 flashplugin-installer N/A adobe-flashplugin N/A icedtea-plugin 1.1~20110420-0ubuntu1.1 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/809988/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
