[Touch-packages] [Bug 1717023] Re: Jarring double gradient when window is maximized
Addition/correction to my above comment, window buttons are actually added to the right of the top bar, fairly closely mimicking the 17.04 approach. Attaching a screenshot. ** Attachment added: "Screenshot from 2017-09-14 08-33-05.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1717023/+attachment/4949881/+files/Screenshot%20from%202017-09-14%2008-33-05.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1717023 Title: Jarring double gradient when window is maximized Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 light-themes: Installed: 16.10+17.10.20170817-0ubuntu1 Candidate: 16.10+17.10.20170817-0ubuntu1 Since windows no longer merge with the top panel when maximized in 17.10, a jarring double gradient is produced instead. Steps to reproduce: Maximize a window Actual outcome: A double gradient with a sharp line where the top of the title bar meets the top panel is produced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1717023/+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 1717023] Re: Jarring double gradient when window is maximized
I found the extension https://extensions.gnome.org/extension/723/pixel- saver/ which brings a behavior much closer to that of 17.04 -- however, with this solution the window buttons are missing once a window has been maximized and merged with the top bar. Perhaps the extension could still serve as an inspiration. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1717023 Title: Jarring double gradient when window is maximized Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 light-themes: Installed: 16.10+17.10.20170817-0ubuntu1 Candidate: 16.10+17.10.20170817-0ubuntu1 Since windows no longer merge with the top panel when maximized in 17.10, a jarring double gradient is produced instead. Steps to reproduce: Maximize a window Actual outcome: A double gradient with a sharp line where the top of the title bar meets the top panel is produced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1717023/+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 1522675] Re: Warning messages about unsandboxed downloads
First, recall user _apt was added recently. Second, not all comments appear to have the same original; some ones refer access rights, so some comments suggest change owner or ACL of some directory. However, another comments point out something that appears to be a parsing error over the directory path. For example, in comment #94, the path: "W: Download is performed unsandboxed as root as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Keine Berechtigung)" looks quite extraneous, because it has an empty directory name at "/tmp/ /tmp_cl". The error I got is quite similar, except it says "/tmp/ /tmp_sh", but in my system I later found directory .synaptic/tmp was empty. For the first problem, I do no see user _apt included in group sudo. And for the second, I remember that while doing a system upgrade I was notified about a change in MIME types. This could be a trace for a parsing error. Hope this comment may help to solve the warning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1704594] Re: Brother MFC 7820N printer is not working in Ubuntu 15.10
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- 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/1704594 Title: Brother MFC 7820N printer is not working in Ubuntu 15.10 Status in cups package in Ubuntu: Expired Bug description: tera@tera-NV57H:~$ lsmod | grep usb usblp 20480 0 usbhid 49152 0 hid 118784 2 hid_generic,usbhid tera@tera-NV57H:~$ tail -f /var/log/syslog Jul 15 15:30:15 tera-NV57H systemd[1]: Started Hostname Service. Jul 15 15:30:20 tera-NV57H org.gnome.zeitgeist.SimpleIndexer[1217]: ** (zeitgeist-fts:1691): WARNING **: Unable to get info on application://nautilus-autostart.desktop Jul 15 15:30:20 tera-NV57H gnome-session[1286]: javaldx: Could not find a Java Runtime Environment! Jul 15 15:30:20 tera-NV57H gnome-session[1286]: Warning: failed to read path from javaldx Jul 15 15:30:27 tera-NV57H com.ubuntu.OneConf[1217]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/tera/.cache/oneconf/ecc8c8b5f47f48d7848575bfc2692722/other_hosts' Jul 15 15:37:13 tera-NV57H kernel: [ 2310.456175] usb 2-1.1: USB disconnect, device number 3 Jul 15 15:37:13 tera-NV57H kernel: [ 2310.456510] usblp0: removed Jul 15 15:37:13 tera-NV57H udev-configure-printer[6879]: remove /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1 Jul 15 15:37:13 tera-NV57H systemd[1]: printer.target: Unit not needed anymore. Stopping. Jul 15 15:37:13 tera-NV57H systemd[1]: Stopped target Printer. Jul 15 15:39:31 tera-NV57H kernel: [ 2448.849130] usb 2-1.1: new full-speed USB device number 5 using ehci-pci Jul 15 15:39:32 tera-NV57H kernel: [ 2448.945798] usb 2-1.1: New USB device found, idVendor=04f9, idProduct=0181 Jul 15 15:39:32 tera-NV57H kernel: [ 2448.945809] usb 2-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=3 Jul 15 15:39:32 tera-NV57H kernel: [ 2448.945824] usb 2-1.1: SerialNumber: 000G5J363027 Jul 15 15:39:32 tera-NV57H kernel: [ 2448.948742] usblp 2-1.1:1.0: usblp0: USB Bidirectional printer dev 5 if 0 alt 0 proto 2 vid 0x04F9 pid 0x0181 Jul 15 15:39:32 tera-NV57H mtp-probe: checking bus 2, device 5: "/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1" Jul 15 15:39:33 tera-NV57H mtp-probe: bus: 2, device: 5 was not an MTP device Jul 15 15:39:33 tera-NV57H systemd[1]: Created slice system-udev\x2dconfigure\x2dprinter.slice. Jul 15 15:39:33 tera-NV57H systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1)... Jul 15 15:39:33 tera-NV57H systemd[1]: Reached target Printer. Jul 15 15:39:33 tera-NV57H udev-configure-printer[6896]: add /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1 Jul 15 15:39:33 tera-NV57H udev-configure-printer[6896]: device devpath is /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1 Jul 15 15:39:33 tera-NV57H udev-configure-printer[6896]: MFG:Brother MDL:MFC-7820N SERN:- serial:000G5J363027 Jul 15 15:39:38 tera-NV57H udev-configure-printer[6896]: IPP request 16395 failed (1280) Jul 15 15:39:38 tera-NV57H systemd[1]: udev-configure-printer@-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1.service: Control process exited, code=exited status=1 Jul 15 15:39:38 tera-NV57H systemd[1]: Failed to start Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1). Jul 15 15:39:38 tera-NV57H systemd[1]: udev-configure-printer@-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1.service: Unit entered failed state. Jul 15 15:39:38 tera-NV57H systemd[1]: udev-configure-printer@-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1.service: Failed with result 'exit-code'. ^C tera@tera-NV57H:~$ lsusb Bus 002 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 005: ID 04f9:0181 Brother Industries, Ltd MFC-7820N Port(FaxModem) Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:288a Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub tera@tera-NV57H:~$ ls -l /dev/usb/lp* /dev/bus/usb/*/* crw-rw-r-- 1 root root 189, 0 Jul 15 14:58 /dev/bus/usb/001/001 crw-rw-r-- 1 root root 189, 1 Jul 15 14:58 /dev/bus/usb/001/002 crw-rw-r-- 1 root root 189, 2 Jul 15 14:58 /dev/bus/usb/001/003 crw-rw-r-- 1 root root 189, 128 Jul 15 14:58 /dev/bus/usb/002/001 crw-rw-r-- 1 root root 189, 129 Jul 15 14:58 /dev/bus/usb/002/002 crw-rw-r-- 1 root root 189, 131 Jul 15 14:58 /dev/bus/usb/002/004 crw-rw-r-- 1 root lp 189, 132 Jul 15 15:39 /d
[Touch-packages] [Bug 1716775] Re: Add option to disable gnome-shell animations
I understand and agree gnome-shell's animations are poor in places. Sub- optimal performance of the shell in general makes them sometimes miss frames and stutter. Plus the chosen easing curves are also questionable (bug 1713021). But these are all fixable bugs. I would be disappointed if we disabled animations to work around the problems rather than fixing the problems. -- 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/1716775 Title: Add option to disable gnome-shell animations Status in ubuntu-settings package in Ubuntu: Invalid Bug description: I believe doing so will provide the better experience for most users. Those that see use in it can enable if desired. Am filing this bug first rather than specific against gnome-shell because this is immediately remedied in settings & there are reports of other poor behavior than the below test case. Test case 1: In current 'pseudo' default of xorg In any common video player (totem, vlc, mpv, ect.) open a video. Go from window to fullscreen, fullscreen to windowed, notice the distortion. May be even worse in wayland or when using hw decoding. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.15 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 17:21:52 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings 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/1716775/+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 1717160] [NEW] [Satellite S55Dt-A, IDT 92HD99BXX, Speaker, ATAPI] No sound at all
Public bug reported: I have added all the relevant outputs below. I am new to Ubuntu so please let me know if you need any more info. I have also checked the levels using alsamixer but had no luck. I have also made sure that nothing is muted. I have also turned auto mute off in the alsamixer. sanjay@sanjay-laptop:~$ alsactl restore alsactl: state_lock:125: file /var/lib/alsa/asound.state lock error: File exists alsactl: load_state:1683: Cannot open /var/lib/alsa/asound.state for reading: File exists Found hardware: "HDA-Intel" "ATI R6xx HDMI" "HDA:1002aa01,00aa0100,00100300" "0x1002" "0x9902" Hardware is initialized using a generic method Found hardware: "HDA-Intel" "IDT 92HD99BXX" "HDA:111d76e5,1179fa95,00100303" "0x1179" "0xfa95" Hardware is initialized using a generic method sanjay@sanjay-laptop:~$ pactl list | grep 'Active Port.*output.*' Active Port: hdmi-output-0 Active Port: analog-output-speaker sanjay@sanjay-laptop:~$ aplay -l List of PLAYBACK Hardware Devices card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 0: 92HD99BXX Analog [92HD99BXX Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 sanjay@sanjay-laptop:~$ cat /proc/asound/card0/codec* | grep Codec Codec: ATI R6xx HDMI sanjay@sanjay-laptop:~$ sudo nano /etc/modprobe.d/alsa-base [sudo] password for sanjay: sanjay@sanjay-laptop:~$ sudo nano /etc/modprobe.d/alsa-base.conf sanjay@sanjay-laptop:~$ cat /proc/asound/card0/pcm0c/info cat: /proc/asound/card0/pcm0c/info: No such file or directory sanjay@sanjay-laptop:~$ cat /proc/asound/card0/codec* Codec: ATI R6xx HDMI Address: 0 AFG Function Id: 0x1 (unsol 0) Vendor Id: 0x1002aa01 Subsystem Id: 0x00aa0100 Revision Id: 0x100300 No Modem Function Group found Default PCM: rates [0x70]: 32000 44100 48000 bits [0x2]: 16 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D3 CLKSTOP EPSS Power: setting=D0, actual=D0, Clock-stop-OK GPIO: io=0, o=0, i=0, unsolicited=0, wake=0 Node 0x02 [Audio Output] wcaps 0x221: Stereo Digital Stripe Converter: stream=1, channel=0 Digital: Enabled Digital category: 0x0 IEC Coding Type: 0x0 Node 0x03 [Pin Complex] wcaps 0x400381: Stereo Digital Control: name="IEC958 Playback Con Mask", index=0, device=0 Control: name="IEC958 Playback Pro Mask", index=0, device=0 Control: name="IEC958 Playback Default", index=0, device=0 Control: name="IEC958 Playback Switch", index=0, device=0 Pincap 0x0094: OUT Detect HDMI Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x40: OUT Unsolicited: tag=01, enabled=1 Connection: 1 0x02 Node 0x04 [Audio Output] wcaps 0x221: Stereo Digital Stripe Converter: stream=0, channel=0 Digital: Digital category: 0x0 IEC Coding Type: 0x0 Node 0x05 [Pin Complex] wcaps 0x400381: Stereo Digital Pincap 0x0094: OUT Detect HDMI Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Connection: 1 0x04 Node 0x06 [Audio Output] wcaps 0x221: Stereo Digital Stripe Converter: stream=0, channel=0 Digital: Digital category: 0x0 IEC Coding Type: 0x0 Node 0x07 [Pin Complex] wcaps 0x400381: Stereo Digital Pincap 0x0094: OUT Detect HDMI Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Connection: 1 0x06 Node 0x08 [Audio Output] wcaps 0x221: Stereo Digital Stripe Converter: stream=0, channel=0 Digital: Digital category: 0x0 IEC Coding Type: 0x0 Node 0x09 [Pin Complex] wcaps 0x400381: Stereo Digital Pincap 0x0094: OUT Detect HDMI Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Connection: 1 0x08 Node 0x0a [Audio Output] wcaps 0x221: Stereo Digital Stripe Converter: stream=0, channel=0 Digital: Digital category: 0x0 IEC Coding Type: 0x0 Node 0x0b [Pin Complex] wcaps 0x400381: Stereo Digital Pincap 0x0094: OUT Detect HDMI Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x40: OUT Unsolicited: tag=00, enabled=0 Connection: 1 0x0a Node 0x0c [Audio Output] wcaps 0x221: Stereo Digital Stripe Converter: stream=0, channel=0 Digital: Digital category: 0x0 IEC Coding Type: 0x0 Node 0x0d [Pin Complex] wcaps 0x400381: Stereo Digital Pincap 0x0094: OUT Detect HDMI Pin Default 0x585600f0: [N/A] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefA
[Touch-packages] [Bug 1716775] Re: Add option to disable gnome-shell animations
At best this would have only been an opinion. (And in retrospect as I only see some issues in video playback not to the greater good.. So marking invalid. I think if others (possibly just weaker hardware) see problems in general then I'm sure you'll all hear about it later. (I can't duplicate any reports I've seen not invoving vidoe playback. ** Changed in: ubuntu-settings (Ubuntu) Status: Incomplete => Invalid -- 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/1716775 Title: Add option to disable gnome-shell animations Status in ubuntu-settings package in Ubuntu: Invalid Bug description: I believe doing so will provide the better experience for most users. Those that see use in it can enable if desired. Am filing this bug first rather than specific against gnome-shell because this is immediately remedied in settings & there are reports of other poor behavior than the below test case. Test case 1: In current 'pseudo' default of xorg In any common video player (totem, vlc, mpv, ect.) open a video. Go from window to fullscreen, fullscreen to windowed, notice the distortion. May be even worse in wayland or when using hw decoding. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.15 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 17:21:52 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings 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/1716775/+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 1717141] Re: package gallery-app 0.0.67+14.04.20140408.1-0ubuntu2 failed to install/upgrade: unable to securely remove '/usr/share/locale/cs/LC_MESSAGES/gallery-app.mo': Not a di
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1717141 Title: package gallery-app 0.0.67+14.04.20140408.1-0ubuntu2 failed to install/upgrade: unable to securely remove '/usr/share/locale/cs/LC_MESSAGES/gallery-app.mo': Not a directory Status in dpkg package in Ubuntu: New Status in gallery-app package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gallery-app 0.0.67+14.04.20140408.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12 Uname: Linux 3.19.0-49-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 AptOrdering: darktable: Remove gallery-app: Remove Architecture: i386 Date: Wed Sep 13 21:51:07 2017 DuplicateSignature: package:gallery-app:0.0.67+14.04.20140408.1-0ubuntu2:unable to securely remove '/usr/share/locale/cs/LC_MESSAGES/gallery-app.mo': Not a directory ErrorMessage: unable to securely remove '/usr/share/locale/cs/LC_MESSAGES/gallery-app.mo': Not a directory InstallationDate: Installed on 2015-11-21 (663 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: gallery-app Title: package gallery-app 0.0.67+14.04.20140408.1-0ubuntu2 failed to install/upgrade: unable to securely remove '/usr/share/locale/cs/LC_MESSAGES/gallery-app.mo': Not a directory UpgradeStatus: Upgraded to trusty on 2017-08-15 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1717141/+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 1717141] Re: package gallery-app 0.0.67+14.04.20140408.1-0ubuntu2 failed to install/upgrade: unable to securely remove '/usr/share/locale/cs/LC_MESSAGES/gallery-app.mo': Not a di
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1717141 Title: package gallery-app 0.0.67+14.04.20140408.1-0ubuntu2 failed to install/upgrade: unable to securely remove '/usr/share/locale/cs/LC_MESSAGES/gallery-app.mo': Not a directory Status in dpkg package in Ubuntu: New Status in gallery-app package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 14.04 Package: gallery-app 0.0.67+14.04.20140408.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12 Uname: Linux 3.19.0-49-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 AptOrdering: darktable: Remove gallery-app: Remove Architecture: i386 Date: Wed Sep 13 21:51:07 2017 DuplicateSignature: package:gallery-app:0.0.67+14.04.20140408.1-0ubuntu2:unable to securely remove '/usr/share/locale/cs/LC_MESSAGES/gallery-app.mo': Not a directory ErrorMessage: unable to securely remove '/usr/share/locale/cs/LC_MESSAGES/gallery-app.mo': Not a directory InstallationDate: Installed on 2015-11-21 (663 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.5 apt 1.0.1ubuntu2.11 SourcePackage: gallery-app Title: package gallery-app 0.0.67+14.04.20140408.1-0ubuntu2 failed to install/upgrade: unable to securely remove '/usr/share/locale/cs/LC_MESSAGES/gallery-app.mo': Not a directory UpgradeStatus: Upgraded to trusty on 2017-08-15 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1717141/+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 1717023] Re: Jarring double gradient when window is maximized
I agree this doesn't look right. I've just removed "Expected outcome" from the description because that's the problem description and not a place where the solution should be decided. But we can list possible solutions here in the comments: * Keep the panel always black. * Keep the panel always translucent. * Merge the panel and titlebar into one. * Something else?... ** Tags added: visual-quality ** Description changed: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 light-themes: - Installed: 16.10+17.10.20170817-0ubuntu1 - Candidate: 16.10+17.10.20170817-0ubuntu1 + Installed: 16.10+17.10.20170817-0ubuntu1 + Candidate: 16.10+17.10.20170817-0ubuntu1 Since windows no longer merge with the top panel when maximized in 17.10, a jarring double gradient is produced instead. Steps to reproduce: Maximize a window - Expected outcome: If the window cannot merge with the top bar, a - seamless visual transition between the top panel and the title bar is - produced. - Actual outcome: A double gradient with a sharp line where the top of the title bar meets the top panel is produced. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1717023 Title: Jarring double gradient when window is maximized Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 light-themes: Installed: 16.10+17.10.20170817-0ubuntu1 Candidate: 16.10+17.10.20170817-0ubuntu1 Since windows no longer merge with the top panel when maximized in 17.10, a jarring double gradient is produced instead. Steps to reproduce: Maximize a window Actual outcome: A double gradient with a sharp line where the top of the title bar meets the top panel is produced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1717023/+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 1276897] Re: bluetoothd assert failure: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed.
Thank you for reporting this bug to Ubuntu. Ubuntu GNOME 14.04 (trusty) reached end-of-life on April 28, 2017 https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/UbuntuGNOME#Support https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004211.html We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1276897 Title: bluetoothd assert failure: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed. Status in bluez package in Ubuntu: New Bug description: I tried to connect via bluetooth to my desktop computer using my Galago Ultrapro Laptop. I connected...and then i recieved this error afterwards. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AssertionMessage: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed. Date: Wed Feb 5 20:22:32 2014 ExecutablePath: /usr/sbin/bluetoothd InstallationDate: Installed on 2014-02-05 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System76, Inc. Galago UltraPro ProcCmdline: /usr/sbin/bluetoothd ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic root=UUID=bb82e1d2-7c73-4c90-9f41-2b7f805b6082 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: bluez StacktraceTop: __assert_fail_base (fmt=0x7fee829afbe0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fee8380b09e "hs->pending != ((void *)0)", file=file@entry=0x7fee8380ae40 "audio/headset.c", line=line@entry=1487, function=function@entry=0x7fee8380bdd4 "get_record_cb") at assert.c:92 __GI___assert_fail (assertion=0x7fee8380b09e "hs->pending != ((void *)0)", file=0x7fee8380ae40 "audio/headset.c", line=1487, function=0x7fee8380bdd4 "get_record_cb") at assert.c:101 ?? () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: bluetoothd assert failure: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 0C:8B:FD:74:45:E5 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:5057 acl:60 sco:0 events:220 errors:0 TX bytes:20189 acl:59 sco:0 commands:141 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1276897/+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 1276897] Re: bluetoothd assert failure: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed.
Sorry, ignore my previous comment. Regular 14.04.5 is still supported: https://wiki.ubuntu.com/Releases ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- 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/1276897 Title: bluetoothd assert failure: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed. Status in bluez package in Ubuntu: New Bug description: I tried to connect via bluetooth to my desktop computer using my Galago Ultrapro Laptop. I connected...and then i recieved this error afterwards. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AssertionMessage: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed. Date: Wed Feb 5 20:22:32 2014 ExecutablePath: /usr/sbin/bluetoothd InstallationDate: Installed on 2014-02-05 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System76, Inc. Galago UltraPro ProcCmdline: /usr/sbin/bluetoothd ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic root=UUID=bb82e1d2-7c73-4c90-9f41-2b7f805b6082 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: bluez StacktraceTop: __assert_fail_base (fmt=0x7fee829afbe0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fee8380b09e "hs->pending != ((void *)0)", file=file@entry=0x7fee8380ae40 "audio/headset.c", line=line@entry=1487, function=function@entry=0x7fee8380bdd4 "get_record_cb") at assert.c:92 __GI___assert_fail (assertion=0x7fee8380b09e "hs->pending != ((void *)0)", file=0x7fee8380ae40 "audio/headset.c", line=1487, function=0x7fee8380bdd4 "get_record_cb") at assert.c:101 ?? () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: bluetoothd assert failure: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 0C:8B:FD:74:45:E5 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:5057 acl:60 sco:0 events:220 errors:0 TX bytes:20189 acl:59 sco:0 commands:141 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1276897/+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 1508146] Re: alt + left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
** Summary changed: - alt + left/right arrows switch between tty consoles, cannot disable + alt + left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable ** Summary changed: - alt + left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable + Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+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 1533670] Re: python 2.7.10 crashes with a QProcess error 1 after reading some files and trying to display them within wxPython
Hello, i have the same problem. When i execute a program with WxPython the terminal (in ninja) show me, qprocess error. I use Ubuntu 16.04 LTS, ninja-ide, python 2.7.3 and the library wxPython version 4.0.0b1. You can helpme with the solution of the bug?. Sory for my english. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1533670 Title: python 2.7.10 crashes with a QProcess error 1 after reading some files and trying to display them within wxPython Status in dbus package in Ubuntu: Invalid Bug description: This bug allready showed up within Ubuntu 14.04, and I thought I this was the result of curious installs. Thinking it could be a good idea, starting from zero and trying out Ubuntu-Mate 15.10, I installed this enviroment completely new and everything worked fine. Except for the wrong keyboard usage of the system before entering the system, after entering everything is fine ( will post a seperate error-issue for this). ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: dbus 1.10.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: MATE Date: Wed Jan 13 13:54:30 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-01-07 (6 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1533670/+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 1624644] Re: Unable to automatically remove packages that become unused in conjunction with updating by other software
I think less advanced users do not install software that is not packaged. Advanced users can configure system to work as they wish. IMO currently Unattended-Upgrade::Remove-New-Unused-Dependencies is more risky as default. -- 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/1624644 Title: Unable to automatically remove packages that become unused in conjunction with updating by other software Status in unattended-upgrades package in Ubuntu: Opinion Status in update-manager package in Ubuntu: New Status in unattended-upgrades source package in Artful: Opinion Status in update-manager source package in Artful: New Bug description: When using default settings for unattended-upgrades i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, U-U is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because U-U compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624644/+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 1716775] Re: Add option to disable gnome-shell animations
I'm not comfortable classifying this as "Wishlist" with the original description because that implies it's something we would do if we had time. Actually, animations are important to achieving optical flow, which guides human perception of what's happening. So I strongly disagree with disabling animations by default, but do agree the current ones are very poor and need improving. For example, see bug 1713021. I'm not quite sure what you mean by distortion in test case 1 though. The transitions to/from fullscreen retain the original square pixel aspect ratio so there is zero distortion. Can you clarify what you mean? Maybe provide an external video or is "distortion" the wrong word? ** Changed in: ubuntu-settings (Ubuntu) Status: New => Incomplete -- 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/1716775 Title: Add option to disable gnome-shell animations Status in ubuntu-settings package in Ubuntu: Incomplete Bug description: I believe doing so will provide the better experience for most users. Those that see use in it can enable if desired. Am filing this bug first rather than specific against gnome-shell because this is immediately remedied in settings & there are reports of other poor behavior than the below test case. Test case 1: In current 'pseudo' default of xorg In any common video player (totem, vlc, mpv, ect.) open a video. Go from window to fullscreen, fullscreen to windowed, notice the distortion. May be even worse in wayland or when using hw decoding. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.15 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 17:21:52 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings 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/1716775/+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 1716775] Re: Add option to disable gnome-shell animations
** Summary changed: - Please consider disabling gnome-shell animations by default + Add option to disable gnome-shell animations -- 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/1716775 Title: Add option to disable gnome-shell animations Status in ubuntu-settings package in Ubuntu: Incomplete Bug description: I believe doing so will provide the better experience for most users. Those that see use in it can enable if desired. Am filing this bug first rather than specific against gnome-shell because this is immediately remedied in settings & there are reports of other poor behavior than the below test case. Test case 1: In current 'pseudo' default of xorg In any common video player (totem, vlc, mpv, ect.) open a video. Go from window to fullscreen, fullscreen to windowed, notice the distortion. May be even worse in wayland or when using hw decoding. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.15 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 17:21:52 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings 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/1716775/+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 1624644] Re: Unable to automatically remove packages that become unused in conjunction with updating by other software
rbalint, user could mark such packages as manually installed (by apt- mark), so autoremove will not remove them. If you mark update-manager affected, you should mark other updaters, too. E.g. 'apt full-upgrade' or Synaptic will not remove newly unused packages, right? -- 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/1624644 Title: Unable to automatically remove packages that become unused in conjunction with updating by other software Status in unattended-upgrades package in Ubuntu: Opinion Status in update-manager package in Ubuntu: New Status in unattended-upgrades source package in Artful: Opinion Status in update-manager source package in Artful: New Bug description: When using default settings for unattended-upgrades i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, U-U is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because U-U compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624644/+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 1698707] Re: package keyboard-configuration 1.108ubuntu15.3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1698707 Title: package keyboard-configuration 1.108ubuntu15.3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in console-setup package in Ubuntu: Confirmed Bug description: This bug happen when trying tu update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: keyboard-configuration 1.108ubuntu15.3 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun Jun 18 17:41:52 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-10 (39 days ago) InstallationMedia: It PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.2.20 SourcePackage: console-setup Title: package keyboard-configuration 1.108ubuntu15.3 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.d.keyboard-setup: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1698707/+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 1712400] Re: [RFE] Show Ubuntu logo on the GDM login screen
This is fixed now: https://launchpad.net/ubuntu/+source/ubuntu-settings/17.10.15 ** Changed in: ubuntu-settings (Ubuntu) Status: New => Fix Released ** Changed in: gdm3 (Ubuntu) Status: New => Invalid ** Changed in: ubuntu-ux Status: New => Fix Released ** Changed in: ubuntu-themes (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1712400 Title: [RFE] Show Ubuntu logo on the GDM login screen Status in Ubuntu UX: Fix Released Status in gdm3 package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Invalid Bug description: Fedora, Debian and many other distributions have their logo displayed on the bottom of the GDM screen, Ubuntu has nothing there. I think it could be a good idea to show Ubuntu logo or other Ubuntu branding there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1712400/+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 1010724] Re: NM fails to start dnsmasq such that it listens on ::1
It's 2017 now, this is still broken. Please fix this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1010724 Title: NM fails to start dnsmasq such that it listens on ::1 Status in network-manager package in Ubuntu: Triaged Bug description: I have IPv6 activated on Ubuntu 12.04 LTS and I receive an IPv6 address through DHCPv6. However, requests sent through IPv6 fail. For example: strainu@emily:~$ dig -6 google.com ; <<>> DiG 9.8.1-P1 <<>> -6 google.com ;; global options: +cmd ;; connection timed out; no servers could be reached But: strainu@emily:~$ dig google.com ; <<>> DiG 9.8.1-P1 <<>> google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60426 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4 ;; QUESTION SECTION: ;google.com. IN ;; ANSWER SECTION: google.com. 94 IN 2a00:1450:400d:805::1000 Looking into /etc/resolv.conf, I see: strainu@emily:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search lan And with netstat: strainu@emily:~$ netstat -ln Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp0 0 127.0.0.1:530.0.0.0:* LISTEN tcp0 0 127.0.0.1:631 0.0.0.0:* LISTEN tcp6 0 0 ::1:631 :::*LISTEN udp0 0 127.0.0.1:530.0.0.0:* udp0 0 0.0.0.0:68 0.0.0.0:* udp0 0 0.0.0.0:53530.0.0.0:* udp0 0 0.0.0.0:38399 0.0.0.0:* udp6 0 0 :::47973:::* udp6 0 0 :::5353 :::* Apparently, the local dnsmasq server does not listen on IPv6, which is wrong. The server should also listen on ::1:53, to allow IPv6-only connections. Alternatively, the resolvconf package should write the actual DNS server received through DHCPv6 in /etc/resolv.conf ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: resolvconf 1.63ubuntu14 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Sat Jun 9 02:27:02 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to precise on 2012-05-28 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1010724/+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 1716752] Re: LightDM Bypass - lock screen doesn't resize after adding new display
** Changed in: lightdm (Ubuntu) Status: New => Invalid -- 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/1716752 Title: LightDM Bypass - lock screen doesn't resize after adding new display Status in lightdm package in Ubuntu: Invalid Bug description: I'm able to consistently bypass LightDM and access my desktop without a password, simply by plugging in my external monitor. I'm running it on Linux Mint - let me know if this bug is more appropriate for their issue tracker. I made a 1 minute video demonstrating the issue, which might be easier to understand than text. Sorry in advance for filming vertically. https://www.youtube.com/watch?v=EWs_SQJ1-Ak 1) $ lsb_release -rd Description: Linux Mint 18.2 Sonya Release: 18.2 2) $ apt-cache policy lightdm lightdm: Installed: 1.18.3-0ubuntu1.1 Candidate: 1.18.3-0ubuntu1.1 Version table: *** 1.18.3-0ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.18.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) I plugged in my external monitor to my laptop while it was locked. I expected my computer to remain locked even though I had plugged in a new display. 4) The new monitor was not covered by LightDM, allowing me to interact with it. Additionally, parts of my laptop monitor became uncovered. Notes: My laptop display is a 3200x1800 QHD (HiDPI) display when it's standalone but I downscale it to 1600x900 when it has an attached monitor, due to Ubuntu's scaling issues when connecting HiDPI and regular monitors. It's possible that LightDM doesn't think to resize, or resizes incorrectly, when the laptop screen automatically downscales as the new display is attached. I use Nvidia's proprietary graphics drivers (nvidia-375) on a GeForce 840M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1716752/+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 1716848] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Marking as "Won't Fix" for the bluez deb -- the postinst is doing the right thing, there just happens to be something installed outside of dpkg/apt that is getting in the way. ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix -- 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/1716848 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: Won't Fix Bug description: Bluetooth no working in my laptop. Therefore, it's not possible to detect other devices or transfer archives. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Wed Sep 13 08:01:25 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-10 (520 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) InterestingModules: bnep bluetooth MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-93-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-03 (283 days ago) dmi.bios.date: 08/17/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.22 dmi.board.name: 30CC dmi.board.vendor: Quanta dmi.board.version: 79.1D dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd08/17/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.1D:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6500 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716848/+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 1716848] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Looking at the logs I see: Sep 13 07:51:08 agda-HP-Pavilion-dv6500-Notebook-PC audit[1221]: AVC apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap.bluez.bluetoothctl" pid=1221 comm="apparmor_parser" This indicates you have the bluez snap installed. This bug is about the bluez deb on your system. You can't have both on the system at the same time because one will fail to start when the other is listening on the well-known DBus name. The failures you list are consistent with this: the snap has claimed the name on the system bus so the deb cannot, and the postinst fails. Use either the snap or the deb. I suggest you use the deb on classic distro since it has working polkit integration. -- 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/1716848 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: Won't Fix Bug description: Bluetooth no working in my laptop. Therefore, it's not possible to detect other devices or transfer archives. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Wed Sep 13 08:01:25 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-10 (520 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) InterestingModules: bnep bluetooth MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-93-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-03 (283 days ago) dmi.bios.date: 08/17/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.22 dmi.board.name: 30CC dmi.board.vendor: Quanta dmi.board.version: 79.1D dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd08/17/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.1D:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6500 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716848/+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 1716833] Re: NM manages /etc/resolv.conf directly in artful after removal of resolvconf
current base cloud-image does not have resolvconf, but has ifupdown. The following happens: 1) cloud-init starts 2) picks ifupdown renderer 3) renders eni 4) which uses auto dhcp 5) which calls dhclient 6) because there is no resolvconf installed, default make_resolve_conf function is used which is internal to isc-dhcp 7) /etc/resolv.conf stops being a symlink and is a regular file 8) NM starts, notices that /etc/resolv.conf is a regular file and thus is not managed by resolvconf/resolved 9) NM decides to manage /etc/resolv.conf, poorly This does kind of mean that on upgrades, if one removes resolvconf without removing ifupdown things go pear shaped. One option is to re-introduce ifupdown dependency on resolvconf. Another option is to ship isc-dhclient (dhcp-enter-hook) in systemd to override make_resolve_conf function. I've started writing such a hook which uses busctl to feed per-link dhcp info to resolved. However, that has it's own problems. dbus is not started early enough, and there is no private socket to resolved, meaning that updates are getting lost on boot when ifup@.service units are udev triggered on hotplug. Currently working on preserving state in /run and replaying isc-dhclient gathered settings to resolved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1716833 Title: NM manages /etc/resolv.conf directly in artful after removal of resolvconf Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Artful: Triaged Bug description: The nplan autopkgtests are now failing in artful following the removal of resolvconf from the base system, with the following error: == FAIL: test_manual_addresses (__main__.TestNetworkManager) -- Traceback (most recent call last): File "/tmp/autopkgtest.4I4oae/build.Xcu/nplan-0.26/tests/integration.py", line 1110, in test_manual_addresses self.assertRegex(resolv_conf, 'search.*fakesuffix') AssertionError: Regex didn't match: 'search.*fakesuffix' not found in '# Generated by NetworkManager\nnameserver 127.0.1.1\n' It is possible that there is *also* a bug with nplan's integration with systemd-resolved; however, what this error message exposes is that NM is overwriting /etc/resolv.conf when this should now be managed by systemd-resolved instead. NM needs to inject its DNS server information into resolved instead of editing /etc/resolv.conf directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1716833/+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 1504079] Re: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()
My workaround for ubuntu setups. Is to put a file called .trackerignore in any directories that contain avi files. The default configuration for tracker appears to set this. gsettings get org.freedesktop.Tracker.Miner.Files ignored-directories-with-content ['.git', '.trackerignore'] The bug itself needs to be (re)raised with gnome. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1504079 Title: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps() Status in tracker package in Ubuntu: Confirmed Bug description: i need ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: tracker-extract 1.4.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2 Uname: Linux 4.2.0-14-generic i686 ApportVersion: 2.19-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Thu Oct 8 16:04:40 2015 ExecutablePath: /usr/lib/tracker/tracker-extract InstallationDate: Installed on 2015-09-13 (25 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422) ProcCmdline: /usr/lib/tracker/tracker-extract ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xad14eb08 :mov (%eax),%eax PC (0xad14eb08) ok source "(%eax)" (0x007c) not located in a known VMA region (needed readable region)! destination "%eax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: gst_video_info_to_caps () from /usr/lib/i386-linux-gnu/libgstvideo-1.0.so.0 ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstlibav.so ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56 ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56 avcodec_decode_video2 () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56 Title: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1504079/+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 1716848] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
It looks like bluetoothd is failing to restart due to: Sep 13 08:01:25 agda-HP-Pavilion-dv6500-Notebook-PC bluetoothd[4864]: Bluetooth daemon 5.37 Sep 13 08:01:25 agda-HP-Pavilion-dv6500-Notebook-PC bluetoothd[4864]: D-Bus setup failed: Name already in use Sep 13 08:01:25 agda-HP-Pavilion-dv6500-Notebook-PC bluetoothd[4864]: Unable to get on D-Bus -- 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/1716848 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: Confirmed Bug description: Bluetooth no working in my laptop. Therefore, it's not possible to detect other devices or transfer archives. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Wed Sep 13 08:01:25 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-10 (520 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) InterestingModules: bnep bluetooth MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-93-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-03 (283 days ago) dmi.bios.date: 08/17/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.22 dmi.board.name: 30CC dmi.board.vendor: Quanta dmi.board.version: 79.1D dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd08/17/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.1D:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6500 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716848/+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 1717023] [NEW] Jarring double gradient when window is maximized
Public bug reported: Description:Ubuntu Artful Aardvark (development branch) Release:17.10 light-themes: Installed: 16.10+17.10.20170817-0ubuntu1 Candidate: 16.10+17.10.20170817-0ubuntu1 Since windows no longer merge with the top panel when maximized in 17.10, a jarring double gradient is produced instead. Steps to reproduce: Maximize a window Expected outcome: If the window cannot merge with the top bar, a seamless visual transition between the top panel and the title bar is produced. Actual outcome: A double gradient with a sharp line where the top of the title bar meets the top panel is produced. ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: artful gnome-17.10 ** Attachment added: "double_gradient.png" https://bugs.launchpad.net/bugs/1717023/+attachment/4949711/+files/double_gradient.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1717023 Title: Jarring double gradient when window is maximized Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 light-themes: Installed: 16.10+17.10.20170817-0ubuntu1 Candidate: 16.10+17.10.20170817-0ubuntu1 Since windows no longer merge with the top panel when maximized in 17.10, a jarring double gradient is produced instead. Steps to reproduce: Maximize a window Expected outcome: If the window cannot merge with the top bar, a seamless visual transition between the top panel and the title bar is produced. Actual outcome: A double gradient with a sharp line where the top of the title bar meets the top panel is produced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1717023/+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 1292879] Re: bluetoothd crashed with SIGSEGV in finalize_setup_errno()
** Information type changed from Private to Public -- 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/1292879 Title: bluetoothd crashed with SIGSEGV in finalize_setup_errno() Status in bluez package in Ubuntu: New Bug description: When I paring bluetooth device sometimes the device was appear only in MONO, but this device is a stereo headphone. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Sat Mar 15 12:07:11 2014 Disassembly: => 0x20: Não é possível acessar a memória no endereço 0x20 ExecutablePath: /usr/sbin/bluetoothd InstallationDate: Installed on 2014-03-13 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Hewlett-Packard HP G42 Notebook PC ProcCmdline: /usr/sbin/bluetoothd ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-17-generic root=UUID=4b2231d5-0eba-4ddf-810c-08dfb9d7b13b ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x20: Não é possível acessar a memória no endereço 0x20 PC (0x0020) not located in a known VMA region (needed executable region)! source "0x20" (0x0020) not located in a known VMA region (needed readable region)! SegvReason: executing NULL VMA reading NULL VMA Signal: 11 SourcePackage: bluez StacktraceTop: ?? () ?? () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: bluetoothd crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1445 dmi.board.vendor: Hewlett-Packard dmi.board.version: 69.37 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.29:bd04/07/2011:svnHewlett-Packard:pnHPG42NotebookPC:pvr05961224271010100:rvnHewlett-Packard:rn1445:rvr69.37:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP G42 Notebook PC dmi.product.version: 05961224271010100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: CC:52:AF:A9:48:7F ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN RX bytes:83416 acl:84 sco:1567 events:124 errors:0 TX bytes:82252 acl:71 sco:1542 commands:65 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1292879/+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 1276897] Re: bluetoothd assert failure: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed.
** Information type changed from Private to Public -- 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/1276897 Title: bluetoothd assert failure: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed. Status in bluez package in Ubuntu: New Bug description: I tried to connect via bluetooth to my desktop computer using my Galago Ultrapro Laptop. I connected...and then i recieved this error afterwards. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AssertionMessage: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed. Date: Wed Feb 5 20:22:32 2014 ExecutablePath: /usr/sbin/bluetoothd InstallationDate: Installed on 2014-02-05 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System76, Inc. Galago UltraPro ProcCmdline: /usr/sbin/bluetoothd ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic root=UUID=bb82e1d2-7c73-4c90-9f41-2b7f805b6082 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: bluez StacktraceTop: __assert_fail_base (fmt=0x7fee829afbe0 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fee8380b09e "hs->pending != ((void *)0)", file=file@entry=0x7fee8380ae40 "audio/headset.c", line=line@entry=1487, function=function@entry=0x7fee8380bdd4 "get_record_cb") at assert.c:92 __GI___assert_fail (assertion=0x7fee8380b09e "hs->pending != ((void *)0)", file=0x7fee8380ae40 "audio/headset.c", line=1487, function=0x7fee8380bdd4 "get_record_cb") at assert.c:101 ?? () ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: bluetoothd assert failure: bluetoothd: audio/headset.c:1487: get_record_cb: Assertion `hs->pending != ((void *)0)' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd12/12/2013:svnSystem76,Inc.:pnGalagoUltraPro:pvrgalu1:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: Galago UltraPro dmi.product.version: galu1 dmi.sys.vendor: System76, Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 0C:8B:FD:74:45:E5 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:5057 acl:60 sco:0 events:220 errors:0 TX bytes:20189 acl:59 sco:0 commands:141 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1276897/+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 1717023] Re: Jarring double gradient when window is maximized
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1717023 Title: Jarring double gradient when window is maximized Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 light-themes: Installed: 16.10+17.10.20170817-0ubuntu1 Candidate: 16.10+17.10.20170817-0ubuntu1 Since windows no longer merge with the top panel when maximized in 17.10, a jarring double gradient is produced instead. Steps to reproduce: Maximize a window Expected outcome: If the window cannot merge with the top bar, a seamless visual transition between the top panel and the title bar is produced. Actual outcome: A double gradient with a sharp line where the top of the title bar meets the top panel is produced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1717023/+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 1305351] Re: bluetoothd crashed with SIGSEGV in g_slist_remove()
** Information type changed from Private to Public -- 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/1305351 Title: bluetoothd crashed with SIGSEGV in g_slist_remove() Status in bluez package in Ubuntu: New Bug description: Tried to get my Bluetooth device to turn on again by installing Blueman. While changing name and visibility, thiis happened. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu12 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 Date: Thu Apr 10 01:16:16 2014 ExecutablePath: /usr/sbin/bluetoothd InstallationDate: Installed on 2014-04-09 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323) InterestingModules: btusb bnep rfcomm bluetooth MachineType: Sony Corporation SVP1321M2EB ProcCmdline: /usr/sbin/bluetoothd ProcEnviron: PATH=(custom, no user) TERM=linux ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f999169 : cmp %rsi,(%rdi) PC (0x7f999169) ok source "%rsi" ok destination "(%rdi)" (0x6567612f6e616d65) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: bluez StacktraceTop: g_slist_remove () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () ?? () Title: bluetoothd crashed with SIGSEGV in g_slist_remove() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/21/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1043V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1043V7:bd11/21/2013:svnSonyCorporation:pnSVP1321M2EB:pvrC60C0754:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: SVP1321M2EB dmi.product.version: C60C0754 dmi.sys.vendor: Sony Corporation hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 5C:51:4F:13:9F:5B ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN RX bytes:9804 acl:89 sco:0 events:504 errors:0 TX bytes:210292 acl:250 sco:0 commands:219 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1305351/+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 1305890] Re: bluez-simple-service crashed with DBusException in call_blocking(): org.bluez.Error.NoSuchAdapter: No such adapter
** Information type changed from Private to Public -- 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/1305890 Title: bluez-simple-service crashed with DBusException in call_blocking(): org.bluez.Error.NoSuchAdapter: No such adapter Status in bluez package in Ubuntu: New Bug description: patryk@Aspire-E1-772G:~$ lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 patryk@Aspire-E1-772G:~$ apt-cache policy bluez bluez: Zainstalowana: 4.101-0ubuntu12 Kandydująca: 4.101-0ubuntu12 Tabela wersji: *** 4.101-0ubuntu12 0 500 http://at.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status patryk@Aspire-E1-772G:~$ bluez-simple-service Traceback (most recent call last): File "/usr/bin/bluez-simple-service", line 112, in path = manager.DefaultAdapter() File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.bluez.Error.NoSuchAdapter: No such adapter patryk@Aspire-E1-772G:~$ patryk@Aspire-E1-772G:~$ sudo hcidump -XYt > $HOME/hci.log Can't open device: No such device patryk@Aspire-E1-772G:~$ On Windows 8 bluetooth working great. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: bluez 4.101-0ubuntu12 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 10 15:19:24 2014 ExecutablePath: /usr/bin/bluez-simple-service InstallationDate: Installed on 2014-03-01 (39 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301) InterestingModules: btusb rfcomm bnep bluetooth InterpreterPath: /usr/bin/python2.7 MachineType: Acer Aspire E1-772G ProcCmdline: /usr/bin/python /usr/bin/bluez-simple-service ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=a121d353-840a-4d56-979e-6870e7bf3541 ro quiet splash vt.handoff=7 PythonArgs: ['/usr/bin/bluez-simple-service'] SourcePackage: bluez Title: bluez-simple-service crashed with DBusException in call_blocking(): org.bluez.Error.NoSuchAdapter: No such adapter UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/28/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HW dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd01/28/2014:svnAcer:pnAspireE1-772G:pvrV1.03:rvnAcer:rnEA70_HW:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire E1-772G dmi.product.version: V1.03 dmi.sys.vendor: Acer hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1305890/+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 1623418] Re: gcc-as-needed.diff patch broke mpx support in GCC
Hello Alexander, or anyone else affected, Accepted gcc-5 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc-5/5.4.0-6ubuntu1~16.04.5 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gcc-5 (Ubuntu Xenial) Status: New => Fix Committed ** Tags removed: verification-done-xenial ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1623418 Title: gcc-as-needed.diff patch broke mpx support in GCC Status in gcc: Unknown Status in binutils package in Ubuntu: Fix Released Status in gcc-5 package in Ubuntu: Fix Released Status in gcc-6 package in Ubuntu: Fix Released Status in binutils source package in Xenial: Fix Released Status in gcc-5 source package in Xenial: Fix Committed Status in binutils source package in Yakkety: Won't Fix Status in gcc-5 source package in Yakkety: Won't Fix Status in gcc-6 source package in Yakkety: Won't Fix Bug description: [SRU Justification] gcc-5 from Ubuntu is configured with MPX support, but it is broken due to always-added linker option "-as-needed". [Test case] 1. Pass -mmpx to gcc when building an arbitrary project on x86. 2. Verify with ldd that the resulting executable is not linked against libmpx.so because the -as-needed flag has discarded the mpx library from being linked in. 3. Install binutils and gcc-5 from -proposed. 4. Rebuild the target, again with -mmpx. 5. Verify with ldd that the new executable is linked against libmpx.so. 6. Verify that there are no regressions in the binutils testsuite on any architectures, by manually checking the results in the build log. [Regression potential] This binutils patch implements new --push-state / --pop-state options which will not be used in the common case, only when -mmpx is passed. When these flags are not in use, which is the default, it should have no effect on the behavior of the toolchain, so risk of regression is minimal. Here is the GCC upstream bug & fix https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77267 https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=240057 Would it be possible to backport this fix to Ubuntu gcc-5 build? To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1623418/+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 1708438] Re: package util-linux 2.29-1ubuntu2 failed to install/upgrade: pacote util-linux não está pronto para configuração não posso configurar (estado atual 'half-installed')
** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1708438 Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: pacote util-linux não está pronto para configuração não posso configurar (estado atual 'half-installed') Status in dpkg package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: Not install ProblemType: Package DistroRelease: Ubuntu 17.04 Package: util-linux 2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Wed Jul 26 06:27:22 2017 DpkgTerminalLog: dpkg: erro ao processar o pacote util-linux (--configure): pacote util-linux não está pronto para configuração não posso configurar (estado atual 'half-installed') ErrorMessage: pacote util-linux não está pronto para configuração não posso configurar (estado atual 'half-installed') InstallationDate: Installed on 2017-06-06 (57 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package util-linux 2.29-1ubuntu2 failed to install/upgrade: pacote util-linux não está pronto para configuração não posso configurar (estado atual 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1708438/+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 1708602] Re: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor
** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1708602 Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. Status in dpkg package in Ubuntu: New Status in util-linux package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Aug 2 20:08:22 2017 DpkgTerminalLog: dpkg: Fehler beim Bearbeiten des Paketes bsdutils (--configure): Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. ErrorMessage: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. InstallationDate: Installed on 2017-04-15 (110 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: Paket ist in einem sehr schlechten inkonsistenten Zustand - Sie sollten es nochmal installieren, bevor Sie die Konfiguration versuchen. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1708602/+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 1716752] Re: LightDM Bypass - lock screen doesn't resize after adding new display
I filed a new bug with Cinnamon at https://github.com/linuxmint /cinnamon-screensaver/issues/246. Feel free to close this issue - I don't seem to have that option available to me. Thanks for your quick response and helpful triage! ** Bug watch added: github.com/linuxmint/cinnamon-screensaver/issues #246 https://github.com/linuxmint/cinnamon-screensaver/issues/246 -- 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/1716752 Title: LightDM Bypass - lock screen doesn't resize after adding new display Status in lightdm package in Ubuntu: New Bug description: I'm able to consistently bypass LightDM and access my desktop without a password, simply by plugging in my external monitor. I'm running it on Linux Mint - let me know if this bug is more appropriate for their issue tracker. I made a 1 minute video demonstrating the issue, which might be easier to understand than text. Sorry in advance for filming vertically. https://www.youtube.com/watch?v=EWs_SQJ1-Ak 1) $ lsb_release -rd Description: Linux Mint 18.2 Sonya Release: 18.2 2) $ apt-cache policy lightdm lightdm: Installed: 1.18.3-0ubuntu1.1 Candidate: 1.18.3-0ubuntu1.1 Version table: *** 1.18.3-0ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.18.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) I plugged in my external monitor to my laptop while it was locked. I expected my computer to remain locked even though I had plugged in a new display. 4) The new monitor was not covered by LightDM, allowing me to interact with it. Additionally, parts of my laptop monitor became uncovered. Notes: My laptop display is a 3200x1800 QHD (HiDPI) display when it's standalone but I downscale it to 1600x900 when it has an attached monitor, due to Ubuntu's scaling issues when connecting HiDPI and regular monitors. It's possible that LightDM doesn't think to resize, or resizes incorrectly, when the laptop screen automatically downscales as the new display is attached. I use Nvidia's proprietary graphics drivers (nvidia-375) on a GeForce 840M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1716752/+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 1613184] Re: method mirror broken at 1.3
** Description changed: - After update to apt 1.3 + [Impact] + The mirror method always dies with a SEGV. It does not initialize _system but calls a function that sometimes uses it. - in /etc/apt/sources.list + [Test case] + Use a mirror sources.list entry like - deb mirror://mirrors.ubuntu.com/mirrors.txt yakkety main restricted + deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted universe multiverse - apt update get error + [Regression potential] + The fix is small, and simply avoids using _system if _system is NULL in the called method. - E: Method mirror has died unexpectedly! - E: Sub-process mirror received a segmentation fault. + https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba ** Description changed: [Impact] The mirror method always dies with a SEGV. It does not initialize _system but calls a function that sometimes uses it. [Test case] Use a mirror sources.list entry like deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted universe multiverse [Regression potential] - The fix is small, and simply avoids using _system if _system is NULL in the called method. + The fix is small, and simply avoids using _system if _system is NULL in the called method. There should not be any regressions due to this. https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba ** Also affects: apt (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Zesty) Status: New => Triaged ** Changed in: apt (Ubuntu Zesty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1613184 Title: method mirror broken at 1.3 Status in apt package in Ubuntu: Fix Released Status in apt source package in Zesty: Triaged Bug description: [Impact] The mirror method always dies with a SEGV. It does not initialize _system but calls a function that sometimes uses it. [Test case] Use a mirror sources.list entry like deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted universe multiverse [Regression potential] The fix is small, and simply avoids using _system if _system is NULL in the called method. There should not be any regressions due to this. https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1613184/+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 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Also affects: apt (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: New => Incomplete ** Changed in: apt (Ubuntu Xenial) Status: Incomplete => Triaged ** Changed in: apt (Ubuntu Zesty) Status: New => Triaged ** Changed in: apt (Ubuntu) Importance: Undecided => Critical ** Changed in: apt (Ubuntu Zesty) Importance: Undecided => Critical ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: New Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: New Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+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 1702326] Re: New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial
** Changed in: apt (Ubuntu) Importance: Undecided => Medium ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1702326 Title: New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: Triaged Status in apt source package in Zesty: Triaged Status in apt package in Debian: Fix Released Bug description: [Impact] This is a new upstream micro release for the first point release of Debian stretch. apt (1.4.7) stretch; urgency=medium [ Robert Luberda ] * fix a "critical" typo in old changelog entry (Closes: 866358) => Remove a letter, and fixes some tool [ David Kalnischkies ] * use port from SRV record instead of initial port => Might have picked the wrong port [ Julian Andres Klode ] * Reset failure reason when connection was successful => Some failures were only treated as warnings, not errors * debian/gbp.conf: Set debian-branch to 1.4.y => Building ... * http: A response with Content-Length: 0 has no content => Downloading failed if server responded with Content-Length: 0, as APT was waiting for content to read. -- Julian Andres Klode Tue, 04 Jul 2017 17:11:59 +0200 [Test case] We don't really have any yet, they require DNS servers and http servers, so it's not really easy to test. [Regression potential] We basically changed just the code used in the http method, and the changes are both very obvious and very small. I reproduced the http change with the tls support from 1.5, because launchpad was causing issues with that. With the failure reason reset, some errors might not be wrongly considered as transient connection errors and now cause scripts to fail. But that's how it should be, really. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1702326/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697120] Re: artful's apt-file and aptitude complains about Ubuntu sources.list
** Description changed: + [Impact] apt-file is now difficult to use with about a dozen warnings like this: W: Target Contents-deb-legacy (Contents-amd64) is configured multiple times in /etc/apt/sources.list:6 and /etc/apt/sources.list:17 For reference, this is line 6: deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted And this is line 17: deb http://us.archive.ubuntu.com/ubuntu/ artful universe This is how Ubuntu's default sources.list has been structured since the beginning? (or at least more than a decade). What I expect - The warning isn't specific enough. Lines 6 and 17 are not actually duplicates. The warning could be removed or fixed so that it doesn't complain about non-duplicates. Or the warning could be disabled on Ubuntu. See also LP: #1579372 + + [Test case] + Install apt-file and update, make sure that the warnings are gone. + + [Regression potential] + Warnings about duplicate index targets containing "legacy" in their configured name are not shown anymore, thus it's harder to "fix" servers. But apart from that, which was the goal, I don't see any. ** Also affects: apt (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Zesty) Status: New => Triaged ** Changed in: apt (Ubuntu Zesty) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1697120 Title: artful's apt-file and aptitude complains about Ubuntu sources.list Status in apt package in Ubuntu: Fix Released Status in apt source package in Zesty: Triaged Status in apt package in Debian: Fix Released Bug description: [Impact] apt-file is now difficult to use with about a dozen warnings like this: W: Target Contents-deb-legacy (Contents-amd64) is configured multiple times in /etc/apt/sources.list:6 and /etc/apt/sources.list:17 For reference, this is line 6: deb http://us.archive.ubuntu.com/ubuntu/ artful main restricted And this is line 17: deb http://us.archive.ubuntu.com/ubuntu/ artful universe This is how Ubuntu's default sources.list has been structured since the beginning? (or at least more than a decade). What I expect - The warning isn't specific enough. Lines 6 and 17 are not actually duplicates. The warning could be removed or fixed so that it doesn't complain about non-duplicates. Or the warning could be disabled on Ubuntu. See also LP: #1579372 [Test case] Install apt-file and update, make sure that the warnings are gone. [Regression potential] Warnings about duplicate index targets containing "legacy" in their configured name are not shown anymore, thus it's harder to "fix" servers. But apart from that, which was the goal, I don't see any. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1697120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702326] Re: New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial
Sorry for the status noise, I sometimes keep forgetting that statuses have a very different meaning for SRUs than for normal uploads. ** Changed in: apt (Ubuntu Zesty) Status: Fix Committed => In Progress ** Changed in: apt (Ubuntu Zesty) Status: In Progress => Triaged ** Changed in: apt (Ubuntu Xenial) Status: In Progress => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1702326 Title: New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: Triaged Status in apt source package in Zesty: Triaged Status in apt package in Debian: Fix Released Bug description: [Impact] This is a new upstream micro release for the first point release of Debian stretch. apt (1.4.7) stretch; urgency=medium [ Robert Luberda ] * fix a "critical" typo in old changelog entry (Closes: 866358) => Remove a letter, and fixes some tool [ David Kalnischkies ] * use port from SRV record instead of initial port => Might have picked the wrong port [ Julian Andres Klode ] * Reset failure reason when connection was successful => Some failures were only treated as warnings, not errors * debian/gbp.conf: Set debian-branch to 1.4.y => Building ... * http: A response with Content-Length: 0 has no content => Downloading failed if server responded with Content-Length: 0, as APT was waiting for content to read. -- Julian Andres Klode Tue, 04 Jul 2017 17:11:59 +0200 [Test case] We don't really have any yet, they require DNS servers and http servers, so it's not really easy to test. [Regression potential] We basically changed just the code used in the http method, and the changes are both very obvious and very small. I reproduced the http change with the tls support from 1.5, because launchpad was causing issues with that. With the failure reason reset, some errors might not be wrongly considered as transient connection errors and now cause scripts to fail. But that's how it should be, really. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1702326/+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 1702326] Re: New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial
** Changed in: apt (Ubuntu Zesty) Status: Triaged => In Progress ** Changed in: apt (Ubuntu Zesty) Status: In Progress => Fix Committed ** Changed in: apt (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1702326 Title: New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: In Progress Status in apt source package in Zesty: Fix Committed Status in apt package in Debian: Fix Released Bug description: [Impact] This is a new upstream micro release for the first point release of Debian stretch. apt (1.4.7) stretch; urgency=medium [ Robert Luberda ] * fix a "critical" typo in old changelog entry (Closes: 866358) => Remove a letter, and fixes some tool [ David Kalnischkies ] * use port from SRV record instead of initial port => Might have picked the wrong port [ Julian Andres Klode ] * Reset failure reason when connection was successful => Some failures were only treated as warnings, not errors * debian/gbp.conf: Set debian-branch to 1.4.y => Building ... * http: A response with Content-Length: 0 has no content => Downloading failed if server responded with Content-Length: 0, as APT was waiting for content to read. -- Julian Andres Klode Tue, 04 Jul 2017 17:11:59 +0200 [Test case] We don't really have any yet, they require DNS servers and http servers, so it's not really easy to test. [Regression potential] We basically changed just the code used in the http method, and the changes are both very obvious and very small. I reproduced the http change with the tls support from 1.5, because launchpad was causing issues with that. With the failure reason reset, some errors might not be wrongly considered as transient connection errors and now cause scripts to fail. But that's how it should be, really. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1702326/+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 1716979] Re: clean up unmodified /etc/rc.local on upgrade
Dimitri intends to handle this in systemd postinst instead. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Won't Fix -- 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/1716979 Title: clean up unmodified /etc/rc.local on upgrade Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Won't Fix Bug description: If a user's system was installed before zesty, the initscripts package was installed as part of the base system, and a stub /etc/rc.local was created on install. rc.local is very much a legacy interface (it was legacy under Debian's sysvinit, so it's three generations of legacy); and if /etc/rc.local is present and executable, systemd runs an additional unit, rc-local.service, which is After=network-online.target (due to /lib/systemd/system/rc-local.service.d/debian.conf). This can unnecessarily impact boot speed in the event that the network is not available at boot. Since the initscripts package no longer exists in zesty and later, and this package should preferably be removed on upgrade, we can't put maintainer script code in this package to manage the removal of /etc/rc.local. Adding this to any other system package would be a kludge. I think this belongs as a quirk on upgrade, to remove the /etc/rc.local left behind by initscripts if it is unmodified. Here is the md5sum of the stock file, which has remained consistent from (at least) lucid through xenial: $ md5sum /etc/rc.local 10fd9f051accb6fd1f753f2d48371890 /etc/rc.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716979/+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 1716976] Re: DNS resolver silently switches to an unknown DNS server
Maybe interesting: systemd-resolve --status eth2 always reports the correct, internal DNS server, even though names are incorrectly resolved to their public IPs (I tried resolving with both dig and systemd- resolve). gpothier@tadzim3:~$ systemd-resolve --status eth2 Link 3 (eth2) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.0.2 DNS Domain: ozone.caligrafix.cl Also, sudo systemd-resolve --flush-caches temporarily solves the problem, in the same way restarting the service does. -- 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/1716976 Title: DNS resolver silently switches to an unknown DNS server Status in systemd package in Ubuntu: New Bug description: In our network we have a DNS server that resolves some names to local addresses, while the same names are resolved to our public IP when public DNSs are used. For instance (using fictitious names and IPs), xyz.mydomain.com resolves to the public IP 65.254.242.180 when using an external DNS server, but resolves to 192.168.0.14 when using our internal DNS server (which all our computers are told to use via DHCP). This used to work fine until a somewhat recent update in Ubuntu 17.10. Now, xyz.domain.com almost always resolves to the public IP instead of the internal IP. Interestingly, restarting the systemd-resolved service fixes the problem for a while (from a few seconds to a few minutes). Right after restarting the service, the dig command reports the expected internal IP, but after a while it gets back to reporting the public IP. Forcing the dig command to query our DNS server instead of the local resolver returns the correct IP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu9 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 13:34:50 2017 InstallationDate: Installed on 2015-01-23 (963 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-06-15 (90 days ago) dmi.bios.date: 03/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN43WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.family: IDEAPAD dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716976/+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 1716979] Re: clean up unmodified /etc/rc.local on upgrade
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Confirmed ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-17.09 -- 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/1716979 Title: clean up unmodified /etc/rc.local on upgrade Status in systemd package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: If a user's system was installed before zesty, the initscripts package was installed as part of the base system, and a stub /etc/rc.local was created on install. rc.local is very much a legacy interface (it was legacy under Debian's sysvinit, so it's three generations of legacy); and if /etc/rc.local is present and executable, systemd runs an additional unit, rc-local.service, which is After=network-online.target (due to /lib/systemd/system/rc-local.service.d/debian.conf). This can unnecessarily impact boot speed in the event that the network is not available at boot. Since the initscripts package no longer exists in zesty and later, and this package should preferably be removed on upgrade, we can't put maintainer script code in this package to manage the removal of /etc/rc.local. Adding this to any other system package would be a kludge. I think this belongs as a quirk on upgrade, to remove the /etc/rc.local left behind by initscripts if it is unmodified. Here is the md5sum of the stock file, which has remained consistent from (at least) lucid through xenial: $ md5sum /etc/rc.local 10fd9f051accb6fd1f753f2d48371890 /etc/rc.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1716979/+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 1716976] [NEW] DNS resolver silently switches to an unknown DNS server
Public bug reported: In our network we have a DNS server that resolves some names to local addresses, while the same names are resolved to our public IP when public DNSs are used. For instance (using fictitious names and IPs), xyz.mydomain.com resolves to the public IP 65.254.242.180 when using an external DNS server, but resolves to 192.168.0.14 when using our internal DNS server (which all our computers are told to use via DHCP). This used to work fine until a somewhat recent update in Ubuntu 17.10. Now, xyz.domain.com almost always resolves to the public IP instead of the internal IP. Interestingly, restarting the systemd-resolved service fixes the problem for a while (from a few seconds to a few minutes). Right after restarting the service, the dig command reports the expected internal IP, but after a while it gets back to reporting the public IP. Forcing the dig command to query our DNS server instead of the local resolver returns the correct IP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu9 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 13:34:50 2017 InstallationDate: Installed on 2015-01-23 (963 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-06-15 (90 days ago) dmi.bios.date: 03/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN43WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.family: IDEAPAD dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1716976 Title: DNS resolver silently switches to an unknown DNS server Status in systemd package in Ubuntu: New Bug description: In our network we have a DNS server that resolves some names to local addresses, while the same names are resolved to our public IP when public DNSs are used. For instance (using fictitious names and IPs), xyz.mydomain.com resolves to the public IP 65.254.242.180 when using an external DNS server, but resolves to 192.168.0.14 when using our internal DNS server (which all our computers are told to use via DHCP). This used to work fine until a somewhat recent update in Ubuntu 17.10. Now, xyz.domain.com almost always resolves to the public IP instead of the internal IP. Interestingly, restarting the systemd-resolved service fixes the problem for a while (from a few seconds to a few minutes). Right after restarting the service, the dig command reports the expected internal IP, but after a while it gets back to reporting the public IP. Forcing the dig command to query our DNS server instead of the local resolver returns the correct IP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu9 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 13 13:34:50 2017 InstallationDate: Installed on 2015-01-23 (963 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic.efi.signed root=UUID=eecad38d-4fff-462c-92bc-357fa12e5515 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-06-15 (90 days ago) dmi.bios.date: 03/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN43WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN43WW:bd03/30/2015:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.family: IDEAPAD dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO To manage n
[Touch-packages] [Bug 1716775] Re: Please consider disabling gnome-shell animations by default
** Changed in: ubuntu-settings (Ubuntu) Importance: Undecided => Wishlist -- 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/1716775 Title: Please consider disabling gnome-shell animations by default Status in ubuntu-settings package in Ubuntu: New Bug description: I believe doing so will provide the better experience for most users. Those that see use in it can enable if desired. Am filing this bug first rather than specific against gnome-shell because this is immediately remedied in settings & there are reports of other poor behavior than the below test case. Test case 1: In current 'pseudo' default of xorg In any common video player (totem, vlc, mpv, ect.) open a video. Go from window to fullscreen, fullscreen to windowed, notice the distortion. May be even worse in wayland or when using hw decoding. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-settings 17.10.15 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 17:21:52 2017 InstallationDate: Installed on 2017-09-10 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings 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/1716775/+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 1716973] [NEW] Don't pull in network-online.target in apt-daily.timer
Public bug reported: [Impact] apt-daily.timer is enabled on every boot and pulls in network-online.target via Wants and After. While nothing has an After=apt-daily.timer (or rather an After=timers.target) and this should thus not impact boot performance, the rc-local.service specifies an After=network-online.target and the login stuff (getty, gdm, etc) is ordered After=rc-local, thus severely increasing the time to login if nothing else pulls in network-online (like an LSB script). This works around the problem on most boots, the problem will only occur if the timer would have elapsed while the machine was off. [Test case] Well, the change is fairly obvious. Actually testing that is pointless, and depending on the system configuration, network-online.target might be pulled in by something else. So just look at the file and check that the network-online.target dependency moved to the service. [Regression potential] Literally none. We just move the dependency to the service which actually needs it. ** Affects: apt (Ubuntu) Importance: High Status: Fix Released ** Affects: apt (Ubuntu Xenial) Importance: High Status: Triaged ** Affects: apt (Ubuntu Zesty) Importance: High Status: Triaged ** Also affects: apt (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: apt (Ubuntu Zesty) Status: New => Triaged ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => High ** Changed in: apt (Ubuntu Zesty) Importance: Undecided => High ** Changed in: apt (Ubuntu) Importance: Undecided => High ** Changed in: apt (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1716973 Title: Don't pull in network-online.target in apt-daily.timer Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Triaged Status in apt source package in Zesty: Triaged Bug description: [Impact] apt-daily.timer is enabled on every boot and pulls in network-online.target via Wants and After. While nothing has an After=apt-daily.timer (or rather an After=timers.target) and this should thus not impact boot performance, the rc-local.service specifies an After=network-online.target and the login stuff (getty, gdm, etc) is ordered After=rc-local, thus severely increasing the time to login if nothing else pulls in network-online (like an LSB script). This works around the problem on most boots, the problem will only occur if the timer would have elapsed while the machine was off. [Test case] Well, the change is fairly obvious. Actually testing that is pointless, and depending on the system configuration, network-online.target might be pulled in by something else. So just look at the file and check that the network-online.target dependency moved to the service. [Regression potential] Literally none. We just move the dependency to the service which actually needs it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1716973/+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 1702326] Re: New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial
** Summary changed: - New microrelease 1.4.7 for zesty + New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1702326 Title: New microrelease 1.4.7+1.48/zesty, 1.2.25/xenial Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: Triaged Status in apt source package in Zesty: Triaged Status in apt package in Debian: Fix Released Bug description: [Impact] This is a new upstream micro release for the first point release of Debian stretch. apt (1.4.7) stretch; urgency=medium [ Robert Luberda ] * fix a "critical" typo in old changelog entry (Closes: 866358) => Remove a letter, and fixes some tool [ David Kalnischkies ] * use port from SRV record instead of initial port => Might have picked the wrong port [ Julian Andres Klode ] * Reset failure reason when connection was successful => Some failures were only treated as warnings, not errors * debian/gbp.conf: Set debian-branch to 1.4.y => Building ... * http: A response with Content-Length: 0 has no content => Downloading failed if server responded with Content-Length: 0, as APT was waiting for content to read. -- Julian Andres Klode Tue, 04 Jul 2017 17:11:59 +0200 [Test case] We don't really have any yet, they require DNS servers and http servers, so it's not really easy to test. [Regression potential] We basically changed just the code used in the http method, and the changes are both very obvious and very small. I reproduced the http change with the tls support from 1.5, because launchpad was causing issues with that. With the failure reason reset, some errors might not be wrongly considered as transient connection errors and now cause scripts to fail. But that's how it should be, really. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1702326/+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 1716601] Re: video decoders don't work correctly
*** This bug is a duplicate of bug 1716250 *** https://bugs.launchpad.net/bugs/1716250 ** Changed in: gstreamer1.0 (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1716250 totem and cheese show bright pink/purple video -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1716601 Title: video decoders don't work correctly Status in gstreamer1.0 package in Ubuntu: New Bug description: Playing videos sometimes just displays black images (audio coming in clearly) or with one colour channel missing (magenta tint mostly). Tried with several videos, there seems to be no pattern (avi as well as mpeg, different encoders). A significant amount of first calls (after waiting a period of minutes) brings up black (no video). Ubuntu 17.10 plain installation (with additional media support though) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.2-1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 10:03:44 2017 InstallationDate: Installed on 2017-09-05 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1716601/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Hi! There is a fix submitted as a patch i. The thread I have been using for a while. Works flawlessly for me. -- Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com 13. Sep 2017 14:55 by 1624...@bugs.launchpad.net: > Does anyone know if this happens to be fixed in 17.10? I have little > hope that the fix is ever going to make into 17.04... > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1624317 > > Title: > systemd-resolved breaks VPN with split-horizon DNS > > Status in NetworkManager: > Unknown > Status in network-manager package in Ubuntu: > Confirmed > Status in network-manager source package in Zesty: > Confirmed > Status in network-manager source package in Artful: > Confirmed > > Bug description: > [Impact] > >* NetworkManager incorrectly handles dns-priority of the VPN-like > connections, which leads to leaking DNS queries outside of the VPN > into the general internet. > >* Upstream has resolved this issue in master and 1.8 to correctly > configure any dns backends with negative dns-priority settings. > > [Test Case] > > #FIXME# > >* detailed instructions how to reproduce the bug > >* these should allow someone who is not familiar with the affected > package to reproduce the bug and verify that the updated package fixes > the problem. > > #FIXME# > > [Regression Potential] > >* If this issue is changed DNS resolution will change, for certain > queries, to go via VPN rather than general internet. And therefore, > one may get new/different results or even loose access to > resolve/access certain parts of the interent depending on what the DNS > server on VPN chooses to respond to. > > [Other Info] > >* Original bug report > > I use a VPN configured with network-manager-openconnect-gnome in which > a split-horizon DNS setup assigns different addresses to some names > inside the remote network than the addresses seen for those names from > outside the remote network. However, systemd-resolved often decides > to ignore the VPN’s DNS servers and use the local network’s DNS > servers to resolve names (whether in the remote domain or not), > breaking the split-horizon DNS. > > This related bug, reported by Lennart Poettering himself, was closed with > the current Fedora release at the time reaching EOL: > > https://bugzilla.redhat.com/show_bug.cgi?id=1151544 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/network-manager/+bug/1624317/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Zesty: Confirmed Status in network-manager source package in Artful: Confirmed Bug description: [Impact] * NetworkManager incorrectly handles dns-priority of the VPN-like connections, which leads to leaking DNS queries outside of the VPN into the general internet. * Upstream has resolved this issue in master and 1.8 to correctly configure any dns backends with negative dns-priority settings. [Test Case] #FIXME# * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. #FIXME# [Regression Potential] * If this issue is changed DNS resolution will change, for certain queries, to go via VPN rather than general internet. And therefore, one may get new/different results or even loose access to resolve/access certain parts of the interent depending on what the DNS server on VPN chooses to respond to. [Other Info] * Original bug report I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More he
[Touch-packages] [Bug 1702326] Re: New microrelease 1.4.7 for zesty
** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1702326 Title: New microrelease 1.4.7 for zesty Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: Triaged Status in apt source package in Zesty: Triaged Status in apt package in Debian: Fix Released Bug description: [Impact] This is a new upstream micro release for the first point release of Debian stretch. apt (1.4.7) stretch; urgency=medium [ Robert Luberda ] * fix a "critical" typo in old changelog entry (Closes: 866358) => Remove a letter, and fixes some tool [ David Kalnischkies ] * use port from SRV record instead of initial port => Might have picked the wrong port [ Julian Andres Klode ] * Reset failure reason when connection was successful => Some failures were only treated as warnings, not errors * debian/gbp.conf: Set debian-branch to 1.4.y => Building ... * http: A response with Content-Length: 0 has no content => Downloading failed if server responded with Content-Length: 0, as APT was waiting for content to read. -- Julian Andres Klode Tue, 04 Jul 2017 17:11:59 +0200 [Test case] We don't really have any yet, they require DNS servers and http servers, so it's not really easy to test. [Regression potential] We basically changed just the code used in the http method, and the changes are both very obvious and very small. I reproduced the http change with the tls support from 1.5, because launchpad was causing issues with that. With the failure reason reset, some errors might not be wrongly considered as transient connection errors and now cause scripts to fail. But that's how it should be, really. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1702326/+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 1714505] Re: systemd kmod builtin uses out of date kmod context
opened upstream merge request 6814: https://github.com/systemd/systemd/pull/6814 -- 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/1714505 Title: systemd kmod builtin uses out of date kmod context Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Trusty: New Status in systemd source package in Xenial: In Progress Status in systemd source package in Zesty: In Progress Status in systemd source package in Artful: In Progress Bug description: [Impact] udev's rules use a built-in 'kmod' instead of the system modprobe/insmod, and this built-in kmod only validates/refreshes its kmod 'context' every 3 seconds (or longer) during event processing. However, because other parts of the system rely on udev to load modules correctly, it is not acceptable for it to use an out of date module context. For example, during a system installation: -the system boots with kernel and initrd with a reduced set of modules, not including nvme module -udevd starts, and creates its kmod module context, which does not include nvme module -system installer adds 'block-modules' udeb, which adds nvme module to system -system installer immediately calls hw-detect->update-dev->udevadm trigger -udevd sees its kmod module context is not more than 3 seconds old, and does not update it -udevd rule 80-drivers.rules finds NVMe pci modalias and asks kmod builtin to load matching driver -udevd kmod builtin does not find NVMe pci modalias because its context is out of date this results in the system installer complaining to the user that it found no disks, even though there is a NVMe drive in the system, and the nvme module is installed in the system. [Test Case] This is reproducable when trying to install using debian-installer and a preseed file that skips all questions, although not on all systems, since other events can cause udevd to reload all its builtins, or the installer may take longer than 3 seconds to call udevadm trigger after installing the nvme module udeb. However, the bug is easily reproducable on any system with a nvme drive using this script: #!/bin/bash MOD_DIR=/lib/modules/$( uname -r )/kernel/drivers/nvme/host modprobe -rq nvme mv $MOD_DIR/nvme.ko . depmod -a sleep 3 udevadm trigger sleep 1 mv nvme.ko $MOD_DIR/ depmod -a udevadm trigger sleep 3 grep -q nvme /proc/partitions && echo PASS || echo FAIL that script does: 1) remove nvme module from the system, reproducing situation where nvme module had not yet been installed 2) waits 3 seconds, because the udev kmod validation timeout is 3 seconds 3) triggers udev, which forces it to reload its kmod context (this could be done with udevadm control -R instead) 4) waits 1 second for the udev trigger to finish, then puts the nvme module back into the system, reproducing the initial installation of the deb/udeb containing the nvme module 5) immediately triggers udev, which should load the nvme module when it sees the nvme pci device 6) wait 3 seconds for udev trigger to finish (plenty of time), and check if the nvme module was loaded this script reproduces the error every time, due to the stale kmod context. With a fixed udev, this should succeed in loading the nvme module. [Regression Potential] The most potential for regression with a fix to this involves slowing down udev due to validating the kmod context for every kmod load call. However, slightly higher performance does not make up for broken operation. [Other Info] This needs fixing upstream, which I'm in progress on. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1714505/+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 1716930] Re: package libnih-dbus1 1.0.1-1 failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: fsys-tarfile-error ** Changed in: libnih (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1716930 Title: package libnih-dbus1 1.0.1-1 failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 Status in libnih package in Ubuntu: Invalid Bug description: I am not an experience user- I was trying to upgrade from Ubuntu10 to Xubuntu12. It failed to find some lib packs Finally it found Error 127 I tried sudo apt-get update to see if it would find the lost packs. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: libnih-dbus1 1.0.1-1 ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-generic i686 Architecture: i386 Date: Wed Sep 13 15:18:06 2017 Dependencies: gcc-4.4-base 4.4.3-4ubuntu5 libc6 2.19-0ubuntu6.13 libdbus-1-3 1.2.16-2ubuntu4.2 libgcc1 1:4.4.3-4ubuntu5 libnih1 1.0.1-1 ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) SourcePackage: libnih Title: package libnih-dbus1 1.0.1-1 failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1716930/+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 1716929] Re: package libjson-c2 (not installed) failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that there was an error on your system when trying to install a particular package. Please execute the following command, as it will clear your package cache, in a terminal: sudo apt-get clean Then try performing the update again. This will likely resolve your issue, but the failure could be caused by filesystem or memory corruption. So please also run a fsck on your filesystem(s) and a memory test. Thanks in advance! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: fsys-tarfile-error ** Changed in: json-c (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1716929 Title: package libjson-c2 (not installed) failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 Status in json-c package in Ubuntu: Invalid Bug description: I was trying to upgrade from Ubuntu10 to Xubuntu12. It failed to find some lib packs Finally it found Error 127 I tried sudo apt-get update to see if it would find the lost packs ProblemType: Package DistroRelease: Ubuntu 10.04 Package: libjson-c2 (not installed) ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-generic i686 Architecture: i386 Date: Wed Sep 13 15:18:06 2017 ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) SourcePackage: json-c Title: package libjson-c2 (not installed) failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1716929/+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 1615482] Re: apt-daily timer runs at random hours of the day
This bug was fixed in the package apt - 1.4.6~17.04.1 --- apt (1.4.6~17.04.1) zesty; urgency=medium * apt.systemd.daily: Do not pass -d to unattended-upgrade for the download job. This actually enables debugging. Instead check if unattended-upgrade supports an option --download-only (which is yet to be implemented) and use that (Closes: #863859) apt (1.4.5) unstable; urgency=medium * Fix parsing of or groups in build-deps with ignored packages (LP: #1694697) apt (1.4.4) unstable; urgency=medium [ Alan Jenkins ] * apt.systemd.daily: fix error from locking code (Closes: #862567) apt (1.4.3) unstable; urgency=medium [ Julian Andres Klode ] * Do not try to (re)start timers outside 'apt' package (Closes: #862001) [ Miroslav Kure ] * Updated Czech translation of apt (Closes: #861943) apt (1.4.2) unstable; urgency=medium [ Julian Andres Klode ] * Run unattended-upgrade -d in download part * apt.systemd.daily: Add locking * Split apt-daily timer into two (LP: #1686470) [ Matt Kraai ] * bash-completion: Fix spelling of autoclean (Closes: #861846) apt (1.4.1) unstable; urgency=medium [ Julian Andres Klode ] * systemd: Rework timing and add After=network-online (LP: #1615482) * debian/rules: Actually invoke dh_clean in override_dh_clean [ Unit 193 ] * apt-ftparchive: Support '.ddeb' dbgsym packages -- Julian Andres Klode Thu, 01 Jun 2017 10:50:26 +0200 ** Changed in: apt (Ubuntu Zesty) Status: Won't Fix => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1615482 Title: apt-daily timer runs at random hours of the day Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Won't Fix Status in apt source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Released Bug description: apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a systemd timer instead of a cron.daily job. This is a good thing, decoupling apt daily runs from the rest of cron, and ensuring other cron.daily jobs are not blocked by up to half an hour by the default settings of unattended-upgrades. However the policy chosen is to have the apt daily script run at a random hour of the day in a wrong headed attempt to reduce server load. This has the side effect of running unattended-upgrades at random hours of the day — such as business hours — rather than being confined to between 6:25am and 6:55am, using the defaults. A better policy would be to have the script activate at 6:00am plus an interval of 20 minutes at one second intervals reducing the impact of timezone population spikes, while still allowing unattended-upgrades to run within a predictable interval, before 7am. At the very least, some sort of note in the NEWS file detailing the new behaviour would be welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+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 1615482] Update Released
The verification of the Stable Release Update for apt 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1615482 Title: apt-daily timer runs at random hours of the day Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Won't Fix Status in apt source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Released Bug description: apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a systemd timer instead of a cron.daily job. This is a good thing, decoupling apt daily runs from the rest of cron, and ensuring other cron.daily jobs are not blocked by up to half an hour by the default settings of unattended-upgrades. However the policy chosen is to have the apt daily script run at a random hour of the day in a wrong headed attempt to reduce server load. This has the side effect of running unattended-upgrades at random hours of the day — such as business hours — rather than being confined to between 6:25am and 6:55am, using the defaults. A better policy would be to have the script activate at 6:00am plus an interval of 20 minutes at one second intervals reducing the impact of timezone population spikes, while still allowing unattended-upgrades to run within a predictable interval, before 7am. At the very least, some sort of note in the NEWS file detailing the new behaviour would be welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+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 1694697] Re: build-depends keeps OR flag if end of or group is ignored
This bug was fixed in the package apt - 1.4.6~17.04.1 --- apt (1.4.6~17.04.1) zesty; urgency=medium * apt.systemd.daily: Do not pass -d to unattended-upgrade for the download job. This actually enables debugging. Instead check if unattended-upgrade supports an option --download-only (which is yet to be implemented) and use that (Closes: #863859) apt (1.4.5) unstable; urgency=medium * Fix parsing of or groups in build-deps with ignored packages (LP: #1694697) apt (1.4.4) unstable; urgency=medium [ Alan Jenkins ] * apt.systemd.daily: fix error from locking code (Closes: #862567) apt (1.4.3) unstable; urgency=medium [ Julian Andres Klode ] * Do not try to (re)start timers outside 'apt' package (Closes: #862001) [ Miroslav Kure ] * Updated Czech translation of apt (Closes: #861943) apt (1.4.2) unstable; urgency=medium [ Julian Andres Klode ] * Run unattended-upgrade -d in download part * apt.systemd.daily: Add locking * Split apt-daily timer into two (LP: #1686470) [ Matt Kraai ] * bash-completion: Fix spelling of autoclean (Closes: #861846) apt (1.4.1) unstable; urgency=medium [ Julian Andres Klode ] * systemd: Rework timing and add After=network-online (LP: #1615482) * debian/rules: Actually invoke dh_clean in override_dh_clean [ Unit 193 ] * apt-ftparchive: Support '.ddeb' dbgsym packages -- Julian Andres Klode Thu, 01 Jun 2017 10:50:26 +0200 ** Changed in: apt (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1694697 Title: build-depends keeps OR flag if end of or group is ignored Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: New Status in apt source package in Xenial: Fix Released Status in apt source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Released Bug description: [Impact] If the last alternative(s) of an Or group is ignored, because it does not match an architecture list, we would end up keeping the or flag, effectively making the next AND an OR. For example, when parsing (on amd64): debhelper (>= 9), libnacl-dev [amd64] | libnacl-dev [i386] => debhelper (>= 9), libnacl-dev | Which can cause python-apt and apt-get build-dep to crash. Even worse: debhelper (>= 9), libnacl-dev [amd64] | libnacl-dev [i386], foobar => debhelper (>= 9), libnacl-dev [amd64] | foobar [Test case] On amd64: cat > segv.dsc << EOF Format: 3.0 (native) Source: foobar Binary: foobar Architecture: all Version: 1 Maintainer: Joe Sixpack Build-Depends: build-essential [amd64] | build-essential [fancy] Standards-Version: 3.9.8 EOF cat > failure.dsc << EOF Format: 3.0 (native) Source: foobar Binary: foobar Architecture: all Version: 1 Maintainer: Joe Sixpack Build-Depends: build-essential [amd64] | build-essential [fancy], a-non-existing-package Standards-Version: 3.9.8 EOF (1) apt-get build-dep -s ./segv.dsc should succeed instead of crash (2) apt-get build-dep -s ./failure.dsc should complain about "Depends: a-non-existing-package but it is not installable" instead of succeeding. This is the same test as run by CI and autopkgtests, so if they pass the tests passed. You can also run apt-get build-dep -s dq for a real life example that should not segfault. [Regression Potential] apt-get build-dep and friends can now fail where they succeeded previously for packages that employ architecture-limited alternatives in their build depends, as in the second example given above, because now additional packages need to be installed (which is correct, though). [Other info] By setting the previous alternatives Or flag to the current Or flag if the current alternative is ignored, we solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1694697/+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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
This bug was fixed in the package apt - 1.4.6~17.04.1 --- apt (1.4.6~17.04.1) zesty; urgency=medium * apt.systemd.daily: Do not pass -d to unattended-upgrade for the download job. This actually enables debugging. Instead check if unattended-upgrade supports an option --download-only (which is yet to be implemented) and use that (Closes: #863859) apt (1.4.5) unstable; urgency=medium * Fix parsing of or groups in build-deps with ignored packages (LP: #1694697) apt (1.4.4) unstable; urgency=medium [ Alan Jenkins ] * apt.systemd.daily: fix error from locking code (Closes: #862567) apt (1.4.3) unstable; urgency=medium [ Julian Andres Klode ] * Do not try to (re)start timers outside 'apt' package (Closes: #862001) [ Miroslav Kure ] * Updated Czech translation of apt (Closes: #861943) apt (1.4.2) unstable; urgency=medium [ Julian Andres Klode ] * Run unattended-upgrade -d in download part * apt.systemd.daily: Add locking * Split apt-daily timer into two (LP: #1686470) [ Matt Kraai ] * bash-completion: Fix spelling of autoclean (Closes: #861846) apt (1.4.1) unstable; urgency=medium [ Julian Andres Klode ] * systemd: Rework timing and add After=network-online (LP: #1615482) * debian/rules: Actually invoke dh_clean in override_dh_clean [ Unit 193 ] * apt-ftparchive: Support '.ddeb' dbgsym packages -- Julian Andres Klode Thu, 01 Jun 2017 10:50:26 +0200 ** Changed in: apt (Ubuntu Zesty) Status: Fix Committed => Fix Released ** Changed in: unattended-upgrades (Ubuntu Zesty) Status: Fix Committed => Fix Released -- 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/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Released Status in unattended-upgrades source package in Zesty: Fix Released Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Fix Released Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: Fix Released Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. * Downgrade systemd to the release version of the package (from -security). Remove apt periodic stamp files rm /var/lib/apt/periodic/*. Then run 'sudo systemctl start apt-daily.service'. Confirm that the syst
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
This bug was fixed in the package unattended-upgrades - 0.93.1ubuntu2.3 --- unattended-upgrades (0.93.1ubuntu2.3) zesty; urgency=medium * Cherry-pick 2e5deed, f26edb4 from upstream to add support for a --download-only option, enabling us to download updates at a random time of day by default but apply them predictably in the 6am-7am window. LP: #1686470. -- Steve Langasek Mon, 31 Jul 2017 12:40:12 -0700 -- 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/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Released Status in unattended-upgrades source package in Zesty: Fix Released Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Fix Released Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: Fix Released Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. * Downgrade systemd to the release version of the package (from -security). Remove apt periodic stamp files rm /var/lib/apt/periodic/*. Then run 'sudo systemctl start apt-daily.service'. Confirm that the systemd package is downloaded, but not upgraded. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they prefer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+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 1624644] Re: Unable to automatically remove packages that become unused in conjunction with updating by other software
Added update-manager as affected package because update-manager is the tool leaving newly unused packages around. ** Also affects: update-manager (Ubuntu) Importance: Undecided Status: New -- 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/1624644 Title: Unable to automatically remove packages that become unused in conjunction with updating by other software Status in unattended-upgrades package in Ubuntu: Opinion Status in update-manager package in Ubuntu: New Status in unattended-upgrades source package in Artful: Opinion Status in update-manager source package in Artful: New Bug description: When using default settings for unattended-upgrades i.e. Unattended-Upgrade::Remove-Unused-Dependencies "false"; # default "false" Unattended-Upgrade::Remove-New-Unused-Dependencies "true"; # default "true" in configuration file /etc/apt/apt.conf.d/50unattended-upgrades, U-U is unable to remove packages that become unused in conjunction with updating by other software such as update-manager or apt full-upgrade. This is because U-U compares the list of unneeded packages before and after it upgrades packages to detect which packages are new unused ones. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CurrentDesktop: XFCE Date: Sat Sep 17 11:28:44 2016 InstallationDate: Installed on 2016-09-05 (11 days ago) InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1624644/+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 1693226] Re: Break the conflicts with click the optparser
on Ubuntu Xenial this still gives this error: ``` Traceback (most recent call last): File "/usr/bin/click", line 37, in import click_package as click ImportError: No module named 'click_package' dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... Traceback (most recent call last): File "/usr/bin/click", line 37, in import click_package as click ImportError: No module named 'click_package' dpkg: error processing archive /var/cache/apt/archives/click-apparmor_0.3.13.1_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 1 ``` i did a little experiment: `sudo apt update && sudo apt install python3-click-package python3-click libclick-0.4-dev libclick-0.4` then reinstalling: `sudo apt install click click-apparmor --reinstall --force-yes` fixes this now on Xenial Xerus -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1693226 Title: Break the conflicts with click the optparser Status in click package in Ubuntu: Fix Released Status in click source package in Xenial: Fix Released Status in click source package in Yakkety: Fix Released Status in click source package in Zesty: Fix Released Status in click source package in Artful: Fix Released Bug description: [Impact] * python-click and python-click-package conflict as they use the same python package for its implementation. * Since python-click-package is an implementation detail for the click package and python3-click is a package meant to be used in other implementations it makes sense to break the conflict by moving the package name for python-click-package to a different name * snapcraft has moved from docopt to python3-click, users that have click installed don't have an upgrade path.his bug. [Test Case] * Where snapcraft 2.30 is present: - apt install click - Install snapcraft << 2.30 - update to snapcraft >= 2.30 - the upgrade should not be held on any package. - click and snapcraft commands should work. * Install python3-click and click should be possible. The click command should keep working and python3 -c 'from click import group' shall work. [Regression Potential] * Users depending on click from python-click-package will be importing an unexpected click in any scripts they may have. [Other Info] * While unfortunate, click as a technology is deprecated and not used anymore. This resolution path was discussed with slangasek and apw prior to any work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1693226/+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 1542328] Re: package bluez 5.35-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks RT -- 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/1542328 Title: package bluez 5.35-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: Expired Bug description: bluez failes to install in LXC container. It's come as a dependency of ubuntu-desktop and therefore breaks its installation on Wily. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 NonfreeKernelModules: btrfs ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c xt_multiport unix_diag tcp_diag inet_diag xt_nat ip6table_filter ip6_tables bluetooth veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache snd_hda_codec_hdmi kvm_amd kvm crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw snd_hda_codec_realtek usblp fam15h_power k10temp edac_core edac_mce_amd snd_hda_intel snd_hda_codec nouveau snd_hwdep snd_pcm snd_page_alloc mxm_wmi i2c_piix4 video snd_timer ttm drm_kms_helper drm snd soundcore i2c_algo_bit mac_hid shpchp wmi parport_pc ppdev lp parport dm_snapshot pata_acpi raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 pata_atiixp raid0 r8169 mii multipath ahci libahci linear ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Feb 5 16:47:05 2016 DuplicateSignature: package:bluez:5.35-0ubuntu2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InterestingModules: bluetooth Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-77-generic root=/dev/mapper/system-root ro nosplash nomdmonddf nomdmonisw RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: bluez Title: package bluez 5.35-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: 970DE3/U3S3 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:bd10/05/2012:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970DE3/U3S3: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. getfacl: Error: command ['getfacl', '/dev/rfkill'] failed with exit code 1: getfacl: /dev/rfkill: No such file or directory hciconfig: Error: command hciconfig failed with exit code 1: Can't open HCI socket.: Address family not supported by protocol rfkill: Can't open RFKILL control device: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1542328/+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 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
Ben, I feel your pain and couldn't agree more. I'm under the impression that this attitude is getting more common as Canonical focuses on server and IoT. Where are the days where the 100 Papercuts (https://wiki.ubuntu.com/One%20Hundred%20Papercuts) got a really high priority? IMHO, this bug sure seems to qualify... -- 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/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full Status in unattended-upgrades: New Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+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 1716931] [NEW] package lsb-base 4.0-0ubuntu8 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 127
Public bug reported: I was trying to upgrade from Ubuntu10 to Xubuntu12. It failed to find some lib packs Finally it found Error 127 I tried sudo apt-get update to see if it would find the lost packs I'd appreciate if you could supply some instructions for me to upgrade the system since I can not even use a proper web browse. I am an absolute beginner at on Linux. Thanks in advance ProblemType: Package DistroRelease: Ubuntu 10.04 Package: lsb-base 4.0-0ubuntu8 ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-generic i686 Architecture: i386 Date: Wed Sep 13 15:44:00 2017 ErrorMessage: el subproceso script pre-installation nuevo devolvió el código de salida de error 127 InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) PackageArchitecture: all SourcePackage: lsb Title: package lsb-base 4.0-0ubuntu8 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 127 ** Affects: lsb (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1716931 Title: package lsb-base 4.0-0ubuntu8 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 127 Status in lsb package in Ubuntu: New Bug description: I was trying to upgrade from Ubuntu10 to Xubuntu12. It failed to find some lib packs Finally it found Error 127 I tried sudo apt-get update to see if it would find the lost packs I'd appreciate if you could supply some instructions for me to upgrade the system since I can not even use a proper web browse. I am an absolute beginner at on Linux. Thanks in advance ProblemType: Package DistroRelease: Ubuntu 10.04 Package: lsb-base 4.0-0ubuntu8 ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-generic i686 Architecture: i386 Date: Wed Sep 13 15:44:00 2017 ErrorMessage: el subproceso script pre-installation nuevo devolvió el código de salida de error 127 InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) PackageArchitecture: all SourcePackage: lsb Title: package lsb-base 4.0-0ubuntu8 failed to install/upgrade: el subproceso script pre-installation nuevo devolvió el código de salida de error 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1716931/+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 1716929] [NEW] package libjson-c2 (not installed) failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
Public bug reported: I was trying to upgrade from Ubuntu10 to Xubuntu12. It failed to find some lib packs Finally it found Error 127 I tried sudo apt-get update to see if it would find the lost packs ProblemType: Package DistroRelease: Ubuntu 10.04 Package: libjson-c2 (not installed) ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-generic i686 Architecture: i386 Date: Wed Sep 13 15:18:06 2017 ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) SourcePackage: json-c Title: package libjson-c2 (not installed) failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 ** Affects: json-c (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1716929 Title: package libjson-c2 (not installed) failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 Status in json-c package in Ubuntu: New Bug description: I was trying to upgrade from Ubuntu10 to Xubuntu12. It failed to find some lib packs Finally it found Error 127 I tried sudo apt-get update to see if it would find the lost packs ProblemType: Package DistroRelease: Ubuntu 10.04 Package: libjson-c2 (not installed) ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-generic i686 Architecture: i386 Date: Wed Sep 13 15:18:06 2017 ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) SourcePackage: json-c Title: package libjson-c2 (not installed) failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1716929/+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 1716930] [NEW] package libnih-dbus1 1.0.1-1 failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2
Public bug reported: I am not an experience user- I was trying to upgrade from Ubuntu10 to Xubuntu12. It failed to find some lib packs Finally it found Error 127 I tried sudo apt-get update to see if it would find the lost packs. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: libnih-dbus1 1.0.1-1 ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-generic i686 Architecture: i386 Date: Wed Sep 13 15:18:06 2017 Dependencies: gcc-4.4-base 4.4.3-4ubuntu5 libc6 2.19-0ubuntu6.13 libdbus-1-3 1.2.16-2ubuntu4.2 libgcc1 1:4.4.3-4ubuntu5 libnih1 1.0.1-1 ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) SourcePackage: libnih Title: package libnih-dbus1 1.0.1-1 failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 ** Affects: libnih (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 lucid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1716930 Title: package libnih-dbus1 1.0.1-1 failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 Status in libnih package in Ubuntu: New Bug description: I am not an experience user- I was trying to upgrade from Ubuntu10 to Xubuntu12. It failed to find some lib packs Finally it found Error 127 I tried sudo apt-get update to see if it would find the lost packs. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: libnih-dbus1 1.0.1-1 ProcVersionSignature: Ubuntu 2.6.32-33.70-generic 2.6.32.41+drm33.18 Uname: Linux 2.6.32-33-generic i686 Architecture: i386 Date: Wed Sep 13 15:18:06 2017 Dependencies: gcc-4.4-base 4.4.3-4ubuntu5 libc6 2.19-0ubuntu6.13 libdbus-1-3 1.2.16-2ubuntu4.2 libgcc1 1:4.4.3-4ubuntu5 libnih1 1.0.1-1 ErrorMessage: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 InstallationMedia: Ubuntu 10.04.3 LTS "Lucid Lynx" - Release i386 (20110720.1) SourcePackage: libnih Title: package libnih-dbus1 1.0.1-1 failed to install/upgrade: el subproceso dpkg-deb --fsys-tarfile devolvió el código de salida de error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1716930/+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 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable
In my case, I am also using keepassxc. But I'm using the AppImage version rather than the Snap package. (The Snap version doesn't seem to be able to display a status/tray icon, while the AppImage version does). It's possible keepassxc is related, or it's a coincidence. -- 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/1508146 Title: alt + left/right arrows switch between tty consoles, cannot disable Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+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 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Ethan: Re: ping over IRC, yes, please apt_1.2.25-rbalint2 for testing u-u. When Unattended-Upgrade::InstallOnShutdown is set u-u should also work properly with apt 1.2.24 from -updates. -- 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/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to Status in OEM Priority Project: Triaged Status in OEM Priority Project xenial series: New Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.90 Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Does anyone know if this happens to be fixed in 17.10? I have little hope that the fix is ever going to make into 17.04... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Zesty: Confirmed Status in network-manager source package in Artful: Confirmed Bug description: [Impact] * NetworkManager incorrectly handles dns-priority of the VPN-like connections, which leads to leaking DNS queries outside of the VPN into the general internet. * Upstream has resolved this issue in master and 1.8 to correctly configure any dns backends with negative dns-priority settings. [Test Case] #FIXME# * detailed instructions how to reproduce the bug * these should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. #FIXME# [Regression Potential] * If this issue is changed DNS resolution will change, for certain queries, to go via VPN rather than general internet. And therefore, one may get new/different results or even loose access to resolve/access certain parts of the interent depending on what the DNS server on VPN chooses to respond to. [Other Info] * Original bug report I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1624317/+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 1716892] Re: !!BLUESCREEN!! (Ubuntu Mate with ubuntu-desktop (unity) package) failed to install/upgrade: Paket humanity-icon-theme ist nicht bereit zur Konfiguration kann nicht
** Summary changed: - !!BLUESCREEN!! (Ubuntu Mate with ubuntu-desktop (unity) package) package humanity-icon-theme 0.6.10 [modified: usr/share/icons/Humanity/actions/32/object-inverse.svg usr/share/icons/Humanity/animations/16/process-working.png usr/share/icons/Humanity/animations/22/process-working.png usr/share/icons/Humanity/animations/24/process-working.png usr/share/icons/Humanity/animations/32/process-working.png usr/share/icons/Humanity/categories/32/applications-development.svg usr/share/icons/Humanity/emblems/16/emblem-OK.png usr/share/icons/Humanity/emblems/16/emblem-cool.png usr/share/icons/Humanity/emblems/16/emblem-ohno.png usr/share/icons/Humanity/emblems/22/emblem-OK.png usr/share/icons/Humanity/emblems/22/emblem-cool.png usr/share/icons/Humanity/emblems/22/emblem-ohno.png usr/share/icons/Humanity/emblems/24/emblem-OK.png usr/share/icons/Humanity/emblems/24/emblem-cool.png usr/share/icons/Humanity/emblems/24/emblem-ohno.png usr/share/icons/Humanity/emblems/32/emblem-OK.png usr/share/icons/Humanity/emblems/32/emblem-cool.png usr/share/icons/Humanity/emblems/32/emblem-ohno.png usr/share/icons/Humanity/index.theme usr/share/icons/Humanity/mimes/16/libreoffice-oasis-drawing-template.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-master-document.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-presentation-template.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-web-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-drawing-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-formula.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-presentation-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-text-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-web-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-drawing-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-presentation-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-text-template.png usr/share/icons/Humanity/status/16/audio-volume-high.png usr/share/icons/Humanity/status/16/audio-volume-medium.png usr/share/icons/Humanity/status/22/audio-volume-high.png usr/share/icons/Humanity/status/22/audio-volume-low.png usr/share/icons/Humanity/status/22/audio-volume-medium.png usr/share/icons/Humanity/status/22/audio-volume-muted.png usr/share/icons/Humanity/status/22/gsm-3g-low-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-low.svg usr/share/icons/Humanity/status/22/gsm-3g-medium-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-medium.svg usr/share/icons/Humanity/status/22/gsm-3g-none-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-none.svg usr/share/icons/Humanity/status/24/audio-volume-high.png usr/share/icons/Humanity/status/24/audio-volume-low.png usr/share/icons/Humanity/status/24/audio-volume-medium.png usr/share/icons/Humanity/status/24/audio-volume-muted.png usr/share/icons/Humanity/status/24/gsm-3g-high-secure.svg usr/share/icons/Humanity/status/24/gsm-3g-high.svg usr/share/icons/Humanity/status/24/gsm-3g-low-secure.svg usr/share/icons/Humanity/status/24/gsm-3g-medium-secure.svg usr/share/icons/Humanity/status/48/weather-showers.svg] failed to install/upgrade: Paket humanity-icon-theme ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) + !!BLUESCREEN!! (Ubuntu Mate with ubuntu-desktop (unity) package) failed to install/upgrade: Paket humanity-icon-theme ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1716892 Title: !!BLUESCREEN!! (Ubuntu Mate with ubuntu-desktop (unity) package) failed to install/upgrade: Paket humanity-icon-theme ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) Status in humanity-icon-theme package in Ubuntu: New Bug description: When trying to install anything (gnome-chess) ProblemType: Package DistroRelease: Ubuntu 16.04 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Sep 13 12:26:56 2017 ErrorMessage: Paket humanity-icon-theme ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) InstallationDate: Installed on 2017-09-12 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPack
[Touch-packages] [Bug 1702642] Re: package ubuntu-mono 14.04+16.04.20161024-0ubuntu1 failed to install/upgrade: package ubuntu-mono is already installed and configured
*** This bug is a duplicate of bug 545790 *** https://bugs.launchpad.net/bugs/545790 ** This bug is no longer a duplicate of bug 1702639 package ubuntu-mono 14.04+16.04.20161024-0ubuntu1 failed to install/upgrade: package ubuntu-mono is already installed and configured ** This bug has been marked a duplicate of bug 545790 package PACKAGE failed to install/upgrade: error writing to '': Success -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1702642 Title: package ubuntu-mono 14.04+16.04.20161024-0ubuntu1 failed to install/upgrade: package ubuntu-mono is already installed and configured Status in ubuntu-themes package in Ubuntu: New Bug description: I was installing software updates from Ubuntu center, when these issues corpped up. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ubuntu-mono 14.04+16.04.20161024-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Thu Jul 6 13:01:43 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DuplicateSignature: package:ubuntu-mono:14.04+16.04.20161024-0ubuntu1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package accountsservice (--configure): package accountsservice is already installed and configured ErrorMessage: package ubuntu-mono is already installed and configured InstallationDate: Installed on 2017-06-15 (21 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: ubuntu-themes Title: package ubuntu-mono 14.04+16.04.20161024-0ubuntu1 failed to install/upgrade: package ubuntu-mono is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1702642/+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 1716848] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1716848 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: Confirmed Bug description: Bluetooth no working in my laptop. Therefore, it's not possible to detect other devices or transfer archives. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Wed Sep 13 08:01:25 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-10 (520 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) InterestingModules: bnep bluetooth MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-93-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-03 (283 days ago) dmi.bios.date: 08/17/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.22 dmi.board.name: 30CC dmi.board.vendor: Quanta dmi.board.version: 79.1D dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd08/17/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.1D:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6500 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716848/+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 1716892] [NEW] !!BLUESCREEN!! (Ubuntu Mate with ubuntu-desktop (unity) package) package humanity-icon-theme 0.6.10 [modified: usr/share/icons/Humanity/actions/32/object-inverse.s
Public bug reported: When trying to install anything (gnome-chess) ProblemType: Package DistroRelease: Ubuntu 16.04 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Wed Sep 13 12:26:56 2017 ErrorMessage: Paket humanity-icon-theme ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) InstallationDate: Installed on 2017-09-12 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: humanity-icon-theme UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: humanity-icon-theme (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 humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1716892 Title: !!BLUESCREEN!! (Ubuntu Mate with ubuntu-desktop (unity) package) package humanity-icon-theme 0.6.10 [modified: usr/share/icons/Humanity/actions/32/object-inverse.svg usr/share/icons/Humanity/animations/16/process-working.png usr/share/icons/Humanity/animations/22/process-working.png usr/share/icons/Humanity/animations/24/process-working.png usr/share/icons/Humanity/animations/32/process-working.png usr/share/icons/Humanity/categories/32/applications-development.svg usr/share/icons/Humanity/emblems/16/emblem-OK.png usr/share/icons/Humanity/emblems/16/emblem-cool.png usr/share/icons/Humanity/emblems/16/emblem-ohno.png usr/share/icons/Humanity/emblems/22/emblem-OK.png usr/share/icons/Humanity/emblems/22/emblem-cool.png usr/share/icons/Humanity/emblems/22/emblem-ohno.png usr/share/icons/Humanity/emblems/24/emblem-OK.png usr/share/icons/Humanity/emblems/24/emblem-cool.png usr/share/icons/Humanity/emblems/24/emblem-ohno.png usr/share/icons/Humanity/emblems/32/emblem-OK.png usr/share/icons/Humanity/emblems/32/emblem-cool.png usr/share/icons/Humanity/emblems/32/emblem-ohno.png usr/share/icons/Humanity/index.theme usr/share/icons/Humanity/mimes/16 /libreoffice-oasis-drawing-template.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-master- document.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis- presentation-template.png usr/share/icons/Humanity/mimes/16 /libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/16/libreoffice-oasis-web-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-drawing- template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis- formula.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis- presentation-template.png usr/share/icons/Humanity/mimes/32 /libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-text-template.png usr/share/icons/Humanity/mimes/32/libreoffice-oasis-web-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-drawing- template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis- presentation-template.png usr/share/icons/Humanity/mimes/48 /libreoffice-oasis-spreadsheet-template.png usr/share/icons/Humanity/mimes/48/libreoffice-oasis-text-template.png usr/share/icons/Humanity/status/16/audio-volume-high.png usr/share/icons/Humanity/status/16/audio-volume-medium.png usr/share/icons/Humanity/status/22/audio-volume-high.png usr/share/icons/Humanity/status/22/audio-volume-low.png usr/share/icons/Humanity/status/22/audio-volume-medium.png usr/share/icons/Humanity/status/22/audio-volume-muted.png usr/share/icons/Humanity/status/22/gsm-3g-low-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-low.svg usr/share/icons/Humanity/status/22/gsm-3g-medium-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-medium.svg usr/share/icons/Humanity/status/22/gsm-3g-none-secure.svg usr/share/icons/Humanity/status/22/gsm-3g-none.svg usr/share/icons/Humanity/status/24/audio-volume-high.png usr/share/icons/Humanity/status/24/audio-volume-low.png usr/share/icons/Humanity/status/24/audio-volume-medium.png usr/share/icons/Humanity/status/24/audio-volume-muted.png usr/share/icons/Humanity/status/24/gsm-3g-high-secure.svg usr/share/icons/Humanity/status/24/gsm-3g-high.svg usr/share/icons/Humanity/status/24/gsm-3g-low-secure.svg usr/share/icons/Humanity/status/24/gsm-3g-medium-secure.svg usr/share/icons/Humanity/status/48/weather-showers.svg] failed to install/upgrade: Paket humanity-icon-theme ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) Status in humanity-icon-theme package in Ubuntu: New Bug description: When trying to install anything (gnome-chess) ProblemType: Package DistroRelease: Ubuntu 16.04 ProcVersionSignature: Ubun
[Touch-packages] [Bug 1716752] Re: LightDM Bypass - lock screen doesn't resize after adding new display
LightDM can use the greeter as a lock screen or it can be done by the shell. Yes, you should file against Cinnamon. It may be light-locker which is doing the locking or something else in Cinnamon. -- 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/1716752 Title: LightDM Bypass - lock screen doesn't resize after adding new display Status in lightdm package in Ubuntu: New Bug description: I'm able to consistently bypass LightDM and access my desktop without a password, simply by plugging in my external monitor. I'm running it on Linux Mint - let me know if this bug is more appropriate for their issue tracker. I made a 1 minute video demonstrating the issue, which might be easier to understand than text. Sorry in advance for filming vertically. https://www.youtube.com/watch?v=EWs_SQJ1-Ak 1) $ lsb_release -rd Description: Linux Mint 18.2 Sonya Release: 18.2 2) $ apt-cache policy lightdm lightdm: Installed: 1.18.3-0ubuntu1.1 Candidate: 1.18.3-0ubuntu1.1 Version table: *** 1.18.3-0ubuntu1.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.18.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3) I plugged in my external monitor to my laptop while it was locked. I expected my computer to remain locked even though I had plugged in a new display. 4) The new monitor was not covered by LightDM, allowing me to interact with it. Additionally, parts of my laptop monitor became uncovered. Notes: My laptop display is a 3200x1800 QHD (HiDPI) display when it's standalone but I downscale it to 1600x900 when it has an attached monitor, due to Ubuntu's scaling issues when connecting HiDPI and regular monitors. It's possible that LightDM doesn't think to resize, or resizes incorrectly, when the laptop screen automatically downscales as the new display is attached. I use Nvidia's proprietary graphics drivers (nvidia-375) on a GeForce 840M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1716752/+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 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
Is anyone working on this? I see that the bug is assigned, but apart from that only messages from affected users. -- 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/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." Status in systemd package in Ubuntu: Confirmed Bug description: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 from checkpoint. May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device /dev/md/Volume0 I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 > /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without any keyboard. [EDIT]But I can still switch back to tty1.[/EDIT] I have also tried with much lower values for vm.dirty_background_ratio and vm.dirty_ratio, but to no avail. Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not help either. More information below: $ lsb_release -rd Description:
[Touch-packages] [Bug 1716884] Re: network-manager consume too much file descriptor and is not able to work correctly
Looks like the issue starts when connect a USB wifi dongle (based on ath9k_htc). After a fresh NetworkManager restart, journalctl shows that USB device is enumerated periodically, and for some reasons, failed to be configured correctly. We can conclude that there is a FD leakage every time a new interface is inserted/removed. I will check what is wrong with the enumeration/configuration. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1716884/+attachment/4949346/+files/journalctl.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1716884 Title: network-manager consume too much file descriptor and is not able to work correctly Status in network-manager package in Ubuntu: New Bug description: Detected when I failed to start a vpn client session. journalctl shows line like: sept. 13 10:37:29 xxx NetworkManager[1092]: [1505291849.7302] vpn-connection[0x2786800,4cd810de-c299-41e9-bf4b-c6df18d09b66,"xxx",0]: Could not launch the VPN service. error: Trop de fichiers ouverts. Indeed, /proc/$PID/fd is full of socket file descriptors. (with PID the pid of NetworkManager) "strace -e socket -p $PID -f" shows that a netlink socket is opened every 3s and never closed. [pid 9384] socket(PF_NETLINK, SOCK_RAW|SOCK_CLOEXEC, NETLINK_GENERIC) = 361 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Uname: Linux 4.11.0-14-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 13 11:12:05 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-06-23 (447 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160622) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1716884/+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 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low
Sorry, in comment #12 I mean "clutter" (in its gdk subdir), not "clutter-gtk". ** Changed in: clutter-1.0 (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698270 Title: Totem pauses and stutters during video playback even when CPU usage is low Status in Totem: Incomplete Status in clutter-1.0 package in Ubuntu: Won't Fix Status in clutter-gtk package in Ubuntu: New Status in gstreamer package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: In Progress Status in totem package in Ubuntu: Fix Released Bug description: Totem pauses and stutters during video playback even when CPU usage is low. After figuring out how to play videos with full hardware accelerated decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses and stutters during playback. Other apps like Mplayer, VLC and even gst-play-1.0 never have this problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 12:03:18 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1698270/+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 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low
Smoothness issue 4 above I have tracked down to this clutter-gtk code:
-
static void
clutter_master_clock_gdk_update (GdkFrameClock *frame_clock,
ClutterMasterClockGdk *master_clock)
{
GList *stages, *l;
_clutter_threads_acquire_lock ();
/* Get the time to use for this frame */
master_clock->cur_tick = gdk_frame_clock_get_frame_time (frame_clock);
-
The problem is not in clutter-gtk though. It's a general lack of
precision in the GdkFrameClock logic. Despite my monitor running at
around 60Hz, the GDK frame_time interval is erratic and mostly varies
between 17 and 18 milliseconds. So the root cause is just poor timing
logic in GDK.
I have an experimental fix already for gdk so probably don't need to
propose changes to clutter-gtk any more.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1698270
Title:
Totem pauses and stutters during video playback even when CPU usage is
low
Status in Totem:
Incomplete
Status in clutter-1.0 package in Ubuntu:
Won't Fix
Status in clutter-gtk package in Ubuntu:
New
Status in gstreamer package in Ubuntu:
Triaged
Status in gtk+3.0 package in Ubuntu:
In Progress
Status in totem package in Ubuntu:
Fix Released
Bug description:
Totem pauses and stutters during video playback even when CPU usage is
low.
After figuring out how to play videos with full hardware accelerated
decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
and stutters during playback. Other apps like Mplayer, VLC and even
gst-play-1.0 never have this problem.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: totem 3.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
ApportVersion: 2.20.5-0ubuntu4
Architecture: amd64
Date: Fri Jun 16 12:03:18 2017
InstallationDate: Installed on 2017-05-03 (44 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
SourcePackage: totem
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/totem/+bug/1698270/+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 1688663] Re: udev 97-hid2hci.rules missing usb id for logitech dinovo 2
Meaning that it is out :)
--
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/1688663
Title:
udev 97-hid2hci.rules missing usb id for logitech dinovo 2
Status in bluez package in Ubuntu:
Fix Released
Bug description:
Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech
dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor
after being installed using another keyboard and mouse.
In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech
devices:
# Logitech devices
KERNEL=="hiddev*", ATTRS{idVendor}=="046d",
ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"
# Logitech, Inc. diNovo Edge Keyboard
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"
lsusb shows in my computer:
Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless
Desktop
The id is almost equal (c714 <> c704). After adding a new line with
the missing id, the keyboard and mouse started to work:
# Logitech, Inc. diNovo 2
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"
I've also followed these other bugs to find out the file that I needed
to modify and that my keyboard needs hidraw instead of hiddev:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688663/+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 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Status: New => In Progress ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Medium ** Changed in: gtk+3.0 (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698270 Title: Totem pauses and stutters during video playback even when CPU usage is low Status in Totem: Incomplete Status in clutter-1.0 package in Ubuntu: Won't Fix Status in clutter-gtk package in Ubuntu: New Status in gstreamer package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: In Progress Status in totem package in Ubuntu: Fix Released Bug description: Totem pauses and stutters during video playback even when CPU usage is low. After figuring out how to play videos with full hardware accelerated decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses and stutters during playback. Other apps like Mplayer, VLC and even gst-play-1.0 never have this problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 12:03:18 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/1698270/+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 1688663] Re: udev 97-hid2hci.rules missing usb id for logitech dinovo 2
Shall be or was released? :)
--
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/1688663
Title:
udev 97-hid2hci.rules missing usb id for logitech dinovo 2
Status in bluez package in Ubuntu:
Fix Released
Bug description:
Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech
dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor
after being installed using another keyboard and mouse.
In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech
devices:
# Logitech devices
KERNEL=="hiddev*", ATTRS{idVendor}=="046d",
ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"
# Logitech, Inc. diNovo Edge Keyboard
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"
lsusb shows in my computer:
Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless
Desktop
The id is almost equal (c714 <> c704). After adding a new line with
the missing id, the keyboard and mouse started to work:
# Logitech, Inc. diNovo 2
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"
I've also followed these other bugs to find out the file that I needed
to modify and that my keyboard needs hidraw instead of hiddev:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688663/+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 1716884] [NEW] network-manager consume too much file descriptor and is not able to work correctly
Public bug reported: Detected when I failed to start a vpn client session. journalctl shows line like: sept. 13 10:37:29 xxx NetworkManager[1092]: [1505291849.7302] vpn-connection[0x2786800,4cd810de-c299-41e9-bf4b-c6df18d09b66,"xxx",0]: Could not launch the VPN service. error: Trop de fichiers ouverts. Indeed, /proc/$PID/fd is full of socket file descriptors. (with PID the pid of NetworkManager) "strace -e socket -p $PID -f" shows that a netlink socket is opened every 3s and never closed. [pid 9384] socket(PF_NETLINK, SOCK_RAW|SOCK_CLOEXEC, NETLINK_GENERIC) = 361 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Uname: Linux 4.11.0-14-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 13 11:12:05 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-06-23 (447 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160622) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1716884 Title: network-manager consume too much file descriptor and is not able to work correctly Status in network-manager package in Ubuntu: New Bug description: Detected when I failed to start a vpn client session. journalctl shows line like: sept. 13 10:37:29 xxx NetworkManager[1092]: [1505291849.7302] vpn-connection[0x2786800,4cd810de-c299-41e9-bf4b-c6df18d09b66,"xxx",0]: Could not launch the VPN service. error: Trop de fichiers ouverts. Indeed, /proc/$PID/fd is full of socket file descriptors. (with PID the pid of NetworkManager) "strace -e socket -p $PID -f" shows that a netlink socket is opened every 3s and never closed. [pid 9384] socket(PF_NETLINK, SOCK_RAW|SOCK_CLOEXEC, NETLINK_GENERIC) = 361 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Uname: Linux 4.11.0-14-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 13 11:12:05 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-06-23 (447 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160622) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1716884/+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 1688663] Re: udev 97-hid2hci.rules missing usb id for logitech dinovo 2
This shall be released
** Changed in: bluez (Ubuntu)
Status: New => Fix Released
--
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/1688663
Title:
udev 97-hid2hci.rules missing usb id for logitech dinovo 2
Status in bluez package in Ubuntu:
Fix Released
Bug description:
Trying to install kubuntu 16.04.2 (Xenial Xerus) today, the Logitech
dinovo 2 bluetooth keyboard and mouse didn't work, nor in live cd nor
after being installed using another keyboard and mouse.
In /lib/udev/rules.d/97-hid2hci.rules there are two lines for Logitech
devices:
# Logitech devices
KERNEL=="hiddev*", ATTRS{idVendor}=="046d",
ATTRS{idProduct}=="c70[345abce]|c71[3bc]", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"
# Logitech, Inc. diNovo Edge Keyboard
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c714", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"
lsusb shows in my computer:
Bus 001 Device 006: ID 046d:c704 Logitech, Inc. diNovo Wireless
Desktop
The id is almost equal (c714 <> c704). After adding a new line with
the missing id, the keyboard and mouse started to work:
# Logitech, Inc. diNovo 2
KERNEL=="hidraw*", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c704", \
RUN+="hid2hci --method=logitech-hid --devpath=%p"
I've also followed these other bugs to find out the file that I needed
to modify and that my keyboard needs hidraw instead of hiddev:
https://bugs.launchpad.net/ubuntu/+source/udev/+bug/872940
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/123920
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1688663/+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 1716601] Re: video decoders don't work correctly
Seems so. Sorry, didn't find it when filing the issue. Should be merged with 1716250 as the descriptions there are accurate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1716601 Title: video decoders don't work correctly Status in gstreamer1.0 package in Ubuntu: New Bug description: Playing videos sometimes just displays black images (audio coming in clearly) or with one colour channel missing (magenta tint mostly). Tried with several videos, there seems to be no pattern (avi as well as mpeg, different encoders). A significant amount of first calls (after waiting a period of minutes) brings up black (no video). Ubuntu 17.10 plain installation (with additional media support though) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.2-1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 10:03:44 2017 InstallationDate: Installed on 2017-09-05 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1716601/+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 1700930] Re: Default action policy for "Security Updates" changed between 14.04 and 16.04
So, errata. Turns out I was wrong too. I met @kirkland Dustin Kirkland at ubuncon-europe last week end and we talked about this. It turns out this change IS official policy and is advertised here: https://insights.ubuntu.com/2016/12/08/ubuntu-16-04-lts-security-a-comprehensive-overview/ https://wiki.ubuntu.com/Security/Features I still feel this was somewhat under reported and that the classic media sources that cover Ubuntu have dropped the ball big time but I can't fault Ubuntu for that so I'm closing this issue. I'll just have to remember to turn this off on any new install or mention it to the machine's owner and explain the possible consequences. ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Invalid -- 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/1700930 Title: Default action policy for "Security Updates" changed between 14.04 and 16.04 Status in unattended-upgrades package in Ubuntu: Invalid Bug description: In Ubuntu 14.04.5, the default policy under the "Updates" tab for "Security Updates" is set to "Display Immediately". In Ubuntu 16.04+, the default policy is now "Download and Install Immediately". I think this occurred due to the fix rolled out for bug #1554099. This has the following consequences: - Users may be denied apt lock when trying to install software because unattended-upgrades is running in the background. - If a shutdown is forced when the background update is running, users may be left with an unstable system - In case the update server is compromised and made to deliver malware, the blow to the userbase will be massive - From a PR standpoint, this moves away from the previous "your system won't ever do stuff without your permission" default policy. I'm of the opinion that the "Display Immediately" default should be rolled back. Failing that at least an official policy change announcement should be published so that users are made aware of this new default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1700930/+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 1716601] Re: video decoders don't work correctly
is that the same issue than bug #1716250? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1716601 Title: video decoders don't work correctly Status in gstreamer1.0 package in Ubuntu: New Bug description: Playing videos sometimes just displays black images (audio coming in clearly) or with one colour channel missing (magenta tint mostly). Tried with several videos, there seems to be no pattern (avi as well as mpeg, different encoders). A significant amount of first calls (after waiting a period of minutes) brings up black (no video). Ubuntu 17.10 plain installation (with additional media support though) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libgstreamer1.0-0 1.12.2-1 ProcVersionSignature: Ubuntu 4.13.0-10.11-generic 4.13.1 Uname: Linux 4.13.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 10:03:44 2017 InstallationDate: Installed on 2017-09-05 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1716601/+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 1716848] Re: package bluez 5.37-0ubuntu5.1 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1716848 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: Bluetooth no working in my laptop. Therefore, it's not possible to detect other devices or transfer archives. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Wed Sep 13 08:01:25 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-10 (520 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) InterestingModules: bnep bluetooth MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-93-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-03 (283 days ago) dmi.bios.date: 08/17/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.22 dmi.board.name: 30CC dmi.board.vendor: Quanta dmi.board.version: 79.1D dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd08/17/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.1D:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6500 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716848/+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 1716700] Re: "Please sync pulseaudio from debian Buster" where pulseaudio (11.0-1)
** Changed in: pulseaudio (Ubuntu) Importance: Medium => Wishlist -- 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/1716700 Title: "Please sync pulseaudio from debian Buster" where pulseaudio (11.0-1) Status in pulseaudio package in Ubuntu: Triaged Bug description: PulseAudio 11.0 release notes Changes at a glance Support for newer AirPlay hardware USB and bluetooth devices preferred over internal sound cards The default sink and source configuration is remembered better Bluetooth HSP headset role implemented Bluetooth HFP audio gateway role implemented (requires oFono) Bluetooth HSP audio gateway and HFP hands-free unit roles can be enabled simultaneously Upmixing can now be disabled without bad side effects Avoid having unavailable sinks or sources as the default Option to avoid resampling more often Option to automatically switch bluetooth profile to HSP more often Better latency regulation in module-loopback Changed module argument names in module-ladspa-sink and module-virtual-surround-sink Fixed input device handling on Windows Improved bluetooth MTU configuration (warning! this causes some hardware to not work any more, see the details below for how to fix it) GNU Hurd support Applications can request LADSPA or virtual surround filtering for their streams Support for 32-bit applications on 64-bit systems in padsp https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1716700/+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 1716848] [NEW] package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Bluetooth no working in my laptop. Therefore, it's not possible to detect other devices or transfer archives. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Wed Sep 13 08:01:25 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-10 (520 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) InterestingModules: bnep bluetooth MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-93-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-03 (283 days ago) dmi.bios.date: 08/17/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.22 dmi.board.name: 30CC dmi.board.vendor: Quanta dmi.board.version: 79.1D dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd08/17/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.1D:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6500 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard hciconfig: ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- 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/1716848 Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: New Bug description: Bluetooth no working in my laptop. Therefore, it's not possible to detect other devices or transfer archives. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 Date: Wed Sep 13 08:01:25 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-04-10 (520 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1) InterestingModules: bnep bluetooth MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-93-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: bluez Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-12-03 (283 days ago) dmi.bios.date: 08/17/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.22 dmi.board.name: 30CC dmi.board.vendor: Quanta dmi.board.version: 79.1D dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.22:bd08/17/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.1D:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6500 Notebook PC dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716848/+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 1682731] Re: package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1682731 Title: package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in bluez package in Ubuntu: Confirmed Bug description: passwd root ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bluez 5.43-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Apr 14 10:38:35 2017 DpkgHistoryLog: Start-Date: 2017-04-14 10:35:52 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-04-02 (12 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Micro-Star International Co., Ltd. CR61 2M/CX61 2OC/CX61 2OD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=f5a8ba7b-5759-4d4c-99a4-6cad4db08728 ro quiet splash RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: bluez Title: package bluez 5.43-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16GDIMS.20G dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16GD dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: CR61 2M/CX61 2OC/CX61 2OD dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16GDIMS.20G:bd01/18/2014:svnMicro-StarInternationalCo.,Ltd.:pnCR612M/CX612OC/CX612OD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GD:rvrREV1.0:cvnCR612M/CX612OC/CX612OD:ct10:cvrN/A: dmi.product.name: CR61 2M/CX61 2OC/CX61 2OD dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 54:27:1E:9E:18:49 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:1274 acl:0 sco:0 events:129 errors:0 TX bytes:25311 acl:0 sco:0 commands:129 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1682731/+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
