[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Ubuntu 18.04.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
> rm /etc/initramfs-tools/conf.d/resume > sudo update-initramfs -u I tried this method, but the bug still exists -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1743079] Re: apparmor exit code 123
Snapd is not installed so I believe the bug is in Apparmor. We are currently running Apparmor "2.12-4ubuntu5 amd64" ** Package changed: snapd (Ubuntu) => apparmor (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1743079 Title: apparmor exit code 123 Status in apparmor package in Ubuntu: Confirmed Bug description: Dear IT worker, Since I have kernel 4.14.12 I have two errors, for apparmor: apparmor failed because It failed to start LSB the status exit code is 123 and there is a error by program /etc/apparmor.d/usr.lib.snapd- confine.real in line 11 unable to open /var/lib/snapd/apparmor/snap- confine.d (skipping profile in /etc/apparmor.d/disable : usr.sbin.rsyslogd Also thank you in advance to all the team to help me and repair this two problem, Regards. Dorian ROSSE. System: ubuntu 16.04.3 Apparmor: 2.10.95-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1743079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to console-setup 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/~touch-packages Post to :
[Touch-packages] [Bug 1743079] [NEW] apparmor exit code 123
You have been subscribed to a public bug: Dear IT worker, Since I have kernel 4.14.12 I have two errors, for apparmor: apparmor failed because It failed to start LSB the status exit code is 123 and there is a error by program /etc/apparmor.d/usr.lib.snapd- confine.real in line 11 unable to open /var/lib/snapd/apparmor/snap- confine.d (skipping profile in /etc/apparmor.d/disable : usr.sbin.rsyslogd Also thank you in advance to all the team to help me and repair this two problem, Regards. Dorian ROSSE. System: ubuntu 16.04.3 Apparmor: 2.10.95-0ubuntu2.7 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: Confirmed -- apparmor exit code 123 https://bugs.launchpad.net/bugs/1743079 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded packages, which is subscribed to attr 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784776] Re: kbd_mode - "Couldn't get fd referring to console"
** Description changed:
Sorry for using your bug reporting mechanism directly. 'ubuntu-bug
'/'apport-cli' do not seem to agree with modifications to the text that
they generate (:@{).
Actually, bug #1621824 does fairly well in describing the problem.
Unfortunately, that was a xenial {"ubuntu 16.04"?) bug and the report is
closed. This bug is in "ubuntu 18.04" (bionic) and it is still
occurring. Below is output from 'apport-cli' with a bit of ADDITIONAL
INFORMATION. Right now 'apport-cli' rejects the text below as
"damaged".
-- Thanks,
--Paul Townsend
+
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jul 31 22:31:41 2018
Dependencies:
- adduser 3.116ubuntu1
- apt 1.6.3
- apt-utils 1.6.3
- ca-certificates 20180409
- console-setup 1.178ubuntu2.3
- console-setup-linux 1.178ubuntu2.3
- debconf 1.5.66
- debconf-i18n 1.5.66
- dpkg 1.19.0.5ubuntu2
- gcc-8-base 8-20180414-1ubuntu2
- gpgv 2.2.4-1ubuntu1.1
- init-system-helpers 1.51
- kbd 2.0.4-2ubuntu1
- keyboard-configuration 1.178ubuntu2.3
- libacl1 2.2.52-3build1
- libapt-inst2.0 1.6.3
- libapt-pkg5.0 1.6.3
- libattr1 1:2.4.47-2build1
- libaudit-common 1:2.8.2-1ubuntu1
- libaudit1 1:2.8.2-1ubuntu1
- libbz2-1.0 1.0.6-8.1
- libc6 2.27-3ubuntu1
- libcap-ng0 0.7.7-3.1
- libdb5.3 5.3.28-13.1ubuntu1
- libffi6 3.2.1-8
- libgcc1 1:8-20180414-1ubuntu2
- libgcrypt20 1.8.1-4ubuntu1.1
- libgmp10 2:6.1.2+dfsg-2
- #1347 aab@ideapad330 $ cat /tmp/apport.kbd.aif1oyib.apport
- ProblemType: Bug
- ApportVersion: 2.20.9-0ubuntu7.2
- Architecture: amd64
- Date: Tue Jul 31 22:31:41 2018
- Dependencies:
- adduser 3.116ubuntu1
- apt 1.6.3
- apt-utils 1.6.3
- ca-certificates 20180409
- console-setup 1.178ubuntu2.3
- console-setup-linux 1.178ubuntu2.3
- debconf 1.5.66
- debconf-i18n 1.5.66
- dpkg 1.19.0.5ubuntu2
- gcc-8-base 8-20180414-1ubuntu2
- gpgv 2.2.4-1ubuntu1.1
- init-system-helpers 1.51
- kbd 2.0.4-2ubuntu1
- keyboard-configuration 1.178ubuntu2.3
- libacl1 2.2.52-3build1
- libapt-inst2.0 1.6.3
- libapt-pkg5.0 1.6.3
- libattr1 1:2.4.47-2build1
- libaudit-common 1:2.8.2-1ubuntu1
- libaudit1 1:2.8.2-1ubuntu1
- libbz2-1.0 1.0.6-8.1
- libc6 2.27-3ubuntu1
- libcap-ng0 0.7.7-3.1
- libdb5.3 5.3.28-13.1ubuntu1
- libffi6 3.2.1-8
- libgcc1 1:8-20180414-1ubuntu2
- libgcrypt20 1.8.1-4ubuntu1.1
- libgmp10 2:6.1.2+dfsg-2
- libgnutls30 3.5.18-1ubuntu1
- libgpg-error0 1.27-6
- libhogweed4 3.4-1
- libidn2-0 2.0.4-1.1build2
- liblocale-gettext-perl 1.07-3build2
- liblz4-1 0.0~r131-2ubuntu3
- liblzma5 5.2.2-1.3
- libnettle6 3.4-1
- libp11-kit0 0.23.9-2
- libpam-modules 1.1.8-3.6ubuntu2
- libpam-modules-bin 1.1.8-3.6ubuntu2
- libpam0g 1.1.8-3.6ubuntu2
- libpcre3 2:8.39-9
- libseccomp2 2.3.1-2.1ubuntu4
- libselinux1 2.7-2build2
- libsemanage-common 2.7-2build2
- libsemanage1 2.7-2build2
- libsepol1 2.7-1
- libssl1.1 1.1.0g-2ubuntu4.1
- libstdc++6 8-20180414-1ubuntu2
- libtasn1-6 4.13-2
- libtext-charwidth-perl 0.04-7.1
- libtext-iconv-perl 1.7-5build6
- libtext-wrapi18n-perl 0.06-7.1
- libudev1 237-3ubuntu10.3
- libunistring2 0.9.9-0ubuntu1
- libzstd1 1.3.3+dfsg-2ubuntu1
- openssl 1.1.0g-2ubuntu4.1
- passwd 1:4.5-1ubuntu1
- perl-base 5.26.1-6ubuntu0.2
- tar 1.29b-2
- ubuntu-keyring 2018.02.28
- xkb-data 2.23.1-1ubuntu1
- zlib1g 1:1.2.11.dfsg-0ubuntu2
+ adduser 3.116ubuntu1
+ apt 1.6.3
+ apt-utils 1.6.3
+ ca-certificates 20180409
+ console-setup 1.178ubuntu2.3
+ console-setup-linux 1.178ubuntu2.3
+ debconf 1.5.66
+ debconf-i18n 1.5.66
+ dpkg 1.19.0.5ubuntu2
+ gcc-8-base 8-20180414-1ubuntu2
+ gpgv 2.2.4-1ubuntu1.1
+ init-system-helpers 1.51
+ kbd 2.0.4-2ubuntu1
+ keyboard-configuration 1.178ubuntu2.3
+ libacl1 2.2.52-3build1
+ libapt-inst2.0 1.6.3
+ libapt-pkg5.0 1.6.3
+ libattr1 1:2.4.47-2build1
+ libaudit-common 1:2.8.2-1ubuntu1
+ libaudit1 1:2.8.2-1ubuntu1
+ libbz2-1.0 1.0.6-8.1
+ libc6 2.27-3ubuntu1
+ libcap-ng0 0.7.7-3.1
+ libdb5.3 5.3.28-13.1ubuntu1
+ libffi6 3.2.1-8
+ libgcc1 1:8-20180414-1ubuntu2
+ libgcrypt20 1.8.1-4ubuntu1.1
+ libgmp10 2:6.1.2+dfsg-2
+ libgnutls30 3.5.18-1ubuntu1
+ libgpg-error0 1.27-6
+ libhogweed4 3.4-1
+ libidn2-0 2.0.4-1.1build2
+ liblocale-gettext-perl 1.07-3build2
+ liblz4-1 0.0~r131-2ubuntu3
+ liblzma5 5.2.2-1.3
+ libnettle6 3.4-1
+ libp11-kit0 0.23.9-2
+ libpam-modules 1.1.8-3.6ubuntu2
+ libpam-modules-bin 1.1.8-3.6ubuntu2
+ libpam0g 1.1.8-3.6ubuntu2
+ libpcre3 2:8.39-9
+ libseccomp2 2.3.1-2.1ubuntu4
+ libselinux1 2.7-2build2
+ libsemanage-common 2.7-2build2
+ libsemanage1 2.7-2build2
+ libsepol1 2.7-1
+ libssl1.1 1.1.0g-2ubuntu4.1
+ libstdc++6 8-20180414-1ubuntu2
+ libtasn1-6 4.13-2
+ libtext-charwidth-perl 0.04-7.1
+ libtext-iconv-perl 1.7-5build6
+ libtext-wrapi18n-perl 0.06-7.1
+ libudev1 237-3ubuntu10.3
+ libunistring2 0.9.9-0ubuntu1
+ libzstd1 1.3.3+dfsg-2ubuntu1
+ openssl 1.1.0g-2ubuntu4.1
+ passwd 1:4.5-1ubuntu1
+ perl-base
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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
[Touch-packages] [Bug 1784942] [NEW] Recovery from standby
Public bug reported: I have updated my laptop from ubuntu 14.4 - 143 to ubuntu 14.4 - 153. From that on the recovery from standby didn't work any more. The computer seems to start, but after some seconds the activity LED didn't show any activity and the screen stayed black except the back light. After forced shut down and boot all was working. I activated version 143. With version 143 recovery from standby worked again perfectly. ** Affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1784942 Title: Recovery from standby Status in ubuntu-touch-meta package in Ubuntu: New Bug description: I have updated my laptop from ubuntu 14.4 - 143 to ubuntu 14.4 - 153. From that on the recovery from standby didn't work any more. The computer seems to start, but after some seconds the activity LED didn't show any activity and the screen stayed black except the back light. After forced shut down and boot all was working. I activated version 143. With version 143 recovery from standby worked again perfectly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1784942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu Touch seeded 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/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-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 Ubuntu
Touch seeded 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
[Touch-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 Ubuntu
Touch seeded 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
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
** Changed in: python3-defaults (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1768379 Title: python3-minimal should predepend on versioned version of python3-minimal Status in python3-defaults package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python3-defaults source package in Artful: Fix Released Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: Fix Released Status in ubuntu-release-upgrader source package in Bionic: Invalid Status in python3-defaults package in Debian: Fix Released Bug description: [Impact] Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 LTS can fail if python3-minimial is unpacked before python3.x-minimal so a system won't have a usable python3 symlink. Then upgrades will fail because py3clean, used in prerm scripts of python3 packages, will fail with "not found". [Test Case] 1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt 2) dpkg --unpack python3-minimal... 3) dpkg --unpack python3-apt... Observe the following Traceback: Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ... /var/lib/dpkg/info/python3-apt.prerm: 6: /var/lib/dpkg/info/python3-apt.prerm: py3clean: not found dpkg: warning: subprocess old pre-removal script returned error exit status 127 dpkg: trying script from the new package instead ... /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found dpkg: error processing archive /home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 127 /var/lib/dpkg/info/python3-apt.postinst: 6: /var/lib/dpkg/info/python3-apt.postinst: py3compile: not found dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 127 With the deb python3-minimal from -proposed you won't be able to unpack python3-minimal without first installing python3.6-minimal. While that may qualify as verification it'd still be good to test unpacking python3-apt. To do that you'll need to install python3.6-minimal from the target release by editing you /etc/apt/sources.list to the new release, running 'apt-get update', and then 'apt-get install python3.6-minimal'. After that's all done you can try steps 2 and 3 from the test case again and you should not receive a Traceback. [Regression Potential] Its possible this could cause or reveal different upgrade failures so some extensive (desktop, cloud, server) upgrade testing should be done. [A Portion of the Original Description (it was a huge blob of failure)] do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1768379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665695] Re: OpenSSH PKCS#11 interface does not support ECC.
I doubt the patch will be added to a linux distribution before it's applied upstream, since it's of a very security sensitive nature. I linked the upstream bug report to this launchpad ticket, though, so we should get notice when it's closed there. ** Bug watch added: OpenSSH Portable Bugzilla #2474 https://bugzilla.mindrot.org/show_bug.cgi?id=2474 ** Also affects: openssh via https://bugzilla.mindrot.org/show_bug.cgi?id=2474 Importance: Unknown Status: Unknown ** Changed in: openssh (Ubuntu) Importance: Undecided => Wishlist ** Changed in: openssh (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1665695 Title: OpenSSH PKCS#11 interface does not support ECC. Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Triaged Bug description: OpenSSH client doesn't support Eliptics Curve keys on PKCS11 smartcard ssh-keygen -v -D /usr/lib/libeTPkcs11.so debug1: manufacturerID cryptokiVersion 2.20 libraryDescription libraryVersion 9.1 debug1: label manufacturerID model serial <> flags 0x60d C_GetAttributeValue failed: 18 debug1: X509_get_pubkey failed or no rsa debug1: X509_get_pubkey failed or no rsa debug1: X509_get_pubkey failed or no rsa no keys cannot read public key from pkcs11 pkcs11-tool --module /usr/lib/libeTPkcs11.so -O ... Public Key Object; EC EC_POINT 256 bits EC_POINT: 04410474c5423bd0aa44b7825b3e79cd839e06736b18466b131d0884dbf8d946fbdc7f3297e73b998acf56550c303dc972a4dec51b9a3b746d3fe9fb4a44bd84b080fc EC_PARAMS: 06082a8648ce3d030107 label: TestECCpair Usage: encrypt, verify, wrap There is upstream bug: https://bugzilla.mindrot.org/show_bug.cgi?id=2474 Suggested patch: https://bugzilla.mindrot.org/attachment.cgi?id=2728 release: Ubuntu 16.04.2 LTS openssh version: 7.2p2-4ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1665695/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784914] [NEW] bad graphics
Public bug reported: 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1784914 Title: bad graphics Status in xorg package in Ubuntu: New 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
[Touch-packages] [Bug 395605] Re: Cups dies repeatedly
Hello Thiago, 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 Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/395605 Title: Cups dies repeatedly Status in cups package in Ubuntu: Incomplete Bug description: Package: cups Version: 1.3.9-17ubuntu3.2 Cups is _very_ unstable in this version, dying with the following messages (in /var/log/cups/error_log) (looks very similar to this http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=524201) d [04/Jul/2009:16:44:22 -0300] cupsdDoSelect: polling 3 fds for 1 seconds... d [04/Jul/2009:16:44:22 -0300] cupsdDoSelect: epoll() returned -1... d [04/Jul/2009:16:44:22 -0300] cupsdDoSelect: polling 3 fds for 1 seconds... d [04/Jul/2009:16:44:22 -0300] cupsdDoSelect: poll() returned -1... X [04/Jul/2009:16:44:22 -0300] cupsdDoSelect() failed - Success! X [04/Jul/2009:16:44:22 -0300] Listeners[0] = 3 X [04/Jul/2009:16:44:22 -0300] Listeners[1] = 4 X [04/Jul/2009:16:44:22 -0300] BrowseSocket = -1 X [04/Jul/2009:16:44:22 -0300] CGIPipes[0] = 5 X [04/Jul/2009:16:44:22 -0300] printer[casa] 0 X [04/Jul/2009:16:44:22 -0300] printer[tt4c] 0 E [04/Jul/2009:16:44:22 -0300] Scheduler shutting down due to program error. It's not a crash per se, but cups exits gracefully. Strace shows very strange things (see attached) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/395605/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 368977] Re: System print config "forgets" printer status / settings on reboot
** Changed in: system-config-printer (Ubuntu) Status: New => Incomplete ** Changed in: cups (Ubuntu) Status: New => Incomplete ** Changed in: system-config-printer Status: New => Incomplete ** Changed in: gnome-print Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/368977 Title: System print config "forgets" printer status / settings on reboot Status in CUPS: New Status in Gnome Print: Incomplete Status in System Config Printer: Incomplete Status in cups package in Ubuntu: Incomplete Status in kubuntu-meta package in Ubuntu: Invalid Status in system-config-printer package in Ubuntu: Incomplete Bug description: I will update this bug the next time it happens. If anybody can suggest debugging information that would be helpful, I'll include it. So far, this has happened twice, both in very recent versions of KDE 4.2 (Kubuntu 9.04; I was on the RCs). I have a Laserjet 8150. I try to print (e.g. from Firefox), choose the printer, and nothing happens. Then I look in the KDE printer applet, and it says the printer is unavailable, or busy, or... No combination of restarting the printer, clearing the print job queue, or restarting the computer seems to work. The only workaround I have is to go through KDE's printer configuration and remove/install the printer. After that, it works. My working theory based on this is that something about the printer config is being screwed up. Before a week or so ago, I never had this problem, and the printer worked reliably. So, it's a recent bug. At what point in the workflow I don't know. More information when I have it. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/368977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 368977] Re: System print config "forgets" printer status / settings on reboot
Hello Reuben, 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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/368977 Title: System print config "forgets" printer status / settings on reboot Status in CUPS: New Status in Gnome Print: Incomplete Status in System Config Printer: Incomplete Status in cups package in Ubuntu: Incomplete Status in kubuntu-meta package in Ubuntu: Invalid Status in system-config-printer package in Ubuntu: Incomplete Bug description: I will update this bug the next time it happens. If anybody can suggest debugging information that would be helpful, I'll include it. So far, this has happened twice, both in very recent versions of KDE 4.2 (Kubuntu 9.04; I was on the RCs). I have a Laserjet 8150. I try to print (e.g. from Firefox), choose the printer, and nothing happens. Then I look in the KDE printer applet, and it says the printer is unavailable, or busy, or... No combination of restarting the printer, clearing the print job queue, or restarting the computer seems to work. The only workaround I have is to go through KDE's printer configuration and remove/install the printer. After that, it works. My working theory based on this is that something about the printer config is being screwed up. Before a week or so ago, I never had this problem, and the printer worked reliably. So, it's a recent bug. At what point in the workflow I don't know. More information when I have it. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/368977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784903] [NEW] Volume keys auto-repeat indefinitely in Medion laptop
Public bug reported: Summary: Several models of Medion laptops need to be added to `/lib/udev/hwdb.d/60-keyboard.hwdb` so that volume keys don't auto- repeat indefinitely. I just installed Xubuntu on a Medion P6689 MD61019 laptop, and it turns out that pressing the volume keys (Fn-F11/F12) causes them to auto- repeat indefinitely, increasing/decreasing the volume until reaching 100%/0%. Same happens with mute (Fn-F10). Apparently these keys only send key press events but not key release ones. It seems that this issue is common in Medion laptops: * https://askubuntu.com/questions/994333/volume-buttons-stay-pressed * https://askubuntu.com/questions/1048531/volume-control-keys-mute-volume-up-down-auto-repeat-key-presses * https://bbs.archlinux.org/viewtopic.php?id=233114 For those affected by this bug, I posted a workaround here: https://askubuntu.com/a/1061500/854656 I've attached the file with the workaround as I have it in my laptop right now. Ubuntu release: Xubuntu 18.04.1 64b (bionic) Package version: udev 237-3ubuntu10.3 Laptop model:Medion P6689 MD61019 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: auto-repeat keyboard keys laptop medion udev volume ** Attachment added: "Lines to add to /lib/udev/hwdb.d/60-keyboard.hwdb (possibly with a different :pn pattern)" https://bugs.launchpad.net/bugs/1784903/+attachment/5170491/+files/99-keyboard-medion-vol-fix.hwdb ** Tags added: laptop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784903 Title: Volume keys auto-repeat indefinitely in Medion laptop Status in systemd package in Ubuntu: New Bug description: Summary: Several models of Medion laptops need to be added to `/lib/udev/hwdb.d/60-keyboard.hwdb` so that volume keys don't auto- repeat indefinitely. I just installed Xubuntu on a Medion P6689 MD61019 laptop, and it turns out that pressing the volume keys (Fn-F11/F12) causes them to auto-repeat indefinitely, increasing/decreasing the volume until reaching 100%/0%. Same happens with mute (Fn-F10). Apparently these keys only send key press events but not key release ones. It seems that this issue is common in Medion laptops: * https://askubuntu.com/questions/994333/volume-buttons-stay-pressed * https://askubuntu.com/questions/1048531/volume-control-keys-mute-volume-up-down-auto-repeat-key-presses * https://bbs.archlinux.org/viewtopic.php?id=233114 For those affected by this bug, I posted a workaround here: https://askubuntu.com/a/1061500/854656 I've attached the file with the workaround as I have it in my laptop right now. Ubuntu release: Xubuntu 18.04.1 64b (bionic) Package version: udev 237-3ubuntu10.3 Laptop model:Medion P6689 MD61019 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1784903/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784897] [NEW] [HDA-Intel - HDA Intel PCH, playback] Playback problem
Public bug reported: Plus de son sur la prise jack depuis le noyau 4.4.0.131. Le noyau 4.4.0.127 continue à bien fonctionner. Dell inspiron 5667. 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: USERPID ACCESS COMMAND /dev/snd/controlC0: pierre 1521 F pulseaudio CurrentDesktop: GNOME Date: Wed Aug 1 18:28:12 2018 InstallationDate: Installed on 2016-10-12 (658 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_Type: None of the above Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.9 dmi.board.name: 03XWWJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5767:pvr:rvnDellInc.:rn03XWWJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5767 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T10:48:57.448177 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784897 Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Plus de son sur la prise jack depuis le noyau 4.4.0.131. Le noyau 4.4.0.127 continue à bien fonctionner. Dell inspiron 5667. 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: USERPID ACCESS COMMAND /dev/snd/controlC0: pierre 1521 F pulseaudio CurrentDesktop: GNOME Date: Wed Aug 1 18:28:12 2018 InstallationDate: Installed on 2016-10-12 (658 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Audio interne - HDA Intel PCH Symptom_Type: None of the above Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/30/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.9 dmi.board.name: 03XWWJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.9:bd11/30/2016:svnDellInc.:pnInspiron5767:pvr:rvnDellInc.:rn03XWWJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5767 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T10:48:57.448177 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update
>From the upstream policykit bug entry, it is actually a misuse of the policykit API from brltty. I have uploaded a fix in Debian's brltty 5.6-5. Ubuntu should definitely include the policykit-fix patch contained in that 5.6-5 version as an update to ubuntu 18.04, otherwise all blind users will have the issue, thus unable to use the graphical desktop. ** Package changed: policykit-1 (Ubuntu) => brltty (Ubuntu) ** Changed in: brltty (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1782320 Title: Braille display inoperable in GUI since polkit-update Status in brltty package in Ubuntu: Confirmed Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy brltty brltty: Installed: 5.5-4ubuntu2 Candidate: 5.5-4ubuntu2 Version table: *** 5.5-4ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy policykit-1-gnome policykit-1-gnome: Installed: (none) Candidate: 0.105-6ubuntu2 Version table: 0.105-6ubuntu2 500 500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Expected behavior: After a system upgrade, the braille display should function as before the upgrade. Actual behavior: Since the upgrade, the braille display only works in console mode (Ctrl+Alt+F3, -F4, etc.) In GUI mode, the display reads "Screen not in text mode". Restarting Orca (screenreader) has no effect. Restarting the system has no effect. This is the upgrade command, taken from /var/log/apt/history.log: Start-Date: 2018-07-17 07:47:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1) End-Date: 2018-07-17 07:47:04 These are the error messages taken from /var/log/syslog: Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 accepted: local Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: polkit_authority_check_authorization_sync error 11: Resource temporarily unavailable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: brltty 5.5-4ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jul 18 11:03:27 2018 ExecutablePath: /bin/brltty InstallationDate: Installed on 2018-05-15 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 /usr/local/lib/libgcrypt.so.20.2.2 SourcePackage: brltty UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1782320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
The attachment "proposed_solution.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: New Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 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 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1710637] Re: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland
Seeing this same issue in 18.04 since a recent update. The dumpkeys fix appears to resolve for now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1710637 Title: Input falls through to gdm3 and terminates the session on Ctrl+C after udevadm trigger is executed under wayland Status in Snappy: Won't Fix Status in console-setup package in Ubuntu: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in console-setup source package in Trusty: New Status in gdm3 source package in Trusty: New Status in gnome-shell source package in Trusty: New Status in mutter source package in Trusty: New Status in systemd source package in Trusty: New Status in console-setup source package in Xenial: New Status in gdm3 source package in Xenial: New Status in gnome-shell source package in Xenial: New Status in mutter source package in Xenial: New Status in systemd source package in Xenial: New Bug description: = Test Cases = Test Case 1: - Login under Wayland (session Ubuntu) - Open a terminal - snap install gimp - Wait until installation finishes successfully - In the terminal window press CTRL+C Result: - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed Test Case 2: - Login under Wayland (session Ubuntu) - Open a terminal and type the following command: $ sudo udevadm trigger - In the terminal window press CTRL+C Result - Expected: ^C is displayed in the terminal and the prompt is at the start of a new line - Actual: The session is terminated and the login screen is displayed = Original Description = Multiple times a day I find myself without a session after hitting Ctrl+C in a terminal, it seems the input falls through the Ubuntu/GNOME session and to gdm, which itself decides to terminate. Even worse, when this happens, you can briefly see your login password in plaintext in the virtual terminal. You can see the password however long you want if you stop the gdm service when this happens. I don't have a good way to reproduce, but it seems locking the session with a keyboard shortcut, subsequently unlocking it, maybe suspending, at some point brings this behaviour into the picture, until the session dies with a Ctrl+C. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12 Uname: Linux 4.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Aug 14 15:54:34 2017 InstallationDate: Installed on 2016-05-06 (464 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gdm3 UpgradeStatus: Upgraded to artful on 2017-07-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1710637/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784887] [NEW] Python3
Public bug reported: I am trying to install a smart card reader on USB, and it requires the following commands fro terminal: sudo apt-get update sudo apt-get install libacr38u sudo apt-get install libccid sudo apt-get libpcsclite1 sudo apt-get install pcscd Most of them reported a failure on Python3. I have tried an upgrade of Python3 thru Syynaptic but I received a similar answer. I am a newbie on Linux/Ubuntu so I apologize, but I need help. I use: Ubuntu 18.04.1 LTS ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1784887 Title: Python3 Status in python3-defaults package in Ubuntu: New Bug description: I am trying to install a smart card reader on USB, and it requires the following commands fro terminal: sudo apt-get update sudo apt-get install libacr38u sudo apt-get install libccid sudo apt-get libpcsclite1 sudo apt-get install pcscd Most of them reported a failure on Python3. I have tried an upgrade of Python3 thru Syynaptic but I received a similar answer. I am a newbie on Linux/Ubuntu so I apologize, but I need help. I use: Ubuntu 18.04.1 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1784887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315212] Re: [CA0106 - CA0106, playback] Playback problem - Surround dies, no valid output
** Changed in: alsa-driver Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1315212 Title: [CA0106 - CA0106, playback] Playback problem - Surround dies, no valid output Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Incomplete Bug description: This is tested against a Creative Labs Sounblaster live! (sb0410) card and a SoundBlaster Audigy se (sb0570). Both of them behave strangely, output coming through some, but not all speakers, etc. This was working in 13.10 under the sb0410. the ca0106 driver is the same for both cards. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshp 30385 F pulseaudio /dev/snd/controlC0: joshp 30385 F pulseaudio CurrentDesktop: Unity Date: Thu May 1 21:37:12 2014 InstallationDate: Installed on 2014-04-28 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed Symptom_Card: Built-in Audio - Intel ICH6 Symptom_Type: None of the above Title: [CA0106 - CA0106, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0G8310 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2006:svnDellInc.:pnOptiPlexGX280:pvr:rvnDellInc.:rn0G8310:rvr:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex GX280 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1315212/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 425704] Re: [Ubuntu server] Capslock don't turn on LED
Just lost an afternoon thanks to that. This introduces fun bugs with QEMU and remote viewers because the VM can't tell that it has the capslock led on (since it's not really) leading to the state blinking when the viewer tries to sync it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/425704 Title: [Ubuntu server] Capslock don't turn on LED Status in console-setup package in Ubuntu: Triaged Status in console-setup package in Debian: Confirmed Bug description: Karmic server i386 alpha 5 When I press Capslock then LED don't turn on. But Shift switch register normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/425704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315212]
-- 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/308. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1315212 Title: [CA0106 - CA0106, playback] Playback problem - Surround dies, no valid output Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Incomplete Bug description: This is tested against a Creative Labs Sounblaster live! (sb0410) card and a SoundBlaster Audigy se (sb0570). Both of them behave strangely, output coming through some, but not all speakers, etc. This was working in 13.10 under the sb0410. the ca0106 driver is the same for both cards. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: joshp 30385 F pulseaudio /dev/snd/controlC0: joshp 30385 F pulseaudio CurrentDesktop: Unity Date: Thu May 1 21:37:12 2014 InstallationDate: Installed on 2014-04-28 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:CA0106 failed Symptom_Card: Built-in Audio - Intel ICH6 Symptom_Type: None of the above Title: [CA0106 - CA0106, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2006 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0G8310 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2006:svnDellInc.:pnOptiPlexGX280:pvr:rvnDellInc.:rn0G8310:rvr:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex GX280 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1315212/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697120] Re: artful's apt-file and aptitude complains about Ubuntu sources.list
** Changed in: apt (Ubuntu Zesty) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1697120 Title: artful's apt-file and aptitude complains about Ubuntu sources.list Status in apt package in Ubuntu: Fix Released Status in apt source package in Zesty: Won't Fix Status in apt package in Debian: Fix Released Bug description: [Impact] apt-file is now difficult to use with about a dozen warnings like this: W: Target Contents-deb-legacy (Contents-amd64) is configured multiple times in /etc/apt/sources.list:6 and /etc/apt/sources.list:17 For reference, this is line 6: deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted And this is line 17: deb http://us.archive.ubuntu.com/ubuntu/ artful universe This is how Ubuntu's default sources.list has been structured since the beginning? (or at least more than a decade). What I expect - The warning isn't specific enough. Lines 6 and 17 are not actually duplicates. The warning could be removed or fixed so that it doesn't complain about non-duplicates. Or the warning could be disabled on Ubuntu. See also LP: #1579372 [Test case] Install apt-file and update, make sure that the warnings are gone. [Regression potential] Warnings about duplicate index targets containing "legacy" in their configured name are not shown anymore, thus it's harder to "fix" servers. But apart from that, which was the goal, I don't see any. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1697120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667725] Re: [feature request] make full ppa signing public key available over https
** Also affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
** Changed in: software-properties (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1667725
Title:
[feature request] make full ppa signing public key available over
https
Status in Launchpad itself:
Fix Released
Status in software-properties package in Ubuntu:
In Progress
Bug description:
Currently, for a ppa, launchpad makes the long key fingerprint
available over https. I'd like to request that it also make the full
public key available over https.
Many people use add-apt-repository extensively for using ppas ('add-
apt-repository -y smoser/archive')
As I understand it, that basically does:
a. request the 'archive urls', 'description' and long key fingerprint over
https from launchpad.net
b. does gpg --recv from
hkp://keyserver.ubuntu.com:80/ (or the --keyserver argument)
c. adds the result of 'b' to apt using 'apt-key'
Since launchpad is the owner of the signing key for the ppa, why not
have it just give us the full public key over the same api that it
provides the other bits of information?
My experience is that gpg servers are less reliable than we'd like,
and even if they were as reliable as launchpad, any use of a ppa now
effectively depends on 2 external systems when 1 could suffice.
To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad/+bug/1667725/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
Here is my proposed solution (attached) to the problem - I do not claim to fully understand cups' authentication system but it seems to me from looking at the old code to cups/auth.c and the new broken code that this patch would make the unix domain socket authentication work the same as it did before: ** Patch added: "proposed_solution.patch" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+attachment/5170387/+files/proposed_solution.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: New Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 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 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783298] Re: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
My suggested work around above does not fix the issue (completely) because systemd is in charge of the socket - so as well as commenting out "Listen /run/cups/cups.sock" in /etc/cups/cupsd.conf you have to also do the following: systemctl stop cups.service systemctl stop cups.socket rm /run/cups/cups.sock systemctl disable cups.socket systemctl start cups.service -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1783298 Title: AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work Status in cups package in Ubuntu: New Bug description: Hi, We have our printers configured to print to a Windows print server. In Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup seems to be acting more like AuthInfoRequired username,password i.e. it prompts for a password when printing rather than using the available Kerberos credentials. We are using an unaltered cupsd.conf file and are adding printers with the following command: lpadmin -p "printer" -D "Printer" -L "room" -v "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4 -o printer-error-policy=abort-job -o auth-info-required=negotiate -m "CIS/hp-officejet_pro_476_576_series-ps.ppd" the smb backend has been linked to /usr/lib/x86_64-linux- gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile as it's blocked by default) and the permissions on this file changed to 700 (owner root) as per manpage instructions. When using lp -d printer /tmp/test.txt I get the following response: Password for myuid on localhost? Typing my password gets the job accepted to the queue but it does spool to the Windows Print Server and in the error_log file I can see D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_INFO_REQUIRED=negotiate D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0 D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set As I said earlier this all works perfectly on Xenial and Trusty. (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 10.13) Any ideas how to fix this? Thanks, Ian. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 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 Date: Tue Jul 24 10:03:57 2018 InstallationDate: Installed on 2018-06-22 (31 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical Mouse Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 790 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0HY9JP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 790 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 389632] Re: "100 papercuts" must setup wireless printing each time router is reset
Hello Nidoo, 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 Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/389632 Title: "100 papercuts" must setup wireless printing each time router is reset Status in cups package in Ubuntu: Incomplete Bug description: Binary package hint: cups To put it simply, when the wireless router or printer is reset, it connects to each other no problem. Ubuntu still has the configuration of the printer, but all sends timeout because Ubuntu doesn't automatically detect the new wireless address of the printer. The only workaround is to delete the current settings and reinstall the printer so it can detect the new printer address. As a usability issue having to reinstall a wireless printer each time it's turned off or reset instead of automatically detecting the new wireless address would be a major turnoff to any user old or new. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 Lpstat: device for Photosmart-C7200-series: hp:/net/Photosmart_C7200_series?ip=192.168.2.10 MachineType: Dell Inc. Inspiron 1720 NonfreeKernelModules: nvidia Package: cups 1.3.9-17ubuntu3.2 Papersize: letter PpdFiles: Photosmart-C7200-series: HP Photosmart c7200 Series hpijs, 3.9.2 ProcCmdLine: root=UUID=d4bbf262-5064-454f-89b6-e5a3b1300bf0 ro quiet splash ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.28-13.44-generic SourcePackage: cups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/389632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783138] Re: hinic interfaces aren't getting predictable names
** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in systemd source package in Bionic: Invalid Bug description: [Impact] Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system with both 2-port hinic and 2-port igb devices, the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic before igb loaded. But if igb completes loading first, the hinic interfaces would be eth2 & eth3. [*] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ [Test Case] grep ^eth /proc/net/dev [Fix] There's an upstream fix that properly associates the hinic interfaces with their PCI devices, providing udev with the info it needs to generate a predictable name. [Regression Risk] The big regression risk here is with existing bionic installs w/ hinic devices. They will be currently using "eth" names by default, and this change will cause those names to change to "enP" names after upgrade. However, in only certain configs are those "eth" names reliable (e.g. only NIC in the system is a hinic plug-in card). It sucks to introduce such a change in a stable release - but users will be bitten by this when they upgrade or transition to the HWE kernel anyway if we don't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
** Changed in: linux (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1780227 Title: locking sockets broken due to missing AppArmor socket mediation patches Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Committed Status in apparmor source package in Xenial: Invalid Status in linux source package in Xenial: Fix Committed Status in apparmor source package in Bionic: Invalid Status in linux source package in Bionic: Fix Committed Bug description: Hey, Newer systemd makes use of locks placed on AF_UNIX sockets created with the socketpair() syscall to synchronize various bits and pieces when isolating services. On kernels prior to 4.18 that do not have backported the AppArmor socket mediation patchset this will cause the locks to be denied with EACCESS. This causes systemd to be broken in LXC and LXD containers that do not run unconfined which is a pretty big deal. We have seen various bug reports related to this. See for example [1] and [2]. If feasible it would be excellent if we could backport the socket mediation patchset to all LTS kernels. Afaict, this should be 4.4 and 4.15. This will unbreak a whole range of use-cases. The socket mediation patchset is available here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4 [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779 [2]: https://github.com/systemd/systemd/issues/9493 Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1780227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 363497] Re: Cups/printers.conf file prompts for password.
Hello George, 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 Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/363497 Title: Cups/printers.conf file prompts for password. Status in cups package in Ubuntu: Incomplete Bug description: Have an issue with network printing. I keep getting this error tree connect failed (NT_STATUS_ACCESS_DENIED). I don't know why but out of nowhere this started. Somehow, it wants a password but none have been set. So, I read the printers.conf file after setting up the printer BUT before doing a print test. sudo gedit /etc/cups/printers.conf # Printer configuration file for CUPS v1.3.9 # Written by cupsd on 2009-04-18 09:11 Info Canon i950 Location DeviceURI smb://192.168.0.4/i950 State Idle StateTime 1240060296 Accepting Yes Shared Yes JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job Looks good. Then trying to test print it reads; # Printer configuration file for CUPS v1.3.9 # Written by cupsd on 2009-04-18 09:11 AuthInfoRequired username,password Info Canon i950 Location DeviceURI smb://192.168.0.4/i950 State Idle StateTime 1240060296 Accepting Yes Shared Yes JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job It adds AuthInfoRequired username,password bt itself! I tried to delete AuthInfoRequired username,password but it simply rewrites the line. How can this be fixed? George To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/363497/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 365170] Re: Printing pdf creates huge file in /var/spool/cups/tmp
Hello David, 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 Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/365170 Title: Printing pdf creates huge file in /var/spool/cups/tmp Status in cups package in Ubuntu: Incomplete Bug description: When I try to print the attached pdf, my disk space fills up with a 984M file in /var/spool/cups/tmp . Distribution: Jaunty. Evince version: 2.26.0. Poppler: 0.10.5 (cairo) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/365170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 384791] Re: Turn on browsing
Hello Jimmy, 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 Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/384791 Title: Turn on browsing Status in cups package in Ubuntu: Incomplete Bug description: Binary package hint: cups When having a printer server it makes sense to have Browsing On (instead of Browsing Off). I find no reason to have it turned off when running a single system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/384791/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 388850] Re: /etc/init.d/cups writes to /usr
Hello Test tools, 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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/388850 Title: /etc/init.d/cups writes to /usr Status in cups package in Ubuntu: New Bug description: Binary package hint: cups Hello, in /etc/init.d/cups it writes to /usr hierarchy, as fas as I understood violating FHS. chown root:lpadmin /usr/share/ppd/custom 2>/dev/null || true chmod 3775 /usr/share/ppd/custom 2>/dev/null || true Don't know if at runtime write access is necessary, but that directory should then moved to /var $ lsb_release -rd Description: Ubuntu karmic (development branch) Release: 9.10 $ LANG= apt-cache policy cups cups: Installed: 1.3.10-5 Candidate: 1.3.10-5 Version table: *** 1.3.10-5 0 500 http://nl.archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status This is the only package I have seen, writing unattended to /usr Best regards, Roland "Test-tools" Bär To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/388850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 346707] Re: missing ssl-certificate results in misleading error "Unable to read configuration file '/etc/cups/cupsd.conf' - exiting
Hello H. Dirk, 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 Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/346707 Title: missing ssl-certificate results in misleading error "Unable to read configuration file '/etc/cups/cupsd.conf' - exiting Status in cups package in Ubuntu: Incomplete Bug description: Binary package hint: cups if the symlink /etc/cups/ssl/server.crt is broken (e.g. snakeoil certificate removed by incident) in the syslog occures the following misleading error message: Unable to read configuration file '/etc/cups/cupsd.conf' - exiting! In contradiction the entry in the cups/error.log is more helpfull ;-) "/etc/cups/ssl/server.crt" is a bad symlink - No such file or directory ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: nvidia Package: cups 1.3.9-2ubuntu8 ProcEnviron: LC_PAPER=de_DE.UTF-8 SHELL=/bin/bash PATH=/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11/bin:/usr/games:/c42home/username/bin LANG=de_DE.UTF-8 LANGUAGE=de_DE:de:en_GB:en SourcePackage: cups Uname: Linux 2.6.27-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/346707/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784850] [NEW] Xorg crashed with SIGABRT in Osabort
Public bug reported: 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1784850 Title: Xorg crashed with SIGABRT in Osabort Status in xorg package in Ubuntu: New 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
[Touch-packages] [Bug 1769386] Re: Cable network does not get recognized anymore, wifi works
After a fresh install of 18.04 Bionic, my USB wireless adapter didn't show up. Running 'lsusb' provided the device ID for the adapter as 0bda:a811 Realtek Semiconductor Corp. Cross-referencing that ID with 'Ubuntu 18.04' I eventually fell down the rabbit hole at askubuntu.com and landed here: https://askubuntu.com/questions/970283/ubuntu-17-10 -drivers-not-found-working-properly This page has instructions on cloning this git repo: git clone https://github.com/gnab/rtl8812au.git After a 'make make install' and a reboot, wireless networks show up and internet connectivity is restored. Hope this helps anyone with a similar device ID -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1769386 Title: Cable network does not get recognized anymore, wifi works Status in network-manager package in Ubuntu: Confirmed Status in Arch Linux: New Bug description: ubuntu 16.04 LTS cable does not connect anymore, wifi working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 5 19:27:18 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-30 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/1 WiFi-2.4-3569 7103236e-31c4-43d6-871d-14f3cda4b657 /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0f1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783571] Re: Set Yaru as default
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 Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783571] Re: Set Yaru as default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: yaru-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783571] Re: Set Yaru as default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783571] Re: Set Yaru as default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783571] Re: Set Yaru as default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Confirmed Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776074] Re: indicator-datetime shouldn't recommend big ubuntu-touch-sounds package (maybe Suggests should be used instead)
** Branch linked: lp:~baltix-members/baltix-default-settings/ubuntu- defaults-baltix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1776074 Title: indicator-datetime shouldn't recommend big ubuntu-touch-sounds package (maybe Suggests should be used instead) Status in Default settings and artwork for Baltix OS: In Progress Status in indicator-datetime package in Ubuntu: Confirmed Bug description: indicator-datetime package has big ubuntu-touch-sounds package in Recommends field even in latest Ubuntu Bionic release. gnome-panel recommends indicator-applet-complete and indicator-applet- complete recommends indicator-datetime, so big and not useful ubuntu- touch-sounds is installed in all desktop systems, where gnome- flashback (gnome-panel) desktop environment is used. I think ubuntu-touch-sounds should be removed from Recommends field and if there are some cases, where ubuntu-touch-sounds is usefull for indicator-datetime, then Suggests should be used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1776074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782190] Re: Set default interface font size to 11 for communitheme sessions
Hello Frederik, or anyone else affected, Accepted ubuntu-settings into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- settings/18.04.6 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! ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1782190 Title: Set default interface font size to 11 for communitheme sessions Status in ubuntu-settings package in Ubuntu: Fix Committed Status in ubuntu-settings source package in Bionic: Fix Committed Bug description: [Impact] * communitheme snap users see the gnome shell overview window thumbnail labels cutted off * 18.04 users can install the communitheme snap from within gnome- software * To fix this the default font size of the interface needs to be switched to 11 (again) [Test Case] * Install ubuntu * install the communitheme snap * reboot * select the communitheme snap session and login * Open "activities" by clicking "activities" in the GNOME shell's upper left corner or by pressing the super/ubuntu/windows key * Each window thumbnail is labeled with a text which is now cut * This is caused by a bug in gnome-shell which can't handle any other font size than 11 for any other font beside cantarell * install the new ubuntu-settings version * open again activities * check that window thumbnails aren't cut anymore [Regression Potential] * It's affecting only the communitheme session, not available by default and reverting to the same default than ubuntu main session [Other Info] * Gitlab upstream issue: https://gitlab.gnome.org/GNOME/gnome- shell/issues/378 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1782190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784833] [NEW] package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: this occured during update from 16.04.5 to 18.04.1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-25.27~16.04.1-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 1 07:33:46 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-08-28 (702 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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: dbus Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1784833 Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in dbus package in Ubuntu: New Bug description: this occured during update from 16.04.5 to 18.04.1 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-25.27~16.04.1-generic 4.8.1 Uname: Linux 4.8.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 1 07:33:46 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-08-28 (702 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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: dbus Title: package dbus 1.12.2-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1784833/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776074] Re: indicator-datetime shouldn't recommend big ubuntu-touch-sounds package (maybe Suggests should be used instead)
indicator-datetime is the only package in Ubuntu 18.04 and older that recommends/depends on ubuntu-touch-sounds, no more packages uses ubuntu- touch-sounds, so, please make usage of ubuntu-touch-sounds in indicator- datetime optional for Desktop systems ** Changed in: baltix-default-settings Status: New => In Progress ** Changed in: baltix-default-settings Importance: Undecided => Medium ** Changed in: baltix-default-settings Assignee: (unassigned) => Mantas Kriaučiūnas (mantas) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1776074 Title: indicator-datetime shouldn't recommend big ubuntu-touch-sounds package (maybe Suggests should be used instead) Status in Default settings and artwork for Baltix OS: In Progress Status in indicator-datetime package in Ubuntu: Confirmed Bug description: indicator-datetime package has big ubuntu-touch-sounds package in Recommends field even in latest Ubuntu Bionic release. gnome-panel recommends indicator-applet-complete and indicator-applet- complete recommends indicator-datetime, so big and not useful ubuntu- touch-sounds is installed in all desktop systems, where gnome- flashback (gnome-panel) desktop environment is used. I think ubuntu-touch-sounds should be removed from Recommends field and if there are some cases, where ubuntu-touch-sounds is usefull for indicator-datetime, then Suggests should be used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1776074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711101] Re: Audio doesn't auto switch away from HDMI after unplugging HDMI
Launchpad has imported 10 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=96211. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-05-25T12:47:51+00:00 Christian Hergert wrote: Setup: Lenovo Gen3 X1 Carbon w/ Intel GPU Audio redirected via HDMI to a samsung TV Both Wayland and Xorg sessions I manually set the audio output to the HDMI output in GNOME control center. I thought it would remember my setting like it does for monitor layout, but that does not seem to happen. It sounds like is supposed to be handled by PulseAudio? Likewise, when I remove the HDMI device, I would expect audio to be redirected back to my laptop speakers. Is it correct that this should be handled by PulseAudio and not by something like gnome-settings-daemon/control-center? Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711101/comments/0 On 2016-05-25T12:56:26+00:00 Tanu Kaskinen wrote: What's the PulseAudio version? What does "pactl list cards" show when you have the TV plugged in and directed audio to it, and what does it show after unplugging the TV? Close gnome-control-center when plugging out the cable - I've seen g-c-c interfering with the routing during unplug events. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711101/comments/1 On 2016-05-25T13:23:03+00:00 Christian Hergert wrote: (In reply to Tanu Kaskinen from comment #1) > What's the PulseAudio version? >From F24 - pulseaudio-8.0-6.fc24.x86_64 > What does "pactl list cards" show when you have the TV plugged in and > directed audio to it, and what does it show after unplugging the TV? I'll attach two versions. First is connected and sound directed to TV. Second is TV unplugged but before manually changing output back to laptop speakers. > Close gnome-control-center when plugging out the cable - I've seen g-c-c > interfering with the routing during unplug events. I've seen this too. I think it has to do with GtkTreeViewSelection updating the "browse-mode" selection when displaying the sound settings. Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711101/comments/2 On 2016-05-25T13:23:35+00:00 Christian Hergert wrote: Created attachment 124083 with audio directed to TV via HDMI Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711101/comments/3 On 2016-05-25T13:24:12+00:00 Christian Hergert wrote: Created attachment 124084 with tv/hdmi disconnected but sound has not been redirected to local speakers Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711101/comments/4 On 2016-05-25T13:42:08+00:00 Tanu Kaskinen wrote: Ok, so HDMI is on a different alsa card than analog output. That explains why unplugging HDMI doesn't result in moving audio to the analog output. We don't currently automatically reroute from one card to another on an unplug event. This should be fixed, but I can't give any timeline. You also had some issue with remembering routing choices. Is it so that if you route to HDMI and reboot, audio isn't routed to HDMI any more, even if the HDMI cable stays plugged in all the time? Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711101/comments/5 On 2016-05-25T14:00:52+00:00 Christian Hergert wrote: (In reply to Tanu Kaskinen from comment #5) > You also had some issue with remembering routing choices. Is it so that if > you route to HDMI and reboot, audio isn't routed to HDMI any more, even if > the HDMI cable stays plugged in all the time? I haven't tested that (and it's a bit hard for me to test right now). My problem is that I unplug the HDMI, go work in another part of the house, and then come back and plug the HDMI back in. I would expect the audio/video to be redirected as a pair (even though they are separate sub-systems in implementation). Reply at: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1711101/comments/6 On 2016-05-28T01:22:02+00:00 Raymond wrote: (In reply to Tanu Kaskinen from comment #5) > Ok, so HDMI is on a different alsa card than analog output. That explains > why unplugging HDMI doesn't result in moving audio to the analog output. We > don't currently automatically reroute from one card
[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps
but still present on Cosmic from last ISO: corrado@corrado-HP-p5-cc-0731:~$ snap list Name VersionRev Tracking Publisher Notes core 16-2.33.1 4917 stablecanonical core gnome-3-26-1604 3.26.0 70stable/… canonical - gnome-calculator 3.28.2 180 stable/… canonical - corrado@corrado-HP-p5-cc-0731:~$ cat /var/log/installer/media-info Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180731) corrado@corrado-HP-p5-cc-0731:~$ apt policy livecd-rootfs livecd-rootfs: Installed: (none) Candidate: 2.533 Version table: 2.533 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages corrado@corrado-HP-p5-cc-0731:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1772844 Title: snapd didn't initialize all the seeded snaps Status in OEM Priority Project: Fix Released Status in snapd: New Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Status in livecd-rootfs source package in Bionic: Fix Released Status in ubuntu-meta source package in Bionic: New Bug description: snapd didn't initialize all the seeded snaps bionic-desktop-amd64.iso (20180522) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snapd 2.32.9+18.04 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 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 22 22:59:18 2018 InstallationDate: Installed on 2018-05-23 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782510] Re: lightdm automatically logs in after logout
After the second login, the session is not comlete, e.g. groups from pam+ldap are missing. Also the default KDE Wallet is not opened upon the first successful login. sddm works as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1782510 Title: lightdm automatically logs in after logout Status in lightdm package in Ubuntu: Confirmed Bug description: Lightdm makes it impossible to logout. After I logout the lightdm logs me automatically backs in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jul 19 01:18:52 2018 InstallationDate: Installed on 2016-04-26 (814 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1782510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782510] Re: lightdm automatically logs in after logout
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1782510 Title: lightdm automatically logs in after logout Status in lightdm package in Ubuntu: Confirmed Bug description: Lightdm makes it impossible to logout. After I logout the lightdm logs me automatically backs in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jul 19 01:18:52 2018 InstallationDate: Installed on 2016-04-26 (814 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1782510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784796] [NEW] apt update fails - 'std::runtime_error' what(): random_device::__x86_rdrand(void)
Public bug reported: I am seeing the following error randomly on issuing sudo apt update: Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [65.4 kB] 0% [1 InRelease gpgv 69.9 kB] [3 InRelease 7,779 B/65.4 kB 12%]terminate called after throwing an instance of 'std::runtime_error' what(): random_device::__x86_rdrand(void) Aborted Once this occurs, it normally takes at least one, but frequently more than one reboot to resolve. It only happens on one of my systems - a self-build server based on Asrock Rack motherboard C3758D4I-4L running Ubuntu server. I've observed the same issue on the same hardware with the Ubuntu 18.04.1 live ISO. I'm booting in Legacy mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.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 Date: Wed Aug 1 08:37:28 2018 InstallationDate: Installed on 2018-04-28 (94 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1784796 Title: apt update fails - 'std::runtime_error' what(): random_device::__x86_rdrand(void) Status in apt package in Ubuntu: New Bug description: I am seeing the following error randomly on issuing sudo apt update: Get:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [65.4 kB] 0% [1 InRelease gpgv 69.9 kB] [3 InRelease 7,779 B/65.4 kB 12%]terminate called after throwing an instance of 'std::runtime_error' what(): random_device::__x86_rdrand(void) Aborted Once this occurs, it normally takes at least one, but frequently more than one reboot to resolve. It only happens on one of my systems - a self-build server based on Asrock Rack motherboard C3758D4I-4L running Ubuntu server. I've observed the same issue on the same hardware with the Ubuntu 18.04.1 live ISO. I'm booting in Legacy mode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.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 Date: Wed Aug 1 08:37:28 2018 InstallationDate: Installed on 2018-04-28 (94 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1784796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784788] Re: package udev 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784788 Title: package udev 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: System fails to boot automativally ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu21.4 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 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.ubuntu-social-kit.rules Date: Tue Jul 31 12:55:43 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-12-07 (236 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0177 Realtek Semiconductor Corp. Bus 001 Device 003: ID 04f2:b52d Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=5b0c6631-87e0-4f15-a111-57ecba5de5da ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: systemd Title: package udev 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EF dmi.board.vendor: HP dmi.board.version: 63.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=250 dmi.product.name: HP 250 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1784788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784788] [NEW] package udev 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: System fails to boot automativally ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu21.4 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 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.ubuntu-social-kit.rules Date: Tue Jul 31 12:55:43 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-12-07 (236 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0177 Realtek Semiconductor Corp. Bus 001 Device 003: ID 04f2:b52d Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=5b0c6631-87e0-4f15-a111-57ecba5de5da ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: systemd Title: package udev 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EF dmi.board.vendor: HP dmi.board.version: 63.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=250 dmi.product.name: HP 250 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1784788 Title: package udev 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: System fails to boot automativally ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu21.4 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 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.ubuntu-social-kit.rules Date: Tue Jul 31 12:55:43 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-12-07 (236 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:0177 Realtek Semiconductor Corp. Bus 001 Device 003: ID 04f2:b52d Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP 250 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=5b0c6631-87e0-4f15-a111-57ecba5de5da ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: systemd Title: package udev 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.09 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EF dmi.board.vendor: HP dmi.board.version: 63.28 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=250 dmi.product.name: HP 250 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1784788/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps
problem disappeared in Ubuntu Bionic 18.04.1 corrado@corrado-HP-p3-bionic:~$ apt policy livecd-rootfs livecd-rootfs: Installed: (none) Candidate: 2.525.5 Version table: 2.525.5 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 2.525 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages corrado@corrado-HP-p3-bionic:~$ cat /var/log/installer/media-info Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) corrado@corrado-HP-p3-bionic:~$ snap list Name VersionRev Tracking Publisher Notes core 16-2.33.1 4917 stablecanonical core gnome-3-26-1604 3.26.0 70stable/… canonical - gnome-calculator 3.28.2 180 stable/… canonical - gnome-characters 3.28.2 103 stable/… canonical - gnome-logs3.28.2 37stable/… canonical - gnome-system-monitor 3.28.2 51stable/… canonical - gtk-common-themes 0.1319 stable/… canonical - corrado@corrado-HP-p3-bionic:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1772844 Title: snapd didn't initialize all the seeded snaps Status in OEM Priority Project: Fix Released Status in snapd: New Status in livecd-rootfs package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Status in livecd-rootfs source package in Bionic: Fix Released Status in ubuntu-meta source package in Bionic: New Bug description: snapd didn't initialize all the seeded snaps bionic-desktop-amd64.iso (20180522) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snapd 2.32.9+18.04 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 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 22 22:59:18 2018 InstallationDate: Installed on 2018-05-23 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
