[Touch-packages] [Bug 1739531] Re: apport-collect SHOULD NOT collect gnome-shell command history and favorites
I agree. I've never seen that happen before either, till now. ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1739531 Title: apport-collect SHOULD NOT collect gnome-shell command history and favorites Status in apport package in Ubuntu: Confirmed Bug description: In https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1739525/comments/4, I ran apport-collect for that bug report. To my horror, it posted "org.gnome.shell command-history" and "favorites" in the "GsettingsChanges.txt"! https://launchpadlibrarian.net/349970997/GsettingsChanges.txt It's _completely_ reasonable to see: * enabled-extensions * org.gnome.shell.* diffs * org.gnome.desktop.* diffs But it is _NOT_ acceptable (privacy reasons) to automatically harvest a user's favorites in the gnome-shell, nor their command histories. _IF_ we must harvest for bug-data gathering, it MUST come in a secure mechanism that is private only to submitter + the assigned dev. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1739531/+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
Re: [Touch-packages] [Bug 1738907] Re: Bluetooth audio latency / delay increasing on video streamig
many thx, i Was thinking about bad buffering or wavelength. i'will check this Le 19 déc. 2017 03:41, "Daniel van Vugt" a écrit : > If the delay increases over time then mathematically it sounds like the > output is consuming bits slower than the input. So /maybe/ you have > 48kHz audio being played at 44.1kHz but I would have thought that would > be noticeable (sounding distorted - too low). And even if that's not the > problem, the delay should hit a limit via some buffering limit, after > which it turns into skipping (bug 405294). > > Another thought is to see the suggestion in bug 1677202. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1738907 > > Title: > Bluetooth audio latency / delay increasing on video streamig > > Status in bluez package in Ubuntu: > New > Status in pulseaudio package in Ubuntu: > New > > Bug description: > With my bluetooth headset (A2DP audio protocole) when I watch videos > streaming with Google Chrome for example. there is a delay increasing > between audio and video. I tried to change and set up the audio > latency, but the delay increase, as much as I play bigger video > > > ubuntu 17.04 or 17.10 64bit > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/ > 1738907/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1738907 Title: Bluetooth audio latency / delay increasing on video streamig Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: With my bluetooth headset (A2DP audio protocole) when I watch videos streaming with Google Chrome for example. there is a delay increasing between audio and video. I tried to change and set up the audio latency, but the delay increase, as much as I play bigger video ubuntu 17.04 or 17.10 64bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1738907/+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 1737662] Comment bridged from LTC Bugzilla
--- Comment From indira.pr...@in.ibm.com 2017-12-21 01:06 EDT--- Able to install ubunu1804 build which is out on 20/12 with ISO file successfully without any debootstrap messages. Issue fixed on 20/12 dated daily build (using ISO ) root@whip:/home/dev# uname -a Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@whip:/home/dev# uname -r 4.13.0-17-generic Regards, Indira -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1737662 Title: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system Status in The Ubuntu-power-systems project: Fix Committed Status in busybox package in Ubuntu: Fix Released Status in debian-installer package in Ubuntu: Fix Released Bug description: Problem Description: === Ubuntu1804 installer shows Debootstrap warning messages and not able to proceed with installation Steps to re-create: == > on Witherspoon test system, tried to install ubuntu1804 using netboot install. > Selected mirror path:http://10.xx.11.31:3128 [!] Choose a mirror of the Ubuntu archive ? ? ? Please select an Ubuntu archive mirror. You should use a mirror in ? ? your country or region if you do not know which mirror has the best ? ? Internet connection to you. ? ? ? ? Usually, .archive.ubuntu.com is a good choice. ? ? ? ? Ubuntu archive mirror: ? ? ? ? us.ports.ubuntu.com ? ? ? ?? ? ? ??? > Able to select the disks ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ?/dev/nvme0n1 - 409.6 GB Unknown ? ?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB ? ?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB ? ? ? ?? ? ? ??? > Started installing base system ??? Installing the base system ? ? ?6% ? ? ? ? Retrieving libc6... ? ? ? ??? > Then seen Debootstrap warning messages as below ??? [!!] Install the base system ??? ? ? ?? ? ? Debootstrap warning? ? ? ? Warning: Failure trying to run: chroot /target dpkg-deb -f ? ? ? ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ? ? ? Ex? ? ? ? ? ? ? ? ? ?? ??? [!!] Install the base system ?? ?
[Touch-packages] [Bug 1739509] Re: Why was gstreamer0.10 dropped from Ubuntu
There are still some versions with it https://launchpad.net/ubuntu/+source/gstreamer0.10 ** Changed in: gstreamer0.10 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1739509 Title: Why was gstreamer0.10 dropped from Ubuntu Status in gstreamer0.10 package in Ubuntu: Incomplete Bug description: Why was gstreamer0.10 dropped from Ubuntu? It is still available in debian and many applications do use it https://packages.debian.org/search?keywords=libgstreamer0.10&searchon=names&suite=all§ion=all , e.g. proprietary eTXT Antiplagiat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1739509/+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 1739532] [NEW] apport-collect SHOULD prune out /home/%USER/ from JournalErrors
Public bug reported: During https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1739525, I ran apport-collect. I was happy to see that my hostname from the system logs was pruned to "hostname". Great! However, there are some logs that complain about /home/FOO user ... we SHOULD NOT leak a user's $HOME directory contents (a potential list of local user accounts) into these reports. This MAY be considered as sensitive information. The JournalErrors.txt should prune it. Example of CULPRITS: {{{ Dec 20 21:39:20 hostname com.ubuntu.OneConf[3069]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/FOO/.cache/oneconf/1dfe6d2e52223c637c7bddd90002/other_hosts' Dec 20 21:39:33 hostname com.ubuntu.OneConf[18688]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/BAR/.cache/oneconf/1dfe6d2e52223c637c7bddd90002/other_hosts' }}} The suggestion here, is simply to also prune out usernames from ANY "/home/%USER" or "~%USER" type regexes. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport privacy ** Description changed: During https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1739525, I ran apport-collect. I was happy to see that my hostname from the system logs was pruned to "hostname". Great! However, there are some logs that complain about /home/FOO user ... we SHOULD NOT leak a user's $HOME directory contents (a potential list of local user accounts) into these reports. This MAY be considered as sensitive information. The JournalErrors.txt should prune it. Example of CULPRITS: {{{ Dec 20 21:39:20 hostname com.ubuntu.OneConf[3069]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/FOO/.cache/oneconf/1dfe6d2e52223c637c7bddd90002/other_hosts' Dec 20 21:39:33 hostname com.ubuntu.OneConf[18688]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/BAR/.cache/oneconf/1dfe6d2e52223c637c7bddd90002/other_hosts' }}} + + The suggestion here, is simply to also prune out usernames from ANY + "/home/%USER" or "~%USER" type regexes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1739532 Title: apport-collect SHOULD prune out /home/%USER/ from JournalErrors Status in apport package in Ubuntu: New Bug description: During https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1739525, I ran apport-collect. I was happy to see that my hostname from the system logs was pruned to "hostname". Great! However, there are some logs that complain about /home/FOO user ... we SHOULD NOT leak a user's $HOME directory contents (a potential list of local user accounts) into these reports. This MAY be considered as sensitive information. The JournalErrors.txt should prune it. Example of CULPRITS: {{{ Dec 20 21:39:20 hostname com.ubuntu.OneConf[3069]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/FOO/.cache/oneconf/1dfe6d2e52223c637c7bddd90002/other_hosts' Dec 20 21:39:33 hostname com.ubuntu.OneConf[18688]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/BAR/.cache/oneconf/1dfe6d2e52223c637c7bddd90002/other_hosts' }}} The suggestion here, is simply to also prune out usernames from ANY "/home/%USER" or "~%USER" type regexes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1739532/+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 1739531] [NEW] apport-collect SHOULD NOT collect gnome-shell command history and favorites
Public bug reported: In https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1739525/comments/4, I ran apport-collect for that bug report. To my horror, it posted "org.gnome.shell command-history" and "favorites" in the "GsettingsChanges.txt"! https://launchpadlibrarian.net/349970997/GsettingsChanges.txt It's _completely_ reasonable to see: * enabled-extensions * org.gnome.shell.* diffs * org.gnome.desktop.* diffs But it is _NOT_ acceptable (privacy reasons) to automatically harvest a user's favorites in the gnome-shell, nor their command histories. _IF_ we must harvest for bug-data gathering, it MUST come in a secure mechanism that is private only to submitter + the assigned dev. ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport privacy ** Description changed: In https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1739525/comments/4, I ran apport-collect for that bug report. - To my horror, it posted "org.gnome.shell command-history" in the "GsettingsChanges.txt"! + To my horror, it posted "org.gnome.shell command-history" and "favorites" in the "GsettingsChanges.txt"! https://launchpadlibrarian.net/349970997/GsettingsChanges.txt It's _completely_ reasonable to see: - * enabled-extensions - * org.gnome.shell.* diffs - * org.gnome.desktop.* diffs + * enabled-extensions + * org.gnome.shell.* diffs + * org.gnome.desktop.* diffs But it is _NOT_ acceptable (privacy reasons) to automatically harvest a user's favorites in the gnome-shell, nor their command histories. _IF_ we must harvest for bug-data gathering, it MUST come in a secure mechanism that is private only to submitter + the assigned dev. ** Summary changed: - apport-collect SHOULD NOT collect gnome-shell command history + apport-collect SHOULD NOT collect gnome-shell command history and favorites -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1739531 Title: apport-collect SHOULD NOT collect gnome-shell command history and favorites Status in apport package in Ubuntu: New Bug description: In https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1739525/comments/4, I ran apport-collect for that bug report. To my horror, it posted "org.gnome.shell command-history" and "favorites" in the "GsettingsChanges.txt"! https://launchpadlibrarian.net/349970997/GsettingsChanges.txt It's _completely_ reasonable to see: * enabled-extensions * org.gnome.shell.* diffs * org.gnome.desktop.* diffs But it is _NOT_ acceptable (privacy reasons) to automatically harvest a user's favorites in the gnome-shell, nor their command histories. _IF_ we must harvest for bug-data gathering, it MUST come in a secure mechanism that is private only to submitter + the assigned dev. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1739531/+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 1721839] Re: [REGRESSION] Services asked for by UDEV do not get triggered
** Summary changed: - Services asked for by UDEV do not get triggered + [REGRESSION] Services asked for by UDEV do not get triggered ** Tags added: regression-release -- 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/1721839 Title: [REGRESSION] Services asked for by UDEV do not get triggered Status in systemd: New Status in Release Notes for Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Bug description: The packages system-config-printer-udev and ippusbxd are installed, having the following UDEV rule files: /lib/udev/rules.d/70-printers.rules -- # Low-level USB device add trigger ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer", TAG+="systemd", PROGRAM="/bin/systemd-escape --template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="%c" # Low-level USB device remove trigger ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p" -- /lib/udev/rules.d/55-ippusbxd.rules -- # ippusbxd udev rules file ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device" ENV{ID_USB_INTERFACES}=="*:070104:*", OWNER="root", GROUP="lp", MODE="0664", PROGRAM="/bin/systemd-escape --template=ippusbxd@.service $env{BUSNUM}:$env{DEVNUM}", ENV{SYSTEMD_WANTS}+="%c" -- If I turn on an appropriate printer (USB, supporting IPP-over-USB, here the HP DeskJet 2540) I get in the output of "udevadm monitor --environment" -- UDEV [17527.514150] add /devices/pci:00/:00:14.0/usb2/2-2 (usb) ACTION=add BUSNUM=002 DEVNAME=/dev/bus/usb/002/033 DEVNUM=033 DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2 DEVTYPE=usb_device DRIVER=usb ID_BUS=usb ID_MODEL=Deskjet_2540_series ID_MODEL_ENC=Deskjet\x202540\x20series ID_MODEL_ID=c211 ID_REVISION=0100 ID_SERIAL=HP_Deskjet_2540_series_BR54BFB02C05XK ID_SERIAL_SHORT=BR54BFB02C05XK ID_USB_INTERFACES=:ffcc00:070104:070102:ff0401: ID_VENDOR=HP ID_VENDOR_ENC=HP ID_VENDOR_FROM_DATABASE=Hewlett-Packard ID_VENDOR_ID=03f0 MAJOR=189 MINOR=160 PRODUCT=3f0/c211/100 SEQNUM=9891 SUBSYSTEM=usb SYSTEMD_WANTS=ippusbxd@002:033.service udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service printer.target TAGS=:udev-configure-printer:systemd: TYPE=0/0/0 USEC_INITIALIZED=17527513940 UDEV [17527.517724] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) .MM_USBIFNUM=00 ACTION=add DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 DEVTYPE=usb_interface ID_VENDOR_FROM_DATABASE=Hewlett-Packard INTERFACE=255/204/0 MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFiscCCip00in00 PRODUCT=3f0/c211/100 SEQNUM=9892 SUBSYSTEM=usb TYPE=0/0/0 USEC_INITIALIZED=17527517478 UDEV [17527.522565] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2 (usb) .MM_USBIFNUM=02 ACTION=add DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2 DEVTYPE=usb_interface ID_VENDOR_FROM_DATABASE=Hewlett-Packard INTERFACE=255/4/1 MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFisc04ip01in02 PRODUCT=3f0/c211/100 SEQNUM=9895 SUBSYSTEM=usb TYPE=0/0/0 USEC_INITIALIZED=17527522332 UDEV [17527.523761] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1 (usb) .MM_USBIFNUM=01 ACTION=add DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1 DEVTYPE=usb_interface DRIVER=usblp ID_VENDOR_FROM_DATABASE=Hewlett-Packard INTERFACE=7/1/2 MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00ic07isc01ip02in01 PRODUCT=3f0/c211/100 SEQNUM=9893 SUBSYSTEM=usb TYPE=0/0/0 USEC_INITIALIZED=17527523500 UDEV [17527.527275] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1 (usbmisc) .MM_USBIFNUM=01 ACTION=add DEVNAME=/dev/usb/lp1 DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1 MAJOR=180 MINOR=1 SEQNUM=9894 SUBSYSTEM=usbmisc USEC_INITIALIZED=17527527175 -- Here one can see that the UDEV rules files are correct, leading to the correct systemd services being requested SYSTEMD_WANTS=ippusbxd@002:033.service udev-configure-printer @-devices-pci:00-:00:14.0-usb2-2\x2d2.service printer.target but neither the service ippusbxd@002:033.service nor the service udev- configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service get started (note that I have put the .service file for ippusbxd in place by "sudo cp /usr/share/doc/ippusbxd/examples/ippusbxd@.service /lib/systemd/system/"). I can start each of these services manually though: sudo systemctl start 'udev-configure-printer@-devices- pci:00-:00:14.0-usb2-2\x2d2.service' sudo systemctl start ippusbxd@00
[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
Hello Martin, or anyone else affected, Accepted ntp into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p10+dfsg- 5ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. 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: ntp (Ubuntu Artful) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Artful: Fix Committed Status in ntp source package in Bionic: Fix Released Bug description: [Impact] * NTP has new isolation features which makes it trigger apparmor issues. * Those apparmor issues not only clutter the log and make other things less readable, they also prevent ntp from reporting its actual messages. * Fix is opening the apparmor profile to follow ntp through the disconnect by the isolation feature. [Test Case] * This is hard to trigger, but then also not. Which means it is not entirely sorted out when it triggers and when not, but the following does trigger it in tests of Pitti and also mine (while at the same time sometimes it does not - mabye I had other guests or kvm instead of lxd) * First install ntp in Artful (or above unless fixed) * Install ntp and check demsg for denies * Once an issue triggers instead of the error in syslog you'll see the apparmor Deny like: apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [Regression Potential] * We are slightly opening up the apparmor profile which is far lower risk than adding more constraints. So safe from that POV. * OTOH one could think this might be a security issue, but in fact this isn't a new suggestion if you take a look at [1] with an ack by Seth of the Security Team. [Other Info] * n/a [1]: https://lists.ubuntu.com/archives/apparmor/2015-May/007858.html Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+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 1739510] [NEW] ill install you signature
Public bug reported: hope you can help me. i cant affort another computer and spain is acting violence ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.14 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: Thu Dec 21 01:27:15 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:81ed] InstallationDate: Installed on 2017-12-19 (1 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 0c45:651b Microdia Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 276d:1160 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.10.0-42-generic.efi.signed root=UUID=d6ad60b5-3719-45b3-8b42-1bb91b324af7 ro nopat vesafb.invalid=1 plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81ED dmi.board.vendor: HP dmi.board.version: 62.39 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd01/20/2017:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81ED:rvr62.39:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP 250 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: 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: Thu Dec 21 00:06:27 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset ** 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/1739510 Title: ill install you signature Status in xorg package in Ubuntu: New Bug description: hope you can help me. i cant affort another computer and spain is acting violence ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.14 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: Thu Dec 21 01:27:15 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:81ed] InstallationDate: Installed on 2017-12-19 (1 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 0c45:651b Microdia Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 276d:1160 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.10.0-42-generic.efi.signed root=UUID=d6ad60b5-3719-45b3-8b42-1bb91b324af7 ro nopat vesafb.invalid=1 plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/20/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.bo
[Touch-packages] [Bug 1739509] [NEW] Why was gstreamer0.10 dropped from Ubuntu
Public bug reported: Why was gstreamer0.10 dropped from Ubuntu? It is still available in debian and many applications do use it https://packages.debian.org/search?keywords=libgstreamer0.10&searchon=names&suite=all§ion=all , e.g. proprietary eTXT Antiplagiat. ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1739509 Title: Why was gstreamer0.10 dropped from Ubuntu Status in gstreamer0.10 package in Ubuntu: New Bug description: Why was gstreamer0.10 dropped from Ubuntu? It is still available in debian and many applications do use it https://packages.debian.org/search?keywords=libgstreamer0.10&searchon=names&suite=all§ion=all , e.g. proprietary eTXT Antiplagiat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1739509/+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 1739506] Re: package apport 2.20.1-0ubuntu2.14 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1739506 Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: New Bug description: Quit installing ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.14 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportLog: ERROR: apport (pid 8048) Wed Dec 20 18:47:05 2017: called for pid 6252, signal 3, core limit 0, dump mode 1 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashReports: 600:0:117:328983:2017-12-20 18:46:50.603565454 -0500:2017-12-20 18:46:51.603565454 -0500:/var/crash/apport.0.crash 600:0:117:332021:2017-12-20 08:18:11.965021662 -0500:2017-12-20 08:17:50.893693707 -0500:/var/crash/rsync.0.crash Date: Wed Dec 20 18:46:51 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-16 (34 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1739506/+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 1739506] [NEW] package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Quit installing ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.14 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportLog: ERROR: apport (pid 8048) Wed Dec 20 18:47:05 2017: called for pid 6252, signal 3, core limit 0, dump mode 1 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashReports: 600:0:117:328983:2017-12-20 18:46:50.603565454 -0500:2017-12-20 18:46:51.603565454 -0500:/var/crash/apport.0.crash 600:0:117:332021:2017-12-20 08:18:11.965021662 -0500:2017-12-20 08:17:50.893693707 -0500:/var/crash/rsync.0.crash Date: Wed Dec 20 18:46:51 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-16 (34 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1739506 Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in apport package in Ubuntu: New Bug description: Quit installing ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.14 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportLog: ERROR: apport (pid 8048) Wed Dec 20 18:47:05 2017: called for pid 6252, signal 3, core limit 0, dump mode 1 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashReports: 600:0:117:328983:2017-12-20 18:46:50.603565454 -0500:2017-12-20 18:46:51.603565454 -0500:/var/crash/apport.0.crash 600:0:117:332021:2017-12-20 08:18:11.965021662 -0500:2017-12-20 08:17:50.893693707 -0500:/var/crash/rsync.0.crash Date: Wed Dec 20 18:46:51 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-11-16 (34 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1739506/+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 1733700] Re: python tools do not understand 'non-magic' include rules
** Description changed: The apparmor parser supports 'include' and '#include' rules for specifying absolute paths, but the python tools only understand include rules for so called 'magic' '<>' file locations. - Reproducer: - + + = test case #1 (aa-enforce) = $ mkdir /tmp/test1 /tmp/test2 $ cat /etc/apparmor.d/lp1733700 profile lp1733700 { - #include "/tmp/test1" - include "/tmp/test2" + #include "/tmp/test1" + include "/tmp/test2" } $ apparmor_parser -QTK /etc/apparmor.d/lp1733700 && echo ok - $ sudo aa-enforce /etc/apparmor.d/lp1733700 - - ERROR: Syntax Error: Missing '}' or ','. Reached end of file - /etc/apparmor.d/lp1733700 while inside profile lp1733700. + $ sudo aa-enforce /etc/apparmor.d/lp1733700 # currently fails + + + = test case #2 (aa-genprof) = + + This assumes test case #1 was already performed and + /etc/apparmor.d/lp1733700 exists with the above includes. + + $ cat /tmp/lp1733700 + #!/bin/sh + set -e + sh -c "$@" + + # run without confinement: + $ /tmp/lp1733700 'cat /etc/fstab' | head -1 + # /etc/fstab: static file system information. + + # invoke genprof + $ sudo aa-genprof /tmp/lp1733700 + ... + [(S)can system log for AppArmor events] / (F)inish - PRESS 's' - currently fails + ... don't exercise the application any so we just have the default profile ... + [(S)can system log for AppArmor events] / (F)inish - PRESS 'f' + ... + Finished generating profile for /tmp/lp1733700. + + $ sudo cat /etc/apparmor.d/tmp.lp1733700 + # Last Modified: Wed Dec 20 15:53:07 2017 + #include + + /tmp/lp1733700 { + #include + #include + + /bin/dash ix, + /lib/x86_64-linux-gnu/ld-*.so mr, + /tmp/lp1733700 r, + + } + + + = test case #3 (aa-logprof) = + + This assumes test case #1 was already performed and + /etc/apparmor.d/lp1733700 exists with the above includes. + + This also assumes test case #2 was already performed and + /etc/apparmor.d/tmp.lp1733700 exists. + + Disable kernel rate limiting: + $ sudo sysctl -w kernel.printk_ratelimit=0 + + Create mark entry in syslog: + $ logger mark-lp1733700 + + Try running logprof with no new denials: + + $ sudo aa-logprof -m mark-lp1733700 # currently fails + Reading log entries from /var/log/syslog. + Updating AppArmor profiles in /etc/apparmor.d. + $ + + Adjust /etc/apparmor.d/tmp.lp1733700 to add: + + #include "/tmp/test1" + include "/tmp/test2" + + Load it into the kernel: + $ sudo apparmor_parser -r /etc/apparmor.d/tmp.lp1733700 + + Create a new denial: + $ /tmp/lp1733700 'uptime' + sh: 1: uptime: Permission denied + $ + + Try running logprof: + + $ sudo aa-logprof -m mark-lp1733700 # currently fails + Reading log entries from /var/log/syslog. + Updating AppArmor profiles in /etc/apparmor.d. + + Profile: /tmp/lp1733700 + Execute: /usr/bin/uptime + Severity: unknown + + (I)nherit / (C)hild / (N)amed / (X) ix On / (D)eny / Abo(r)t / (F)inish + ... + The following local profiles were changed. Would you like to save them? + + [1 - /tmp/lp1733700] + (S)ave Changes / Save Selec(t)ed Profile / [(V)iew Changes] / View Changes b/w (C)lean profiles / Abo(r)t + + + Writing updated profile for /tmp/lp1733700. + $ + + Verify the profile for 'uptime' addition and that the /tmp/test1 and + /tmp/test2 includes were not removed (it is ok that they are both + '#include'): + + $ sudo cat /etc/apparmor.d/tmp.lp1733700 + # Last Modified: Wed Dec 20 16:19:19 2017 + #include + + /tmp/lp1733700 { + #include "/tmp/test1" + #include "/tmp/test2" + #include + #include + + /bin/dash ix, + /lib/x86_64-linux-gnu/ld-*.so mr, + /tmp/lp1733700 r, + /usr/bin/uptime mrix, + + } + + + = test case #4 (aa-mergeprof) = + + $ mkdir -p /tmp/aa-mergeprof/new + $ mkdir /tmp/aa-mergeprof/new/tunables /tmp/aa-mergeprof/new/abstractions + $ touch /tmp/aa-mergeprof/new/tunables/global /tmp/aa-mergeprof/new/abstractions/base /tmp/aa-mergeprof/new/abstractions/bash + $ cp -a /tmp/aa-mergeprof/new /tmp/aa-mergeprof/old + + $ cat /tmp/aa-mergeprof/old/tmp.lp1733700 # no test2 include or cat + #include + + /tmp/lp1733700 { + #include + #include + #include "/tmp/test1" + + /bin/dash ix, + /lib/x86_64-linux-gnu/ld-*.so mr, + /tmp/lp1733700 r, + /usr/bin/uptime mrix, + + } + + $ cat /tmp/aa-mergeprof/new/tmp.lp1733700 # no test1 include or uptime + #include + + /tmp/lp1733700 { + #include + #include + #include "/tmp/test2" + + /bin/dash ix, + /lib/x86_64-linux-gnu/ld-*.so mr, + /tmp/lp1733700 r, + /bin/cat ixr, + + } + + $ sudo aa-mergeprof -d /tmp/aa-mergeprof/new /tmp/aa-mergeprof/old/tmp.lp1733700 + ... + [1 - #include "/tmp/test1"] + [(A)llow] / (I)gnore / Abo(r)t / (F)inish + + ... + [1 - /usr/bin/uptime mrix,] + (A)llow / [(D)eny] / (I)gnore / (G)lob / Glob with (E)xtension / (N)ew / Audi(t) / Abo(r)t / (F)inish + + ... + The following local profiles were changed. Would you like to save them? + + [1 - /tmp/lp1733700] + (S)ave Changes / [(V)iew
[Touch-packages] [Bug 1737648] Re: Hold libgweather in -proposed until first bionic language pack
This block-proposed tag proved to not block the SRUs. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1737648 Title: Hold libgweather in -proposed until first bionic language pack Status in libgweather package in Ubuntu: Triaged Bug description: In https://launchpad.net/ubuntu/+source/libgweather/3.26.0-1ubuntu1 we worked around a Launchpad configuration bug for Ubuntu language packs. That configuration issue has been fixed but we still need a language pack to be built after the change was made or we'll end up reintroducing LP: #1704533. Therefore, I'm filing this bug to keep libgweather in proposed until the first bionic language pack is published. Feel free to close this bug once that happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgweather/+bug/1737648/+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 1704533] Re: French language locale missing : Gnome-Weather
This bug was fixed in the package libgweather - 3.18.2-0ubuntu0.2 --- libgweather (3.18.2-0ubuntu0.2) xenial; urgency=medium * Add langpack-hack.patch: - Rename the gettext template to work around Launchpad issue. This fixes the untranslated weather conditions in the GNOME Weather app. (LP: #1704533) -- Gunnar Hjalmarsson Mon, 11 Dec 2017 20:25:00 +0100 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Xenial: Fix Released Status in libgweather source package in Zesty: Fix Released Status in libgweather source package in Artful: Fix Released Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+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 1704533] Re: French language locale missing : Gnome-Weather
This bug was fixed in the package libgweather - 3.24.1-0ubuntu0.2 --- libgweather (3.24.1-0ubuntu0.2) zesty; urgency=medium * Add langpack-hack.patch: - Rename the gettext template to work around Launchpad issue. This fixes the untranslated weather conditions in the GNOME Weather app. (LP: #1704533) -- Gunnar Hjalmarsson Mon, 11 Dec 2017 20:29:00 +0100 ** Changed in: libgweather (Ubuntu Zesty) Status: Fix Committed => Fix Released ** Changed in: libgweather (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Xenial: Fix Released Status in libgweather source package in Zesty: Fix Released Status in libgweather source package in Artful: Fix Released Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+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 1704533] Re: French language locale missing : Gnome-Weather
This bug was fixed in the package libgweather - 3.26.0-1ubuntu0.1 --- libgweather (3.26.0-1ubuntu0.1) artful; urgency=medium * Add langpack-hack.patch: - Rename the gettext template to work around Launchpad issue. This fixes the untranslated weather conditions in the GNOME Weather app. (LP: #1704533) -- Gunnar Hjalmarsson Mon, 11 Dec 2017 12:54:00 +0100 ** Changed in: libgweather (Ubuntu Artful) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Xenial: Fix Released Status in libgweather source package in Zesty: Fix Released Status in libgweather source package in Artful: Fix Released Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+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 1704533] Update Released
The verification of the Stable Release Update for libgweather has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Xenial: Fix Released Status in libgweather source package in Zesty: Fix Released Status in libgweather source package in Artful: Fix Released Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+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 1739478] [NEW] lightdm does not start any desktop environment
Public bug reported: Since latest updates lightdm does not start any desktop environment. After loging in a blank screen (if you had set a desktop background the desktop background) is shown. No window manager, no session manager gets started. To start a desktop environment you'll have to switch to a console (CTRL-ALT-F1). Login with your username and password. Give "sudo service lightdm stop". After lightdm is stopped you can start your desktop environment with "startx". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 Uname: Linux 4.13.16+ x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Dec 20 21:29:50 2017 InstallationDate: Installed on 2011-10-19 (2254 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) LightdmConfig: [SeatDefaults] greeter-session=lightdm-gtk-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2017-08-03 (139 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- 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/1739478 Title: lightdm does not start any desktop environment Status in lightdm package in Ubuntu: New Bug description: Since latest updates lightdm does not start any desktop environment. After loging in a blank screen (if you had set a desktop background the desktop background) is shown. No window manager, no session manager gets started. To start a desktop environment you'll have to switch to a console (CTRL-ALT-F1). Login with your username and password. Give "sudo service lightdm stop". After lightdm is stopped you can start your desktop environment with "startx". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 Uname: Linux 4.13.16+ x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Dec 20 21:29:50 2017 InstallationDate: Installed on 2011-10-19 (2254 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) LightdmConfig: [SeatDefaults] greeter-session=lightdm-gtk-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2017-08-03 (139 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1739478/+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 1732447] Re: rename no longer included in perl package, but still linked
*** This bug is a duplicate of bug 1739467 *** https://bugs.launchpad.net/bugs/1739467 I'm marking this as a duplicate of another bug regarding updating command-not-found for artful. ** This bug has been marked a duplicate of bug 1739467 [SRU] update artful data -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1732447 Title: rename no longer included in perl package, but still linked Status in command-not-found package in Ubuntu: Triaged Status in perl package in Ubuntu: Invalid Bug description: typing "rename" in a terminal responds with... The program 'rename' can be found in the following packages: * perl * rename Ask your administrator to install one of them ...but perl is already installed. Internet reports suggest this has started in 17.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: perl 5.26.0-8ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu4 Architecture: amd64 Date: Wed Nov 15 16:24:29 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash LC_PAPER=en_GB.UTF-8 SourcePackage: perl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1732447/+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 1721839] Re: Services asked for by UDEV do not get triggered
** Changed in: systemd (Ubuntu) Importance: High => Critical -- 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/1721839 Title: Services asked for by UDEV do not get triggered Status in systemd: New Status in Release Notes for Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Bug description: The packages system-config-printer-udev and ippusbxd are installed, having the following UDEV rule files: /lib/udev/rules.d/70-printers.rules -- # Low-level USB device add trigger ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701??:*", TAG+="udev-configure-printer", TAG+="systemd", PROGRAM="/bin/systemd-escape --template=udev-configure-printer@.service %p", ENV{SYSTEMD_WANTS}+="%c" # Low-level USB device remove trigger ACTION=="remove", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:0701*:*", RUN+="udev-configure-printer remove %p" -- /lib/udev/rules.d/55-ippusbxd.rules -- # ippusbxd udev rules file ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device" ENV{ID_USB_INTERFACES}=="*:070104:*", OWNER="root", GROUP="lp", MODE="0664", PROGRAM="/bin/systemd-escape --template=ippusbxd@.service $env{BUSNUM}:$env{DEVNUM}", ENV{SYSTEMD_WANTS}+="%c" -- If I turn on an appropriate printer (USB, supporting IPP-over-USB, here the HP DeskJet 2540) I get in the output of "udevadm monitor --environment" -- UDEV [17527.514150] add /devices/pci:00/:00:14.0/usb2/2-2 (usb) ACTION=add BUSNUM=002 DEVNAME=/dev/bus/usb/002/033 DEVNUM=033 DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2 DEVTYPE=usb_device DRIVER=usb ID_BUS=usb ID_MODEL=Deskjet_2540_series ID_MODEL_ENC=Deskjet\x202540\x20series ID_MODEL_ID=c211 ID_REVISION=0100 ID_SERIAL=HP_Deskjet_2540_series_BR54BFB02C05XK ID_SERIAL_SHORT=BR54BFB02C05XK ID_USB_INTERFACES=:ffcc00:070104:070102:ff0401: ID_VENDOR=HP ID_VENDOR_ENC=HP ID_VENDOR_FROM_DATABASE=Hewlett-Packard ID_VENDOR_ID=03f0 MAJOR=189 MINOR=160 PRODUCT=3f0/c211/100 SEQNUM=9891 SUBSYSTEM=usb SYSTEMD_WANTS=ippusbxd@002:033.service udev-configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service printer.target TAGS=:udev-configure-printer:systemd: TYPE=0/0/0 USEC_INITIALIZED=17527513940 UDEV [17527.517724] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 (usb) .MM_USBIFNUM=00 ACTION=add DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0 DEVTYPE=usb_interface ID_VENDOR_FROM_DATABASE=Hewlett-Packard INTERFACE=255/204/0 MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFiscCCip00in00 PRODUCT=3f0/c211/100 SEQNUM=9892 SUBSYSTEM=usb TYPE=0/0/0 USEC_INITIALIZED=17527517478 UDEV [17527.522565] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2 (usb) .MM_USBIFNUM=02 ACTION=add DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.2 DEVTYPE=usb_interface ID_VENDOR_FROM_DATABASE=Hewlett-Packard INTERFACE=255/4/1 MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00icFFisc04ip01in02 PRODUCT=3f0/c211/100 SEQNUM=9895 SUBSYSTEM=usb TYPE=0/0/0 USEC_INITIALIZED=17527522332 UDEV [17527.523761] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1 (usb) .MM_USBIFNUM=01 ACTION=add DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1 DEVTYPE=usb_interface DRIVER=usblp ID_VENDOR_FROM_DATABASE=Hewlett-Packard INTERFACE=7/1/2 MODALIAS=usb:v03F0pC211d0100dc00dsc00dp00ic07isc01ip02in01 PRODUCT=3f0/c211/100 SEQNUM=9893 SUBSYSTEM=usb TYPE=0/0/0 USEC_INITIALIZED=17527523500 UDEV [17527.527275] add /devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1 (usbmisc) .MM_USBIFNUM=01 ACTION=add DEVNAME=/dev/usb/lp1 DEVPATH=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.1/usbmisc/lp1 MAJOR=180 MINOR=1 SEQNUM=9894 SUBSYSTEM=usbmisc USEC_INITIALIZED=17527527175 -- Here one can see that the UDEV rules files are correct, leading to the correct systemd services being requested SYSTEMD_WANTS=ippusbxd@002:033.service udev-configure-printer @-devices-pci:00-:00:14.0-usb2-2\x2d2.service printer.target but neither the service ippusbxd@002:033.service nor the service udev- configure-printer@-devices-pci:00-:00:14.0-usb2-2\x2d2.service get started (note that I have put the .service file for ippusbxd in place by "sudo cp /usr/share/doc/ippusbxd/examples/ippusbxd@.service /lib/systemd/system/"). I can start each of these services manually though: sudo systemctl start 'udev-configure-printer@-devices- pci:00-:00:14.0-usb2-2\x2d2.service' sudo systemctl start ippusbxd@002:033.service In each case ippusbxd gets started for this printer and a print queue auto-created. What I expec
[Touch-packages] [Bug 1693503] Re: Remove mlx4.conf
The kernel will automatically load the mlx4 kernel module which will request to load the mlx4_en and mlx4_ib modules if it detects Ethernet or InfiniBand ports (see mlx4_request_modules() in drivers/net/ethernet/mellanox/mlx4/main.c). So /etc/modprobe.d/mlx4.conf can be dropped from kmod. Can you please test following: * Remove /etc/modprobe.d/mlx4.conf * Update initramfs * check if mlx4_ib.ko, mlx4_en.ko, and mlx4.ko are in the initrd (use lsinitramfs) * then do a boot test -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1693503 Title: Remove mlx4.conf Status in kmod package in Ubuntu: Confirmed Bug description: Hi, we are working on debianizing rdma-core package, it will contain a rdma service that manage the mlx4.conf file, so the conf file “/etc/modprobe.d/mlx4.conf” (that comes with “kmod” package) is not needed anymore, and must be removed. This conf file conflicts with “/lib/modprobe.d/libmlx4.conf” that will come with “rdma-core” package, and prevents running a script (/sbin/mlx4-setup.sh) that configures ConnectX-3 devices port types (IB vs. ETH). thanks Talat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1693503/+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 1269177] Re: Running 'unattended-upgrades --dry-run' reboots the machine
The SRUs are in the queue and awaiting review. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1269177 Title: Running 'unattended-upgrades --dry-run' reboots the machine Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Zesty: In Progress Status in unattended-upgrades source package in Artful: In Progress Status in unattended-upgrades source package in Bionic: Fix Released Bug description: Impact -- An Ubuntu system will unexpectedly reboot if reboot-required exists and you run unattended-upgrades in dry-run mode. Test Case - 1) modify /etc/apt/apt.conf.d/50unattended-upgrades so that Automatic-Reboot is true 2) Ensure all updates are installed 3) sudo touch /var/run/reboot-required 4) run 'sudo unattended-upgrades --dry-run' 5) watch the system reboot With the version of unattended-upgrades from -proposed the system will not reboot. Regression Potential This checks to see if the --dry-run switch is passed to unattended-upgrades before calling the reboot function. I guess it would be a regression to people who expect the system to reboot but that seems like a very strange corner case. Original Description Much to my surprise, when I did a dry-run test of unattended-upgrades my server was forcibly rebooted. I must have had the file '/var/run/reboot-required' present. But needless to say: a --dry-run should NOT perform a reboot of the server with zero warning. Seriously. Output from /var/log/unattended-upgrades.log 2014-01-15 11:14:26,474 INFO Initial blacklisted packages: 2014-01-15 11:14:26,474 INFO Starting unattended upgrades script 2014-01-15 11:14:26,475 INFO Allowed origins are: ['o=Ubuntu,a=precise-security'] 2014-01-15 11:14:35,846 INFO Option --dry-run given, *not* performing real actions 2014-01-15 11:14:35,846 INFO Packages that are upgraded: bind9-host dnsutils libbind9-80 libdns81 libisc83 libisccc80 libisccfg82 liblwres80 libssl1.0.0 linux-generic-pae linux-headers-generic-pae linux-image-generic-pae linux-libc-dev openssl 2014-01-15 11:14:35,847 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg_2014-01-15_11:14:35.846820.log' 2014-01-15 11:15:10,610 INFO All upgrades installed 2014-01-15 11:15:10,611 WARNING Found /var/run/reboot-required, rebooting Version: 0.76ubuntu1 As an aside, it makes a lot of sense to me to put the reboot on a timer, even if it's only a one minute (i.e. shutdown -r 1). That would have at least given me a chance to prevent the reboot if I had seen the warning. If that's a configuration setting I don't see it anywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1269177/+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 934291] Re: Deleting or stopping print jobs does not work
Patch to apply is the one of comment #53. ** Changed in: cups (Ubuntu) Status: Incomplete => Invalid ** Changed in: cups-pk-helper (Ubuntu) Status: Incomplete => In Progress -- 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/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Invalid Status in cups-pk-helper package in Ubuntu: In Progress Status in gnome-control-center package in Ubuntu: Invalid Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 934291] Re: Deleting or stopping print jobs does not work
It is working now. Thank you very much. Can someone upload this version of cups-pk-helper to Bionic? Thanks. -- 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/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Invalid Status in cups-pk-helper package in Ubuntu: In Progress Status in gnome-control-center package in Ubuntu: Invalid Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 934291] Re: Deleting or stopping print jobs does not work
Thanks for testing. It really does not work on a freshly installed Artful, because the mechanism was only allowing root and not lpadmin to run. I changed that and tested it on a freshly installed Artful, and it worked, so here's another debdiff. I also updated my PPA. Please do test. ** Patch added: "run_as_lpadmin5.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/934291/+attachment/5025244/+files/run_as_lpadmin5.debdiff -- 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/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Incomplete Status in cups-pk-helper package in Ubuntu: Incomplete Status in gnome-control-center package in Ubuntu: Invalid Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 1738234] Re: package bash 4.3-14ubuntu1.2 failed to install/upgrade: new bash package pre-installation script subprocess was killed by signal (Aborted), core dumped
Just to follow up, i have done the upgrade to windows 10 version 17063, and the bug is fixed, this should probably be marked as resolved by Microsoft and the WSL team -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1738234 Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: new bash package pre-installation script subprocess was killed by signal (Aborted), core dumped Status in bash package in Ubuntu: Confirmed Bug description: Installing 18.07 on WSL using do-distribution-upgrade -d ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bash 4.3-14ubuntu1.2 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Thu Dec 14 17:46:10 2017 Dmesg: ErrorMessage: new bash package pre-installation script subprocess was killed by signal (Aborted), core dumped RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.2.24 SourcePackage: bash Title: package bash 4.3-14ubuntu1.2 failed to install/upgrade: new bash package pre-installation script subprocess was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to xenial on 2017-12-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1738234/+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 934291] Re: Deleting or stopping print jobs does not work
I have tried the PPA some days ago (Dec 15) and it did not work. Is there a new version on the PPA? -- 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/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Incomplete Status in cups-pk-helper package in Ubuntu: Incomplete Status in gnome-control-center package in Ubuntu: Invalid Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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
Re: [Touch-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work
Does the PPA work? Sent from Mailspring (https://link.getmailspring.com/link/local- 2575ba08-3601@shemgp- x230t/0?redirect=https%3A%2F%2Fgetmailspring.com%2F&recipient=934291%40bugs.launchpad.net), the best free email app for work On Dec 21 2017, at 12:05 am, Till Kamppeter <934...@bugs.launchpad.net> wrote: > shemgp, thank you also for this attempt but it is also not working for > me. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/934291 > > Title: > Deleting or stopping print jobs does not work > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions -- 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/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Incomplete Status in cups-pk-helper package in Ubuntu: Incomplete Status in gnome-control-center package in Ubuntu: Invalid Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 934291] Re: Deleting or stopping print jobs does not work
shemgp, thank you also for this attempt but it is also not working for me. -- 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/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Incomplete Status in cups-pk-helper package in Ubuntu: Incomplete Status in gnome-control-center package in Ubuntu: Invalid Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 1738749] Re: vlc 3 fails to start under wayland: vlc crashed with SIGABRT in qt_message_fatal()
VLC is working on my system after today's updates, but I had to change Video Settings/Output from "Automatic" to "OpenGL video output". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1738749 Title: vlc 3 fails to start under wayland: vlc crashed with SIGABRT in qt_message_fatal() Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: Latest version of vlc fails to start under wayland. The following message is displayed on the console: " This application failed to start because it could not find or load the Qt platform plugin "wayland" in "". Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Reinstalling the application may fix this problem. Abandon (core dumped) " and fatal error in bug 1738746 occurs ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: vlc-bin 3.0.0~rc1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 18 09:38:25 2017 ExecutablePath: /usr/bin/vlc ExecutableTimestamp: 1513462722 InstallationDate: Installed on 2013-09-03 (1566 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcCmdline: /usr/bin/vlc --started-from-file ProcCwd: /home/j-lallement ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: vlc StacktraceTop: QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 QGuiApplicationPrivate::createPlatformIntegration() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 QGuiApplicationPrivate::createEventDispatcher() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 QCoreApplicationPrivate::init() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 QGuiApplicationPrivate::init() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip docker libvirt libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1738749/+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 1739441] [NEW] switching on visibility in applet has no effect
Public bug reported: Switching on bluetooth visibility with the switch in the applet/indicator dropdown doesn't make the device visible and visibility needs to be triggered in the dialog opened after clicking on the settings button. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: indicator-bluetooth 0.0.6+17.10.20170605-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Dec 20 16:16:06 2017 InstallationDate: Installed on 2015-12-12 (739 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: indicator-bluetooth UpgradeStatus: Upgraded to artful on 2017-10-19 (61 days ago) ** Affects: indicator-bluetooth (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1739441 Title: switching on visibility in applet has no effect Status in indicator-bluetooth package in Ubuntu: New Bug description: Switching on bluetooth visibility with the switch in the applet/indicator dropdown doesn't make the device visible and visibility needs to be triggered in the dialog opened after clicking on the settings button. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: indicator-bluetooth 0.0.6+17.10.20170605-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Dec 20 16:16:06 2017 InstallationDate: Installed on 2015-12-12 (739 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: indicator-bluetooth UpgradeStatus: Upgraded to artful on 2017-10-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1739441/+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 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule
** Tags added: ppc64el -- 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/1679704 Title: libvirt profile is blocking global setrlimit despite having no rlimit rule Status in apparmor package in Ubuntu: In Progress Bug description: Hi, while debugging bug 1678322 I was running along apparmor issues. Thanks to jjohansen we debugged some of it and eventually I was asked to report to a bug. Symptom: [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" rlimit=memlock value=1610612736 But none of the profiles has any rlimit statement in it: $ grep -Hirn limit /etc/apparmor* /etc/apparmor.d/sbin.dhclient:58: # such, if the dhclient3 daemon is subverted, this effectively limits it to /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations: /etc/apparmor.d/abstractions/ubuntu-helpers:64: # in limited libraries so glibc's secure execution should be enough to not /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime The profile contains a child profile which makes reading the dumps a bit painful, but I'll attach them anyway for you to take a look. To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via libvirt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1679704/+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 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
This bug was fixed in the package initramfs-tools - 0.125ubuntu13 --- initramfs-tools (0.125ubuntu13) bionic; urgency=medium [ Oliver Grawert ] * make fixrtc catch "n/a" string and fall back to a sane value for the date command instead (LP: #1623125) -- Michael Vogt Wed, 20 Dec 2017 09:44:43 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Released -- 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/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Bug description: [TEST CASE] * this will be tested by the snappy team * without this fix the dragonboard will not boot on a freshly written image [REGRESSION POTENTIAL] * low as it only fixes an invalid string trying to boot a new dragonboard image results in: error: assertion is signed with expired public key "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by canonical this is due to a clock skew that should normally be catched by the fixrtc script in the initrd. the script is supposed to check the last mount time of the writable disk (SD card) and if this does not exist, fall back to the filesystem creation time ... in former versions of mkfs.ext4 the last mount time filed was simply left empty, so this fallback worked fine ... in xenial the fields now look like: Filesystem created: Tue Sep 13 17:32:20 2016 Last mount time: n/a Last write time: Tue Sep 13 17:32:20 2016 due to the script running with "set -e" it falls over on the "n/a" and exists before falling back to creation time, there needs to be a check added for the "n/a" string now. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+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 1679704] Re: libvirt profile is blocking global setrlimit despite having no rlimit rule
In testing newer virt stack I still hit this and need the workarounds to get it to work :-/ Any update and/or ETA on this? -- 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/1679704 Title: libvirt profile is blocking global setrlimit despite having no rlimit rule Status in apparmor package in Ubuntu: In Progress Bug description: Hi, while debugging bug 1678322 I was running along apparmor issues. Thanks to jjohansen we debugged some of it and eventually I was asked to report to a bug. Symptom: [ 8976.950635] audit: type=1400 audit(1491310016.224:48): apparmor="DENIED" operation="setrlimit" profile="/usr/sbin/libvirtd" pid=10034 comm="libvirtd" rlimit=memlock value=1610612736 But none of the profiles has any rlimit statement in it: $ grep -Hirn limit /etc/apparmor* /etc/apparmor.d/sbin.dhclient:58: # such, if the dhclient3 daemon is subverted, this effectively limits it to /etc/apparmor.d/abstractions/ubuntu-helpers:16:# Limitations: /etc/apparmor.d/abstractions/ubuntu-helpers:64: # in limited libraries so glibc's secure execution should be enough to not /etc/apparmor.d/cache/.features:13:rlimit {mask {cpu fsize data stack core rss nproc nofile memlock as locks sigpending msgqueue nice rtprio rttime The profile contains a child profile which makes reading the dumps a bit painful, but I'll attach them anyway for you to take a look. To "recreate" if needed check out bug 1678322 - TL;DR hot-add some VFs via libvirt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1679704/+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 1489730] Re: after upgrading, tap-to-click no longer works by default
Hello, I still have the same issue on Linux 16.04 ... Every time I log off /shut down and login, I can not use the tap to click on my laptop... Anyone has a permanent solution? Cheers! -- 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/1489730 Title: after upgrading, tap-to-click no longer works by default Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: After apt upgrade on wily, one finger tap on touchpad no longer works. libunity-settings-daemon1: - 15.04.1+15.10.20150720-0ubuntu1 + 15.04.1+15.10.20150825-0ubuntu1 libunity-control-center1: - 15.04.0+15.10.20150814-0ubuntu1 + 15.04.0+15.10.20150818-0ubuntu1 unity-settings-daemon: - 15.04.1+15.10.20150720-0ubuntu1 + 15.04.1+15.10.20150825-0ubuntu1 unity-control-center: - 15.04.0+15.10.20150814-0ubuntu1 + 15.04.0+15.10.20150818-0ubuntu1 gnome-settings-daemon-schemas: - 3.14.2-3ubuntu2 + 3.16.2-3ubuntu1 [before the upgrade] $ synclient | grep TapButton TapButton1 = 1 TapButton2 = 3 TapButton3 = 0 [after the upgrade] $ synclient | grep TapButton TapButton1 = 0 TapButton2 = 0 TapButton3 = 0 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: unity-settings-daemon 15.04.1+15.10.20150825-0ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 28 15:39:04 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-13 (106 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150512) SourcePackage: unity-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1489730/+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 1714301] Re: systemd-networkd hangs my boot (wireless)
I still see this issue with Ununtu 17.10 with all updates installed. -- 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/1714301 Title: systemd-networkd hangs my boot (wireless) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Fix Released Bug description: Since that systemd-networkd is enabled, my laptop doesn't boot (hangs) until I plug in an ethernet cable. Here is the journal from this boot, note the hang up until I connect my cable at 17:51:35: août 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo août 31 17:50:08 tidus systemd-networkd-wait-online[2047]: ignoring: lo août 31 17:50:08 tidus systemd[1]: emergency-tmp.service: Cannot add dependency job, ignoring: Unit emergency-tmp.service is not loaded properly: Inva août 31 17:50:08 tidus ntpdate[3836]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3836]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3836]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3836]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3836]: Can't find host ntp.ubuntu.com: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3836]: no servers can be used, exiting août 31 17:50:08 tidus systemd[1]: systemd-resolved-update-resolvconf.service: Start request repeated too quickly. août 31 17:50:08 tidus systemd[1]: Failed to start systemd-resolved-update-resolvconf.service. août 31 17:50:08 tidus systemd[1]: systemd-resolved-update-resolvconf.service: Failed with result 'start-limit-hit'. août 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server. août 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting. août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server. août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 " août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2 août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22. août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22. août 31 17:50:08 tidus nm-dispatcher[2511]: req:3 'up' [virbr0], "/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script '/etc/Ne août 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0]: start running ordered scripts... août 31 17:50:08 tidus NetworkManager[2340]: [1504194608.6148] dispatcher: (6) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat août 31 17:50:08 tidus ntpdate[3908]: Can't find host 0.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3908]: Can't find host 1.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3908]: Can't find host 2.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3908]: Can't find host 3.ubuntu.pool.ntp.org: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3908]: Can't find host ntp.ubuntu.com: Name or service not known (-2) août 31 17:50:08 tidus ntpdate[3908]: no servers can be used, exiting août 31 17:50:08 tidus systemd[1]: Reloading OpenBSD Secure Shell server. août 31 17:50:08 tidus sshd[2573]: Received SIGHUP; restarting. août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server. août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22. août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22. août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 " août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2 août 31 17:50:08 tidus nm-dispatcher[2511]: req:4 'up' [docker0], "/etc/NetworkManager/dispatcher.d/01-ifupdown": complete: failed with Script '/etc/N août 31 17:50:08 tidus NetworkManager[2340]: [1504194608.6612] dispatcher: (7) 01-ifupdown failed (failed): Script '/etc/NetworkManager/dispat août 31 17:50:08 tidus systemd[1]: Reloaded OpenBSD Secure Shell server. août 31 17:50:08 tidus sshd[2573]: Server listening on 0.0.0.0 port 22. août 31 17:50:08 tidus sshd[2573]: Server listening on :: port 22. août 31 17:50:08 tidus nm-dispatcher[2511]: /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 " août 31 17:50:08 tidus nm-dispatcher[2511]: run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 2 août 31 17:50:08 tidu
[Touch-packages] [Bug 1732032] Re: ip maddr show and ip maddr show dev enP20p96s0 show different data
Could someone look at the autopkgtest failures listed against iproute2 in http://people.canonical.com/~ubuntu-archive/pending-sru.html please? IIRC, firejail on s390x is a false positive? But there are some others, too. Also, has anyone done a quite smoke on amd64 to make sure the "ip" command still works there? If not, could you please do that? It's quite a core package and I don't want to find out that regressed the world by pressing the button to release this without checking this. Sorry, I should have asked for that at review/accept time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1732032 Title: ip maddr show and ip maddr show dev enP20p96s0 show different data Status in The Ubuntu-power-systems project: Fix Committed Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Trusty: Fix Committed Status in iproute2 source package in Xenial: Fix Committed Status in iproute2 source package in Zesty: Fix Committed Status in iproute2 source package in Artful: Fix Committed Bug description: [Impact] When a nic has a long enough name such that there is no space between the name and the ":" in /proc/net/igmp, ip maddr show dev will miss the IPV4 addresses which is otherwise shown with "ip maddr show". This is inconsistent behavior and can break scripts and tests, as shown in this bug's original description. Three patches from upstream were taken to fix this bug, and they were used individually instead of being merged into one single patch so it's easier to track and recognize authorship: https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=530903dd9003492edb0714e937ad4a5d1219e376 https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=b48a1161f5f9b6a0cda399a224bbbf72eba4a5c6 https://git.kernel.org/pub/scm/linux/kernel/git/shemminger/iproute2.git/commit/?id=21503ed2af233ffe795926f6641ac84ec1b15bf9 [Test Case] * deploy the ubuntu release under test. Please use bare metal or a VM instead of containers, because the ip tool parses a file in /proc. Make sure iproute2 is installed: sudo apt install iproute2 * Run these commands to setup a dummy interface with a long name and an IPv4 address. Please change the address if it conflicts with a real network you might have available on that machine: sudo ip link add dummylongnic0 type dummy sudo ip addr add 192.168.199.10/24 dev dummylongnic0 sudo ip link set dev dummylongnic0 up * Compare the output of these two commands with regards to the dummylongnic0 interface: sudo ip maddr show sudo ip maddr show dev dummylongnic0 * With the buggy iproute2 package installed, the more specific output "ip maddr show dev dummylongnic0" should lack the "inet 224.0.0.1" line: ip maddr show dev dummylongnic0 2:dummylongnic0 link 33:33:00:00:00:01 link 01:00:5e:00:00:01 inet6 ff02::1 inet6 ff01::1 Whereas the less specific command, which lists all interfaces, will have it listed for dummylongnic0: 2:dummylongnic0 link 33:33:00:00:00:01 link 01:00:5e:00:00:01 inet 224.0.0.1 inet6 ff02::1 inet6 ff01::1 * With the fixed iproute2 package, all dummylongnic0 addresses will be present in both outputs. [Regression Potential] In the end, the ip tool is parsing a text file produced by the kernel. As most parsing done in C, it's pretty low level and sensitive to changes in the file it's reading. [Other Info] I suggest to conduct the tests in VMs instead of containers (LXD) because the ip maddr command parses /proc/net/igmp, which is produced by the kernel. If you use a container, then it's the host's kernel that will be providing that file and it might not be the same as with the native kernel of that particular ubuntu release. --- Original description --- Attn. Canonical: Please make sure that the existing iproute2 package gets updated with the two referenced patches as the missing information is impacting our standard test suites. Thanks. == Comment: #0 - Alton L. Pundt - 2017-03-29 14:37:57 == ---Problem Description--- ip maddr show and ip maddr show dev enP20p96s0 show different data ---uname output--- Linux roselp1 4.10.0-14-generic #16-Ubuntu SMP Fri Mar 17 15:19:05 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = 8286-42A ---Steps to Reproduce--- run these at command line: root@roselp1:~# ip maddr show ... 10: enP20p96s0 link 33:33:00:00:00:01 link 01:00:5e:00:00:01 link 33:33:ff:6d:d0:d0 link 01:00:5e:00:00:fc link 33:33:00:01:00:03 inet 224.0.0.252 inet 224.0.0.1 inet6 ff02::1:3 inet6 ff02::1:ff6d:d0d0 users 3 inet6 ff02::
[Touch-packages] [Bug 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
** Changed in: snappy Status: Triaged => Fix Released ** Changed in: initramfs-tools-ubuntu-core (Ubuntu) Status: Triaged => Confirmed ** Changed in: initramfs-tools-ubuntu-core (Ubuntu) Status: Confirmed => Fix Released ** Changed in: initramfs-tools-ubuntu-core (Ubuntu Xenial) Status: New => Fix Released -- 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/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Fix Released Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools-ubuntu-core package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: Fix Released Bug description: [TEST CASE] * this will be tested by the snappy team * without this fix the dragonboard will not boot on a freshly written image [REGRESSION POTENTIAL] * low as it only fixes an invalid string trying to boot a new dragonboard image results in: error: assertion is signed with expired public key "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by canonical this is due to a clock skew that should normally be catched by the fixrtc script in the initrd. the script is supposed to check the last mount time of the writable disk (SD card) and if this does not exist, fall back to the filesystem creation time ... in former versions of mkfs.ext4 the last mount time filed was simply left empty, so this fallback worked fine ... in xenial the fields now look like: Filesystem created: Tue Sep 13 17:32:20 2016 Last mount time: n/a Last write time: Tue Sep 13 17:32:20 2016 due to the script running with "set -e" it falls over on the "n/a" and exists before falling back to creation time, there needs to be a check added for the "n/a" string now. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+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 1626248] Re: libunistring0 has not been updated since 2010
Thanks for reporting. I see that libunistring 0.9.8-1 has been packaged in Debian (https://tracker.debian.org/pkg/libunistring). However, the Ubuntu package seems to have some additional patches (0.9.3-5.2ubuntu1), so it is possible this will need a manual merge. ** Tags added: needs-debian-merge -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1626248 Title: libunistring0 has not been updated since 2010 Status in libunistring package in Ubuntu: New Bug description: Libunistring is updated by FSF for every new version of Unicode. The current version of libunistring is 0.9.6 and has support for unicode version 9. The version shipped with Ubuntu is 0.9.3 which supports Unicode 7. Since the lib was last updated Unicode has added more than 14,000 new code points which includes emoji support. Because of the number of Ubuntu packages that depend on libunistring I believe that it should be updated every time a new version is released, which is usually yearly following the release schedule of Unicode versions. Libunistring in Ubuntu has not been updated since 2010. Thank You for Ubuntu. Bob Pendleton ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libunistring0 0.9.3-5.2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 21 14:35:34 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu3 InstallationDate: Installed on 2015-01-16 (613 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libunistring UpgradeStatus: Upgraded to xenial on 2016-05-19 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1626248/+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 1736142] Re: No app icon for qpaeq in cinnamon environment
Confirmed on Gnome Shell too. And looking at the source code I can't find an icon at all. In fact I can't see any icons present in the PulseAudio source :) Please log a bug with upstream: https://bugs.freedesktop.org/enter_bug.cgi?product=PulseAudio You may also want to find the Ubuntu package for your current icon set and log a bug against that package too. ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- 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/1736142 Title: No app icon for qpaeq in cinnamon environment Status in pulseaudio package in Ubuntu: New Bug description: This bug affects qpaeq from pulseaudio-equalizer package. Steps to reproduce: 1. Boot into cinnamon desktop 2. Run qpaeq Expected result: Application in task bar with icon Actual result: icon 'missing icon' for application in task bar. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio-equalizer 1:11.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Dec 4 14:35:42 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-07-19 (1598 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2017-06-22 (165 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4298R86 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X220 Tablet dmi.product.name: 4298R86 dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO modified.conffile..etc.init.pulseaudio.conf: [modified] mtime.conffile..etc.init.pulseaudio.conf: 2013-11-19T01:27:09.605730 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1736142/+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 1734960] Re: Bluetooth headset profile HSP/HFP doesn't work
P.S. I believe in Gnome settings, when profile changes fail (and they do - I agree), Gnome just ignores it and displays the old profile. No error message there, but it feels like the same issue. -- 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/1734960 Title: Bluetooth headset profile HSP/HFP doesn't work Status in blueman package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: My bluetooth headphones Bluedio T2S has a microphone and support HSP/HFP profile, but when i try change sound profile in blueman-manager to HSP/HFP - then i get error "Failed to change profile to headset_head_unit". With profile a2dp headphones work good(clementine, chromium etc..), but I could not get work output headphones in steam games, i listen only silence(i think it's problem of pulseaudio) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pl7ofit3040 F pulseaudio /dev/snd/controlC1: pl7ofit3040 F pulseaudio CurrentDesktop: MATE Date: Tue Nov 28 19:51:59 2017 InstallationDate: Installed on 2016-06-22 (524 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: Bluedio Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pl7ofit3040 F pulseaudio /dev/snd/controlC1: pl7ofit3040 F pulseaudio Symptom_Type: No sound at all Title: [Bluedio, recording] No sound at all UpgradeStatus: Upgraded to zesty on 2017-11-24 (4 days ago) dmi.bios.date: 07/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.38 dmi.board.name: AM2NF6G-VSTA dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL2.38:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2017-11-24T19:23:23.458810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1734960/+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 1734960] Re: Bluetooth headset profile HSP/HFP doesn't work
I agree it sounds like a pulseaudio problem (or a general Bluetooth problem). But that error it seems is specific to blueman so we should keep both options open. ** Also affects: blueman (Ubuntu) Importance: Undecided Status: New -- 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/1734960 Title: Bluetooth headset profile HSP/HFP doesn't work Status in blueman package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: My bluetooth headphones Bluedio T2S has a microphone and support HSP/HFP profile, but when i try change sound profile in blueman-manager to HSP/HFP - then i get error "Failed to change profile to headset_head_unit". With profile a2dp headphones work good(clementine, chromium etc..), but I could not get work output headphones in steam games, i listen only silence(i think it's problem of pulseaudio) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pl7ofit3040 F pulseaudio /dev/snd/controlC1: pl7ofit3040 F pulseaudio CurrentDesktop: MATE Date: Tue Nov 28 19:51:59 2017 InstallationDate: Installed on 2016-06-22 (524 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: Bluedio Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pl7ofit3040 F pulseaudio /dev/snd/controlC1: pl7ofit3040 F pulseaudio Symptom_Type: No sound at all Title: [Bluedio, recording] No sound at all UpgradeStatus: Upgraded to zesty on 2017-11-24 (4 days ago) dmi.bios.date: 07/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L2.38 dmi.board.name: AM2NF6G-VSTA dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL2.38:bd07/08/2009:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAM2NF6G-VSTA:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2017-11-24T19:23:23.458810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1734960/+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 1734503] Re: In Xfce, Gnome3, Ubuntu Studio, and Mate Desktop the pulse audio gui application is corrupted, I can't switch outputs.
Your system is logging a couple of issues repeatedly: Nov 25 15:00:52 username-desktop pulseaudio[2489]: [pulseaudio] alsa- mixer.c: Volume element Speaker has 8 channels. That's too much! I can't handle that! and Nov 25 15:12:09 username-desktop pulseaudio[3489]: [pulseaudio] shm.c: shm_open() failed: No such file or directory Bug 1652505 mentions that second one too. In that case the solution was to get a newer version of PulseAudio. Can you try Ubuntu 17.10 or 18.04 by any chance? -- 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/1734503 Title: In Xfce, Gnome3, Ubuntu Studio, and Mate Desktop the pulse audio gui application is corrupted, I can't switch outputs. Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 16.04.3 LTS 1.8.0 I expected to be able to switch to different outputs of my sound hardware. That list is gone and all I have is a volume circle knob. This doesn't effect the cinnamon DE but it does effect Gnome3, Mate, Xfce, and Xfce ubuntu studio edition. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Sat Nov 25 22:12:43 2017 InstallationDate: Installed on 2017-09-29 (57 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: Z87-M8 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd11/07/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87-M8:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-10-18T18:43:48.348315 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1734503/+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
Re: [Touch-packages] [Bug 1070873] Re: kde-telepathy, impossible to connect to gmail accounts
On 20/12/17 09:15, MarcoPau wrote: > Hi, I have artful and I have build kio-gdrive-1.1.80. > > Don't know if kio-gdrive is related with the userActionFinished error: 2 > while trying to add the Google account. I am stuck there. > > Do you have any hint? > > Thanks! > > @Rik Mills, your link does not work any more. > A working signon-ui can be found in our updates PPA https://launchpad.net/~kubuntu- ppa/+archive/ubuntu/ppa?field.series_filter=artful It is also in our backports PPA, along with kio-gdrive 1.2.1 prebuilt .deb https://launchpad.net/~kubuntu- ppa/+archive/ubuntu/backports/+packages?field.name_filter=kio-gdrive -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1070873 Title: kde-telepathy, impossible to connect to gmail accounts Status in meta-kde-telepathy package in Ubuntu: Confirmed Status in signon-ui package in Ubuntu: Confirmed Bug description: Im running ubuntu 12.10 quantal and i have installed kde, when running kde-telepathy i have added a gmail account, and after entering the password it has revealed impossible to connect to it, it always says that the password is wrong when that is false. When using empathy, i have removed the gmail account and have added it again, now appears a XMLL window asking ubuntu permission to conenct to it, and now i was able to conenct to the gmail account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+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 1734384] Re: No sound in ubuntu14.04.5 On running aplay -l two sound cards are showing but in setting>sound>output, in Play sound through box no card is showing. Not even keyboar
If pulseaudio has crashed then ideally you will find .crash files in /var/crash. If you find one then please run: ubuntu-bug /var/crash/YOURFILE.crash and tell us here the ID of the new bug that creates. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete ** Changed in: pulseaudio (Ubuntu) Assignee: Ubuntu Audio Team (ubuntu-audio) => (unassigned) -- 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/1734384 Title: No sound in ubuntu14.04.5 On running aplay -l two sound cards are showing but in setting>sound>output, in Play sound through box no card is showing. Not even keyboard sound button is working. HELP!!! Status in pulseaudio package in Ubuntu: Incomplete Bug description: my laptop volume is mute. and it didn't unmute whatever i do. in bug report it says- pulseaudio crashed. ubuntu 14.04 LTS ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-135.184-generic 3.13.11-ckt39 Uname: Linux 3.13.0-135-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sat Nov 25 01:01:25 2017 InstallationDate: Installed on 2016-09-15 (435 days ago) InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 (20140807.1) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to trusty on 2017-09-10 (74 days ago) dmi.bios.date: 09/05/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CPE Ver. F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1950 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.0B dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.21:bd09/05/2013:svnHewlett-Packard:pnHPProBook445G1:pvrA2018CD200:rvnHewlett-Packard:rn1950:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 445 G1 dmi.product.version: A2018CD200 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1734384/+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 1727390] Re: New bugfix release 17.2.4
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1727390 Title: New bugfix release 17.2.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] A new upstream bugfix release is available. Release note diff compared to 17.2.2: "Mesa 17.2.3 is now available. In this release we have: The Vulkan drivers ANV and RADV have multiple small fixes. The EGL code has improved handling of the new wl_dmabuf codepath. SWR no longer crashes when checking environment variables. Other gallium drivers have also seen updates - freedreno, nouveau and radeonsi. The gallivm module, used by llvmpipe et al. has gained little endian PPC64 fixes. The VA and VDPAU state-trackers have seems improvements handling interlaced videos. We're using python3 compatible constructs which gives us SCons 3.0 support." "Mesa 17.2.4 is now available. In this release we have: In Mesa Core we have included a change to prevent KOTOR from breaking when in combination with the ATI fragment shader extension. Additionally, NIR has also received a correction. Mesa's state tracker has gotten a patch to avoid leaks in certain situations like when resizing a window. Intel drivers have received several fixes. The compiler has gotten a couple, while anv also received one. i965 got a patch to avoid VA- API, Beignet and other contexts in the system to break when in combination with previous versions of Mesa 17.2.x. AMD's compiler has received a couple of fixes while radv has also received another couple, including one to avoid a hang due to an overflow on huge textures. Broadcom's vc4 has corrected a problem when compiling with Android's clang. clover has also seen fixed a problem compiling after a specific clang revision. Vulkan's WSI has gotten plugged a memory leak for X11." [Test case] Test typical use cases on the most common hw/driver combinations: intel/i965 nvidia/nouveau radeon/radeonsi [Regression potential] These releases are tested against compliance, bugfix releases in particular have minimal risk of regressing anything major at least. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1733143] Re: Network sound devices are always set as default
It sounds like the definition of an audio device "connecting" is a little too broad in this case, so understandably annoying. There is a simple workaround that should work for you though: 1. mkdir ~/.config/pulse 2. cp /etc/pulse/default.pa ~/.config/pulse/default.pa 3. Edit ~/.config/pulse/default.pa and remove this: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif 4. If that didn't work then try removing: ### Should be after module-*-restore but before module-*-detect load-module module-switch-on-port-available ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu) Status: New => Triaged -- 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/1733143 Title: Network sound devices are always set as default Status in pulseaudio package in Ubuntu: Triaged Bug description: I notice that when I connect to a wireless network with an Apple TV, the network device is set as the default audio device. This happens even if I have manually set it otherwise. STEPS TO REPRODUCE: 1. Connect to network with an Apple TV. 2. PulseAudio picks up the Apple TV device and sets it as default. 3. Manually set the built-in audio card as default. 4. Disconnect from the audio network, and reconnect. 5. PulseAudio again sets the Apple TV device as default. EXPECTED BEHAVIOR: Step 2 is debatable, but step 5 definitely should not happen. This is on Kubuntu 17.04 with pulseaudio 1:10.0-1ubuntu2 and plasma-pa 4:5.9.5-0ubuntu0.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1733143/+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 1727390] Re: New bugfix release 17.2.4
mesa 17.2.4 works well on my two devices. Here is the test result: 1) AMD [1002:9874] (rev e2) glxgear -info: Pass Unigine_Heaven-4.0 (5mins): Pass 2) Intel [8086:5917] (rev 07) + AMD [1002:6900] (rev ff) glxgear -info: Pass DRI_PRIME=1 glxgear -info: Pass Unigine_Heaven-4.0 (5mins): Pass DRI_PRIME=1 Unigine_Heaven-4.0.run (5mins): Pass --- Installed package: (Online Update: xenial-proposed: mesa) libdrm-common all 2.4.83-1~16.04.1 libdrm2 amd64 2.4.83-1~16.04.1 libcapnp-0.5.3 amd64 0.5.3-2ubuntu1 libdrm-amdgpu1 amd64 2.4.83-1~16.04.1 libwayland-egl1-mesa amd64 17.2.4-0ubuntu1~16.04.2 libwayland-client0 amd64 1.12.0-1~ubuntu16.04.2 libwayland-server0 amd64 1.12.0-1~ubuntu16.04.2 libegl1-mesa amd64 17.2.4-0ubuntu1~16.04.2 libgbm1 amd64 17.2.4-0ubuntu1~16.04.2 libmircore1 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmircommon7 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmirprotobuf3 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libmirclient9 amd64 0.26.3+16.04.20170605-0ubuntu1.1 libllvm5.0 amd64 1:5.0-3~16.04.1 libgl1-mesa-dri amd64 17.2.4-0ubuntu1~16.04.2 -- 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/1727390 Title: New bugfix release 17.2.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: [Impact] A new upstream bugfix release is available. Release note diff compared to 17.2.2: "Mesa 17.2.3 is now available. In this release we have: The Vulkan drivers ANV and RADV have multiple small fixes. The EGL code has improved handling of the new wl_dmabuf codepath. SWR no longer crashes when checking environment variables. Other gallium drivers have also seen updates - freedreno, nouveau and radeonsi. The gallivm module, used by llvmpipe et al. has gained little endian PPC64 fixes. The VA and VDPAU state-trackers have seems improvements handling interlaced videos. We're using python3 compatible constructs which gives us SCons 3.0 support." "Mesa 17.2.4 is now available. In this release we have: In Mesa Core we have included a change to prevent KOTOR from breaking when in combination with the ATI fragment shader extension. Additionally, NIR has also received a correction. Mesa's state tracker has gotten a patch to avoid leaks in certain situations like when resizing a window. Intel drivers have received several fixes. The compiler has gotten a couple, while anv also received one. i965 got a patch to avoid VA- API, Beignet and other contexts in the system to break when in combination with previous versions of Mesa 17.2.x. AMD's compiler has received a couple of fixes while radv has also received another couple, including one to avoid a hang due to an overflow on huge textures. Broadcom's vc4 has corrected a problem when compiling with Android's clang. clover has also seen fixed a problem compiling after a specific clang revision. Vulkan's WSI has gotten plugged a memory leak for X11." [Test case] Test typical use cases on the most common hw/driver combinations: intel/i965 nvidia/nouveau radeon/radeonsi [Regression potential] These releases are tested against compliance, bugfix releases in particular have minimal risk of regressing anything major at least. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1070873] Re: kde-telepathy, impossible to connect to gmail accounts
Hi, I have artful and I have build kio-gdrive-1.1.80. Don't know if kio-gdrive is related with the userActionFinished error: 2 while trying to add the Google account. I am stuck there. Do you have any hint? Thanks! @Rik Mills, your link does not work any more. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1070873 Title: kde-telepathy, impossible to connect to gmail accounts Status in meta-kde-telepathy package in Ubuntu: Confirmed Status in signon-ui package in Ubuntu: Confirmed Bug description: Im running ubuntu 12.10 quantal and i have installed kde, when running kde-telepathy i have added a gmail account, and after entering the password it has revealed impossible to connect to it, it always says that the password is wrong when that is false. When using empathy, i have removed the gmail account and have added it again, now appears a XMLL window asking ubuntu permission to conenct to it, and now i was able to conenct to the gmail account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meta-kde-telepathy/+bug/1070873/+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 1732629] Re: Selecting USB Amp/Dac audio output in gnome sound does nothing
Your fix sounds good. I'll do some testing and see about getting it into Ubuntu properly. ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: pulseaudio (Ubuntu) Status: New => Triaged -- 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/1732629 Title: Selecting USB Amp/Dac audio output in gnome sound does nothing Status in pulseaudio package in Ubuntu: Triaged Bug description: Running Ubuntu 17.10, when I plug an external USB Amp/Dac it is correctly recognized and I can play audio through it via aplay, but when I select it as my output sink from gnome sound, nothing happens: apps still output sound via the speakers. In order to fix it I have to restart pulseaudio. I've also found online that modifying /etc/pulse/default.pa, moving module-switch-on-connect.so loading before module-udev-detect.so, permanently fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: sergio 1374 F...m pulseaudio /dev/snd/controlC1: sergio 1374 F pulseaudio /dev/snd/controlC0: sergio 1374 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Nov 16 09:03:19 2017 InstallationDate: Installed on 2017-10-24 (22 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.4 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2017-11-15T18:42:36.359190 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1732629/+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 1623125] Re: fixrtc script does not catch "Last mount time: n/a" string
** Also affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: initramfs-tools-ubuntu-core (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: + [TEST CASE] + * this will be tested by the snappy team + * without this fix the dragonboard will not boot on a freshly written image + + trying to boot a new dragonboard image results in: error: assertion is signed with expired public key "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by canonical this is due to a clock skew that should normally be catched by the fixrtc script in the initrd. the script is supposed to check the last mount time of the writable disk (SD card) and if this does not exist, fall back to the filesystem creation time ... in former versions of mkfs.ext4 the last mount time filed was simply left empty, so this fallback worked fine ... in xenial the fields now look like: Filesystem created: Tue Sep 13 17:32:20 2016 Last mount time: n/a Last write time: Tue Sep 13 17:32:20 2016 due to the script running with "set -e" it falls over on the "n/a" and exists before falling back to creation time, there needs to be a check added for the "n/a" string now. ** Description changed: [TEST CASE] * this will be tested by the snappy team * without this fix the dragonboard will not boot on a freshly written image + [REGRESSION POTENTIAL] + * low as it only fixes an invalid string trying to boot a new dragonboard image results in: error: assertion is signed with expired public key "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by canonical this is due to a clock skew that should normally be catched by the fixrtc script in the initrd. the script is supposed to check the last mount time of the writable disk (SD card) and if this does not exist, fall back to the filesystem creation time ... in former versions of mkfs.ext4 the last mount time filed was simply left empty, so this fallback worked fine ... in xenial the fields now look like: Filesystem created: Tue Sep 13 17:32:20 2016 Last mount time: n/a Last write time: Tue Sep 13 17:32:20 2016 due to the script running with "set -e" it falls over on the "n/a" and exists before falling back to creation time, there needs to be a check added for the "n/a" string now. -- 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/1623125 Title: fixrtc script does not catch "Last mount time: n/a" string Status in Snappy: Triaged Status in initramfs-tools package in Ubuntu: In Progress Status in initramfs-tools-ubuntu-core package in Ubuntu: Triaged Status in initramfs-tools source package in Xenial: New Status in initramfs-tools-ubuntu-core source package in Xenial: New Bug description: [TEST CASE] * this will be tested by the snappy team * without this fix the dragonboard will not boot on a freshly written image [REGRESSION POTENTIAL] * low as it only fixes an invalid string trying to boot a new dragonboard image results in: error: assertion is signed with expired public key "-CvQKAwRQ5h3Ffn10FILJoEZUXOv6km9FwA80-Rcj-f-6jadQ89VRswHNiEB9Lxk" by canonical this is due to a clock skew that should normally be catched by the fixrtc script in the initrd. the script is supposed to check the last mount time of the writable disk (SD card) and if this does not exist, fall back to the filesystem creation time ... in former versions of mkfs.ext4 the last mount time filed was simply left empty, so this fallback worked fine ... in xenial the fields now look like: Filesystem created: Tue Sep 13 17:32:20 2016 Last mount time: n/a Last write time: Tue Sep 13 17:32:20 2016 due to the script running with "set -e" it falls over on the "n/a" and exists before falling back to creation time, there needs to be a check added for the "n/a" string now. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1623125/+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 1731550] Re: module-switch-on-connect switches to virtual devices
This sounds like a valid bug still, but low priority if PulseEffects is not part of standard Ubuntu. So most people will never notice. We're working on the assumption that many more people want USB and Bluetooth devices to work well, than PulseEffects. But still, this sounds like a valid bug. Please log your request for switch-on-connect to ignore virtual devices here: https://bugs.freedesktop.org/enter_bug.cgi?product=PulseAudio ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Triaged -- 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/1731550 Title: module-switch-on-connect switches to virtual devices Status in pulseaudio package in Ubuntu: Triaged Bug description: The module-switch-on-connect module that has been enabled by default in Artful is causing virtual devices added by PulseEffects (https://github.com/wwmm/pulseeffects) to be activated and set to the default/failsafe device. This also changes which device the system volume control changes. It should only automatically switch when a physical audio device is plugged in. If there is no way to detect this automatically, then I would say this should not be the default configuration, or it should be added as an optional preference. In the meantime, I have worked around the issue by copying /etc/pulse/default.pa into ~/.config/pulse and commenting out loading the module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1731550/+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 1274115] Re: snd_pcm_avail() returned a value that is exceptionally large
Similar condition to Stefan, my Asus UX305LA became completely unresponsive when listening youtube music and the computer and I have to force close and restart. Mint 18.1 Cinnamon 64-bit (Ubuntu 16.04) ALSA 1.0.25+dfsg-0ubuntu5 Firefox Dev Edition: 58.0b12 (64-bit) Pulse Audio: 1:8.0-0ubuntu3.7 My syslog is attached. The incident happened exactly at Dec 20 15:10 so I'm quite sure it's the issue. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274115/+attachment/5025001/+files/syslog -- 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/1274115 Title: snd_pcm_avail() returned a value that is exceptionally large Status in pulseaudio package in Ubuntu: Confirmed Bug description: Sometimese sound begins stutter while listen to music or watching youtube. In syslog I see: Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] alsa-util.c: snd_pcm_avail() returned a value that is exceptionally large: 866944 bytes (4914 ms). Jan 29 16:31:08 bazilio-laptop pulseaudio[2155]: [alsa-sink-ALC271X Analog] alsa-util.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. I'm using Kubuntu 13.10 $ uname -a Linux bazilio-laptop 3.11.0-15-generic #23-Ubuntu SMP Mon Dec 9 18:17:04 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $ kde4-config --version Qt: 4.8.4 KDE Development Platform: 4.12.0 kde4-config: 1.0 $ pulseaudio --version pulseaudio 4.0 $ alsactl --version alsactl version 1.0.27.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1274115/+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 1574354] Re: playing .mp4 in VLC freezes machine
Hi everyone ! Considering the potentially very wide scope of a bug that would freeze the X server, could you guys & gals give more details ? - OS / ARCH - GPU - Proprietary or open source driver ? - X or Wayland ? - Any PPA ? - How often the bug occurs ? Is it completely random ? - Does it occur with specific videos ? Codecs ? - Does it only occur when seeking into the video ? - In the VLC preferences, what video mode chosen ? - Does it freeze only VLC, the whole session or the whole server ? Can you kill it from the console ? - Do you have similar freezes / crashes in other apps ? As for me : it occurs in Ubuntu 16.04 (KDE Neon actually). Nvidia GTX 1060 + proprietary driver. Bug is random and occurs when seeking a lot into the video. It seems only to occur in VDPAU mode (hardware decoding). I have no other crash at all in any video player or even complex Steam game. I didn't double check with other VDPAU player. This is potentially a massive bug (it occurred on secveral of my machines and freezes the whole session)... Maybe it'll just "disappear" when switching to VLC 3 or Wayland... -- 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/1574354 Title: playing .mp4 in VLC freezes machine Status in mesa package in Ubuntu: Confirmed Bug description: VLC was running fine on 15.10 but since upgrading, video files (e.g. .mp4) play for a few minutes and then crash the whole machine (i.e. I have to power off and on). Possibly linked is that audio (in web pages or playing audio files thru Banshee) loops (stutters) for about a second every few minutes (but doesn't crash the machine). vlc-nox: /usr/bin/vlc Description: Ubuntu 16.04 LTS Release: 16.04 vlc: Installed: 2.2.2-5 Candidate: 2.2.2-5 Version table: *** 2.2.2-5 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: vlc 2.2.2-5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 24 19:20:41 2016 InstallationDate: Installed on 2014-02-17 (797 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1574354/+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