[Touch-packages] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)
backtrace by apport-retrace
crash buntu:/var/crash# apport-retrace --stdout
/var/crash/_usr_lib_xorg_Xorg.0.c
gpgv: Signature made Tue 01 Nov 2016 04:15:19 PM CST using RSA key ID A88984DC
gpgv: Can't check signature: public key not found
dpkg-source: warning: failed to verify signature on
./xorg-server_1.18.4-0ubuntu0.2.dsc
dpkg-source: info: extracting xorg-server in xorg-server-1.18.4
dpkg-source: info: unpacking xorg-server_1.18.4.orig.tar.gz
dpkg-source: info: applying xorg-server_1.18.4-0ubuntu0.2.diff.gz
dpkg-source: info: upstream files that have been modified:
xorg-server-1.18.4/.dir-locals.el
xorg-server-1.18.4/ChangeLog
xorg-server-1.18.4/config/dbus-api
xorg-server-1.18.4/damageext/damageext.h
xorg-server-1.18.4/doc/c-extensions
xorg-server-1.18.4/dri3/dri3int.h
xorg-server-1.18.4/fix-miregion
xorg-server-1.18.4/fix-miregion-private
xorg-server-1.18.4/fix-patch-whitespace
xorg-server-1.18.4/fix-region
xorg-server-1.18.4/hw/kdrive/Xkdrive.man
xorg-server-1.18.4/hw/kdrive/fbdev/Xfbdev.man
xorg-server-1.18.4/hw/xfree86/os-support/shared/platform_noop.c
xorg-server-1.18.4/hw/xquartz/GL/glcontextmodes.c
xorg-server-1.18.4/hw/xquartz/GL/glcontextmodes.h
xorg-server-1.18.4/hw/xwin/winclipboard/internal.h
xorg-server-1.18.4/xkb/XKM_file_format.txt
W: Can't drop privileges for downloading as file
'xorg-server_1.18.4-0ubuntu0.2.dsc' couldn't be accessed by user '_apt'. -
pkgAcquire::Run (13: Permission denied)
--- stack trace ---
#0 0x9220b528 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
_sys_result = 0
pd = 0x91fa7000
pid = 7478
selftid = 7478
#1 0x9220c9e0 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0xa6530de4,
sa_sigaction = 0xa6530de4}, sa_mask = {__val = {2676586395008836901,
2676586395008836901, 2594, 6730122966621824347, 32, 2910292295676945778,
18446744073709486080, 0, 18446744073709551360, 0, 4616194021471027200, 1024,
4616194021471028224, 0, 4616194021471028225, 4616194021471028225}}, sa_flags =
-1054354032, sa_restorer = 0xc122fa28 }
sigs = {__val = {32, 0 }}
#2 0xc122fa28 in OsAbort () at ../../os/utils.c:1408
No locals.
#3 0xc1116364 in ddxGiveUp (error=error@entry=EXIT_ERR_ABORT) at
../../../../hw/xfree86/common/xf86Init.c:1102
i =
#4 0xc111643c in AbortDDX (error=error@entry=EXIT_ERR_ABORT) at
../../../../hw/xfree86/common/xf86Init.c:1146
i =
#5 0xc12358e0 in AbortServer () at ../../os/log.c:874
No locals.
#6 0xc1236624 in FatalError (f=f@entry=0xc1266988 "Caught signal
%d (%s). Server aborting\n") at ../../os/log.c:1015
args = {__stack = 0xd085b680, __gr_top = 0xd085b680, __vr_top =
0xd085b640, __gr_offs = -56, __vr_offs = -128}
args2 = {__stack = 0xd085b680, __gr_top = 0xd085b680, __vr_top
= 0xd085b640, __gr_offs = -56, __vr_offs = -128}
beenhere = 1
#7 0xc122d294 in OsSigHandler (signo=11, sip=0xd085b6a0,
unused=) at ../../os/osinit.c:150
unused =
sip = 0xd085b6a0
signo = 11
#8
No symbol table info available.
#9 0xc1192254 in RRSetChanged (pScreen=) at
../../randr/randr.c:562
master =
mastersp = 0x0
#10 0xc119654c in RRScreenSetSizeRange
(pScreen=pScreen@entry=0xaaab00cd7860, minWidth=,
minHeight=, maxWidth=, maxHeight=)
at ../../randr/rrinfo.c:228
No locals.
#11 0xc11510d4 in xf86RandR12CreateScreenResources12
(pScreen=0xaaab00cd7860) at ../../../../hw/xfree86/modes/xf86RandR12.c:1649
c =
pScrn =
config = 0xaaab00d02f50
#12 xf86RandR12CreateScreenResources (pScreen=pScreen@entry=0xaaab00cd7860) at
../../../../hw/xfree86/modes/xf86RandR12.c:833
pScrn = 0xaaab00cd0fd0
config =
c =
width =
height =
mmWidth =
mmHeight =
#13 0xc1144bbc in xf86CrtcCreateScreenResources (screen=0xaaab00cd7860)
at ../../../../hw/xfree86/modes/xf86Crtc.c:719
screen = 0xaaab00cd7860
scrn =
#14 0xc10d5cf0 in dix_main (argc=1, argv=0xd085cbb8,
envp=) at ../../dix/main.c:215
pScreen = 0xaaab00cd7860
i = 0
alwaysCheckForInput = {0, 1}
#15 0x921f98a0 in __libc_start_main (main=0x0, argc=0, argv=0x0,
init=, fini=, rtld_fini=,
stack_end=) at libc-start.c:291
self =
result =
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {187650361516128, 0, 0, 0,
0, 0, 0, 0, 0, 0, 281474180172400, 3655814494272476266, 129,
3655814493156378226, 0, 0, 0, 0, 0, 0, 0, 0}, mask_was_saved = 0}}, priv = {pad
= {0x0, 0x0, 0xc127d120, 0xc10bfce8 <_start+52>}, data = {prev = 0x0,
cleanup = 0x0, canceltype = -1054355168}}}
not_first_call =
#16 0xc10bfce8 in _start ()
No symbol table info available.
Backtrace stopped: previous frame i
[Touch-packages] [Bug 1692437] [NEW] Monitors on second GPU not working after upgrade to zesty
Public bug reported: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+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 1692437] Re: Monitors on second GPU not working after upgrade to zesty
** Attachment added: "lshw output" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/4881175/+files/lshw.txt -- 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/1692437 Title: Monitors on second GPU not working after upgrade to zesty Status in lightdm package in Ubuntu: New Bug description: I'm not 100% sure this is the right package to file the bug against, but since upgrading to zesty the two monitors on my second GPU are no longer detected once I reach the greeter screen at login time. However, both of them display information during boot. Let me know how I can narrow down the bug report. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: lightdm 1.22.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Mon May 22 01:42:58 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-29 (388 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: lightdm UpgradeStatus: Upgraded to zesty on 2017-05-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
Lev: The problem you describe in comment #69 sounds like it might be fixed by this (which is missing from xenial AFAIK): https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/service.c?id=2e2edc36a91d6a8f2c65d793273df28a166d6bed -- 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/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1594902] Re: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit
ChristianEhrhardt (paelzer) and John Johansen (jjohansen), I tried your sha1sum checks and all looks good, but the problem still persists. Nothing suggested in this bug reports works for me. Luckily, on my system where it fails, I do not make use of libvirt; this issue is just an annoying error message when I upgrade my system. My server does not suffer from this problem; wonder why only some system suffer from this problem suddenly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1594902 Title: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit Status in apparmor package in Ubuntu: Confirmed Status in libvirt package in Ubuntu: Confirmed Bug description: Output from 'apt-get upgrade': Setting up libvirt-bin (1.3.1-1ubuntu10.1) ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'screen-cleanup' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `screen-cleanup' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `screen-cleanup' initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused insserv: warning: script 'binfmt-support' missing LSB tags and overrides insserv: Default-Start undefined, assuming empty start runlevel(s) for script `binfmt-support' insserv: Default-Stop undefined, assuming empty stop runlevel(s) for script `binfmt-support' Job for libvirt-bin.service failed because the control process exited with error code. See "systemctl status libvirt-bin.service" and "journalctl -xe" for details. invoke-rc.d: initscript libvirt-bin, action "restart" failed. dpkg: error processing package libvirt-bin (--configure): subprocess installed post-installation script returned error exit status 1 E: Sub-process /usr/bin/dpkg returned an error code (1) Output from 'systemctl status libvirt-bin.service': ● libvirt-bin.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor preset: enabled) Active: inactive (dead) (Result: exit-code) since Tue 2016-06-21 17:55:16 BST; 4min 52s ago Docs: man:libvirtd(8) http://libvirt.org Process: 2984 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, status=6) Main PID: 2984 (code=exited, status=6) Jun 21 17:55:15 lydia systemd[1]: Failed to start Virtualization daemon. Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Unit entered failed state. Jun 21 17:55:15 lydia systemd[1]: libvirt-bin.service: Failed with result 'exit-code'. Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Service hold-off time over, scheduling restart. Jun 21 17:55:16 lydia systemd[1]: Stopped Virtualization daemon. Jun 21 17:55:16 lydia systemd[1]: libvirt-bin.service: Start request repeated too quickly. Jun 21 17:55:16 lydia systemd[1]: Failed to start Virtualization daemon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1594902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help
[Touch-packages] [Bug 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
** Tags added: a2dp -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first --- I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1582213/+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 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
** Tags added: a2dp -- 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/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+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 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)
** Summary changed: - [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety + [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) ** Tags added: a2dp -- 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/1438510 Title: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1362313] Re: a2dp bluetooth music playback broken after bluetooth device reconnect
** Tags added: a2dp ** Summary changed: - a2dp bluetooth music playback broken after bluetooth device reconnect + PulseAudio can't find Bluetooth device after reconnecting ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: 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/1362313 Title: PulseAudio can't find Bluetooth device after reconnecting Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: What happens? 1. connct a2dp device 2. start playback 3. reconnect a2dp device from remote 4. ubuntu reports device is connected 5. a2dp device does not show up in pulseaudio nor does music playback work (via a2dp device). sometimes there are "timeout" error messages in kde. 6. try to reconnect from ubuntu, restart bluetooth daemon, restart pulseaudio daemon. it all does not help. 7. what does help is restarting 1. dbus 2. bluetooth and 3. pulseaudio then connect the device (if not already auto-connected) After step 3, there is the following error message in syslog (no other errors in syslog or dmesg): pulseaudio[7812]: [bluetooth] bluetooth-util.c: Failed to release transport /org/bluez/7791/hci0/dev_C8_84_47_10_24_A2/fd2: Method "Release" with signature "s" on interface "org.bluez.MediaTransport" doesn't exist What I expected to happen? After the device reconnect, the music playback switches playback back to the bluetooth device. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Wed Aug 27 21:41:34 2014 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/linux64-root64 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-06-18 (70 days ago) dmi.bios.date: 12/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: B85 Pro4 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.:bvrP2.00:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85Pro4: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. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 00:02:72:CC:E6:D5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:100536 acl:18 sco:0 events:14179 errors:0 TX bytes:24059553 acl:28186 sco:0 commands:77 errors:0 syslog: Aug 27 20:46:20 charlie bluetoothd[1538]: /org/bluez/1538/hci0/dev_C8_84_47_10_24_A2/fd0: fd(25) ready To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1362313/+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 1692448] [NEW] Bluetooth speaker fails to reconnect when turned on (but it tries)
Public bug reported: Bluetooth speaker fails to reconnect when turned on. Watching the Bluetooth icon in the Unity panel I can see it is trying (B icon briefly gets the expected padlock and then loses it). The speaker doesn't reconnect then unless initiated by the laptop (set Connection = ON in the panel). Sounds like of like this (which is fixed in newer releases than xenial, but not in xenial): https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/service.c?id=2e2edc36a91d6a8f2c65d793273df28a166d6bed Note this bug is only about the Bluetooth connection, and not about audio problems (of which there are a few). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 16:28:37 2017 InstallationDate: Installed on 2017-05-19 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20CM0010AU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic.efi.signed root=UUID=ae0f1ee2-ca1c-4a64-985f-b27f9a8c0e50 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET45W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CM0010AU dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET45W(1.24):bd09/05/2016:svnLENOVO:pn20CM0010AU:pvrThinkPadX250:rvnLENOVO:rn20CM0010AU:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CM0010AU dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 34:02:86:EE:0F:47 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:1298997 acl:147 sco:25046 events:1846 errors:0 TX bytes:1750802 acl:1411 sco:18166 commands:299 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1692448 Title: Bluetooth speaker fails to reconnect when turned on (but it tries) Status in bluez package in Ubuntu: New Bug description: Bluetooth speaker fails to reconnect when turned on. Watching the Bluetooth icon in the Unity panel I can see it is trying (B icon briefly gets the expected padlock and then loses it). The speaker doesn't reconnect then unless initiated by the laptop (set Connection = ON in the panel). Sounds like of like this (which is fixed in newer releases than xenial, but not in xenial): https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/service.c?id=2e2edc36a91d6a8f2c65d793273df28a166d6bed Note this bug is only about the Bluetooth connection, and not about audio problems (of which there are a few). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 16:28:37 2017 InstallationDate: Installed on 2017-05-19 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20CM0010AU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic.efi.signed root=UUID=ae0f1ee2-ca1c-4a64-985f-b27f9a8c0e50 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET45W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CM0010AU dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET45W(1.24):bd09/05/2016:svnLENOVO:pn20CM0010AU:pvrThinkPadX250:rvnLENOVO:rn20CM0010AU:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CM0010AU dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 34:02:86:EE:0F:47 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING RX bytes:1298997 acl:147 sco:25046 events:1846 errors:0 TX bytes:1750802 acl:1411 sco:18166 commands:299 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1692448/+subscriptions -- Mailing list: https://la
[Touch-packages] [Bug 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()
** Information type changed from Private Security to Public Security -- 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/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: New Bug description: This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()
** Tags added: patch -- 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/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: New Bug description: This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1692454] [NEW] [ENS1371 - Ensoniq AudioPCI, playback] No sound at all
Public bug reported: no audio at all ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hariharan 1985 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon May 22 14:08:44 2017 InstallationDate: Installed on 2017-05-17 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI successful Symptom_Card: ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) - Ensoniq AudioPCI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hariharan 1985 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1692454 Title: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all Status in pulseaudio package in Ubuntu: New Bug description: no audio at all ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: pulseaudio 1:10.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hariharan 1985 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Mon May 22 14:08:44 2017 InstallationDate: Installed on 2017-05-17 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:AudioPCI successful Symptom_Card: ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) - Ensoniq AudioPCI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hariharan 1985 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [ENS1371 - Ensoniq AudioPCI, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1692454/+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 1582213] Re: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first
Confirmed on xenial, exactly how hife describes it. -- 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/1582213 Title: [xenial] Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Bluetooth device doesn't play any sound in A2DP mode unless set to HSP/HFP first --- I have a Sennheiser MM 450-X headset. In 15.10, connection & playback was straightforward. In 16.04, the headset connects, and shows up as default playback device on `pavucontrol`, but there is no sound. A functional workaround is to, after having connected it, to go the `Configuration` tab, and in the `Profile` dropdown, to choose `... HSP/HFP`, which will make them play as expected (but in low quality), then switch to `... A2DP Sink` (they will play in high quality). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio-module-bluetooth 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: myuser2936 F pulseaudio /dev/snd/controlC2: myuser2936 F pulseaudio /dev/snd/controlC0: myuser2936 F pulseaudio Date: Mon May 16 14:18:58 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-03-11 (66 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XN-WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd04/22/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1582213/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Changed in: aptdaemon Assignee: (unassigned) => aden iwa rante (radeniw) ** Changed in: debconf (Ubuntu) Status: Triaged => New ** Changed in: aptdaemon (Ubuntu) Status: Triaged => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Confirmed Status in Debconf: New Status in aptdaemon package in Ubuntu: New Status in debconf package in Ubuntu: New Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1692448] Re: Bluetooth speaker fails to reconnect when turned on (but it tries)
** Description changed: Bluetooth speaker fails to reconnect when turned on. Watching the Bluetooth icon in the Unity panel I can see it is trying (B icon briefly gets the expected padlock and then loses it). The speaker doesn't reconnect then unless initiated by the laptop (set Connection = ON in the panel). - Sounds like of like this (which is fixed in newer releases than xenial, but not in xenial): + Sounds kind of like this (which is fixed in newer releases than xenial, but not in xenial): https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/service.c?id=2e2edc36a91d6a8f2c65d793273df28a166d6bed Note this bug is only about the Bluetooth connection, and not about audio problems (of which there are a few). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 16:28:37 2017 InstallationDate: Installed on 2017-05-19 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20CM0010AU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic.efi.signed root=UUID=ae0f1ee2-ca1c-4a64-985f-b27f9a8c0e50 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET45W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CM0010AU dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET45W(1.24):bd09/05/2016:svnLENOVO:pn20CM0010AU:pvrThinkPadX250:rvnLENOVO:rn20CM0010AU:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CM0010AU dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO hciconfig: - hci0:Type: BR/EDR Bus: USB - BD Address: 34:02:86:EE:0F:47 ACL MTU: 1021:5 SCO MTU: 96:6 - UP RUNNING - RX bytes:1298997 acl:147 sco:25046 events:1846 errors:0 - TX bytes:1750802 acl:1411 sco:18166 commands:299 errors:0 + hci0:Type: BR/EDR Bus: USB + BD Address: 34:02:86:EE:0F:47 ACL MTU: 1021:5 SCO MTU: 96:6 + UP RUNNING + RX bytes:1298997 acl:147 sco:25046 events:1846 errors:0 + TX bytes:1750802 acl:1411 sco:18166 commands:299 errors:0 -- 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/1692448 Title: Bluetooth speaker fails to reconnect when turned on (but it tries) Status in bluez package in Ubuntu: New Bug description: Bluetooth speaker fails to reconnect when turned on. Watching the Bluetooth icon in the Unity panel I can see it is trying (B icon briefly gets the expected padlock and then loses it). The speaker doesn't reconnect then unless initiated by the laptop (set Connection = ON in the panel). Sounds kind of like this (which is fixed in newer releases than xenial, but not in xenial): https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/src/service.c?id=2e2edc36a91d6a8f2c65d793273df28a166d6bed Note this bug is only about the Bluetooth connection, and not about audio problems (of which there are a few). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 16:28:37 2017 InstallationDate: Installed on 2017-05-19 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20CM0010AU ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-generic.efi.signed root=UUID=ae0f1ee2-ca1c-4a64-985f-b27f9a8c0e50 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET45W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CM0010AU dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET45W(1.24):bd09/05/2016:svnLENOVO:pn20CM0010AU:pvrThinkPadX250:rvnLENOVO:rn20CM0010AU:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CM0010AU dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 34:02:86:EE:0F:47 ACL MTU: 1021
[Touch-packages] [Bug 1692474] [NEW] Sound settings don't remember my preferred audio output device
Public bug reported: Sound settings don't remember my preferred audio output device. Every time I (manage to) connect a bluetooth audio device, the default output remains the built-in PC speaker. Same when I connect USB audio devices... Ubuntu sticks to the built-in speakers until manually set otherwise. This is a bug rather than opinion because there are at least three ways that Ubuntu could be better prioritizing audio devices: 1. Prefer what the user manually selected last; or 2. Prefer what the user dragged to the top of the list (a missing feature, but nice idea); or 3. Prefer what audio device appeared in the list most recently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-control-center (not installed) ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 17:23:59 2017 InstallationDate: Installed on 2017-05-19 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1692474 Title: Sound settings don't remember my preferred audio output device Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Sound settings don't remember my preferred audio output device. Every time I (manage to) connect a bluetooth audio device, the default output remains the built-in PC speaker. Same when I connect USB audio devices... Ubuntu sticks to the built-in speakers until manually set otherwise. This is a bug rather than opinion because there are at least three ways that Ubuntu could be better prioritizing audio devices: 1. Prefer what the user manually selected last; or 2. Prefer what the user dragged to the top of the list (a missing feature, but nice idea); or 3. Prefer what audio device appeared in the list most recently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-control-center (not installed) ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 17:23:59 2017 InstallationDate: Installed on 2017-05-19 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1692474/+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 1692474] Re: Sound settings don't remember my preferred audio output device
** Package changed: gnome-control-center (Ubuntu) => unity-control- center (Ubuntu) ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1692474 Title: Sound settings don't remember my preferred audio output device Status in gnome-control-center package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in unity-control-center package in Ubuntu: New Bug description: Sound settings don't remember my preferred audio output device. Every time I (manage to) connect a bluetooth audio device, the default output remains the built-in PC speaker. Same when I connect USB audio devices... Ubuntu sticks to the built-in speakers until manually set otherwise. This is a bug rather than opinion because there are at least three ways that Ubuntu could be better prioritizing audio devices: 1. Prefer what the user manually selected last; or 2. Prefer what the user dragged to the top of the list (a missing feature, but nice idea); or 3. Prefer what audio device appeared in the list most recently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-control-center (not installed) ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 17:23:59 2017 InstallationDate: Installed on 2017-05-19 (2 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1692474/+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 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()
** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: New Bug description: This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1672499] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf
** Changed in: systemd (Ubuntu Zesty) Status: New => Confirmed ** Changed in: systemd (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Zesty) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu Zesty) Milestone: None => zesty-updates -- 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/1672499 Title: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Confirmed Status in systemd source package in Artful: Fix Released Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz root-unittests fails: -> Unit a.service: Description: a.service Instance: n/a Unit Load State: not-found Unit Active State: inactive State Change Timestamp: n/a Inactive Exit Timestamp: n/a Active Enter Timestamp: n/a Activeerror: org.freedesktop.systemd1.NoSuchUnit: Unit c.service not found. Assertion 'r == 0' failed at ../src/test/test-engine.c:62, function main(). Aborting. Exit Timestamp: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672499/+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 1682154] Re: loginctl ignoring user given sessions IDs at command-line
Just did a release to artful; I will do this one in the next update after this one. ** Changed in: systemd (Ubuntu) Milestone: None => ubuntu-17.06 ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu Zesty) Milestone: None => zesty-updates ** Changed in: systemd (Ubuntu Zesty) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- 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/1682154 Title: loginctl ignoring user given sessions IDs at command-line Status in systemd: New Status in systemd package in Ubuntu: Triaged Status in systemd source package in Zesty: Triaged Bug description: Kubuntu zesty, 232-21ubuntu2 See upstream bug https://github.com/systemd/systemd/issues/5733 with patch attached. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1682154/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
Remove zesty task; added xenial task. ** Changed in: systemd (Ubuntu) Milestone: ubuntu-17.04 => ubuntu-17.06 ** Changed in: systemd (Ubuntu Zesty) Milestone: ubuntu-17.04 => zesty-updates ** Also affects: landscape-client (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: systemd (Ubuntu Zesty) ** Changed in: systemd (Ubuntu Xenial) Milestone: None => ubuntu-16.04.3 ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => High ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed ** No longer affects: landscape-client (Ubuntu Zesty) -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in landscape-client source package in Xenial: New Status in systemd source package in Xenial: Confirmed Bug description: Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release * Apply * Wait 2 hours * Alert comes in a seperate Landscape message Machine is ready for reboot * Choose Info... Power * Deliver to selected computers as soon as possible * Error message I found this thread on reddit about this issue maybe the solution can be built into the upgrade script https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1672499] Re: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf
** Changed in: systemd (Ubuntu Zesty) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1672499 Title: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Zesty: Fix Committed Status in systemd source package in Artful: Fix Released Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz root-unittests fails: -> Unit a.service: Description: a.service Instance: n/a Unit Load State: not-found Unit Active State: inactive State Change Timestamp: n/a Inactive Exit Timestamp: n/a Active Enter Timestamp: n/a Activeerror: org.freedesktop.systemd1.NoSuchUnit: Unit c.service not found. Assertion 'r == 0' failed at ../src/test/test-engine.c:62, function main(). Aborting. Exit Timestamp: n/a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672499/+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 1686361] Re: systemd does not respect nofile ulimit when running in container
** Changed in: systemd (Ubuntu Zesty) Status: New => Fix Committed ** Changed in: systemd (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Zesty) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu Zesty) Milestone: None => zesty-updates -- 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/1686361 Title: systemd does not respect nofile ulimit when running in container Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: Fix Committed Status in systemd source package in Artful: Fix Released Bug description: When systemd currently starts in a container that has RLIMIT_NOFILE set to e.g. 10 systemd will lower it to 65536 since this value is hard-coded into systemd. I've pushed a patch to systemd upstream that will try to set the nofile limit to the allowed kernel maximum. If this fails, it will compute the minimum of the current set value (the limit that is set on the container) and the maximum value as soft limit and the currently set maximum value as the maximum value. This way it retains the limit set on the container. It would be great if we could backport this patch to have system adhere to nofile limits set for the container. This is especially important since user namespaces will allow you to lower the limit but not raise it back up afterwards. The upstream patch is appended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686361/+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 1383470] Re: scp does not work (fails at 'Sending command scp -v -t')
It's still an issue because there is some network failure that is not timeouted correctly. But I cannot provide steps to reproduce it because I don't yet know how to identify what exactly is wrong. Looks like it's a hosting-side issue because I've tried connecting from completely different locations and the issue persists. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1383470 Title: scp does not work (fails at 'Sending command scp -v -t') Status in openssh package in Ubuntu: Incomplete Bug description: Following the last update of Ubuntu 14.02, scp (in the default system) has ceased working. It hangs after authentication at the point where it wold start an interactive session. I've verified that the problem is in my system: scp still works at the target machine and scp won't work on my machine to various hosts. Output below. rasmith@rasmith-Lemur-Ultra:~$ scp -v testfil apacentral.org: Executing: program /usr/bin/ssh host apacentral.org, user (unspecified), command scp -v -t . OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /home/rasmith/.ssh/config debug1: /home/rasmith/.ssh/config line 17: Applying options for * debug1: /home/rasmith/.ssh/config line 20: Deprecated option "rhostsauthentication" debug1: /home/rasmith/.ssh/config line 25: Deprecated option "fallbacktorsh" debug1: /home/rasmith/.ssh/config line 26: Deprecated option "usersh" debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to apacentral.org [65.19.130.61] port 22. debug1: Connection established. debug1: could not open key file '/etc/ssh/ssh_host_key': No such file or directory debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such file or directory debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such file or directory debug1: identity file /home/rasmith/.ssh/identity type 0 debug1: identity file /home/rasmith/.ssh/identity-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.4_hpn13v11 FreeBSD-2013 debug1: match: OpenSSH_6.4_hpn13v11 FreeBSD-2013 pat OpenSSH* compat 0x0400 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5-...@openssh.com none debug1: kex: client->server aes128-ctr hmac-md5-...@openssh.com none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: RSA 61:40:9f:26:85:d2:57:34:f9:52:7b:c3:47:9d:7a:ae debug1: Host 'apacentral.org' is known and matches the RSA host key. debug1: Found key in /home/rasmith/.ssh/known_hosts:26 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering DSA public key: rasm...@aristotle.tamu.edu debug1: Server accepts key: pkalg ssh-dss blen 433 debug1: Authentication succeeded (publickey). Authenticated to apacentral.org ([65.19.130.61]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: Sending command: scp -v -t . (at this point, the command hangs more or less indefinitely until killed with Ctrl-C) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ssh 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 20 15:25:14 2014 InstallationDate: Installed on 2012-10-18 (732 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: Upgraded to trusty on 2014-05-02 (170 days ago) To manage notification
[Touch-packages] [Bug 1686784] Re: no predictable names for platform (non-PCI) NICs
** Description changed: [Impact] Systems may have NICs attached to the "platform" bus. These are NICs that are onboard, but not attached to a PCI(-like) bus. Rather, they are described by firmware directly. None of the naming policies enabled by Ubuntu by default matches these NICs, so they end up having unpredictable names. In the case where other NICs are attached (e.g. PCIe cards), the ethN enumeration race occurs, making it impossible to have an interface name that is persistent across reboots. That is, if you do a network install over "eth0", on reboot that NIC now maybe "eth3", which causes it to fail to start the network on boot. The HiSilicon D05 boards are an example of this. It has 4 onboard NICs that are described by ACPI directly, and may also have other PCIe NICs plugged in. [Test Case] Boot a system with the characteristics described above, and check to see if any "ethN" interfaces exist. [Regression Risk] - TBD - depends on the proposed solution. + Unless one fixed the names locally with .netlink / .rules files the interface names will change for the ACPI/platform bus network interfaces, from random ethX names to stable names named like enaVENDORMODELiX. Thus we should check that this update doesn't negatively break certified ARM64 platforms with: ARM, NVIDIA, HISILICON platform bus ethernet devices. ** Changed in: systemd (Ubuntu Zesty) Status: New => Fix Committed ** Changed in: systemd (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Zesty) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu Zesty) Milestone: None => zesty-updates -- 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/1686784 Title: no predictable names for platform (non-PCI) NICs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: Fix Committed Bug description: [Impact] Systems may have NICs attached to the "platform" bus. These are NICs that are onboard, but not attached to a PCI(-like) bus. Rather, they are described by firmware directly. None of the naming policies enabled by Ubuntu by default matches these NICs, so they end up having unpredictable names. In the case where other NICs are attached (e.g. PCIe cards), the ethN enumeration race occurs, making it impossible to have an interface name that is persistent across reboots. That is, if you do a network install over "eth0", on reboot that NIC now maybe "eth3", which causes it to fail to start the network on boot. The HiSilicon D05 boards are an example of this. It has 4 onboard NICs that are described by ACPI directly, and may also have other PCIe NICs plugged in. [Test Case] Boot a system with the characteristics described above, and check to see if any "ethN" interfaces exist. [Regression Risk] Unless one fixed the names locally with .netlink / .rules files the interface names will change for the ACPI/platform bus network interfaces, from random ethX names to stable names named like enaVENDORMODELiX. Thus we should check that this update doesn't negatively break certified ARM64 platforms with: ARM, NVIDIA, HISILICON platform bus ethernet devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686784/+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 1629226] Re: systemd's service killed by cgroup controller pids
** Changed in: bash (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1629226
Title:
systemd's service killed by cgroup controller pids
Status in The Ubuntu-power-systems project:
New
Status in bash package in Ubuntu:
In Progress
Bug description:
Problem Description
===
I write a simple systemd service which will fork child processes fiercely.
But quickly the service failed:
% sudo systemctl status reproducer.service
? reproducer.service - Reproducer of systemd services killed by ips
Loaded: loaded (/etc/systemd/system/reproducer.service; disabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Fri 2016-03-18 06:58:37 CDT; 2min
43s ago
Process: 5103 ExecStart=/home/hpt/reproducer/reproducer.sh (code=exited,
status=0/SUCCESS)
Main PID: 5105 (code=exited, status=254)
Mar 18 06:58:36 pinelp3 reproducer.sh[5103]:
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
Mar 18 06:58:36 pinelp3 reproducer.sh[5103]:
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
Mar 18 06:58:37 pinelp3 reproducer.sh[5103]:
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
Mar 18 06:58:37 pinelp3 reproducer.sh[5103]:
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
Mar 18 06:58:37 pinelp3 reproducer.sh[5103]:
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
Mar 18 06:58:37 pinelp3 reproducer.sh[5103]:
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Main process exited,
code=exited, status=254/n/a
Mar 18 06:58:37 pinelp3 reproducer.sh[5103]:
/home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable
Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Unit entered failed
state.
Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Failed with result
'exit-code'.
The default task limit of systemd services is 512. Looks like the
service is terminated by the kernel's ips cgroup controller. I think
this isn't correct. Child processes cannot be forked shouldn't cause
parent to die.
% cat /etc/systemd/system/reproducer.service
[Unit]
Description=Reproducer of systemd services killed by ips
After=multi-user.target
[Service]
ExecStart=/home/hpt/reproducer/reproducer.sh
Type=forking
[Install]
WantedBy=multi-user.target
% cat /home/hpt/reproducer/reproducer.sh
#!/bin/bash
foo()
{
#exec sh -c "echo $1: \$\$;sleep 60"
echo $1:
sleep 60
}
bar()
{
c=1
while true
do
for ((i=1;i<=2048;i++))
do
foo $c &
((c++))
done
wait
c=1
done
}
# main
bar &
disown -a
exit 0
---uname output---
Linux pinelp3 4.4.0-12-generic #28-Ubuntu SMP Wed Mar 9 00:40:38 UTC 2016
ppc64le ppc64le ppc64le GNU/Linux
Machine Type = IBM,8408-E8E,lpar
Steps to Reproduce
1. install the simple service in "Problem description"
2. sudo systemctl start reproducer.service
3. wait 2~3 minutes
== Comment: #3 - Vaishnavi Bhat - 2016-03-22 11:21:55 ==
From the machine,
root@pinelp3:~# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 48192
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size(512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 48192
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
root@pinelp3:~# ps aux | wc -l ->While the service is
running
1084
root@pinelp3:~# ps aux | wc -l "
1084
root@pinelp3:~# ps aux | wc -l "
1084
root@pinelp3:~# ps aux | wc -l "
1084
root@pinelp3:~# ps aux | wc -l-->While the service is not
running.
572
root@pinelp3:~# free -m --> While service is running
totalusedfree shared buff/cache
available
Mem: 12117 628 459 22 11029
9541
Swap:
[Touch-packages] [Bug 997331] Re: Some alsa applications play bad sound
Same bug here on a 16.04, agw3's workaround doesn't fix the issue for me. It occurs when my browser (firefox 53.0.2 64b) display a google research with google translate content. The way I fix it is: pulseaudio -k && sudo alsa force-reload It's a bit annoying, I would like to fix it permanently. -- 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/997331 Title: Some alsa applications play bad sound Status in pulseaudio package in Ubuntu: Incomplete Bug description: Some applications using ALSA plays bad sound. One is WINE applications. Winecfg test sound is distorted (sounds awful). Spotify running WINE plays songs way too fast. A flash based program play distorted sound. The common thing for all of them is that under Applications in Sound settings it says alsa-plugin and it flashes very rapidly between "No application is currently playing" and alsa-plugin. It almost looks like flickering. I've testet a normal wave file using aplay and that was okey, no problems. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: oeriksen 3299 F pulseaudio /dev/snd/controlC0: oeriksen 3299 F pulseaudio /dev/snd/controlC1: oeriksen 3299 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xfa40 irq 60' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,10438410,00100302' Controls : 41 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'Socialize'/'Creative Labs VF0640 Live! Cam Socialize at usb-:00:1d.0-1.4, high speed' Mixer name : 'USB Mixer' Components : 'USB041e:4083' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 48 Mono: Capture 45 [94%] [18.00dB] [on] Card2.Amixer.info: Card hw:2 'NVidia'/'HDA NVidia at 0xfa08 irq 17' Mixer name : 'Nvidia GPU 16 HDMI/DP' Components : 'HDA:10de0016,10de0101,00100100' Controls : 24 Simple ctrls : 4 Date: Wed May 9 22:41:04 2012 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [System Product Name, Realtek ALC892, Green Line Out, Rear] Playback problem UpgradeStatus: Upgraded to precise on 2012-03-02 (68 days ago) dmi.bios.date: 02/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8P67 REV 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2302:bd02/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8P67REV3.1:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/997331/+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 1687981] Re: Backport packages for 16.04.3 HWE stack
About Vulkan package: Vulkan loader (libvulkan) has moved to newer version and that is needed to make use of all the recently proposed vulkan extensions in the application. The main application that doesn't work currently is with Vulkan CTS: https://github.com/KhronosGroup/VK-GL-CTS Vulkan CTS passing is required for a device to be called as Vulkan compatible. We support only LTS releases on our devices so need latest version on 16.04. Can you please upgrade the libvulkan.so version to 1.0.42 for Xenial? This version is already available for latest ubuntu version (17.04). Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1687981 Title: Backport packages for 16.04.3 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in libinput package in Ubuntu: Invalid Status in libwacom package in Ubuntu: Invalid Status in libxfont package in Ubuntu: Invalid Status in libxfont2 package in Ubuntu: Invalid Status in llvm-toolchain-4.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: New Status in vulkan package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in x11proto-core package in Ubuntu: Invalid Status in xfonts-utils package in Ubuntu: New Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: New Status in libdrm source package in Xenial: New Status in libinput source package in Xenial: New Status in libwacom source package in Xenial: New Status in libxfont source package in Xenial: Fix Committed Status in libxfont2 source package in Xenial: Fix Committed Status in llvm-toolchain-4.0 source package in Xenial: New Status in mesa source package in Xenial: New Status in vulkan source package in Xenial: New Status in wayland source package in Xenial: New Status in x11proto-core source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.3 *** Revert changes to use debhelper10. xorg-server-hwe-16.04 needs updates - wayland 1.11 (but zesty has 1.12 which mesa needs so backport that) - x11proto-core 7.0.31 - libxfont-dev 2.0.1, which also means backporting libxfont1 (NEW) x-x-i-libinput will not replace -evdev in x-x-i-all-hwe-16.04 because the unity mouse config doesn't work with -libinput. x-x-i-libinput needs newer libinput, which in turn needs libwacom update. Mesa needs llvm-4.0 and libclc, libdrm, wayland updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] zesty hasn't blown up [Other information] build order: 1. x11proto-core, libdrm, libxfont, libxfont1, libwacom, llvm-toolchain-4.0, vulkan, wayland 2. libclc, libinput, xorg-server (build-dep libxfont1-dev) 3. mesa, xorg-server-hwe-16.04 4. drivers 5. xorg-hwe-16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1687981/+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 1692494] Re: klibc does not support reboot arguments
** Patch added: "add-reboot-argument-support.patch" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+attachment/4881283/+files/add-reboot-argument-support.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1692494 Title: klibc does not support reboot arguments Status in klibc package in Ubuntu: New Bug description: ... so we cannot do things like "reboot recovery" in devices that follow the Android partitions conventions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+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 1692496] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: after cancel download ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Mon May 22 12:51:01 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-18 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1692496 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: after cancel download ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Mon May 22 12:51:01 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-18 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1692496/+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 1692494] [NEW] klibc does not support reboot arguments
Public bug reported: ... so we cannot do things like "reboot recovery" in devices that follow the Android partitions conventions. ** Affects: klibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1692494 Title: klibc does not support reboot arguments Status in klibc package in Ubuntu: New Bug description: ... so we cannot do things like "reboot recovery" in devices that follow the Android partitions conventions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+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 1692492] [NEW] package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported:
No further information to provide, this bug report was submitted
automatically.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.6
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri May 19 08:43:02 2017
ErrorMessage: subprocess installed post-installation script returned error exit
status 1
InstallationDate: Installed on 2016-09-08 (255 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
PackageArchitecture: all
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.2
apt 1.2.20
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::AutocleanInterval "7";
APT::Periodic::Unattended-Upgrade "1";
modified.conffile..etc.apt.apt.conf.d.99update-notifier:
#DPkg::Post-Invoke {"if [ -d /var/lib/update-notifier ]; then touch
/var/lib/update-notifier/dpkg-run-stamp; fi;
/usr/lib/update-notifier/update-motd-updates-available 2>/dev/null || true";};
#APT::Update::Post-Invoke-Success
{"/usr/lib/update-notifier/update-motd-updates-available 2>/dev/null || true";};
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-01-07T17:02:35.486143
mtime.conffile..etc.apt.apt.conf.d.99update-notifier: 2016-11-16T17:39:04.061871
** Affects: unattended-upgrades (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1692492
Title:
package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade:
subprocess installed post-installation script returned error exit
status 1
Status in unattended-upgrades package in Ubuntu:
New
Bug description:
No further information to provide, this bug report was submitted
automatically.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.6
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri May 19 08:43:02 2017
ErrorMessage: subprocess installed post-installation script returned error
exit status 1
InstallationDate: Installed on 2016-09-08 (255 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
PackageArchitecture: all
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.2
apt 1.2.20
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::AutocleanInterval "7";
APT::Periodic::Unattended-Upgrade "1";
modified.conffile..etc.apt.apt.conf.d.99update-notifier:
#DPkg::Post-Invoke {"if [ -d /var/lib/update-notifier ]; then touch
/var/lib/update-notifier/dpkg-run-stamp; fi;
/usr/lib/update-notifier/update-motd-updates-available 2>/dev/null || true";};
#APT::Update::Post-Invoke-Success
{"/usr/lib/update-notifier/update-motd-updates-available 2>/dev/null || true";};
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-01-07T17:02:35.486143
mtime.conffile..etc.apt.apt.conf.d.99update-notifier:
2016-11-16T17:39:04.061871
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1692492/+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 1692492] Re: package unattended-upgrades 0.90ubuntu0.6 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1692492
Title:
package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade:
subprocess installed post-installation script returned error exit
status 1
Status in unattended-upgrades package in Ubuntu:
New
Bug description:
No further information to provide, this bug report was submitted
automatically.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: unattended-upgrades 0.90ubuntu0.6
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Fri May 19 08:43:02 2017
ErrorMessage: subprocess installed post-installation script returned error
exit status 1
InstallationDate: Installed on 2016-09-08 (255 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
PackageArchitecture: all
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.2
apt 1.2.20
SourcePackage: unattended-upgrades
Title: package unattended-upgrades 0.90ubuntu0.6 failed to install/upgrade:
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.apt.apt.conf.d.10periodic:
APT::Periodic::Update-Package-Lists "1";
APT::Periodic::Download-Upgradeable-Packages "1";
APT::Periodic::AutocleanInterval "7";
APT::Periodic::Unattended-Upgrade "1";
modified.conffile..etc.apt.apt.conf.d.99update-notifier:
#DPkg::Post-Invoke {"if [ -d /var/lib/update-notifier ]; then touch
/var/lib/update-notifier/dpkg-run-stamp; fi;
/usr/lib/update-notifier/update-motd-updates-available 2>/dev/null || true";};
#APT::Update::Post-Invoke-Success
{"/usr/lib/update-notifier/update-motd-updates-available 2>/dev/null || true";};
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2017-01-07T17:02:35.486143
mtime.conffile..etc.apt.apt.conf.d.99update-notifier:
2016-11-16T17:39:04.061871
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1692492/+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 1383470] Re: scp does not work (fails at 'Sending command scp -v -t')
I've found a clue. It's a server with limited bandwidth and it's currently using all of it. Not sure how the limit works, but I'm sure that's the problem: something is placing nginx traffic above scp traffic and the latter waits for hours. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1383470 Title: scp does not work (fails at 'Sending command scp -v -t') Status in openssh package in Ubuntu: Incomplete Bug description: Following the last update of Ubuntu 14.02, scp (in the default system) has ceased working. It hangs after authentication at the point where it wold start an interactive session. I've verified that the problem is in my system: scp still works at the target machine and scp won't work on my machine to various hosts. Output below. rasmith@rasmith-Lemur-Ultra:~$ scp -v testfil apacentral.org: Executing: program /usr/bin/ssh host apacentral.org, user (unspecified), command scp -v -t . OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /home/rasmith/.ssh/config debug1: /home/rasmith/.ssh/config line 17: Applying options for * debug1: /home/rasmith/.ssh/config line 20: Deprecated option "rhostsauthentication" debug1: /home/rasmith/.ssh/config line 25: Deprecated option "fallbacktorsh" debug1: /home/rasmith/.ssh/config line 26: Deprecated option "usersh" debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to apacentral.org [65.19.130.61] port 22. debug1: Connection established. debug1: could not open key file '/etc/ssh/ssh_host_key': No such file or directory debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such file or directory debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such file or directory debug1: identity file /home/rasmith/.ssh/identity type 0 debug1: identity file /home/rasmith/.ssh/identity-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.4_hpn13v11 FreeBSD-2013 debug1: match: OpenSSH_6.4_hpn13v11 FreeBSD-2013 pat OpenSSH* compat 0x0400 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5-...@openssh.com none debug1: kex: client->server aes128-ctr hmac-md5-...@openssh.com none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: RSA 61:40:9f:26:85:d2:57:34:f9:52:7b:c3:47:9d:7a:ae debug1: Host 'apacentral.org' is known and matches the RSA host key. debug1: Found key in /home/rasmith/.ssh/known_hosts:26 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering DSA public key: rasm...@aristotle.tamu.edu debug1: Server accepts key: pkalg ssh-dss blen 433 debug1: Authentication succeeded (publickey). Authenticated to apacentral.org ([65.19.130.61]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: Sending command: scp -v -t . (at this point, the command hangs more or less indefinitely until killed with Ctrl-C) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ssh 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 20 15:25:14 2014 InstallationDate: Installed on 2012-10-18 (732 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: Upgraded to trusty on 2014-05-02 (170 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/138347
[Touch-packages] [Bug 1692496] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1688721, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1688721 package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1692496 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: after cancel download ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Mon May 22 12:51:01 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-18 (3 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1692496/+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 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()
** Changed in: systemd (Ubuntu Zesty) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: Fix Committed Bug description: This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1692136] Re: Backport "core/timer: downgrade message about random time addition (#5229)".
** Changed in: systemd (Ubuntu Zesty) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1692136 Title: Backport "core/timer: downgrade message about random time addition (#5229)". Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Triaged Status in systemd source package in Yakkety: Triaged Status in systemd source package in Zesty: Fix Committed Bug description: Please backport upstream systemd v233 commit 382852fd581efe3cc0ae11154102ab9f435adea1 "core/timer: downgrade message about random time addition (#5229)". https://github.com/systemd/systemd/commit/382852fd581efe3cc0ae11154102ab9f435adea1 This removes "random time" messages flooding dmesg. The spew was introduced with v229 commit "core: add new RandomSec= setting for time units". https://github.com/systemd/systemd/commit/744c7693751830149ae78fdaf95c6c6f99d59f07 trusty based off v204 is not affected. xenial based off v229, yakkety based off v231, and zesty based off v232 need this fix. artful based off v233 has the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1692136/+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 1692510] [NEW] package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/l
Public bug reported: This is occur while installing openastro.org ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 17:04:26 2017 DuplicateSignature: package:iproute2:4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package iproute2 (--configure): package iproute2 is not ready for configuration ErrorMessage: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-05-11 (11 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iproute2 (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 iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692510 Title: package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') Status in iproute2 package in Ubuntu: New Bug description: This is occur while installing openastro.org ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 17:04:26 2017 DuplicateSignature: package:iproute2:4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package iproute2 (--configure): package iproute2 is not ready for configuration ErrorMessage: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-05-11 (11 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1692510/+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 1692510] Re: package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692510 Title: package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') Status in iproute2 package in Ubuntu: New Bug description: This is occur while installing openastro.org ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 17:04:26 2017 DuplicateSignature: package:iproute2:4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package iproute2 (--configure): package iproute2 is not ready for configuration ErrorMessage: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-05-11 (11 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 [modified: bin/ip bin/ss sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/bin/lnstat usr/bin/nstat usr/lib/tc/m_xt.so usr/lib/tc/q_atm.so usr/sbin/arpd usr/sbin/genl usr/share/doc/iproute2/changelog.Debian.gz usr/share/man/man8/tc.8.gz] failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1692510/+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 1692517] [NEW] crash on install new package package iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] failed to install/upgra
Public bug reported: Maybe a conflict with the ubuntu softwares library. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-lowlatency 4.8.17 Uname: Linux 4.8.0-52-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: synaptic: Install iproute2: Configure synaptic: Configure NULL: ConfigurePending Architecture: amd64 Date: Mon May 22 14:19:11 2017 DuplicateSignature: package:iproute2:4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package iproute2 (--configure): package iproute2 is not ready for configuration ErrorMessage: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-05-13 (9 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iproute2 (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 iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692517 Title: crash on install new package package iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half- installed') Status in iproute2 package in Ubuntu: New Bug description: Maybe a conflict with the ubuntu softwares library. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-lowlatency 4.8.17 Uname: Linux 4.8.0-52-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: synaptic: Install iproute2: Configure synaptic: Configure NULL: ConfigurePending Architecture: amd64 Date: Mon May 22 14:19:11 2017 DuplicateSignature: package:iproute2:4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package iproute2 (--configure): package iproute2 is not ready for configuration ErrorMessage: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-05-13 (9 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1692517/+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 1686618] Re: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04
** Changed in: openssh (Ubuntu Artful) Status: Triaged => Fix Committed ** Changed in: openssh (Ubuntu Zesty) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1686618 Title: ssh connection attempts fail if hw crypto support on s390x is enabled on 17.04 Status in Ubuntu on IBM z Systems: Fix Committed Status in openssh package in Ubuntu: Fix Committed Status in openssh source package in Zesty: In Progress Status in openssh source package in Artful: Fix Committed Bug description: [ Impact ] * Unable to ssh into Ubuntu, using default sshd configuration, when hw acceleration is enabled in openssl. [ Proposed solution ] * Cherrypick upstream fixes for: - sandboxing code on big endian - allowing hw accel iocls in the sandbox short: after investigations the following commits are needed by openssh-server version 7.4p1 that is part of 17.04: - 5f1596e11d55539678c41f68aed358628d33d86f - 9e96b41682aed793fadbea5ccd472f862179fb02 on master branch in https://github.com/openssh/openssh-portable that belong to openssh 7.5 release notes statement: "sshd(8): Avoid sandbox errors for Linux S390 systems using an ICA crypto coprocessor." __ [Test case] long: enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x like this: sudo apt-get install openssl-ibmca libica-utils libica2 sudo tee -a /etc/ssl/openssl.cnf < /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' /etc/ssl/openssl.cnf sudo sed -i '10i openssl_cnf = openssl_def' /etc/ssl/openssl.cnf afterwards ssh login attempts fail: $ ssh ubuntu@zlin42 ubuntu@zlin42's password: Connection to zlin42 closed by remote host. Connection to zlin42 closed. the normal logs don't provide any interesting details: mit log: Apr 24 12:37:52 zlin42 kernel: [933567.994312] audit: type=1326 audit(1493051872.112:29): auid=4294967295 uid=107 gid=65534 ses=4294967295 pid=25105 comm="sshd" exe="/usr/sbin/sshd" sig=31 arch=8016 syscall=201 compat=0 ip=0x3ffb8a3fb32 code=0x0 Verbose: OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /home/fheimes/.ssh/config debug1: /home/fheimes/.ssh/config line 6: Deprecated option "useroaming" debug1: /home/fheimes/.ssh/config line 7: Applying options for * debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to 10.245.208.7 [10.245.208.7] port 22. debug1: Connection established. debug1: identity file /home/fheimes/.ssh/id_rsa type 1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/fheimes/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.1 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 Ubuntu-10 debug1: match: OpenSSH_7.4p1 Ubuntu-10 pat OpenSSH* compat 0x0400 debug1: Authenticating to 10.245.208.7:22 as 'ubuntu' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha...@libssh.org debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ecdsa-sha2-nistp256 SHA256:ss9j12+jMMKL9u2vxNeb3XjOeH0E9lw24IG5LxUeJXk debug1: Host '10.245.208.7' is known and matches the ECDSA host key. debug1: Found key in /home/fheimes/.ssh/known_hosts:87 debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debu
[Touch-packages] [Bug 1266675] Re: newusers error adding more than one user
i met this error too.anyone know where to get the patch??? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1266675 Title: newusers error adding more than one user Status in shadow package in Ubuntu: Confirmed Bug description: 1) mcegielka@ftp-geodezja:~$ lsb_release -rd Description:Ubuntu 13.10 Release:13.10 2) mcegielka@ftp-geodezja:~$ sudo apt-cache policy passwd passwd: Installed: 1:4.1.5.1-1ubuntu6 Candidate: 1:4.1.5.1-1ubuntu6 3) Expected: add system users from file given as argument: mcegielka@ftp-geodezja:~$ cat testusers.txt test1:a:::test user 1,,,:/home/test1:/bin/bash test2:b:::test user 2,,,:/home/test2:/bin/bash 4) Instead: errors: mcegielka@ftp-geodezja:~$ sudo newusers testusers.txt *** Error in `newusers': free(): invalid next size (fast): 0x09319cd0 *** *** Error in `newusers': malloc(): memory corruption: 0x09319d00 *** ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: passwd 1:4.1.5.1-1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 Date: Tue Jan 7 09:04:11 2014 InstallationDate: Installed on 2014-01-07 (0 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release i386 (20131016) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1266675/+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 1692517] Re: crash on install new package package iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] failed to install/upgrade
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692517 Title: crash on install new package package iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half- installed') Status in iproute2 package in Ubuntu: New Bug description: Maybe a conflict with the ubuntu softwares library. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-lowlatency 4.8.17 Uname: Linux 4.8.0-52-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: synaptic: Install iproute2: Configure synaptic: Configure NULL: ConfigurePending Architecture: amd64 Date: Mon May 22 14:19:11 2017 DuplicateSignature: package:iproute2:4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package iproute2 (--configure): package iproute2 is not ready for configuration ErrorMessage: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2017-05-13 (9 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 [modified: sbin/bridge sbin/rtacct sbin/rtmon sbin/tc sbin/tipc usr/sbin/genl] failed to install/upgrade: package iproute2 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1692517/+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 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
** Patch added: "init-system-helpers-zesty-1691474.debdiff" https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+attachment/4881359/+files/init-system-helpers-zesty-1691474.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1691474 Title: invoke-rc.d service start fails on services with upstart-only scripts Status in init-system-helpers package in Ubuntu: In Progress Status in init-system-helpers source package in Xenial: New Status in init-system-helpers source package in Yakkety: New Status in init-system-helpers source package in Zesty: New Bug description: [Impact] On 16.04+ if you using upstart as your primary init system "enabled" services that _only_ have upstart scripts fail to start with invoke-rc.d (with a default policy). This is problematic as #DEBHELPER# tokens in maintscripts rely on invoke-rc.d to start/stop services and fail to start services on installation. [Test Case] Boot into affected system with upstart as default init. Try starting an 'upstart only' service with 'invoke-rc.d service start'. It is expected this should work. [Regression Potential] 14.04/upstart behavior is that invoke-rc.d works, and 16.04/systemd also has invoke-rc.d start working with enabled services and default policy. 16.04/upstart should be the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+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 1692494] Re: klibc does not support reboot arguments
The attachment "add-reboot-argument-support.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1692494 Title: klibc does not support reboot arguments Status in klibc package in Ubuntu: New Bug description: ... so we cannot do things like "reboot recovery" in devices that follow the Android partitions conventions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+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 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
** Patch added: "init-system-helpers-yakkety-lp1691474.debdiff" https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+attachment/4881367/+files/init-system-helpers-yakkety-lp1691474.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1691474 Title: invoke-rc.d service start fails on services with upstart-only scripts Status in init-system-helpers package in Ubuntu: In Progress Status in init-system-helpers source package in Xenial: New Status in init-system-helpers source package in Yakkety: New Status in init-system-helpers source package in Zesty: New Bug description: [Impact] On 16.04+ if you using upstart as your primary init system "enabled" services that _only_ have upstart scripts fail to start with invoke-rc.d (with a default policy). This is problematic as #DEBHELPER# tokens in maintscripts rely on invoke-rc.d to start/stop services and fail to start services on installation. [Test Case] Boot into affected system with upstart as default init. Try starting an 'upstart only' service with 'invoke-rc.d service start'. It is expected this should work. [Regression Potential] 14.04/upstart behavior is that invoke-rc.d works, and 16.04/systemd also has invoke-rc.d start working with enabled services and default policy. 16.04/upstart should be the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+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 1629226] Re: systemd's service killed by cgroup controller pids
Regarding the original report this is a simple program which keeps the maximal
allowed children running and it does not get killed by cgroups, just the fork()
call fails:
---
#include
#include
#include
#include
#include
#include
#include
#include
#define MASTER_SLEEP_NS 100L
#define CHILD_SLEEP_S 5
void main(void)
{
pid_t pid;
struct timespec master_sleep = {0, MASTER_SLEEP_NS};
for (;;) {
pid = fork();
if (pid < 0) {
perror("fork failed:");
nanosleep(&master_sleep, NULL);
}
if (pid == 0) {
sleep(CHILD_SLEEP_S);
exit(0);
}
nanosleep(&master_sleep, NULL);
/* collect exited children */
while (waitpid(-1, NULL, WNOHANG) > 0);
}
}
---
[Unit]
Description=Reproducer
After=multi-user.target
[Service]
ExecStart=/home/user/reproducer
Type=simple
TasksMax=512
[Install]
WantedBy=multi-user.target
---
● reproducer.service - Reproducer
Loaded: loaded (/etc/systemd/system/reproducer.service; disabled; vendor
preset: enabled)
Active: active (running) since Mon 2017-05-22 13:16:50 UTC; 3min 3s ago
Main PID: 11778 (reproducer)
Tasks: 512 (limit: 512)
Memory: 55.4M
CPU: 1min 2.794s
CGroup: /system.slice/reproducer.service
├─11778 /home/rbalint/reproducer
├─18144 /home/rbalint/reproducer
...
├─26763 /home/rbalint/reproducer
├─26764 /home/rbalint/reproducer
├─26765 /home/rbalint/reproducer
└─26766 /home/rbalint/reproducer
May 22 13:20:14 zesty-test reproducer[11778]: fork failed:: Resource
temporarily unavailable
May 22 13:20:14 zesty-test reproducer[11778]: fork failed:: Resource
temporarily unavailable
May 22 13:20:14 zesty-test reproducer[11778]: fork failed:: Resource
temporarily unavailable
---
Bash on the other hand kills itself after a few failing forks:
● reproducer.service - Reproducer
Loaded: loaded (/etc/systemd/system/reproducer.service; disabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Mon 2017-05-22 13:22:38 UTC; 3s ago
Process: 14281 ExecStart=/home/rbalint/reproducer.sh (code=exited,
status=0/SUCCESS)
Main PID: 14287 (code=exited, status=254)
CPU: 639ms
May 22 13:22:35 zesty-test reproducer.sh[14281]: /home/rbalint/reproducer.sh:
fork: retry: Resource temporarily unavailable
May 22 13:22:35 zesty-test reproducer.sh[14281]: /home/rbalint/reproducer.sh:
fork: retry: Resource temporarily unavailable
May 22 13:22:35 zesty-test reproducer.sh[14281]: /home/rbalint/reproducer.sh:
fork: retry: Resource temporarily unavailable
May 22 13:22:35 zesty-test reproducer.sh[14281]: /home/rbalint/reproducer.sh:
fork: retry: Resource temporarily unavailable
May 22 13:22:35 zesty-test reproducer.sh[14281]: /home/rbalint/reproducer.sh:
fork: retry: Resource temporarily unavailable
May 22 13:22:35 zesty-test reproducer.sh[14281]: /home/rbalint/reproducer.sh:
fork: retry: Resource temporarily unavailable
May 22 13:22:38 zesty-test reproducer.sh[14281]: /home/rbalint/reproducer.sh:
fork: Interrupted system call
May 22 13:22:38 zesty-test systemd[1]: reproducer.service: Main process exited,
code=exited, status=254/n/a
May 22 13:22:38 zesty-test systemd[1]: reproducer.service: Unit entered failed
state.
http://sources.debian.net/src/bash/4.4-5/jobs.c/?hl=1919#L1919
/* Create the child, handle severe errors. Retry on EAGAIN. */
while ((pid = fork ()) < 0 && errno == EAGAIN && forksleep < FORKSLEEP_MAX)
{
/* bash-4.2 */
sigprocmask (SIG_SETMASK, &oset, (sigset_t *)NULL);
/* If we can't create any children, try to reap some dead ones. */
waitchld (-1, 0);
errno = EAGAIN; /* restore errno */
sys_error ("fork: retry");
RESET_SIGTERM;
if (sleep (forksleep) != 0)
break;
forksleep <<= 1;
if (interrupt_state)
break;
sigprocmask (SIG_SETMASK, &set, (sigset_t *)NULL);
}
...
if (pid < 0)
{
sys_error ("fork");
/* Kill all of the processes in the current pipeline. */
terminate_current_pipeline ();
/* Discard the current pipeline, if any. */
if (the_pipeline)
kill_current_pipeline ();
last_command_exit_value = EX_NOEXEC;
throw_to_top_level ();/* Reset signals, etc. */
}
...
I believe this is by design and I think this approach is reasonable.
A shell should not try to keep itself alive forking new processes when
it hit system limits already for a few times. There are other tools
available for implementing servers with worker pools which adapt to
system limits which are not defined in advance.
If you know the number of workers need in advance I suggest setting
TasksMax to high enough or to infinity in case you don't want to rely on
cgroup fork limits.
** Changed in: bash (Ubuntu)
Status: In Progress => Invalid
** Summary changed:
- systemd's service killed by cgroup controller pids
+ Bash exits after a few failed fork()-s
--
You
[Touch-packages] [Bug 1692201] Re: package bash 4.4-2ubuntu1 failed to install/upgrade: il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed")
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bash (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1692201 Title: package bash 4.4-2ubuntu1 failed to install/upgrade: il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") Status in bash package in Ubuntu: Confirmed Bug description: non so ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bash 4.4-2ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic i686 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: bash:i386: Configure NULL: ConfigurePending Architecture: i386 Date: Sat May 20 11:42:03 2017 DpkgTerminalLog: dpkg: errore nell'elaborare il pacchetto bash (--configure): il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") ErrorMessage: il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") InstallationDate: Installed on 2017-03-27 (54 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: bash Title: package bash 4.4-2ubuntu1 failed to install/upgrade: il pacchetto bash non è pronto per la configurazione impossibile configurarlo (stato corrente "half-installed") UpgradeStatus: Upgraded to zesty on 2017-04-16 (33 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1692201/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports
Hi Eric, Sorry for the delay in getting back to this. As it has been a while I have reviewed everything again from the beginning. Can I confirm that by "with expected result" you mean that on Trusty->Xenial upgrade, in both cases (isc-client-dhcp installed and isc-client-dhcp-noddns installed) you end up with isc-client-dhcp installed in Xenial? The latest debdiffs in comments 51 and 53 look fine to me - please go ahead and upload. For SRU verification, please could you make sure you test each upgrade path permutation again, and before upload, just update the SRU information to confirm that you will be doing this? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: In Progress Status in isc-dhcp source package in Xenial: Fix Released Status in isc-dhcp source package in Yakkety: Fix Released Bug description: [Impact] In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. The DDNS functionnality, generate 2 random extra ports between 1024-65535. Impact reported by users : "One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown." "We have software that was using one of the lower udp ports but it happened to collide with dhclient which seems to allocate 2 random ports." There is a randomization mechanism in libdns that prevent dhclient to take the sysctl values into account (net.ipv4.ip_local_port_range & net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion isc-dhcp upstream doesn't want to rely on kernel for randomization. There is no realtime configuration to disable the feature or workaround this. The only possible way is at compile time. I also talk with upstream maintainers, and there is no way they will accept to reduce the range (1024-65535) for security reason. Reducing the port range may facilitate the spoofing. Xenial has separated dhclient in two packages : isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random extra ports) The goal here is to reproduce the same situation in Trusty, for this bug to be less painful for at least users that doesn't require DDNS functionnality. [Test Case] Run a Trusty image with following package : isc-dhcp-client isc-dhcp-common ``` dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port ``` [Regression Potential] I did the split such that Trusty users will automatically get "isc- dhcp-client-ddns" installed but users bothered by this bug will have the option to switch to "isc-dhcp-client-noddns". Existing Trusty users can continue to use this DDNS functionality after the SRU without any necessary intervention. With isc-dhcp-client: dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port With isc-dhcp-client-noddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc Xenial also has both distinct dhclient binary package but in the opposite way. We have decided to use the opposite way approach for not impacting actual Trusty users by changing the nature of isc-dhcp- client itself. Caribou and I, slashd, have also tested a couple of release upgrades from Trusty to Xenial with both scenarios : 1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns" 2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns" and both scenarios worked as expected for caribou and I. (See comment #42) Results : === ** Upgrade tested with isc-dhcp-client ** # dpkg -l ii isc-dhcp-client 4.2.4-7ubuntu12.8 amd64ISC DHCP client ii isc-dhcp-common 4.2.4-7ubuntu12.8 amd64common files used by all the isc-dhcp* packages # netstat -anputa | grep -i dhclient udp0 0 0.0.0.0:20114 0.0.0.0:* 632/dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 632/dhclient udp6 0 0 :::52249:::* 632/dhclient After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2) ii isc-dhcp-client
[Touch-packages] [Bug 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
setting to high given the frequency of this defect. ** Description changed: + = Test Case = + 1. Download the debian package of Chrome from google + 2. Open nautilus and double-click on the file to launch ubuntu software + 3. Install the package and proceed with the installation + + = Expected result = + Chrome installs correctly + + = Actual result = + The installation hangs on the following command in gconf2-common.postinst + + ucf /usr/share/gconf/default.path /etc/gconf/2/path + + + = Original Report = I received this error when trying to install local file google-chrome-stable.deb version 58.0.3029.96-1. This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. Other times, the installation process just hangs at some percentage. I am testing this gnome-software version due to Bug (LP: #1672424). The same file was successfully installed with gdebi. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: gconf2-common:amd64: Install libgconf-2-4:amd64: Install gconf-service-backend:amd64: Install gconf-service:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat May 6 13:56:26 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-04 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: gconf (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1688721 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: Confirmed Bug description: = Test Case = 1. Download the debian package of Chrome from google 2. Open nautilus and double-click on the file to launch ubuntu software 3. Install the package and proceed with the installation = Expected result = Chrome installs correctly = Actual result = The installation hangs on the following command in gconf2-common.postinst ucf /usr/share/gconf/default.path /etc/gconf/2/path = Original Report = I received this error when trying to install local file google-chrome-stable.deb version 58.0.3029.96-1. This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. Other times, the installation process just hangs at some percentage. I am testing this gnome-software version due to Bug (LP: #1672424). The same file was successfully installed with gdebi. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: gconf2-common:amd64: Install libgconf-2-4:amd64: Install gconf-service-backend:amd64: Install gconf-service:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat May 6 13:56:26 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-04 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1688721/+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 1692543] [NEW] Regression tests cannot write to apparmor path_max module parameter in artful/4.11
Public bug reported: The longpath regression tests tries to write to /sys/module/apparmor/parameters/path_max, but this is read-only in artful/4.11: commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6 Author: John Johansen Date: Thu Apr 6 05:14:20 2017 -0700 apparmor: Make path_max parameter readonly This is causing ADT to fail. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful-canonical-kernel-team- ppa/artful/amd64/l/linux/20170519_170900_9130b@/log.gz running longpath longpath.sh: line 53: /sys/module/apparmor/parameters/path_max: Permission denied Fatal Error (longpath): Unexpected shell error. Run with -x to debug ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1692543 Title: Regression tests cannot write to apparmor path_max module parameter in artful/4.11 Status in apparmor package in Ubuntu: New Bug description: The longpath regression tests tries to write to /sys/module/apparmor/parameters/path_max, but this is read-only in artful/4.11: commit cdc8e09e16bb7eb7d23fcbdbe416aa91770fb4d6 Author: John Johansen Date: Thu Apr 6 05:14:20 2017 -0700 apparmor: Make path_max parameter readonly This is causing ADT to fail. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful-canonical-kernel-team- ppa/artful/amd64/l/linux/20170519_170900_9130b@/log.gz running longpath longpath.sh: line 53: /sys/module/apparmor/parameters/path_max: Permission denied Fatal Error (longpath): Unexpected shell error. Run with -x to debug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1692543/+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 124743] Re: Sony Sixaxis Controller does not work over bluetooth
@jamestheawesomedude I also have issues with the PS3 controller in 16.04. I can't get it to pair over bluetooth and it constantly rumbles. -- 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/124743 Title: Sony Sixaxis Controller does not work over bluetooth Status in Ubuntu PS3 Port: New Status in bluez package in Ubuntu: Invalid Bug description: Sixaxis controller has limited functionality as a USB device (no motion sensor axis support) but is not able to pair and be recognized from Feisty install. External tools are needed to allow it to pair, but kernel support may also be required. Please see: http://ubuntuforums.org/showthread.php?p=2983423#post2983423 tools and patch available here: http://www.pabr.org/sixlinux/sixlinux.en.html Bluetooth packet log from attempt on OS X: http://mt.creativepony.com/drop-box/PacketLogger%20Sixaxis%20Bluetooth.pklg.zip To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ps3-port/+bug/124743/+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 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()
** Patch added: "xenial.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+attachment/4881430/+files/xenial.patch -- 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/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Confirmed Bug description: This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()
** Patch added: "yakkety.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+attachment/4881441/+files/yakkety.patch -- 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/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Confirmed Bug description: This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1621396] Re: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for()
** Patch added: "zesty.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+attachment/4881443/+files/zesty.patch ** Changed in: systemd (Ubuntu Zesty) Status: Fix Committed => Confirmed ** Changed in: systemd (Ubuntu Yakkety) Status: New => Confirmed ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- 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/1621396 Title: systemd-resolved crashed with SIGSEGV in dns_packet_is_reply_for() Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Confirmed Status in systemd source package in Yakkety: Confirmed Status in systemd source package in Zesty: Confirmed Bug description: This is one of background errors that happens without any active app being involved. For the records, I had open: Firefox, Slack, Franz and the Terminal ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-5 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Thu Sep 8 09:33:55 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-06-06 (1189 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Dell Inc. Dell System XPS L322X ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=2850be62-a05e-4ab9-af2b-5f1fd159ce5d ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so sd_event_dispatch () from /lib/systemd/libsystemd-shared-231.so sd_event_run () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch() UpgradeStatus: Upgraded to yakkety on 2016-09-03 (4 days ago) UserGroups: dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/18/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1621396/+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 1669270] [NEW] package grub-pc 2.02~beta2-36ubuntu3.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
You have been subscribed to a public bug: When I start my screen, a blue screen appears with 2 options, 1. GNU/grub-pc 2. Advanced options for ubuntu. And I have to always click on 1 to get my PC started(or it automatically chooses 1). ProblemType: Package DistroRelease: Ubuntu 16.04 Package: grub-pc 2.02~beta2-36ubuntu3.7 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Thu Mar 2 10:55:13 2017 DpkgHistoryLog: Start-Date: 2017-03-02 10:55:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libgd3:amd64 (2.1.1-4ubuntu0.16.04.5, 2.1.1-4ubuntu0.16.04.6), libtiff5:amd64 (4.0.6-1, 4.0.6-1ubuntu0.1) DuplicateSignature: package:grub-pc:2.02~beta2-36ubuntu3.7 Setting up unattended-upgrades (0.90ubuntu0.3) ... dpkg: error processing package unattended-upgrades (--configure): subprocess installed post-installation script returned error exit status 10 ErrorMessage: subprocess installed post-installation script returned error exit status 10 InstallationDate: Installed on 2017-02-16 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InvalidGrubScript: /etc/default/grub ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic root=UUID=3cfa4b16-e389-41c3-a5c6-98add8a87218 ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: grub2 Title: package grub-pc 2.02~beta2-36ubuntu3.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ucf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- package grub-pc 2.02~beta2-36ubuntu3.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 https://bugs.launchpad.net/bugs/1669270 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688310] Update Released
The verification of the Stable Release Update for krb5 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 krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1688310 Title: KDC/kadmind may fail to start on IPv4-only systems Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Zesty: Fix Released Status in krb5 package in Debian: Fix Released Bug description: This is fixed in artful in krb5 1.15-2 - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531 - debian: conflated into https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767 - debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch [Impact] getaddrinfo() called on a wildcard address might return the IPv6 "::1" address. On machines without IPv6 support, binding to it will most likely fail and the kdc/kadmin services won't start. The provided patch is applied upstream and in Debian testing. [Test Case] Steps to reproduce the problem on zesty: a) install krb5-kdc krb5-admin-server $ sudo apt install krb5-kdc krb5-admin-server when prompted, use EXAMPLE.ORG (all caps) as the default realm when prompted, use the IP of this machine for the KDC and the Admin servers b) configure a new realm called EXAMPLE.ORG $ sudo krb5_newrealm use any password of your liking when prompted c) confirm the kdc and admin services are running. $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep 4275 ?Ss 0:00 /usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid 4306 ?Ss 0:00 /usr/sbin/kadmind -nofork d) create a principal and obtain a ticket to confirm kerberos is working properly: $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu $ kinit Password for ubu...@example.org: $ klist Ticket cache: FILE:/tmp/krb5cc_1000 Default principal: ubu...@example.org Valid starting Expires Service principal 05/04/2017 14:20:17 05/05/2017 00:20:17 krbtgt/example@example.org renew until 05/05/2017 14:20:13 e) Confirm the kerberos services are bound to IPv6 local sockets: $ sudo netstat -anp|grep -E "^(tcp|udp)6.*(krb5kdc|kadmind)" tcp6 0 0 :::88 :::*LISTEN 1078/krb5kdc tcp6 0 0 :::749 :::*LISTEN 1065/kadmind tcp6 0 0 :::464 :::*LISTEN 1065/kadmind udp6 0 0 :::88 :::* 1078/krb5kdc udp6 0 0 :::464 :::* 1065/kadmind udp6 0 0 :::750 :::* 1078/krb5kdc f) configure the system to not support IPv6. There are probably many ways to do this, but the one sure way is to reboot it with ipv6.disable=1 in the kernel command line: e.1) edit /etc/default/grub e.2) add "ipv6.disable=1" to GRUB_CMDLINE_LINUX and save e.3) run sudo update-grub e.4) reboot f) Confirm the kdc and admin services are NOT running: $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep $ g) /var/log/auth.log will contain the reason: $ sudo grep -E "(kadmind|krb5kdc).*Failed" /var/log/auth.log May 4 14:11:54 22-96 krb5kdc[1087]: Failed setting up a UDP socket (for ::.750) May 4 14:11:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for ::.464) May 4 14:15:36 22-96 krb5kdc[1510]: Failed setting up a UDP socket (for ::.750) May 4 14:16:36 22-96 krb5kdc[1652]: Failed setting up a UDP socket (for ::.750) May 4 14:25:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for ::.464) May 4 14:25:54 22-96 krb5kdc[1079]: Failed setting up a UDP socket (for ::.750) With the updated packages, krb5-kdc and krb5-admin-server will startup just fine in the same conditions. [Regression Potential] We now tolerate a EAFNOSUPPORT error as long as at least one socket was bound to correctly. Maybe there could be a scenario when this one bound socket is useless, or unexpected: in that case, bailing out because of the EAFNOSUPPORT error could be seen as a more robust approach because it's immediately visible, instead of silently listening on the useless socket. That being said, I believe single stack systems (only IPv4, or only IPv6) take an extra configuration effort and most systems are dual stack. Zesty certainly is, out of the box. To manage notifications about this bug go
[Touch-packages] [Bug 1688121] Re: KDC/kadmind explicit wildcard listener addresses do not use pktinfo
This bug was fixed in the package krb5 - 1.15-1ubuntu0.1
---
krb5 (1.15-1ubuntu0.1) zesty; urgency=medium
* Pulled in Debian fixes from Sam Hartman for:
- kinit fails for OTP user when using kdc discovery via DNS
(LP: #1683237)
- KDC/kadmind explicit wildcard listener addresses do not use pktinfo
(LP: #1688121)
- KDC/kadmind may fail to start on IPv4-only systems (LP: #1688310)
-- Andreas Hasenack Fri, 05 May 2017 14:05:38
+
** Changed in: krb5 (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 krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1688121
Title:
KDC/kadmind explicit wildcard listener addresses do not use pktinfo
Status in krb5 package in Ubuntu:
Fix Released
Status in krb5 source package in Zesty:
Fix Released
Bug description:
This is fixed in artful in krb5 1.15-2
- upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
- debian: conflated into
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
- debian patch in artful's krb5:
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch
[Impact]
When the KDC is configured to listen on the wildcard address (0.0.0.0) and
receives a kinit request via UDP on an aliased interface, the response is sent
with the wrong source IP and never received by kinit.
After a short timeout, kinit tries again with TCP, in which case it works.
But if using PREAUTH (the default), that means this first request will
correctly fail, with the server demanding PREAUTH, and the client will try
again with a changed request. The whole dance starts again: first UDP, ignored,
then TCP, and finally we have a ticket.
Most clients will just see an increased lag when obtaining tickets. If
for some reason 88/TCP is blocked on the KDC and clients are expected
to use UDP at all times, then kinit requests will just fail.
A workaround is to list the aliased interface's address in kdc_listen
besides the wildcard (0.0.0.0) address.
The provided patch is applied upstream and in Debian testing.
[Test Case]
On zesty:
a) install krb5-kdc and krb5-admin-server
$ sudo apt install krb5-kdc krb5-admin-server
when prompted, use EXAMPLE.ORG (all caps) as the default realm
when prompted, select your own IP for the KDC and the Admin servers
b) configure a new realm called EXAMPLE.ORG
$ sudo krb5_newrealm
use any password of your liking when prompted
b.1) Add "kdc_listen = 0.0.0.0" to the EXAMPLE.ORG [realm] section in
/etc/krb5kdc/kdc.conf and restart the kerberos services:
[realms]
EXAMPLE.ORG = {
kdc_listen = 0.0.0.0
(...)
$ sudo service krb5-kdc restart
$ sudo service krb5-admin-server restart
c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and
with mandatory PREAUTH:
$ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
d) extract the ubuntu principal keytab and time how long it takes to obtain a
ticket:
$ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
$ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
$ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
real 0m0.022s
$ klist
Ticket cache: FILE:/tmp/krb5cc_1000
Default principal: ubu...@example.org
Valid starting Expires Service principal
05/03/2017 21:22:08 05/04/2017 07:22:08 krbtgt/example@example.org
renew until 05/04/2017 21:22:08
e) add another IP to your network interface. For example, this adds
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
$ sudo ip addr add 10.0.5.155/24 dev ens3
f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc
and admin server's IP to this new IP you just added in step (e):
[realms]
EXAMPLE.ORG = {
kdc = 10.0.5.155
admin_server = 10.0.5.155
g) Time again how long it takes to obtain a ticket:
$ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
real 0m2.017s
Step (g) shows the bug.
On a more technical level, we can see that the server responds to kinit's UDP
request using an incorrect source IP, therefore kinit never "sees" it. It
quickly times out and switches to TCP, where the server responds using the
correct source IP:
1 0.010.0.5.55 → 10.0.5.155 KRB5 216 AS-REQ
2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error:
KRB5KDC_ERR_PREAUTH_REQUIRED
(2) has the incorrect source ip!
After roughly 1s, kinit switches to tcp and tries again:
3 1.00323150710.0.5.55 → 10.0.5.155 TCP 76 55588 → 88 [SYN] Seq=0
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
4 1.003269692 10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK]
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273
TSecr=3523453804 WS=128
5 1.003302614
[Touch-packages] [Bug 1688310] Re: KDC/kadmind may fail to start on IPv4-only systems
This bug was fixed in the package krb5 - 1.15-1ubuntu0.1 --- krb5 (1.15-1ubuntu0.1) zesty; urgency=medium * Pulled in Debian fixes from Sam Hartman for: - kinit fails for OTP user when using kdc discovery via DNS (LP: #1683237) - KDC/kadmind explicit wildcard listener addresses do not use pktinfo (LP: #1688121) - KDC/kadmind may fail to start on IPv4-only systems (LP: #1688310) -- Andreas Hasenack Fri, 05 May 2017 14:05:38 + ** Changed in: krb5 (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 krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1688310 Title: KDC/kadmind may fail to start on IPv4-only systems Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Zesty: Fix Released Status in krb5 package in Debian: Fix Released Bug description: This is fixed in artful in krb5 1.15-2 - upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8531 - debian: conflated into https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767 - debian patch: 0011-Fix-KDC-kadmind-startup-on-some-IPv4-only-systems.patch [Impact] getaddrinfo() called on a wildcard address might return the IPv6 "::1" address. On machines without IPv6 support, binding to it will most likely fail and the kdc/kadmin services won't start. The provided patch is applied upstream and in Debian testing. [Test Case] Steps to reproduce the problem on zesty: a) install krb5-kdc krb5-admin-server $ sudo apt install krb5-kdc krb5-admin-server when prompted, use EXAMPLE.ORG (all caps) as the default realm when prompted, use the IP of this machine for the KDC and the Admin servers b) configure a new realm called EXAMPLE.ORG $ sudo krb5_newrealm use any password of your liking when prompted c) confirm the kdc and admin services are running. $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep 4275 ?Ss 0:00 /usr/sbin/krb5kdc -P /var/run/krb5-kdc.pid 4306 ?Ss 0:00 /usr/sbin/kadmind -nofork d) create a principal and obtain a ticket to confirm kerberos is working properly: $ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu $ kinit Password for ubu...@example.org: $ klist Ticket cache: FILE:/tmp/krb5cc_1000 Default principal: ubu...@example.org Valid starting Expires Service principal 05/04/2017 14:20:17 05/05/2017 00:20:17 krbtgt/example@example.org renew until 05/05/2017 14:20:13 e) Confirm the kerberos services are bound to IPv6 local sockets: $ sudo netstat -anp|grep -E "^(tcp|udp)6.*(krb5kdc|kadmind)" tcp6 0 0 :::88 :::*LISTEN 1078/krb5kdc tcp6 0 0 :::749 :::*LISTEN 1065/kadmind tcp6 0 0 :::464 :::*LISTEN 1065/kadmind udp6 0 0 :::88 :::* 1078/krb5kdc udp6 0 0 :::464 :::* 1065/kadmind udp6 0 0 :::750 :::* 1078/krb5kdc f) configure the system to not support IPv6. There are probably many ways to do this, but the one sure way is to reboot it with ipv6.disable=1 in the kernel command line: e.1) edit /etc/default/grub e.2) add "ipv6.disable=1" to GRUB_CMDLINE_LINUX and save e.3) run sudo update-grub e.4) reboot f) Confirm the kdc and admin services are NOT running: $ ps faxw|grep -E "(krb5kdc|kadmind)"|grep -v grep $ g) /var/log/auth.log will contain the reason: $ sudo grep -E "(kadmind|krb5kdc).*Failed" /var/log/auth.log May 4 14:11:54 22-96 krb5kdc[1087]: Failed setting up a UDP socket (for ::.750) May 4 14:11:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for ::.464) May 4 14:15:36 22-96 krb5kdc[1510]: Failed setting up a UDP socket (for ::.750) May 4 14:16:36 22-96 krb5kdc[1652]: Failed setting up a UDP socket (for ::.750) May 4 14:25:54 22-96 kadmind[1085]: Failed setting up a UDP socket (for ::.464) May 4 14:25:54 22-96 krb5kdc[1079]: Failed setting up a UDP socket (for ::.750) With the updated packages, krb5-kdc and krb5-admin-server will startup just fine in the same conditions. [Regression Potential] We now tolerate a EAFNOSUPPORT error as long as at least one socket was bound to correctly. Maybe there could be a scenario when this one bound socket is useless, or unexpected: in that case, bailing out because of the EAFNOSUPPORT error could be seen as a more robust approach because it's immediately visible, instead of silently listening on the useless socket. That being said, I believe single stack systems (only IPv4, or only IPv6) take an extra configuration effort and most systems
[Touch-packages] [Bug 1688121] Update Released
The verification of the Stable Release Update for krb5 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 krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1688121
Title:
KDC/kadmind explicit wildcard listener addresses do not use pktinfo
Status in krb5 package in Ubuntu:
Fix Released
Status in krb5 source package in Zesty:
Fix Released
Bug description:
This is fixed in artful in krb5 1.15-2
- upstream: http://krbdev.mit.edu/rt/Ticket/Display.html?id=8530
- debian: conflated into
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860767
- debian patch in artful's krb5:
0012-Use-pktinfo-for-explicit-UDP-wildcard-listeners.patch
[Impact]
When the KDC is configured to listen on the wildcard address (0.0.0.0) and
receives a kinit request via UDP on an aliased interface, the response is sent
with the wrong source IP and never received by kinit.
After a short timeout, kinit tries again with TCP, in which case it works.
But if using PREAUTH (the default), that means this first request will
correctly fail, with the server demanding PREAUTH, and the client will try
again with a changed request. The whole dance starts again: first UDP, ignored,
then TCP, and finally we have a ticket.
Most clients will just see an increased lag when obtaining tickets. If
for some reason 88/TCP is blocked on the KDC and clients are expected
to use UDP at all times, then kinit requests will just fail.
A workaround is to list the aliased interface's address in kdc_listen
besides the wildcard (0.0.0.0) address.
The provided patch is applied upstream and in Debian testing.
[Test Case]
On zesty:
a) install krb5-kdc and krb5-admin-server
$ sudo apt install krb5-kdc krb5-admin-server
when prompted, use EXAMPLE.ORG (all caps) as the default realm
when prompted, select your own IP for the KDC and the Admin servers
b) configure a new realm called EXAMPLE.ORG
$ sudo krb5_newrealm
use any password of your liking when prompted
b.1) Add "kdc_listen = 0.0.0.0" to the EXAMPLE.ORG [realm] section in
/etc/krb5kdc/kdc.conf and restart the kerberos services:
[realms]
EXAMPLE.ORG = {
kdc_listen = 0.0.0.0
(...)
$ sudo service krb5-kdc restart
$ sudo service krb5-admin-server restart
c) run kadmin.local to create a principal "ubuntu" with password "ubuntu" and
with mandatory PREAUTH:
$ sudo kadmin.local addprinc -pw ubuntu +requires_preauth ubuntu
d) extract the ubuntu principal keytab and time how long it takes to obtain a
ticket:
$ sudo kadmin.local ktadd -k /home/ubuntu/ubuntu.keytab ubuntu
$ sudo chown ubuntu:ubuntu /home/ubuntu/ubuntu.keytab
$ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
real 0m0.022s
$ klist
Ticket cache: FILE:/tmp/krb5cc_1000
Default principal: ubu...@example.org
Valid starting Expires Service principal
05/03/2017 21:22:08 05/04/2017 07:22:08 krbtgt/example@example.org
renew until 05/04/2017 21:22:08
e) add another IP to your network interface. For example, this adds
10.0.5.155 to ens3 (it has 10.0.5.55/24 already in my case):
$ sudo ip addr add 10.0.5.155/24 dev ens3
f) Edit the EXAMPLE.ORG realm section in /etc/krb5.conf and configure the kdc
and admin server's IP to this new IP you just added in step (e):
[realms]
EXAMPLE.ORG = {
kdc = 10.0.5.155
admin_server = 10.0.5.155
g) Time again how long it takes to obtain a ticket:
$ time kinit -k -t /home/ubuntu/ubuntu.keytab ubuntu
real 0m2.017s
Step (g) shows the bug.
On a more technical level, we can see that the server responds to kinit's UDP
request using an incorrect source IP, therefore kinit never "sees" it. It
quickly times out and switches to TCP, where the server responds using the
correct source IP:
1 0.010.0.5.55 → 10.0.5.155 KRB5 216 AS-REQ
2 0.00056668210.0.5.55 → 10.0.5.55KRB5 298 KRB Error:
KRB5KDC_ERR_PREAUTH_REQUIRED
(2) has the incorrect source ip!
After roughly 1s, kinit switches to tcp and tries again:
3 1.00323150710.0.5.55 → 10.0.5.155 TCP 76 55588 → 88 [SYN] Seq=0
Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=3523453804 TSecr=0 WS=128
4 1.003269692 10.0.5.155 → 10.0.5.55TCP 76 88 → 55588 [SYN, ACK]
Seq=0 Ack=1 Win=43690 Len=0 MSS=65495 SACK_PERM=1 TSval=2572724273
TSecr=3523453804 WS=128
5 1.00330261410.0.5.55 → 10.0.5.155 TCP 68 55588 → 88 [ACK] Seq=1
Ack=1 Win=43776 Len=0 TSval=3523453804 T
[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS
This bug was fixed in the package krb5 - 1.15-1ubuntu0.1
---
krb5 (1.15-1ubuntu0.1) zesty; urgency=medium
* Pulled in Debian fixes from Sam Hartman for:
- kinit fails for OTP user when using kdc discovery via DNS
(LP: #1683237)
- KDC/kadmind explicit wildcard listener addresses do not use pktinfo
(LP: #1688121)
- KDC/kadmind may fail to start on IPv4-only systems (LP: #1688310)
-- Andreas Hasenack Fri, 05 May 2017 14:05:38
+
** Changed in: krb5 (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 krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1683237
Title:
krb5-user: kinit fails for OTP user when using kdc discovery via DNS
Status in krb5 package in Ubuntu:
Fix Released
Status in krb5 source package in Zesty:
Fix Released
Status in krb5 package in Debian:
Fix Released
Bug description:
This is fixed in krb5 1.15-2 in artful
Upstream bug : http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554
Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
Debian patch in 1.15-2 in artful:
0013-Fix-udp_preference_limit-with-SRV-records.patch
[Impact]
kinit does not respect udp_preference_limit and always uses TCP to
talk to the KDC when using the DNS SRV records to locate the service
and these records show both udp and tcp entries.
One particular scenario that fails is when OTP (one time password) is
used, as reported.
The provided patch is applied upstream and debian testing.
[Test Case]
Steps to reproduce on zesty, with all services on one machine for
simplicity (I suggest to use LXD):
a) install the packages from zesty (not the proposed ones yet):
$ sudo apt install krb5-kdc krb5-admin-server bind9
When prompted for the realm, choose EXAMPLE.COM
When prompted for the KDC and Admin services server address, use the IP of
your test machine/container (not localhost or 127.0.0.1)
The KDC will fail to start because there is no realm yet, that's not relevant
for this bug.
b) Edit /etc/krb5.conf and make the following changes:
- remove the "default_realm" line from the [libdefaults] section
- remove the EXAMPLE.COM realm block from the [realms] section
- add "dns_lookup_realm = true" to the [libdefaults] section
- add "dns_lookup_kdc = true" to the [libdefaults] section
- add "udp_preference_limit = 1" to the [libdefaults] section
c) Edit /etc/bind/named.conf.local and add this zone block (for simplicity,
we are skipping the reverse zone):
zone "example.com" {
type master;
file "/etc/bind/db.example.com";
};
d) Create /etc/bind/db.example.com with this content:
$TTL604800
@ IN SOA example.com. ubuntu.example.com. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
@ IN NS zesty-bug1683237.example.com.
zesty-bug1683237IN A 10.0.100.249
_kerberos TXT "EXAMPLE.COM"
_kerberos._udp SRV 0 0 88 zesty-bug1683237
_kerberos._tcp SRV 0 0 88 zesty-bug1683237
_kerberos-master._udp SRV 0 0 88 zesty-bug1683237
_kerberos-master._tcp SRV 0 0 88 zesty-bug1683237
_kerberos-adm._tcp SRV 0 0 749 zesty-bug1683237
_kpasswd._udp SRV 0 0 464 zesty-bug1683237
Use the real IP of your test machine/container where I used
"10.0.100.249". You can also choose another hostname if you want, just
be consistent across the board. I chose "zesty-bug1683237".
e) Restart bind
$ sudo service bind9 restart
f) Do a few quick DNS tests:
$ dig +short @10.0.100.249 zesty-bug1683237.example.com
10.0.100.249
$ dig +short @10.0.100.249 -t TXT _kerberos.example.com
"EXAMPLE.COM"
$ dig +short @10.0.100.249 -t SRV _kerberos._udp.example.com
0 0 88 zesty-bug1683237.example.com.
$ dig +short @10.0.100.249 -t SRV _kerberos._tcp.example.com
0 0 88 zesty-bug1683237.example.com.
g) Edit /etc/resolv.conf, ignoring the warning since we are not going to
reboot or change network interfaces:
nameserver 10.0.100.249 # USE YOUR IP HERE
search example.com
h) Create the EXAMPLE.COM kerberos realm:
$ sudo krb5_newrealm
When prompted for a password, use whatever you like. If you get an error
about no default realm, then your TXT record in DNS is not working. Retrace
your DNS configuration steps.
i) Start the kerberos services:
$ sudo service krb5-kdc start
sudo service krb5-admin-server start
j) Create a principal and test it:
$ sudo kadmin.local addprinc -pw ubuntu ubuntu
$ kinit ubuntu
Password for ubu...@example.com:
$ klist
(...)
05/05/2017 13:10:01 05/05/2017 23:10:01 krbtgt/example@example.com
(...)
Now we are ready to test the bug.
Given
[Touch-packages] [Bug 1669270] Re: package grub-pc 2.02~beta2-36ubuntu3.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
It looks like ucf is failing instead of prompting to update the config file. I'm not sure why that would fail. ** Package changed: grub2 (Ubuntu) => ucf (Ubuntu) ** Changed in: ucf (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1669270 Title: package grub-pc 2.02~beta2-36ubuntu3.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 Status in ucf package in Ubuntu: New Bug description: When I start my screen, a blue screen appears with 2 options, 1. GNU/grub-pc 2. Advanced options for ubuntu. And I have to always click on 1 to get my PC started(or it automatically chooses 1). ProblemType: Package DistroRelease: Ubuntu 16.04 Package: grub-pc 2.02~beta2-36ubuntu3.7 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Thu Mar 2 10:55:13 2017 DpkgHistoryLog: Start-Date: 2017-03-02 10:55:02 Commandline: /usr/bin/unattended-upgrade Upgrade: libgd3:amd64 (2.1.1-4ubuntu0.16.04.5, 2.1.1-4ubuntu0.16.04.6), libtiff5:amd64 (4.0.6-1, 4.0.6-1ubuntu0.1) DuplicateSignature: package:grub-pc:2.02~beta2-36ubuntu3.7 Setting up unattended-upgrades (0.90ubuntu0.3) ... dpkg: error processing package unattended-upgrades (--configure): subprocess installed post-installation script returned error exit status 10 ErrorMessage: subprocess installed post-installation script returned error exit status 10 InstallationDate: Installed on 2017-02-16 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InvalidGrubScript: /etc/default/grub ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic root=UUID=3cfa4b16-e389-41c3-a5c6-98add8a87218 ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: grub2 Title: package grub-pc 2.02~beta2-36ubuntu3.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1669270/+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 1683237] Update Released
The verification of the Stable Release Update for krb5 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 krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1683237
Title:
krb5-user: kinit fails for OTP user when using kdc discovery via DNS
Status in krb5 package in Ubuntu:
Fix Released
Status in krb5 source package in Zesty:
Fix Released
Status in krb5 package in Debian:
Fix Released
Bug description:
This is fixed in krb5 1.15-2 in artful
Upstream bug : http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554
Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307
Debian patch in 1.15-2 in artful:
0013-Fix-udp_preference_limit-with-SRV-records.patch
[Impact]
kinit does not respect udp_preference_limit and always uses TCP to
talk to the KDC when using the DNS SRV records to locate the service
and these records show both udp and tcp entries.
One particular scenario that fails is when OTP (one time password) is
used, as reported.
The provided patch is applied upstream and debian testing.
[Test Case]
Steps to reproduce on zesty, with all services on one machine for
simplicity (I suggest to use LXD):
a) install the packages from zesty (not the proposed ones yet):
$ sudo apt install krb5-kdc krb5-admin-server bind9
When prompted for the realm, choose EXAMPLE.COM
When prompted for the KDC and Admin services server address, use the IP of
your test machine/container (not localhost or 127.0.0.1)
The KDC will fail to start because there is no realm yet, that's not relevant
for this bug.
b) Edit /etc/krb5.conf and make the following changes:
- remove the "default_realm" line from the [libdefaults] section
- remove the EXAMPLE.COM realm block from the [realms] section
- add "dns_lookup_realm = true" to the [libdefaults] section
- add "dns_lookup_kdc = true" to the [libdefaults] section
- add "udp_preference_limit = 1" to the [libdefaults] section
c) Edit /etc/bind/named.conf.local and add this zone block (for simplicity,
we are skipping the reverse zone):
zone "example.com" {
type master;
file "/etc/bind/db.example.com";
};
d) Create /etc/bind/db.example.com with this content:
$TTL604800
@ IN SOA example.com. ubuntu.example.com. (
1 ; Serial
604800 ; Refresh
86400 ; Retry
2419200 ; Expire
604800 ) ; Negative Cache TTL
;
@ IN NS zesty-bug1683237.example.com.
zesty-bug1683237IN A 10.0.100.249
_kerberos TXT "EXAMPLE.COM"
_kerberos._udp SRV 0 0 88 zesty-bug1683237
_kerberos._tcp SRV 0 0 88 zesty-bug1683237
_kerberos-master._udp SRV 0 0 88 zesty-bug1683237
_kerberos-master._tcp SRV 0 0 88 zesty-bug1683237
_kerberos-adm._tcp SRV 0 0 749 zesty-bug1683237
_kpasswd._udp SRV 0 0 464 zesty-bug1683237
Use the real IP of your test machine/container where I used
"10.0.100.249". You can also choose another hostname if you want, just
be consistent across the board. I chose "zesty-bug1683237".
e) Restart bind
$ sudo service bind9 restart
f) Do a few quick DNS tests:
$ dig +short @10.0.100.249 zesty-bug1683237.example.com
10.0.100.249
$ dig +short @10.0.100.249 -t TXT _kerberos.example.com
"EXAMPLE.COM"
$ dig +short @10.0.100.249 -t SRV _kerberos._udp.example.com
0 0 88 zesty-bug1683237.example.com.
$ dig +short @10.0.100.249 -t SRV _kerberos._tcp.example.com
0 0 88 zesty-bug1683237.example.com.
g) Edit /etc/resolv.conf, ignoring the warning since we are not going to
reboot or change network interfaces:
nameserver 10.0.100.249 # USE YOUR IP HERE
search example.com
h) Create the EXAMPLE.COM kerberos realm:
$ sudo krb5_newrealm
When prompted for a password, use whatever you like. If you get an error
about no default realm, then your TXT record in DNS is not working. Retrace
your DNS configuration steps.
i) Start the kerberos services:
$ sudo service krb5-kdc start
sudo service krb5-admin-server start
j) Create a principal and test it:
$ sudo kadmin.local addprinc -pw ubuntu ubuntu
$ kinit ubuntu
Password for ubu...@example.com:
$ klist
(...)
05/05/2017 13:10:01 05/05/2017 23:10:01 krbtgt/example@example.com
(...)
Now we are ready to test the bug.
Given that we have udp_preference_limit = 1 in /etc/krb5.conf, kinit
should use TCP instead of UDP. L
[Touch-packages] [Bug 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
** Patch added: "init-system-helpers-xenial-lp1691474.debdiff" https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+attachment/4881468/+files/init-system-helpers-xenial-lp1691474.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1691474 Title: invoke-rc.d service start fails on services with upstart-only scripts Status in init-system-helpers package in Ubuntu: In Progress Status in init-system-helpers source package in Xenial: New Status in init-system-helpers source package in Yakkety: New Status in init-system-helpers source package in Zesty: New Bug description: [Impact] On 16.04+ if you using upstart as your primary init system "enabled" services that _only_ have upstart scripts fail to start with invoke-rc.d (with a default policy). This is problematic as #DEBHELPER# tokens in maintscripts rely on invoke-rc.d to start/stop services and fail to start services on installation. [Test Case] Boot into affected system with upstart as default init. Try starting an 'upstart only' service with 'invoke-rc.d service start'. It is expected this should work. [Regression Potential] 14.04/upstart behavior is that invoke-rc.d works, and 16.04/systemd also has invoke-rc.d start working with enabled services and default policy. 16.04/upstart should be the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+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 1689093] Re: modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04
This bug was fixed in the package apport - 2.20.1-0ubuntu2.6 --- apport (2.20.1-0ubuntu2.6) xenial; urgency=medium * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in every report. (LP: #1673557) * data/general/ubuntu-gnome.py: The GNOME3 PPAs are no longer supported for 14.04 or 16.04 so set an UnreportableReason in those reports. (LP: #1689093) * test_backend_apt_dpkg.py: Move tests from Ubuntu 15.10 "wily" (which is EoL now) to 16.04 LTS "xenial". (LP: #1690437) -- Brian Murray Fri, 12 May 2017 11:39:04 -0700 ** Changed in: apport (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: apport (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1689093 Title: modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04 Status in apport package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Released Status in apport source package in Xenial: Fix Released Bug description: Impact -- As announced, the GNOME3 PPAs for Ubuntu 16.04 LTS are no longer being maintained as of April 2017. Therefore, the Ubuntu GNOME project would like to stop receiving bugs from packages installed from those PPAs for that version, or for 14.04 LTS which is no longer supported by Ubuntu GNOME. See https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3 Test Case - sudo add-apt-repository ppa:gnome3-team/gnome3 sudo apt update sudo apt upgrade Ubuntu 14.04: ubuntu-bug gnome-system-monitor Ubuntu 16.04: ubuntu-bug nautilus What should happen: After several moments, you should see a popup with The GNOME3 PPA you are using is no longer supported for this Ubuntu release. Please run "ppa-purge ppa:gnome3-team/gnome3". Clean up: sudo apt install ppa-purge sudo ppa-purge ppa:gnome3-team/gnome3 Other Info -- Ubuntu GNOME has always installed ppa-purge by default. Regression Potential People will be unable to report bugs with PPA packages like they used to but they'll be told why. The message unfortunately likely won't be translated right away, but since it will land in the development release, it should eventually be translated for future Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689093/+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 1689344] Update Released
The verification of the Stable Release Update for apport 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1689344 Title: print of __glib_assert_msg not returning a message Status in apport package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: New Status in apport source package in Yakkety: Fix Committed Status in glib2.0 source package in Yakkety: New Status in apport source package in Zesty: Fix Released Status in glib2.0 source package in Zesty: New Bug description: [Impact] apport's test, test_add_gdb_info_abort_glib is failing due to a change somewhere in glib2.0, how its built, or gdb. The test shall be disabled while the matter is investigated. [Test Case] Run the autopkgtest and observe the failure. With the version of the package in proposed the test will not be run. [Regression Potential] We are just disabling a broken test so there is none. apport's test test_add_gdb_info_abort_glib has been failing for a bit, since zesty(?), now. Digging into this matter I discovered that using gdb to "print __glib_assert_msg" is resulting in different behavior. With the generated binary, it used to return the following: $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 < 0)" However, now I am seeing: (gdb) print __glib_assert_msg $1 = 1332592064 (gdb) print (char*) __glib_assert_msg $2 = 0x4f6dbdc0 This seems to be a regression in gdb itself, I've added an apport task though to track the disabling of the autopkgtest which utilizes this command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+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 1689093] Update Released
The verification of the Stable Release Update for apport 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1689093 Title: modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04 Status in apport package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Released Status in apport source package in Xenial: Fix Released Bug description: Impact -- As announced, the GNOME3 PPAs for Ubuntu 16.04 LTS are no longer being maintained as of April 2017. Therefore, the Ubuntu GNOME project would like to stop receiving bugs from packages installed from those PPAs for that version, or for 14.04 LTS which is no longer supported by Ubuntu GNOME. See https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3 Test Case - sudo add-apt-repository ppa:gnome3-team/gnome3 sudo apt update sudo apt upgrade Ubuntu 14.04: ubuntu-bug gnome-system-monitor Ubuntu 16.04: ubuntu-bug nautilus What should happen: After several moments, you should see a popup with The GNOME3 PPA you are using is no longer supported for this Ubuntu release. Please run "ppa-purge ppa:gnome3-team/gnome3". Clean up: sudo apt install ppa-purge sudo ppa-purge ppa:gnome3-team/gnome3 Other Info -- Ubuntu GNOME has always installed ppa-purge by default. Regression Potential People will be unable to report bugs with PPA packages like they used to but they'll be told why. The message unfortunately likely won't be translated right away, but since it will land in the development release, it should eventually be translated for future Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689093/+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 1690437] Update Released
The verification of the Stable Release Update for apport 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1690437 Title: xenial autopkgtest fails because its using an End of Life release Status in apport package in Ubuntu: Invalid Status in apport source package in Xenial: Fix Released Bug description: [Impact] A xenial autopackagetest, test_backend_apt_dpkg.py, for apport is failing because they try and get data from ddebs.ubuntu.com for an End of Life release. [Test Case] 1) Observe the autopkgtest failure "SystemError: W:The repository 'http://ddebs.ubuntu.com wily Release' does not have a Release file., W:Data from such a repository can't be authenticated and is therefore potentially dangerous to use., W:See apt-secure(8) manpage for repository creation and user configuration details., E:Failed to fetch http://ddebs.ubuntu.com/dists/wily/main/binary-armhf/Packages 404 Not Found, E:Some index files failed to download. They have been ignored, or old ones used instead." With the version of apport in -proposed their will not be an autopkgtest failure. [Regression Potential] We are switching to the version of the autopkgtest which is currently working in apport and has been working since yakkety's development. Additionally, its just a test change so there should be no regressions. Here's a link to a failure: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- xenial/xenial/amd64/a/apport/20170426_142511_fd07d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1690437/+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 1689344] Re: print of __glib_assert_msg not returning a message
This bug was fixed in the package apport - 2.20.4-0ubuntu4.1 --- apport (2.20.4-0ubuntu4.1) zesty; urgency=medium * Disable report.test_add_gdb_info_abort_glib test case for now, as the glib assertion message is broken under current Ubuntu (LP: #1689344) * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues with apt key ring. Thanks to Dimitri John Ledkov for the patch. (LP: #1651623) -- Brian Murray Wed, 10 May 2017 17:05:11 -0700 ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1689344 Title: print of __glib_assert_msg not returning a message Status in apport package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: New Status in apport source package in Yakkety: Fix Committed Status in glib2.0 source package in Yakkety: New Status in apport source package in Zesty: Fix Released Status in glib2.0 source package in Zesty: New Bug description: [Impact] apport's test, test_add_gdb_info_abort_glib is failing due to a change somewhere in glib2.0, how its built, or gdb. The test shall be disabled while the matter is investigated. [Test Case] Run the autopkgtest and observe the failure. With the version of the package in proposed the test will not be run. [Regression Potential] We are just disabling a broken test so there is none. apport's test test_add_gdb_info_abort_glib has been failing for a bit, since zesty(?), now. Digging into this matter I discovered that using gdb to "print __glib_assert_msg" is resulting in different behavior. With the generated binary, it used to return the following: $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 < 0)" However, now I am seeing: (gdb) print __glib_assert_msg $1 = 1332592064 (gdb) print (char*) __glib_assert_msg $2 = 0x4f6dbdc0 This seems to be a regression in gdb itself, I've added an apport task though to track the disabling of the autopkgtest which utilizes this command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+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 1651623] Re: adt tests fail on zesty for apport
This bug was fixed in the package apport - 2.20.4-0ubuntu4.1 --- apport (2.20.4-0ubuntu4.1) zesty; urgency=medium * Disable report.test_add_gdb_info_abort_glib test case for now, as the glib assertion message is broken under current Ubuntu (LP: #1689344) * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues with apt key ring. Thanks to Dimitri John Ledkov for the patch. (LP: #1651623) -- Brian Murray Wed, 10 May 2017 17:05:11 -0700 ** Changed in: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1651623 Title: adt tests fail on zesty for apport Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Invalid Status in apport source package in Yakkety: Fix Released Status in apport source package in Zesty: Fix Released Bug description: [Impact] Apport autopkgtests are failing with GPG errors e.g.: SystemError: W:GPG error: http://archive.ubuntu.com/ubuntu trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32, E:The repository 'http://archive.ubuntu.com/ubuntu trusty Release' is not signed. [Test Case] Run the autopkgtests and observe failures regarding GPG. With the test fixed there should be no failures. [Regression Potential] While not a regression its possible fixing these tests will reveal other failures. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+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 1673557] Update Released
The verification of the Stable Release Update for apport 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Released Status in whoopsie source package in Trusty: Fix Released Status in apport source package in Xenial: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in apport source package in Yakkety: Fix Released Status in whoopsie source package in Yakkety: Fix Released Bug description: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal With the version of apport from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. To verify the whoopsie change you'll want to do the following: 1) sudo service whoopsie stop 2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 3) kill -11 a process (but not the whoopsie one!) 4) confirm sending the report 5) Find the OOPS ID in the whoopsie output 6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID 7) Verify ProcCpuinfoMinimal appears in the OOPS [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1651623] Update Released
The verification of the Stable Release Update for apport 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1651623 Title: adt tests fail on zesty for apport Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Invalid Status in apport source package in Yakkety: Fix Released Status in apport source package in Zesty: Fix Released Bug description: [Impact] Apport autopkgtests are failing with GPG errors e.g.: SystemError: W:GPG error: http://archive.ubuntu.com/ubuntu trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32, E:The repository 'http://archive.ubuntu.com/ubuntu trusty Release' is not signed. [Test Case] Run the autopkgtests and observe failures regarding GPG. With the test fixed there should be no failures. [Regression Potential] While not a regression its possible fixing these tests will reveal other failures. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+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 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Also affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1688721 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: Confirmed Status in gnome-software package in Ubuntu: New Bug description: = Test Case = 1. Download the debian package of Chrome from google 2. Open nautilus and double-click on the file to launch ubuntu software 3. Install the package and proceed with the installation = Expected result = Chrome installs correctly = Actual result = The installation hangs on the following command in gconf2-common.postinst ucf /usr/share/gconf/default.path /etc/gconf/2/path = Original Report = I received this error when trying to install local file google-chrome-stable.deb version 58.0.3029.96-1. This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. Other times, the installation process just hangs at some percentage. I am testing this gnome-software version due to Bug (LP: #1672424). The same file was successfully installed with gdebi. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: gconf2-common:amd64: Install libgconf-2-4:amd64: Install gconf-service-backend:amd64: Install gconf-service:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat May 6 13:56:26 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-04 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1688721/+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 1689093] Re: modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04
This bug was fixed in the package apport - 2.14.1-0ubuntu3.24 --- apport (2.14.1-0ubuntu3.24) trusty; urgency=medium * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in every report. (LP: #1673557) * data/general/ubuntu-gnome.py: The GNOME3 PPAs are no longer supported for 14.04 or 16.04 so set an UnreportableReason in those reports. (LP: #1689093) -- Brian Murray Fri, 12 May 2017 12:29:08 -0700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1689093 Title: modify ubuntu-gnome hook to set UnreportableReason for 14.04 and 16.04 Status in apport package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Released Status in apport source package in Xenial: Fix Released Bug description: Impact -- As announced, the GNOME3 PPAs for Ubuntu 16.04 LTS are no longer being maintained as of April 2017. Therefore, the Ubuntu GNOME project would like to stop receiving bugs from packages installed from those PPAs for that version, or for 14.04 LTS which is no longer supported by Ubuntu GNOME. See https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3 Test Case - sudo add-apt-repository ppa:gnome3-team/gnome3 sudo apt update sudo apt upgrade Ubuntu 14.04: ubuntu-bug gnome-system-monitor Ubuntu 16.04: ubuntu-bug nautilus What should happen: After several moments, you should see a popup with The GNOME3 PPA you are using is no longer supported for this Ubuntu release. Please run "ppa-purge ppa:gnome3-team/gnome3". Clean up: sudo apt install ppa-purge sudo ppa-purge ppa:gnome3-team/gnome3 Other Info -- Ubuntu GNOME has always installed ppa-purge by default. Regression Potential People will be unable to report bugs with PPA packages like they used to but they'll be told why. The message unfortunately likely won't be translated right away, but since it will land in the development release, it should eventually be translated for future Ubuntu releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689093/+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 1690437] Re: xenial autopkgtest fails because its using an End of Life release
This bug was fixed in the package apport - 2.20.1-0ubuntu2.6 --- apport (2.20.1-0ubuntu2.6) xenial; urgency=medium * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in every report. (LP: #1673557) * data/general/ubuntu-gnome.py: The GNOME3 PPAs are no longer supported for 14.04 or 16.04 so set an UnreportableReason in those reports. (LP: #1689093) * test_backend_apt_dpkg.py: Move tests from Ubuntu 15.10 "wily" (which is EoL now) to 16.04 LTS "xenial". (LP: #1690437) -- Brian Murray Fri, 12 May 2017 11:39:04 -0700 ** Changed in: apport (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1690437 Title: xenial autopkgtest fails because its using an End of Life release Status in apport package in Ubuntu: Invalid Status in apport source package in Xenial: Fix Released Bug description: [Impact] A xenial autopackagetest, test_backend_apt_dpkg.py, for apport is failing because they try and get data from ddebs.ubuntu.com for an End of Life release. [Test Case] 1) Observe the autopkgtest failure "SystemError: W:The repository 'http://ddebs.ubuntu.com wily Release' does not have a Release file., W:Data from such a repository can't be authenticated and is therefore potentially dangerous to use., W:See apt-secure(8) manpage for repository creation and user configuration details., E:Failed to fetch http://ddebs.ubuntu.com/dists/wily/main/binary-armhf/Packages 404 Not Found, E:Some index files failed to download. They have been ignored, or old ones used instead." With the version of apport in -proposed their will not be an autopkgtest failure. [Regression Potential] We are switching to the version of the autopkgtest which is currently working in apport and has been working since yakkety's development. Additionally, its just a test change so there should be no regressions. Here's a link to a failure: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest- xenial/xenial/amd64/a/apport/20170426_142511_fd07d@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1690437/+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 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Robert, can you look please? Sounds to me like it's something to do with debconf support which you've worked on lately. The testcase in the original report was on zesty - not sure if it's still there in artful. ** Changed in: gnome-software (Ubuntu) Assignee: (unassigned) => Robert Ancell (robert-ancell) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1688721 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: Confirmed Status in gnome-software package in Ubuntu: New Bug description: = Test Case = 1. Download the debian package of Chrome from google 2. Open nautilus and double-click on the file to launch ubuntu software 3. Install the package and proceed with the installation = Expected result = Chrome installs correctly = Actual result = The installation hangs on the following command in gconf2-common.postinst ucf /usr/share/gconf/default.path /etc/gconf/2/path = Original Report = I received this error when trying to install local file google-chrome-stable.deb version 58.0.3029.96-1. This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. Other times, the installation process just hangs at some percentage. I am testing this gnome-software version due to Bug (LP: #1672424). The same file was successfully installed with gdebi. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: gconf2-common:amd64: Install libgconf-2-4:amd64: Install gconf-service-backend:amd64: Install gconf-service:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat May 6 13:56:26 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-04 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1688721/+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 1689344] Re: print of __glib_assert_msg not returning a message
This bug was fixed in the package apport - 2.20.3-0ubuntu8.3 --- apport (2.20.3-0ubuntu8.3) yakkety; urgency=medium * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues with apt key ring. Thanks to Dimitri John Ledkov for the patch. (LP: #1651623) * Disable report.test_add_gdb_info_abort_glib test case for now, as the glib assertion message is broken under current Ubuntu (LP: #1689344) * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in every report. (LP: #1673557) -- Brian Murray Wed, 10 May 2017 18:10:32 -0700 ** Changed in: apport (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1689344 Title: print of __glib_assert_msg not returning a message Status in apport package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: New Status in apport source package in Yakkety: Fix Released Status in glib2.0 source package in Yakkety: New Status in apport source package in Zesty: Fix Released Status in glib2.0 source package in Zesty: New Bug description: [Impact] apport's test, test_add_gdb_info_abort_glib is failing due to a change somewhere in glib2.0, how its built, or gdb. The test shall be disabled while the matter is investigated. [Test Case] Run the autopkgtest and observe the failure. With the version of the package in proposed the test will not be run. [Regression Potential] We are just disabling a broken test so there is none. apport's test test_add_gdb_info_abort_glib has been failing for a bit, since zesty(?), now. Digging into this matter I discovered that using gdb to "print __glib_assert_msg" is resulting in different behavior. With the generated binary, it used to return the following: $2 = 0x7fadc0 "ERROR::2:main: assertion failed (1 < 0): (1 < 0)" However, now I am seeing: (gdb) print __glib_assert_msg $1 = 1332592064 (gdb) print (char*) __glib_assert_msg $2 = 0x4f6dbdc0 This seems to be a regression in gdb itself, I've added an apport task though to track the disabling of the autopkgtest which utilizes this command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1689344/+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 1673557] Re: /proc/cpuinfo should be collected
This bug was fixed in the package whoopsie - 0.2.54.1 --- whoopsie (0.2.54.1) yakkety; urgency=medium * src/whoopsie.c: Add ProcCpuinfoMinimal which can be larger than 1KB to the list of accepted fields. (LP: #1673557) -- Brian Murray Wed, 29 Mar 2017 12:03:30 -0700 ** Changed in: whoopsie (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Released Status in whoopsie source package in Trusty: Fix Released Status in apport source package in Xenial: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in apport source package in Yakkety: Fix Released Status in whoopsie source package in Yakkety: Fix Released Bug description: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal With the version of apport from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. To verify the whoopsie change you'll want to do the following: 1) sudo service whoopsie stop 2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 3) kill -11 a process (but not the whoopsie one!) 4) confirm sending the report 5) Find the OOPS ID in the whoopsie output 6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID 7) Verify ProcCpuinfoMinimal appears in the OOPS [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1673557] Re: /proc/cpuinfo should be collected
This bug was fixed in the package whoopsie - 0.2.24.6ubuntu4 --- whoopsie (0.2.24.6ubuntu4) trusty-proposed; urgency=medium * src/whoopsie.c: Add ProcCpuinfoMinimal which can be larger than 1KB to the list of accepted fields. (LP: #1673557) -- Brian Murray Fri, 12 May 2017 10:25:00 -0700 ** Changed in: apport (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Released Status in whoopsie source package in Trusty: Fix Released Status in apport source package in Xenial: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in apport source package in Yakkety: Fix Released Status in whoopsie source package in Yakkety: Fix Released Bug description: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal With the version of apport from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. To verify the whoopsie change you'll want to do the following: 1) sudo service whoopsie stop 2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 3) kill -11 a process (but not the whoopsie one!) 4) confirm sending the report 5) Find the OOPS ID in the whoopsie output 6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID 7) Verify ProcCpuinfoMinimal appears in the OOPS [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1673557] Re: /proc/cpuinfo should be collected
This bug was fixed in the package apport - 2.20.1-0ubuntu2.6 --- apport (2.20.1-0ubuntu2.6) xenial; urgency=medium * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in every report. (LP: #1673557) * data/general/ubuntu-gnome.py: The GNOME3 PPAs are no longer supported for 14.04 or 16.04 so set an UnreportableReason in those reports. (LP: #1689093) * test_backend_apt_dpkg.py: Move tests from Ubuntu 15.10 "wily" (which is EoL now) to 16.04 LTS "xenial". (LP: #1690437) -- Brian Murray Fri, 12 May 2017 11:39:04 -0700 ** Changed in: apport (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: apport (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Released Status in whoopsie source package in Trusty: Fix Released Status in apport source package in Xenial: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in apport source package in Yakkety: Fix Released Status in whoopsie source package in Yakkety: Fix Released Bug description: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal With the version of apport from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. To verify the whoopsie change you'll want to do the following: 1) sudo service whoopsie stop 2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 3) kill -11 a process (but not the whoopsie one!) 4) confirm sending the report 5) Find the OOPS ID in the whoopsie output 6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID 7) Verify ProcCpuinfoMinimal appears in the OOPS [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1673557] Re: /proc/cpuinfo should be collected
This bug was fixed in the package apport - 2.20.3-0ubuntu8.3 --- apport (2.20.3-0ubuntu8.3) yakkety; urgency=medium * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues with apt key ring. Thanks to Dimitri John Ledkov for the patch. (LP: #1651623) * Disable report.test_add_gdb_info_abort_glib test case for now, as the glib assertion message is broken under current Ubuntu (LP: #1689344) * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in every report. (LP: #1673557) -- Brian Murray Wed, 10 May 2017 18:10:32 -0700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Released Status in whoopsie source package in Trusty: Fix Released Status in apport source package in Xenial: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in apport source package in Yakkety: Fix Released Status in whoopsie source package in Yakkety: Fix Released Bug description: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal With the version of apport from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. To verify the whoopsie change you'll want to do the following: 1) sudo service whoopsie stop 2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 3) kill -11 a process (but not the whoopsie one!) 4) confirm sending the report 5) Find the OOPS ID in the whoopsie output 6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID 7) Verify ProcCpuinfoMinimal appears in the OOPS [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1651623] Re: adt tests fail on zesty for apport
This bug was fixed in the package apport - 2.20.3-0ubuntu8.3 --- apport (2.20.3-0ubuntu8.3) yakkety; urgency=medium * Resolve autopkgtest failures in test_backend_apt_dpkg.py due to issues with apt key ring. Thanks to Dimitri John Ledkov for the patch. (LP: #1651623) * Disable report.test_add_gdb_info_abort_glib test case for now, as the glib assertion message is broken under current Ubuntu (LP: #1689344) * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in every report. (LP: #1673557) -- Brian Murray Wed, 10 May 2017 18:10:32 -0700 ** Changed in: apport (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1651623 Title: adt tests fail on zesty for apport Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: Invalid Status in apport source package in Yakkety: Fix Released Status in apport source package in Zesty: Fix Released Bug description: [Impact] Apport autopkgtests are failing with GPG errors e.g.: SystemError: W:GPG error: http://archive.ubuntu.com/ubuntu trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32, E:The repository 'http://archive.ubuntu.com/ubuntu trusty Release' is not signed. [Test Case] Run the autopkgtests and observe failures regarding GPG. With the test fixed there should be no failures. [Regression Potential] While not a regression its possible fixing these tests will reveal other failures. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/a/apport/20161214_232615_2ff4a@/log.gz fails. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1651623/+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 1673557] Re: /proc/cpuinfo should be collected
This bug was fixed in the package apport - 2.14.1-0ubuntu3.24 --- apport (2.14.1-0ubuntu3.24) trusty; urgency=medium * data/general/ubuntu.py: Collect a minimal version of /proc/cpuinfo in every report. (LP: #1673557) * data/general/ubuntu-gnome.py: The GNOME3 PPAs are no longer supported for 14.04 or 16.04 so set an UnreportableReason in those reports. (LP: #1689093) -- Brian Murray Fri, 12 May 2017 12:29:08 -0700 ** Changed in: whoopsie (Ubuntu Yakkety) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Released Status in whoopsie source package in Trusty: Fix Released Status in apport source package in Xenial: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in apport source package in Yakkety: Fix Released Status in whoopsie source package in Yakkety: Fix Released Bug description: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal With the version of apport from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. To verify the whoopsie change you'll want to do the following: 1) sudo service whoopsie stop 2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 3) kill -11 a process (but not the whoopsie one!) 4) confirm sending the report 5) Find the OOPS ID in the whoopsie output 6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID 7) Verify ProcCpuinfoMinimal appears in the OOPS [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1673557] Re: /proc/cpuinfo should be collected
This bug was fixed in the package whoopsie - 0.2.52.3 --- whoopsie (0.2.52.3) xenial-proposed; urgency=medium * src/whoopsie.c: Add ProcCpuinfoMinimal which can be larger than 1KB to the list of accepted fields. (LP: #1673557) -- Brian Murray Fri, 12 May 2017 10:21:20 -0700 ** Changed in: whoopsie (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Fix Released Status in whoopsie package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Released Status in whoopsie source package in Trusty: Fix Released Status in apport source package in Xenial: Fix Released Status in whoopsie source package in Xenial: Fix Released Status in apport source package in Yakkety: Fix Released Status in whoopsie source package in Yakkety: Fix Released Bug description: [Impact] While some apport reports contain ProcCpuinfo not all of them do and it would be useful to determine how many users can only run the i386 version of Ubuntu. Additionally, the existing implementation gathers information about every processor which is quite lengthy - something smaller would be better. [Test Case] 1. Run ubuntu-bug 2vcard 2. Observe there is no report key ProcCpuinfoMinimal With the version of apport from -proposed you will have ProcCpuinfoMinimal which will contain information about your processor. To verify the whoopsie change you'll want to do the following: 1) sudo service whoopsie stop 2) sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com whoopsie -f 3) kill -11 a process (but not the whoopsie one!) 4) confirm sending the report 5) Find the OOPS ID in the whoopsie output 6) Go to http://errors.staging.ubuntu.com/oops/$OOPSID 7) Verify ProcCpuinfoMinimal appears in the OOPS [Regression Potential] This exists in Zesty, and Artful and there have been no issues collecting the information. Even if there are errors in the general ubuntu hook, which was modified for this SRU, apport will continue collecting information for the report and just add a traceback to the report about the hook error. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+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 1679784] Re: Changing from Xorg video driver to NVIDIA driver using Software & Updates does not display debconf prompt
This bug was fixed in the package software-properties - 0.92.37.8
---
software-properties (0.92.37.8) trusty; urgency=medium
* software-properties-gtk:
- fix the backend code to set the gnome debconf frontend, without which
libgtk2-perl goes unused.
- depend on libgtk2-perl to ensure it's available, since it was not seeded
on the desktop at release time. This is only a Recommends: in zesty,
but we need to ensure this isn't ignored on upgrade.
LP: #1679784.
-- Steve Langasek Thu, 27 Apr 2017
16:28:45 -0700
** Changed in: software-properties (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1679784
Title:
Changing from Xorg video driver to NVIDIA driver using Software &
Updates does not display debconf prompt
Status in software-properties package in Ubuntu:
Fix Released
Status in software-properties source package in Trusty:
Fix Released
Status in software-properties source package in Xenial:
Fix Released
Status in software-properties source package in Yakkety:
Fix Released
Bug description:
[SRU Justification]
software-properties does not display debconf prompts. while most debconf
prompts have default answers and this is fine, for installing dkms modules on a
SecureBoot-capable system we specifically have a critical debconf prompt with
no possible default answer that users need to step through in order for their
dkms modules to be usable.
[Test case]
1. sudo apt-add-repository ppa:vorlon/debconf-tests
2. sudo apt update
3. Launch Settings -> Software & Updates -> Additional Drivers
4. Confirm that you are offered the option of using the 'noisy-fake-driver'
package.
5. Select this driver and apply changes.
6. Confirm that no debconf prompt is shown, and the driver package fails to
install ('dpkg -l noisy-fake-driver' shows 'iF').
7. Reset the package state by removing the driver again.
8. Enable -proposed.
9. Run update-manager and verify that the new software-properties package is
successfully installed from -proposed, pulling in libgtk2-perl in the process.
10. Close Software & Updates and re-launch it.
11. Select the 'noisy-fake-driver' package again.
12. Confirm that you are shown a debconf prompt, and the driver package
installs successfully.
[Regression potential]
The actual code change is small and self-contained, but the fix also requires
pulling in new package dependencies which will also need to be promoted from
universe to main in the process. We need to take extra care to ensure the
upgrade path is correct. This SRU should also be done serially one release at
a time to gather feedback at each stage.
[Original bug description]
I've encountered this repeatedly.
In the first installation -- on updating via Software Updater, this
crashed on upgrading the shim-signed package.
On suggestions from here:
I upgrade the system via CLI, i.e. dist-upgrade. This seemed to work,
however when I now try to swap the display driver, from xorg -->
nvidia. This now triggered the same issue.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
Uname: Linux 4.4.0-72-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Tue Apr 4 18:21:32 2017
DuplicateSignature:
package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
Processing triggers for shim-signed
(1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
Running in non-interactive mode, doing nothing.
dpkg: error processing package shim-signed (--configure):
subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error
exit status 1
InstallationDate: Installed on 2017-04-04 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.1
apt 1.2.19
SourcePackage: shim-signed
Title: package shim-signed 1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
failed to install/upgrade: subprocess installed post-installation script
returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1679784/+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 1692561] [NEW] Version 4.5 has beel released
Public bug reported: Version 4.5 has just been released so it would be nice to get it into the repositories some time soon: https://github.com/shadow- maint/shadow/releases/tag/4.5 ** Affects: shadow (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1692561 Title: Version 4.5 has beel released Status in shadow package in Ubuntu: New Bug description: Version 4.5 has just been released so it would be nice to get it into the repositories some time soon: https://github.com/shadow- maint/shadow/releases/tag/4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1692561/+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 1692276] Re: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
>From terminal log: dpkg: error processing package iproute2 (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692276 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in iproute2 package in Ubuntu: Incomplete Bug description: just can't install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 20 21:53:21 2017 DuplicateSignature: package:iproute2:4.3.0-1ubuntu3 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package iproute2 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-15 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1692276/+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 1692276] Re: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Thank you for taking the time to file a bug report. One of your packages is reporting that it is in an inconsistent state. This needs to be solved before you continue further operations. To help you get started please see this question and response: https://askubuntu.com/questions/148715/how-to-fix-package-is-in-a-very-bad-inconsistent-state-error Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'. However, if you believe that this is really a bug in Ubuntu, then we would be grateful if you would provide a more complete description of the problem with steps to reproduce, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: iproute2 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692276 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in iproute2 package in Ubuntu: Incomplete Bug description: just can't install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 20 21:53:21 2017 DuplicateSignature: package:iproute2:4.3.0-1ubuntu3 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package iproute2 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-15 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1692276/+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 1692217] Re: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed
>From terminal log: Dpkg: error processing iproute2 (--configure) package: The iproute2 package is not ready to be configured Can not be configured (current state 'half-installed') >From history log: Error: Sub-process /usr/bin/dpkg exited unexpectedly -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692217 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') Status in iproute2 package in Ubuntu: Incomplete Bug description: estaba actualisando ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 20 07:26:41 2017 ErrorMessage: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') InstallationDate: Installed on 2017-05-17 (2 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1692217/+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 1692561] Re: Version 4.5 has beel released
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1692561 Title: Version 4.5 has beel released Status in shadow package in Ubuntu: New Bug description: Version 4.5 has just been released so it would be nice to get it into the repositories some time soon: https://github.com/shadow- maint/shadow/releases/tag/4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1692561/+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 1692217] Re: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed
Thank you for taking the time to file a bug report. It appears that something killed dpkg while it was doing an install. I would suggest running 'sudo dpkg --configure -a' and 'sudo apt-get install -f' to determine what is left to configure. Since there is not enough information in your report to begin triage or to differentiate between a local configuration problem and a bug in Ubuntu, I am marking this bug as "Incomplete". We would be grateful if you would: provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to "New". For local configuration issues, you can find assistance here: http://www.ubuntu.com/support/community ** Changed in: iproute2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1692217 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') Status in iproute2 package in Ubuntu: Incomplete Bug description: estaba actualisando ProblemType: Package DistroRelease: Ubuntu 16.04 Package: iproute2 4.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sat May 20 07:26:41 2017 ErrorMessage: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') InstallationDate: Installed on 2017-05-17 (2 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: iproute2 Title: package iproute2 4.3.0-1ubuntu3 failed to install/upgrade: el paquete iproute2 no está listo para configurarse no se puede configurar (estado actual `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1692217/+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 1691474] Re: invoke-rc.d service start fails on services with upstart-only scripts
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1691474 Title: invoke-rc.d service start fails on services with upstart-only scripts Status in init-system-helpers package in Ubuntu: In Progress Status in init-system-helpers source package in Xenial: New Status in init-system-helpers source package in Yakkety: New Status in init-system-helpers source package in Zesty: New Bug description: [Impact] On 16.04+ if you using upstart as your primary init system "enabled" services that _only_ have upstart scripts fail to start with invoke-rc.d (with a default policy). This is problematic as #DEBHELPER# tokens in maintscripts rely on invoke-rc.d to start/stop services and fail to start services on installation. [Test Case] Boot into affected system with upstart as default init. Try starting an 'upstart only' service with 'invoke-rc.d service start'. It is expected this should work. [Regression Potential] 14.04/upstart behavior is that invoke-rc.d works, and 16.04/systemd also has invoke-rc.d start working with enabled services and default policy. 16.04/upstart should be the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1691474/+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 1692566] [NEW] package python-pkg-resources 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: I need a fix ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-pkg-resources 20.7.0-1 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 17:17:57 2017 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-21 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: python-setuptools Title: package python-pkg-resources 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-setuptools (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 python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1692566 Title: package python-pkg-resources 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-setuptools package in Ubuntu: New Bug description: I need a fix ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-pkg-resources 20.7.0-1 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 17:17:57 2017 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-21 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: python-setuptools Title: package python-pkg-resources 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1692566/+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 1176046] Re: isc-dhcp dhclient listens on extra random ports
Hi Robie, Thanks for your review/feedbacks. At the moment, there is currently an SRU for isc-dhcp via LP: #1689854 for Trusty. As soon as this SRU is successfully completed. (move to -updates). I'll start the SRU for this particular bug. - Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: In Progress Status in isc-dhcp source package in Xenial: Fix Released Status in isc-dhcp source package in Yakkety: Fix Released Bug description: [Impact] In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. The DDNS functionnality, generate 2 random extra ports between 1024-65535. Impact reported by users : "One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown." "We have software that was using one of the lower udp ports but it happened to collide with dhclient which seems to allocate 2 random ports." There is a randomization mechanism in libdns that prevent dhclient to take the sysctl values into account (net.ipv4.ip_local_port_range & net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion isc-dhcp upstream doesn't want to rely on kernel for randomization. There is no realtime configuration to disable the feature or workaround this. The only possible way is at compile time. I also talk with upstream maintainers, and there is no way they will accept to reduce the range (1024-65535) for security reason. Reducing the port range may facilitate the spoofing. Xenial has separated dhclient in two packages : isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random extra ports) The goal here is to reproduce the same situation in Trusty, for this bug to be less painful for at least users that doesn't require DDNS functionnality. [Test Case] Run a Trusty image with following package : isc-dhcp-client isc-dhcp-common ``` dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port ``` [Regression Potential] I did the split such that Trusty users will automatically get "isc- dhcp-client-ddns" installed but users bothered by this bug will have the option to switch to "isc-dhcp-client-noddns". Existing Trusty users can continue to use this DDNS functionality after the SRU without any necessary intervention. With isc-dhcp-client: dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port With isc-dhcp-client-noddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc Xenial also has both distinct dhclient binary package but in the opposite way. We have decided to use the opposite way approach for not impacting actual Trusty users by changing the nature of isc-dhcp- client itself. Caribou and I, slashd, have also tested a couple of release upgrades from Trusty to Xenial with both scenarios : 1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns" 2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns" and both scenarios worked as expected for caribou and I. (See comment #42) Results : === ** Upgrade tested with isc-dhcp-client ** # dpkg -l ii isc-dhcp-client 4.2.4-7ubuntu12.8 amd64ISC DHCP client ii isc-dhcp-common 4.2.4-7ubuntu12.8 amd64common files used by all the isc-dhcp* packages # netstat -anputa | grep -i dhclient udp0 0 0.0.0.0:20114 0.0.0.0:* 632/dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 632/dhclient udp6 0 0 :::52249:::* 632/dhclient After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2) ii isc-dhcp-client 4.3.3-5ubuntu12.7 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.3.3-5ubuntu12.7 amd64common files used by all of the isc-dhcp packages # netstat -anputa | grep -i dhclient udp0 0 0.0.0.0:68 0.0.0.0:*
[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports
> Can I confirm that by "with expected result" you mean that on Trusty->Xenial upgrade, in both cases (isc-client-dhcp installed and isc-client-dhcp-noddns installed) you end up with isc-client-dhcp installed in Xenial? yes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: In Progress Status in isc-dhcp source package in Xenial: Fix Released Status in isc-dhcp source package in Yakkety: Fix Released Bug description: [Impact] In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. The DDNS functionnality, generate 2 random extra ports between 1024-65535. Impact reported by users : "One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown." "We have software that was using one of the lower udp ports but it happened to collide with dhclient which seems to allocate 2 random ports." There is a randomization mechanism in libdns that prevent dhclient to take the sysctl values into account (net.ipv4.ip_local_port_range & net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion isc-dhcp upstream doesn't want to rely on kernel for randomization. There is no realtime configuration to disable the feature or workaround this. The only possible way is at compile time. I also talk with upstream maintainers, and there is no way they will accept to reduce the range (1024-65535) for security reason. Reducing the port range may facilitate the spoofing. Xenial has separated dhclient in two packages : isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random extra ports) The goal here is to reproduce the same situation in Trusty, for this bug to be less painful for at least users that doesn't require DDNS functionnality. [Test Case] Run a Trusty image with following package : isc-dhcp-client isc-dhcp-common ``` dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port ``` [Regression Potential] I did the split such that Trusty users will automatically get "isc- dhcp-client-ddns" installed but users bothered by this bug will have the option to switch to "isc-dhcp-client-noddns". Existing Trusty users can continue to use this DDNS functionality after the SRU without any necessary intervention. With isc-dhcp-client: dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port With isc-dhcp-client-noddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc Xenial also has both distinct dhclient binary package but in the opposite way. We have decided to use the opposite way approach for not impacting actual Trusty users by changing the nature of isc-dhcp- client itself. Caribou and I, slashd, have also tested a couple of release upgrades from Trusty to Xenial with both scenarios : 1 - Trusty upgrade to Xenial with "isc-dhcp-client-ddns" 2 - Trusty upgrade to Xenial with "isc-dhcp-client-noddns" and both scenarios worked as expected for caribou and I. (See comment #42) Results : === ** Upgrade tested with isc-dhcp-client ** # dpkg -l ii isc-dhcp-client 4.2.4-7ubuntu12.8 amd64ISC DHCP client ii isc-dhcp-common 4.2.4-7ubuntu12.8 amd64common files used by all the isc-dhcp* packages # netstat -anputa | grep -i dhclient udp0 0 0.0.0.0:20114 0.0.0.0:* 632/dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 632/dhclient udp6 0 0 :::52249:::* 632/dhclient After successful upgrade Trusty (14.04.5) -> Xenial (16.04.2) ii isc-dhcp-client 4.3.3-5ubuntu12.7 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.3.3-5ubuntu12.7 amd64common files used by all of the isc-dhcp packages # netstat -anputa | grep -i dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 633/dhclient ** Upg
[Touch-packages] [Bug 1692566] Re: package python-pkg-resources 20.7.0-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 python-setuptools in Ubuntu. https://bugs.launchpad.net/bugs/1692566 Title: package python-pkg-resources 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-setuptools package in Ubuntu: New Bug description: I need a fix ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-pkg-resources 20.7.0-1 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon May 22 17:17:57 2017 Dependencies: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-21 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: python-setuptools Title: package python-pkg-resources 20.7.0-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-setuptools/+bug/1692566/+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 1688721] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Added to Trello: https://trello.com/c/SbWAfmKA/12-bug-1688721-package- gconf2-common-3-2-6-3ubuntu7-failed-to-install-upgrade-subprocess- installed-post-installation-script-returne -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1688721 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: Confirmed Status in gnome-software package in Ubuntu: New Bug description: = Test Case = 1. Download the debian package of Chrome from google 2. Open nautilus and double-click on the file to launch ubuntu software 3. Install the package and proceed with the installation = Expected result = Chrome installs correctly = Actual result = The installation hangs on the following command in gconf2-common.postinst ucf /usr/share/gconf/default.path /etc/gconf/2/path = Original Report = I received this error when trying to install local file google-chrome-stable.deb version 58.0.3029.96-1. This is using gnome-software 3.22.7-0ubuntu3.17.04.2 from zesty-proposed. Other times, the installation process just hangs at some percentage. I am testing this gnome-software version due to Bug (LP: #1672424). The same file was successfully installed with gdebi. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 AptOrdering: gconf2-common:amd64: Install libgconf-2-4:amd64: Install gconf-service-backend:amd64: Install gconf-service:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat May 6 13:56:26 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-04 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1688721/+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 1692582] [NEW] RFE: dbus AppArmor mediation matching by message type
Public bug reported:
Suppose you're writing an AppArmor profile for a D-Bus service like
Tracker. The service might get compromised (perhaps it's network-facing)
so you don't want it to be able to act as a client of privileged
processes like systemd --user. However, imagine you do want arbitrary
third-party "apps" to be allowed to use the service if they have
appropriate rules in their own AppArmor profiles.
One reasonably natural way to encode this without tightly coupling the
service and its clients would be:
profile /usr/bin/my-service {
...
dbus send bus=session type=signal,
dbus receive bus=session type=method_call,
}
profile /usr/bin/my-client-app {
...
dbus (send,receive) bus=session peer=(label=/usr/bin/my-service),
}
However, the AppArmor integration in src:dbus and the rule parser in
src:apparmor don't allow this: they match fine-grained information like
the method name and object path, but have no concept of message types.
This seems backwards: I only expect the object path to be useful in very
rare/niche cases, but the message type is "larger" and more important
than anything else from the message payload.
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1692582
Title:
RFE: dbus AppArmor mediation matching by message type
Status in apparmor package in Ubuntu:
New
Bug description:
Suppose you're writing an AppArmor profile for a D-Bus service like
Tracker. The service might get compromised (perhaps it's network-
facing) so you don't want it to be able to act as a client of
privileged processes like systemd --user. However, imagine you do want
arbitrary third-party "apps" to be allowed to use the service if they
have appropriate rules in their own AppArmor profiles.
One reasonably natural way to encode this without tightly coupling the
service and its clients would be:
profile /usr/bin/my-service {
...
dbus send bus=session type=signal,
dbus receive bus=session type=method_call,
}
profile /usr/bin/my-client-app {
...
dbus (send,receive) bus=session peer=(label=/usr/bin/my-service),
}
However, the AppArmor integration in src:dbus and the rule parser in
src:apparmor don't allow this: they match fine-grained information
like the method name and object path, but have no concept of message
types. This seems backwards: I only expect the object path to be
useful in very rare/niche cases, but the message type is "larger" and
more important than anything else from the message payload.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1692582/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
** Changed in: aptdaemon Assignee: aden iwa rante (radeniw) => (unassigned) ** Changed in: aptdaemon (Ubuntu) Status: New => Triaged ** Changed in: debconf (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Confirmed Status in Debconf: New Status in aptdaemon package in Ubuntu: Triaged Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+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
