[Touch-packages] [Bug 1608646] Re: ip4 static routes added in NetworkManager UI fail and prevent connection
I also have this issue. My PPTP connection was working fine and then I probably added some routes. And now I can't connect. Attach output from 'journalctl -u NetworkManager.service' command. ** Attachment added: "journalctl -u NetworkManager.service" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+attachment/5021227/+files/pptp_logs.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1608646 Title: ip4 static routes added in NetworkManager UI fail and prevent connection Status in network-manager package in Ubuntu: Confirmed Bug description: lsb_release -rd: Description: Ubuntu 16.04.1 LTS Release: 16.04 Network Settings package version in Software Center: 15.04.0+16.04.20160705-0ubuntu1 Prior to upgrading to 16.04 LTS I was running 14.04 LTS. Using the "Edit Connections..." menu option I had created a custom Ethernet connection that had some custom routes added. These routes are required for me to connect to certain resources on a local network while using Wifi for basic internet. (Physical network locked down, no Internet access available) I've attached a screenshot showing the routes. These routes were working great in 14.04 (And prior releases of Ubuntu). However, upon upgrading to 16.04, I noticed this connection would no longer "connect". It would just silently fail. I noticed that if I deleted my custom routes, it would work, but I need those in order to connect to my required network services. When I try to connect with the routes in place, the connection silently fails in the NetworkManager UI (I get no error message in the UI) but I took a look at syslog and found these: Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7268] platform-linux: do-add-ip4-route[2: 10.104.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7271] platform-linux: do-add-ip4-route[2: 10.105.0.0/16 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7272] platform-linux: do-add-ip4-route[2: 10.51.35.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7273] platform-linux: do-add-ip4-route[2: 10.140.76.0/24 0]: failure 101 (Network is unreachable) Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7281] device (enp0s31f6): state change: ip-config -> failed (reason 'config-failed') [70 120 4] Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7289] device (enp0s31f6): Activation: failed for connection 'Windstream' Aug 1 08:15:19 jeremy-ThinkPad-X1-Carbon-4th NetworkManager[2868]: [1470057319.7309] device (enp0s31f6): state change: failed -> disconnected (reason 'none') [120 30 0] Now, if I remove the custom routes from the UI, then I can connect. I them manually add the routes using the "ip" command: sudo /sbin/ip route add 10.104.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.105.0.0/16 dev enp0s31f6 sudo /sbin/ip route add 10.51.35.0/24 dev enp0s31f6 sudo /sbin/ip route add 10.140.76.0/24 dev enp0s31f6 This is able to add the routes successfully. So there has to be some problem in the new implementation of NetworkManager in 16.04, because these routes worked in 14.04 and they still work in 16.04 if I just manually add them from the command line. For now I can work around this issue by manually adding these routes from the command line every time I connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1608646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737479] [NEW] Xorg appears to crash on login
Public bug reported: Upon logging in, a crash report appears detailing that xorg has crashed and also that the problem report is damaged and cannot be processed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 38/28950528 files, 3863331/115784448 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Dec 10 22:21:06 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:075b] InstallationDate: Installed on 2016-12-01 (374 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9360 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed root=UUID=d9ec0f69-d5f3-4e71-ac1c-6e3c5ec32195 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0839Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd09/13/2016:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1737479 Title: Xorg appears to crash on login Status in xorg package in Ubuntu: New Bug description: Upon logging in, a crash report appears detailing that xorg has crashed and also that the problem report is damaged and cannot be processed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 BootLog: Scanning for Btrfs filesystems UBUNTU: clean, 38/28950528 files, 3863331/115784448 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Dec 10 22:21:06 2017 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:075b] InstallationDate: Installed on 2016-12-01 (374 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. Bus 001 Device 003: ID 04f3:20d0 Elan
[Touch-packages] [Bug 1612835] Re: Please remove jasper from Zesty
** Changed in: kopete (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jasper in Ubuntu. https://bugs.launchpad.net/bugs/1612835 Title: Please remove jasper from Zesty Status in digikam package in Ubuntu: Fix Released Status in jasper package in Ubuntu: Fix Released Status in kde4libs package in Ubuntu: Fix Released Status in kimageformats package in Ubuntu: Fix Released Status in kopete package in Ubuntu: Fix Released Status in digikam package in Debian: Fix Released Status in jasper package in Debian: Unknown Status in kde4libs package in Debian: Fix Released Status in kimageformats package in Debian: Fix Released Status in kopete package in Debian: Fix Released Bug description: Jasper has been removed from Debian. It would be great if jasper's source and all binary packages could be removed in Ubuntu before 17.04 is released. Jasper has a long security history and shouldn't remain, unmaintained, in universe. https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html /jasper-rm.html As of 2017-02-10, all reverse depends in Zesty have been updated to drop dependencies on jasper: $ reverse-depends -b src:jasper No reverse dependencies found == Original Report == # reverse-depends -b src:jasper Reverse-Build-Depends = * digikam (for libjasper-dev) * kde4libs (for libjasper-dev) * kimageformats (for libjasper-dev) * kopete(for libjasper-dev) The last 4 are KDE stuff. Since these packages have already removed their jasper dependency in Debian, you should be able to just copy what's already been done. February 2017 Update Here are the remaining commits from Debian that need to be applied in Ubuntu: https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=5c373d77d https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=efe65d118b https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=efad42f0186 https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=b12bc0753c7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1612835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 556372] Re: Please remove the plymouth dependency from mountall / cryptsetup
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/556372
Title:
Please remove the plymouth dependency from mountall / cryptsetup
Status in cryptsetup:
Fix Released
Status in mountall package in Ubuntu:
Won't Fix
Bug description:
Binary package hint: mountall
I noticed that mountall (and cryptsetup) depends on plymouth now.
Whatever plymouth is doing or not doing, my headless system is booting
fine without plymouth (dpkg --force-depends -P plymouth), yet all
disks (local, NFS) are mounted and cryptsetup is setting up encrypted
swap as it used to.
IMHO the "Depends: plymouth" is too hard and should be replaced with
"Recommends:" or "Suggests:" for the following reasons:
- Headless systems won't ever see what plymouth is doing ("graphical boot
animation")
- Plymouth itself depends on quite a few libraries (libdrm-*), unnecessarily
adding code to the installation- Mountall is of "Priority: required" while
plymouth is "optional". The "Depends:" makes plymouth essentially "required" as
well and cannot be uninstalled w/o --force options.
Please reconsider this dependency.
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu lucid (development branch)
Release:10.04
Codename: lucid
# dpkg -l | egrep 'mountall|cryptsetup' | cut -c1-90
ii cryptsetup
2:1.1.0~rc2-1ubuntu13
ii mountall2.10
# apt-cache show plymouth | egrep 'Vers|Depe'
Version: 0.8.1-4ubuntu1
Depends: libc6 (>= 2.8), libdrm-intel1 (>= 2.4.9), libdrm-nouveau1 (>=
2.4.11-1ubuntu1~), libdrm-radeon1 (>= 2.4.17), libdrm2 (>= 2.4.3), libplymouth2
(= 0.8.1-4ubuntu1), upstart-job, udev (>= 149-2), mountall (>= 2.0)
To manage notifications about this bug go to:
https://bugs.launchpad.net/cryptsetup/+bug/556372/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1443853] Re: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display
** Changed in: virtualbox Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/1443853 Title: Ubuntu boot in Oracle VirtualBox ends up with a corrupted display Status in Virtualbox: New Status in console-setup package in Ubuntu: Triaged Status in kbd package in Ubuntu: Triaged Status in virtualbox package in Ubuntu: Triaged Bug description: (Content copied from "Ubuntu 14.10 ISO live boot ends up with a corrupted display" #13615 VirtualBox bug ticket, by piotrjurkiewicz) Booting up live session of Ubuntu MATE 14.10 and Ubuntu Gnome 14.10 from ISO ends up with a corrupted screen. See the screenshot: https://launchpadlibrarian.net/186864347/ubu.png Switching back and forth to the tty7 (ctrl+alt+F1 and then alt+F7) fixes the display. I think that this might be a problem with resolution setting: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. ``` After switching back and forth to the tty7 (what fixes the display) the log says: ``` 00:00:31.226379 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=1152 h=400 bpp=0 cbLine=0x0, flags=0x1 00:00:31.226399 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400, Sending to async-handler.. 00:00:31.226457 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=1152x400 00:00:31.226467 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:37.584616 Display::handleDisplayResize(): uScreenId = 0, pvVRAM= w=720 h=400 bpp=0 cbLine=0x0, flags=0x1 00:01:37.584634 UIFrameBuffer::RequestResize: Screen=0, Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400, Sending to async-handler.. 00:01:37.584680 UIFrameBufferQImage::resizeEvent: Format=0, BitsPerPixel=0, BytesPerLine=0, Size=720x400 00:01:37.584692 UIFrameBufferQImage::resizeEvent: Resizing to FALLBACK buffer due to format is invalid.. 00:01:39.055475 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=0a7f w=1024 h=768 bpp=32 cbLine=0x1000, flags=0x1 00:01:39.055495 UIFrameBuffer::RequestResize: Screen=0, Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768, Sending to async-handler.. 00:01:39.09 UIFrameBufferQImage::resizeEvent: Format=843204434, BitsPerPixel=32, BytesPerLine=4096, Size=1024x768 00:01:39.055568 UIFrameBufferQImage::resizeEvent: Resizing to directly use VGA device content.. ``` I have tested 4.3.18 and also the testbuild 4.3.19 r96825, it happens on both of them. You can download the ISO images of these two systems here: https://ubuntu-mate.r.worldssl.net/download/ubuntu-mate-14.10 -desktop-amd64.iso http://cdimage.ubuntu.com/ubuntu-gnome/releases/14.10/release/ubuntu- gnome-14.10-desktop-amd64.iso To manage notifications about this bug go to: https://bugs.launchpad.net/virtualbox/+bug/1443853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 450533] Re: Build poppler with the openjpeg library / Images not showing in evince, JPX errors
*** This bug is a duplicate of bug 710412 *** https://bugs.launchpad.net/bugs/710412 ** Bug watch removed: freedesktop.org Bugzilla #15629 https://bugs.freedesktop.org/show_bug.cgi?id=15629 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/450533 Title: Build poppler with the openjpeg library / Images not showing in evince, JPX errors Status in Poppler: Won't Fix Status in poppler package in Ubuntu: Confirmed Bug description: Some Images in pdf files from google books fail to show, and generate JPX errors. According to the good folks at poppler this is due to ubuntu not using openjpeg when building poppler, and the depreciated fallback decoder failing. See http://bugs.freedesktop.org/show_bug.cgi?id=24463 ProblemType: Bug Architecture: i386 Date: Tue Oct 13 18:18:13 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: libpoppler5 0.12.0-0ubuntu1 ProcEnviron: PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-13.44-generic SourcePackage: poppler Uname: Linux 2.6.31-13-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/450533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 881407] Re: Can't display PDF with Images - Wrong Colors
*** This bug is a duplicate of bug 710412 *** https://bugs.launchpad.net/bugs/710412 ** This bug has been marked a duplicate of bug 710412 Does Not Display Graphics in PDF Files (needs to build with openjpeg) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/881407 Title: Can't display PDF with Images - Wrong Colors Status in Poppler: Unknown Status in poppler package in Ubuntu: Fix Released Bug description: Evince shows Wrong Colors in Comparison to Adobe Acrobat Reader, opening the attached PDF-Document. To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/881407/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735415] Re: VNC client does not exits after logout
Thanks for the fix!
https://github.com/CanonicalLtd/lightdm/commit/8283fc7b84e456760172f042bafc5827b6fcf29e
** Also affects: lightdm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: lightdm (Ubuntu Zesty)
Importance: Undecided
Status: New
--
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/1735415
Title:
VNC client does not exits after logout
Status in Light Display Manager:
Fix Committed
Status in lightdm package in Ubuntu:
New
Status in lightdm source package in Trusty:
New
Status in lightdm source package in Xenial:
New
Status in lightdm source package in Zesty:
New
Status in lightdm source package in Artful:
New
Status in lightdm source package in Bionic:
New
Bug description:
I have setup the remote desktop using the "[VNCServer]" configuration section.
When I log in using a VNC client and log out with the desktop panel menu,
the VNC client(remmina) does not exits.
I found that a VNC connection(TCP 5900) remains alive even though the Xvnc
server exits.
I also found the cause, GSocket instance is leaking in the "src/vnc-server.c".
static gboolean
read_cb (GSocket *socket, GIOCondition condition, VNCServer *server)
{
...
client_socket = g_socket_accept (socket, NULL, );
...
if (client_socket)
{
...
g_signal_emit (server, signals[NEW_CONNECTION], 0, client_socket);
}
return TRUE;
}
I think that "g_object_unref(client_socket)" should be called after
g_signal_emit().
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1735415/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612835] Re: Please remove jasper from Zesty
** Changed in: kde4libs (Debian) Status: Unknown => Fix Released ** Changed in: kimageformats (Debian) Status: Unknown => Fix Released ** Changed in: digikam (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jasper in Ubuntu. https://bugs.launchpad.net/bugs/1612835 Title: Please remove jasper from Zesty Status in digikam package in Ubuntu: Fix Released Status in jasper package in Ubuntu: Fix Released Status in kde4libs package in Ubuntu: Fix Released Status in kimageformats package in Ubuntu: Fix Released Status in kopete package in Ubuntu: Fix Released Status in digikam package in Debian: Fix Released Status in jasper package in Debian: Unknown Status in kde4libs package in Debian: Fix Released Status in kimageformats package in Debian: Fix Released Status in kopete package in Debian: Unknown Bug description: Jasper has been removed from Debian. It would be great if jasper's source and all binary packages could be removed in Ubuntu before 17.04 is released. Jasper has a long security history and shouldn't remain, unmaintained, in universe. https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html /jasper-rm.html As of 2017-02-10, all reverse depends in Zesty have been updated to drop dependencies on jasper: $ reverse-depends -b src:jasper No reverse dependencies found == Original Report == # reverse-depends -b src:jasper Reverse-Build-Depends = * digikam (for libjasper-dev) * kde4libs (for libjasper-dev) * kimageformats (for libjasper-dev) * kopete(for libjasper-dev) The last 4 are KDE stuff. Since these packages have already removed their jasper dependency in Debian, you should be able to just copy what's already been done. February 2017 Update Here are the remaining commits from Debian that need to be applied in Ubuntu: https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=5c373d77d https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=efe65d118b https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=efad42f0186 https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=b12bc0753c7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1612835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725333] Re: do-release-upgrade broke WSL
can we get instructions on how to fix our installs? running apt to update and upgrade returns errors and breaks because of the locale issue -- 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/1725333 Title: do-release-upgrade broke WSL Status in Gnu Bash: New Status in bash package in Ubuntu: New Bug description: I had Ubuntu 17.04 installed in WSL and decided to upgrade it to 17.10, so I had run do-release-upgrade, as I did before to upgrade to 17.04. Everything was fine before script started upgrading packages. It's started from bash updating, and somehow there is a problem revealed that locale files is missing, and locale-gen can't be run (because of bug in WSL). I've tried to install language-pack-en as was suggested, but problem haven't resolved, any attempt to update leads to this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: bash 4.4-2ubuntu1.1 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Fri Oct 20 18:03:30 2017 Dmesg: DpkgTerminalLog: Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped DuplicateSignature: package:bash:4.4-2ubuntu1.1 Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped ErrorMessage: subprocess new pre-installation script was killed by signal (Aborted), core dumped RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: bash Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnubash/+bug/1725333/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612835] Re: Please remove jasper from Zesty
** Bug watch added: Debian Bug tracker #818219 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818219 ** Also affects: digikam (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818219 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #818206 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818206 ** Also affects: kimageformats (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818206 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jasper in Ubuntu. https://bugs.launchpad.net/bugs/1612835 Title: Please remove jasper from Zesty Status in digikam package in Ubuntu: Fix Released Status in jasper package in Ubuntu: Fix Released Status in kde4libs package in Ubuntu: Fix Released Status in kimageformats package in Ubuntu: Fix Released Status in kopete package in Ubuntu: Fix Released Status in digikam package in Debian: Unknown Status in jasper package in Debian: Unknown Status in kde4libs package in Debian: Unknown Status in kimageformats package in Debian: Unknown Status in kopete package in Debian: Unknown Bug description: Jasper has been removed from Debian. It would be great if jasper's source and all binary packages could be removed in Ubuntu before 17.04 is released. Jasper has a long security history and shouldn't remain, unmaintained, in universe. https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html /jasper-rm.html As of 2017-02-10, all reverse depends in Zesty have been updated to drop dependencies on jasper: $ reverse-depends -b src:jasper No reverse dependencies found == Original Report == # reverse-depends -b src:jasper Reverse-Build-Depends = * digikam (for libjasper-dev) * kde4libs (for libjasper-dev) * kimageformats (for libjasper-dev) * kopete(for libjasper-dev) The last 4 are KDE stuff. Since these packages have already removed their jasper dependency in Debian, you should be able to just copy what's already been done. February 2017 Update Here are the remaining commits from Debian that need to be applied in Ubuntu: https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=5c373d77d https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=efe65d118b https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=efad42f0186 https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=b12bc0753c7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1612835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612835] Re: Please remove jasper from Zesty
** Also affects: jasper (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812630 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jasper in Ubuntu. https://bugs.launchpad.net/bugs/1612835 Title: Please remove jasper from Zesty Status in digikam package in Ubuntu: Fix Released Status in jasper package in Ubuntu: Fix Released Status in kde4libs package in Ubuntu: Fix Released Status in kimageformats package in Ubuntu: Fix Released Status in kopete package in Ubuntu: Fix Released Status in jasper package in Debian: Unknown Status in kde4libs package in Debian: Unknown Status in kopete package in Debian: Unknown Bug description: Jasper has been removed from Debian. It would be great if jasper's source and all binary packages could be removed in Ubuntu before 17.04 is released. Jasper has a long security history and shouldn't remain, unmaintained, in universe. https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html /jasper-rm.html As of 2017-02-10, all reverse depends in Zesty have been updated to drop dependencies on jasper: $ reverse-depends -b src:jasper No reverse dependencies found == Original Report == # reverse-depends -b src:jasper Reverse-Build-Depends = * digikam (for libjasper-dev) * kde4libs (for libjasper-dev) * kimageformats (for libjasper-dev) * kopete(for libjasper-dev) The last 4 are KDE stuff. Since these packages have already removed their jasper dependency in Debian, you should be able to just copy what's already been done. February 2017 Update Here are the remaining commits from Debian that need to be applied in Ubuntu: https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=5c373d77d https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=efe65d118b https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=efad42f0186 https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=b12bc0753c7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1612835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737463] Re: package systemd 229-4ubuntu21 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1737463 Title: package systemd 229-4ubuntu21 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Sat Dec 9 12:05:12 2017 DpkgTerminalLog: Preparing to unpack .../systemd_229-4ubuntu21_amd64.deb ... De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu21_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 DuplicateSignature: package:systemd:229-4ubuntu21 De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu21_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2017-03-30 (255 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic root=UUID=31a90691-3fd3-4160-8281-d456d0d9bd1e ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: systemd Title: package systemd 229-4ubuntu21 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.26 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.26 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.26:bd12/18/2014:svnAcer:pnAspireE5-571:pvrV1.26:rvnAcer:rnEA50_HB:rvrV1.26:cvnAcer:ct10:cvrV1.26: dmi.product.name: Aspire E5-571 dmi.product.version: V1.26 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737463/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612835] Re: Please remove jasper from Zesty
** Changed in: jasper (Ubuntu) Importance: Undecided => High ** Bug watch added: Debian Bug tracker #818205 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818205 ** Also affects: kde4libs (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818205 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #818212 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818212 ** Also affects: kopete (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818212 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jasper in Ubuntu. https://bugs.launchpad.net/bugs/1612835 Title: Please remove jasper from Zesty Status in digikam package in Ubuntu: Fix Released Status in jasper package in Ubuntu: Fix Released Status in kde4libs package in Ubuntu: Fix Released Status in kimageformats package in Ubuntu: Fix Released Status in kopete package in Ubuntu: Fix Released Status in jasper package in Debian: Unknown Status in kde4libs package in Debian: Unknown Status in kopete package in Debian: Unknown Bug description: Jasper has been removed from Debian. It would be great if jasper's source and all binary packages could be removed in Ubuntu before 17.04 is released. Jasper has a long security history and shouldn't remain, unmaintained, in universe. https://web.archive.org/web/20160402170040/https://release.debian.org/transitions/html /jasper-rm.html As of 2017-02-10, all reverse depends in Zesty have been updated to drop dependencies on jasper: $ reverse-depends -b src:jasper No reverse dependencies found == Original Report == # reverse-depends -b src:jasper Reverse-Build-Depends = * digikam (for libjasper-dev) * kde4libs (for libjasper-dev) * kimageformats (for libjasper-dev) * kopete(for libjasper-dev) The last 4 are KDE stuff. Since these packages have already removed their jasper dependency in Debian, you should be able to just copy what's already been done. February 2017 Update Here are the remaining commits from Debian that need to be applied in Ubuntu: https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=5c373d77d https://anonscm.debian.org/git/pkg-kde/applications/kde4libs.git/commit/?id=efe65d118b https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=efad42f0186 https://anonscm.debian.org/git/pkg-kde/applications/kopete.git/commit/?id=b12bc0753c7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1612835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737458] Re: package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1737458 Title: package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando Status in systemd package in Ubuntu: New Bug description: upgrade from Artful to Bionic ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-18.21-lowlatency 4.13.13 Uname: Linux 4.13.0-18-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 Date: Mon Dec 11 02:56:44 2017 ErrorMessage: los disparadores han entrado en bucle, abandonando InstallationDate: Installed on 2012-02-27 (2113 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.4rc1, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando UpgradeStatus: Upgraded to bionic on 2017-12-11 (0 days ago) dmi.bios.date: 01/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.20F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.20F:bd01/13/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737458/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737463] [NEW] package systemd 229-4ubuntu21 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2
Public bug reported: I don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Sat Dec 9 12:05:12 2017 DpkgTerminalLog: Preparing to unpack .../systemd_229-4ubuntu21_amd64.deb ... De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu21_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 DuplicateSignature: package:systemd:229-4ubuntu21 De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu21_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2017-03-30 (255 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic root=UUID=31a90691-3fd3-4160-8281-d456d0d9bd1e ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: systemd Title: package systemd 229-4ubuntu21 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.26 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.26 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.26:bd12/18/2014:svnAcer:pnAspireE5-571:pvrV1.26:rvnAcer:rnEA50_HB:rvrV1.26:cvnAcer:ct10:cvrV1.26: dmi.product.name: Aspire E5-571 dmi.product.version: V1.26 dmi.sys.vendor: Acer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1737463 Title: package systemd 229-4ubuntu21 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Sat Dec 9 12:05:12 2017 DpkgTerminalLog: Preparing to unpack .../systemd_229-4ubuntu21_amd64.deb ... De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu21_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 DuplicateSignature: package:systemd:229-4ubuntu21 De-configuring udev (225-1ubuntu9.1) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu21_amd64.deb (--unpack): subprocess installed pre-removal script returned error exit status 2 ErrorMessage: subprocess installed pre-removal script returned error exit status 2 InstallationDate: Installed on 2017-03-30 (255 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Acer Aspire E5-571 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-103-generic root=UUID=31a90691-3fd3-4160-8281-d456d0d9bd1e ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: systemd Title: package systemd 229-4ubuntu21 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_HB dmi.board.vendor: Acer dmi.board.version: V1.26 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.26 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.26:bd12/18/2014:svnAcer:pnAspireE5-571:pvrV1.26:rvnAcer:rnEA50_HB:rvrV1.26:cvnAcer:ct10:cvrV1.26: dmi.product.name: Aspire E5-571 dmi.product.version: V1.26 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737463/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737458] [NEW] package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando
Public bug reported: upgrade from Artful to Bionic ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-18.21-lowlatency 4.13.13 Uname: Linux 4.13.0-18-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 Date: Mon Dec 11 02:56:44 2017 ErrorMessage: los disparadores han entrado en bucle, abandonando InstallationDate: Installed on 2012-02-27 (2113 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.4rc1, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando UpgradeStatus: Upgraded to bionic on 2017-12-11 (0 days ago) dmi.bios.date: 01/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.20F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.20F:bd01/13/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1737458 Title: package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando Status in systemd package in Ubuntu: New Bug description: upgrade from Artful to Bionic ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-18.21-lowlatency 4.13.13 Uname: Linux 4.13.0-18-lowlatency x86_64 ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 Date: Mon Dec 11 02:56:44 2017 ErrorMessage: los disparadores han entrado en bucle, abandonando InstallationDate: Installed on 2012-02-27 (2113 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: MEDIONPC MS-7616 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-lowlatency root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.4rc1, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 235-3ubuntu2 failed to install/upgrade: los disparadores han entrado en bucle, abandonando UpgradeStatus: Upgraded to bionic on 2017-12-11 (0 days ago) dmi.bios.date: 01/13/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A7616MLN.20F dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7616 dmi.board.vendor: MEDIONPC dmi.board.version: 1.0 dmi.chassis.type: 3 dmi.chassis.vendor: MEDIONPC dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.20F:bd01/13/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: MS-7616 dmi.product.version: 1.0 dmi.sys.vendor: MEDIONPC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737458/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1023259] Re: (CVE-2012-3358) CVE-2012-3358 openjpeg: heap-based buffer overflow when processing JPEG2000 image files
** Changed in: openjpeg (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openjpeg in Ubuntu. https://bugs.launchpad.net/bugs/1023259 Title: (CVE-2012-3358) CVE-2012-3358 openjpeg: heap-based buffer overflow when processing JPEG2000 image files Status in openjpeg package in Ubuntu: Fix Released Status in openjpeg package in Debian: Fix Released Status in openjpeg package in Fedora: Fix Released Bug description: A heap-based buffer overflow was found in the way OpenJPEG, an open-source JPEG 2000 codec written in C language, performed parsing of JPEG2000 having certain number of tiles and tilesizes. A remote attacker could provide a specially crafted JPEG 2000 file, which when opened in an application linked against openjpeg would lead to that application crash, or, potentially arbitrary code execution with the privileges of the user running the application. Upstream patch: http://code.google.com/p/openjpeg/source/detail?r=1727 References: https://bugzilla.redhat.com/show_bug.cgi?id=835767 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681075 This issue has been assigned CVE-2012-3358 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjpeg/+bug/1023259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737453] Re: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1737453 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in libxml2 package in Ubuntu: New Bug description: when I update my system, it fail down and there are some errors. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.4 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Dec 11 09:14:23 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-21 (203 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 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/libxml2/+bug/1737453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737454] Re: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1737453 *** https://bugs.launchpad.net/bugs/1737453 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 #1737453, 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 1737453 package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1737454 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in libxml2 package in Ubuntu: New Bug description: when I update my system, it fail down and there are some errors. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.4 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Dec 11 09:14:23 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-21 (203 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 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/libxml2/+bug/1737454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737455] Re: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1737453 *** https://bugs.launchpad.net/bugs/1737453 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 #1737453, 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 1737453 package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1737455 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in libxml2 package in Ubuntu: New Bug description: when I update my system, it fail down and there are some errors. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.4 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Dec 11 09:14:23 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-21 (203 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 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/libxml2/+bug/1737455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737453] [NEW] package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: when I update my system, it fail down and there are some errors. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.4 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Dec 11 09:14:23 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-21 (203 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxml2 (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 libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1737453 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in libxml2 package in Ubuntu: New Bug description: when I update my system, it fail down and there are some errors. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.4 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Dec 11 09:14:23 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-21 (203 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 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/libxml2/+bug/1737453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737455] [NEW] package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1737453 *** https://bugs.launchpad.net/bugs/1737453 Public bug reported: when I update my system, it fail down and there are some errors. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.4 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Dec 11 09:14:23 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-21 (203 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxml2 (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 libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1737455 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in libxml2 package in Ubuntu: New Bug description: when I update my system, it fail down and there are some errors. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.4 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Dec 11 09:14:23 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-21 (203 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 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/libxml2/+bug/1737455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737454] [NEW] package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1737453 *** https://bugs.launchpad.net/bugs/1737453 Public bug reported: when I update my system, it fail down and there are some errors. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.4 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Dec 11 09:14:23 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-21 (203 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxml2 (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 libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1737454 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in libxml2 package in Ubuntu: New Bug description: when I update my system, it fail down and there are some errors. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python-libxml2 2.9.3+dfsg1-1ubuntu0.4 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Mon Dec 11 09:14:23 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-21 (203 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libxml2 Title: package python-libxml2 2.9.3+dfsg1-1ubuntu0.4 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/libxml2/+bug/1737454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]
i'm using ubuntu 17.10 (single boot) on a macbookpro early 2015 (12,1 model). i have the apple airpods. they work fantastic with my android phone. on linux though, it's another story. "it works" but the result is awful. useless. first, there's lot of time it is not able to connect. it fails. then i retry 5, 6 times and then it connects. when it works: audio is skipping, making long pauses, choppy sound most of the time. and i must stay close to the laptop or signal is lost. - using bluetooth headset on osx and android (both unixes) is a really good experience. they both perform really well. - using bluetooth headset on linux with pulseaudio is a terrible experience. -- 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/405294 Title: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"] Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped working properly. It was working fine in Jaunty. My headphones are detected and configured by pulse, but the audio skips as if it's spending half of each second paused. Music is buffered so that after I click stop on rhythmbox (or whatever--it happens with whatever player I use) the audio continues until it's caught up. syslog is full of the following lines: Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal latency to 1.00 ms Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 15128 us (= 2668 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36586 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 35593 us (= 6276 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 36597 us (= 6452 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32601 us (= 5748 bytes) in audio stream Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 32589 us (= 5748 bytes) in audio stream This is with bluez 4.45-0ubuntu4 pulseaudio1:0.9.15-4ubuntu2 0 pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev didn't help. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737441] Re: /usr/bin/unattended-upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string
I'm not sure what's going on here. Maybe it's deleting the cachefile twice somehow. It's just straight-forward destructors. Very odd. ** Changed in: python-apt (Ubuntu) Status: New => Triaged ** Changed in: python-apt (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1737441 Title: /usr/bin/unattended- upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string Status in python-apt package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1737441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737442] Re: /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-upgrade@1706:main:__init__:__init__:open
Various temporary problems with package lists can make u-u crash (typically in --download-only mode), but those can be handled printing an error and exiting. Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1706, in main(options) File "/usr/bin/unattended-upgrade", line 1394, in main allowed_origins=allowed_origins) File "/usr/bin/unattended-upgrade", line 119, in __init__ apt.Cache.__init__(self, rootdir=rootdir) File "/usr/lib/python3/dist-packages/apt/cache.py", line 113, in __init__ self.open(progress) File "/usr/lib/python3/dist-packages/apt/cache.py", line 164, in open self._cache = apt_pkg.Cache(progress) apt_pkg.Error: E:Encountered a section with no Package: header, E:Problem with MergeList /var/lib/apt/lists/cn.archive.ubuntu.com_ubuntu_dists_artful_universe_i18n_Translation-en, E:The package lists or status file could not be parsed or opened. ** Changed in: unattended-upgrades (Ubuntu) Status: New => In Progress ** Changed in: unattended-upgrades (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) -- 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/1737442 Title: /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended- upgrade@1706:main:__init__:__init__:open Status in unattended-upgrades package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/933de54e4841d617eb5c73ab02bb2d3be522a6ff contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1737442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737441] Re: /usr/bin/unattended-upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string
** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Changed in: unattended-upgrades (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1737441 Title: /usr/bin/unattended- upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string Status in python-apt package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1737441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737442] [NEW] /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-upgrade@1706:main:__init__:__init__:open
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/933de54e4841d617eb5c73ab02bb2d3be522a6ff contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Assignee: Balint Reczey (rbalint) Status: In Progress ** Tags: artful -- 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/1737442 Title: /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended- upgrade@1706:main:__init__:__init__:open Status in unattended-upgrades package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/933de54e4841d617eb5c73ab02bb2d3be522a6ff contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1737442/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737441] [NEW] /usr/bin/unattended-upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: Invalid ** Tags: artful xenial yakkety zesty -- 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/1737441 Title: /usr/bin/unattended- upgrade:11:__GI___libc_free:operator:__gnu_cxx::new_allocator:std::allocator_traits:std::__cxx11::basic_string Status in python-apt package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1737441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725680] Re: DNS name resolution doesn't work on Artful
I'm PXE booting 17.10 live with Serva.
I also found that the booting image DNS is broken.
I traced the problem to Casper within the booting initrd.lz, the file
/script/casper-bottom/23networking
does not populate
/etc/systemd/resolved.conf
therefore the DNS daemon does not work.
I've added to 23networking
if [ -f /root/etc/systemd/resolved.conf ]; then
resolv=/root/etc/systemd/resolved.conf
cat > $resolv <> $resolv
[ -n "$rc_server0" ] && [ "$rc_server0" != "0.0.0.0" ] && echo
"DNS=$rc_server0" >> $resolv
[ -n "$rc_server1" ] && [ "$rc_server1" != "0.0.0.0" ] && echo
"FallbackDNS=$rc_server1" >> $resolv
[ -n "$rc_server1" ] && [ "$rc_server1" = "0.0.0.0" ] && [
"$rc_server0" != "0.0.0.0" ] && echo "FallbackDNS=$rc_server0" >> $resolv
[ -n "$rc_domain" ] && echo "Domains=${rc_domain}" >> $resolv
echo "#LLMNR=yes" >> $resolv
echo "#MulticastDNS=yes" >> $resolv
echo "#DNSSEC=no" >> $resolv
echo "#Cache=yes" >> $resolv
echo "#DNSStubListener=udp" >> $resolv
fi
and now 17.10 live PXE boots correctly with a healthy DNS
Best,
Patrick
** Attachment added: "23networking"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725680/+attachment/5021036/+files/23networking
--
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/1725680
Title:
DNS name resolution doesn't work on Artful
Status in systemd package in Ubuntu:
Confirmed
Bug description:
If I boot my laptop with a live image or an installation of Ubuntu
17.10, DNS name resolution doesn't work (which means I can't access
any website).
Steps to reproduce:
- Boot laptop with Ubuntu 17.10 live image
- Connect to my wireless network
- Try to ping any website, e.g. ping ubuntu.com. This immediately fails with
the error message "Name or service not known"
- Try to ping an IP-adress, e.g. ping 8.8.8.8 : this works.
As a workaround, I can get a temporarily working DNS resolution by
manually editing /etc/resolv.conf (symlink to /run/systemd/resolve
/stub-resolve.conf) and setting the "nameserver" entry to 8.8.8.8 or
some other known DNS server.
On Ubuntu 17.04 this bug is not present.
The original address in /run/systemd/resolve/stub-resolve.conf is
127.0.0.53 . I get immediate replies if I ping this address, but
nevertheless DNS resolution doesn't work.
It seems that the service systemd-networkd isn't active by default:
$ sudo systemctl status systemd-networkd
● systemd-networkd.service - Network Service
Loaded: loaded (/lib/systemd/system/systemd-networkd.service; disabled;
vendo
Active: inactive (dead)
Docs: man:systemd-networkd.service(8)
Manually starting it doesn't seem to help for this bug.
systemd-resolved is active:
$ sudo systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled;
vendor
Active: active (running) since Sat 2017-10-21 12:13:12 UTC; 44min ago
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolved
https://www.freedesktop.org/wiki/Software/systemd/writing-network-con
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-cl
Main PID: 1095 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
CGroup: /system.slice/systemd-resolved.service
└─1095 /lib/systemd/systemd-resolved
Okt 21 12:13:12 ubuntu systemd[1]: Starting Network Name Resolution...
Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Positive Trust Anchors:
Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 19036 8 2
49aac11d7b6f644
Okt 21 12:13:12 ubuntu systemd-resolved[1095]: . IN DS 20326 8 2
e06d44b80b8f1d3
Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Negative trust anchors:
10.in-add
Okt 21 12:13:12 ubuntu systemd-resolved[1095]: Using system hostname 'ubuntu'.
Okt 21 12:13:12 ubuntu systemd[1]: Started Network Name Resolution.
Kind regards,
Jan
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CasperVersion: 1.387
Date: Sat Oct 21 12:26:00 2017
ExecutablePath: /lib/systemd/systemd-resolved
LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Acer Extensa 5635Z
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service →
[Touch-packages] [Bug 219057] Re: Bluetooth does not coexist with WiFi
bUmP -- 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/219057 Title: Bluetooth does not coexist with WiFi Status in bluez package in Ubuntu: Confirmed Bug description: On my system bluetooth and wifi are unusable together. I have a built- in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi transfers slow to a halt whenever there is BT traffic. For example, if I play a music file from another machine through the network using a BT headset, only the first few seconds of the file will play until the player runs out of buffered data. No further data is downloaded. Web pages also do not download, and I even lose connection to AP from time to time. At the same time, it looks like AFH is trying to work. If I monitor the value returned by 'hcitool afh', it changes. But this seems to have little effect on connection quality. Is this a problem with my hardware, or the AFH implementation? Is there a way to force bluetooth to not use the channels in use by WiFi? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low
** Changed in: gtk Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698270 Title: Totem pauses and stutters during video playback even when CPU usage is low Status in GTK+: Fix Released Status in totem-pl-parser: Confirmed Status in clutter-1.0 package in Ubuntu: Won't Fix Status in clutter-gtk package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: In Progress Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Totem pauses and stutters during video playback even when CPU usage is low. After figuring out how to play videos with full hardware accelerated decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses and stutters during playback. Other apps like Mplayer, VLC and even gst-play-1.0 never have this problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 12:03:18 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1605189] Re: Authentication is required for suspending the system
Another solution is to switch from lightdm to gdm or xdm, at least suspend works for me ever since I did that. -- 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/1605189 Title: Authentication is required for suspending the system Status in systemd package in Ubuntu: Confirmed Bug description: Automatic suspend from the xfce power manager does not work, as a window opens and asks for my password. Well, if it wants to suspend the system after a given timeout, I cannot enter my password as I'm not in front of my system then. Once I'm able to enter my password it is too late to run the suspend action. The window asking for my password prints: Password: Details Action: org.freedesktop.login1.suspend Vendor: The systemd project ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 21 13:13:12 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-17 (703 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 4236ML1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/ubuntu--vg-root ro intel_pstate=enable SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to xenial on 2016-05-28 (53 days ago) dmi.bios.date: 07/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236ML1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236ML1:pvrThinkPadT420:rvnLENOVO:rn4236ML1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4236ML1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1605189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737424] [NEW] [MS-7817, Realtek ALC887-VD, Green Headphone Out, Front] No sound at all
Public bug reported:
No output device detected on Sound Settings ("Play sound through" is
empty.) No sound at all.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
Uname: Linux 4.4.0-103-generic i686
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lifman 2163 F pulseaudio
CurrentDesktop: Unity
Date: Sun Dec 10 20:54:33 2017
InstallationDate: Installed on 2013-10-22 (1509 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lifman 2163 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [MS-7817, Realtek ALC887-VD, Green Headphone Out, Front] No sound at all
UpgradeStatus: Upgraded to xenial on 2017-12-09 (1 days ago)
dmi.bios.date: 12/25/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.8
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-P33 (MS-7817)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd12/25/2014:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7817
dmi.product.version: 1.0
dmi.sys.vendor: MSI
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1737424
Title:
[MS-7817, Realtek ALC887-VD, Green Headphone Out, Front] No sound at
all
Status in alsa-driver package in Ubuntu:
New
Bug description:
No output device detected on Sound Settings ("Play sound through" is
empty.) No sound at all.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98
Uname: Linux 4.4.0-103-generic i686
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lifman 2163 F pulseaudio
CurrentDesktop: Unity
Date: Sun Dec 10 20:54:33 2017
InstallationDate: Installed on 2013-10-22 (1509 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lifman 2163 F pulseaudio
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [MS-7817, Realtek ALC887-VD, Green Headphone Out, Front] No sound at
all
UpgradeStatus: Upgraded to xenial on 2017-12-09 (1 days ago)
dmi.bios.date: 12/25/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.8
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-P33 (MS-7817)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV1.8:bd12/25/2014:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnH81M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7817
dmi.product.version: 1.0
dmi.sys.vendor: MSI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1737424/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1605189] Re: Authentication is required for suspending the system
Another way that seem to fix the problem is to create a file named /etc/polkit-1/localauthority/50-local.d/enable-suspend.pkla with this content: [Enable Suspend on Idle] Identity=unix-user:* Action=org.freedesktop.login1.suspend ResultAny=auth_admin_keep ResultInactive=yes ResultActive=yes Reboot isn't seem to be required. Seem to be more secure as there is no need to disable session locking. -- 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/1605189 Title: Authentication is required for suspending the system Status in systemd package in Ubuntu: Confirmed Bug description: Automatic suspend from the xfce power manager does not work, as a window opens and asks for my password. Well, if it wants to suspend the system after a given timeout, I cannot enter my password as I'm not in front of my system then. Once I'm able to enter my password it is too late to run the suspend action. The window asking for my password prints: Password: Details Action: org.freedesktop.login1.suspend Vendor: The systemd project ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 21 13:13:12 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-17 (703 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 4236ML1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/ubuntu--vg-root ro intel_pstate=enable SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to xenial on 2016-05-28 (53 days ago) dmi.bios.date: 07/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236ML1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236ML1:pvrThinkPadT420:rvnLENOVO:rn4236ML1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4236ML1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1605189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start
** No longer affects: shorewall (Ubuntu) ** No longer affects: shorewall (Ubuntu Xenial) ** No longer affects: ipsec-tools (Ubuntu Xenial) ** No longer affects: ipsec-tools (Ubuntu) ** No longer affects: shorewall6 (Ubuntu Xenial) ** No longer affects: shorewall6 (Ubuntu) ** No longer affects: cloud-initramfs-tools (Ubuntu) ** No longer affects: cloud-initramfs-tools (Ubuntu Xenial) ** No longer affects: open-iscsi (Ubuntu Xenial) ** No longer affects: open-iscsi (Ubuntu) ** No longer affects: cloud-init (Ubuntu) ** No longer affects: cloud-init (Ubuntu Xenial) ** No longer affects: xe-guest-utilities (Ubuntu Xenial) ** No longer affects: xe-guest-utilities (Ubuntu) ** No longer affects: aoetools (Ubuntu Xenial) ** No longer affects: aoetools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in avahi package in Ubuntu: Confirmed Status in nbd package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in rpcbind package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Status in avahi source package in Xenial: New Status in nbd source package in Xenial: Triaged Status in network-manager source package in Xenial: New Status in nfs-utils source package in Xenial: New Status in rpcbind source package in Xenial: New Status in systemd source package in Xenial: New Status in util-linux source package in Xenial: New Status in nbd package in Debian: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy nbd-client nbd-client: Installed: 1:3.8-4ubuntu0.1 Candidate: 1:3.8-4ubuntu0.1 Version table: *** 1:3.8-4ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following: Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated. - Bug with NFS-server and RPC-bind is indicated by messages: $ journalctl | grep -i break ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727687] Re: systemd boots system offline ("Breaking ordering cycle by deleting job network.target/stop")
Today my system boot offline again:
dmesg | grep break
[ 4.634456] systemd[1]: sockets.target: Job sockets.target/start deleted to
break ordering cycle starting with basic.target/start
[ 4.634893] systemd[1]: acpid.path: Job acpid.path/start deleted to break
ordering cycle starting with paths.target/start
[ 4.635273] systemd[1]: NetworkManager.service: Job
NetworkManager.service/start deleted to break ordering cycle starting with
NetworkManager-wait-online.service/start
How can I help to Triage this bug? Is it related to bug 1487679?
--
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/1727687
Title:
systemd boots system offline ("Breaking ordering cycle by deleting job
network.target/stop")
Status in systemd package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. Install Ubuntu 16.04 LTS
2. Install LTSP server (dnsmasq as proxy DHCP and tftp; NBD, SSH)
3. Reboot.
4. Boot system
Expected results:
* system boots to online
Actual results:
* system boots offline; it's a security vulnerability as denial of service
Interesting messages from syslog:
Oct 19 15:25:56 server systemd[1]: network-online.target: Found ordering
cycle on network-online.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
network.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
NetworkManager.service/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
basic.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
paths.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
cups.path/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
sysinit.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
nbd-client.service/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
network-online.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Breaking ordering
cycle by deleting job network.target/stop
Oct 19 15:25:56 server systemd[1]: network.target: Job network.target/stop
deleted to break ordering cycle starting with network-online.target/stop
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu19
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
CurrentDesktop: MATE
Date: Thu Oct 26 13:50:49 2017
InstallationDate: Installed on 2016-04-21 (552 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic
root=UUID=26069a01-c072-4021-83c5-f6df23dc51d5 ro net.ifnames=0 biosdevname=0
quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/09/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FD
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A55M-DS2
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.:bvrFD:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-DS2: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/systemd/+bug/1727687/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737394] [NEW] Systemd causing shutdown to hang
Public bug reported: 1 down vote favorite I have Ubuntu 17.10 installed on a Dell XPS 15 using Nvidia proprietary drivers (384.98). The shutdown process can sometimes take up to ten minutes and sometimes not shutdown at all. I used a camera to record the shutdown messages as I couldn't see anything in the logs: wlp2s0: deauthenticating from 90:21:06:96:c2:d1 by local choice (Reason: 3=DEAUTH_LEAVING) systemd-shutdow: 33 output lines suppressed due to ratelimiting systemd-shutdown[1]: Sending SIGTERM to remaining processes... systemd-journald[332]: Received SIGTERM from PID 1 (systemd-shutdow). systemd-shutdown[1]: Sending SIGKILL to remaining processes... systemd-shutdown[1]: Unmounting file systems. systemd-shutdown[1]: Remounting '/' read-only with options 'errors=remount-ro,data=ordered'. EXT4-fs (nvme0n1p1): remounted. Opts: errors=remount-ro,data=ordered systemd-shutdown[1]: Remounting '/' read-only with options 'errors=remount-ro,data=ordered'. EXT4-fs (nvme0n1p1): remounted. Opts: errors=remount-ro,data=ordered systemd-shutdown[1]: All filesystems unmounted. systemd-shutdown[1]: Deactivating swaps. systemd-shutdown[1]: All swaps deactivated. systemd-shutdown[1]: Detaching loop devices. systemd-shutdown[1]: All loop devices detached. kvm: exiting hardware virtualization psmouse serio1: Failed to disable mouse on isa0060/serio1 reboot: Restarting system reboot: machine restart ACPI MEMORY or I/O RESET_REG. The major hang appears after wlp2s0 deauthenticates, and the first systemd-shutdow message takes up to 10 minutes to appear. Is this a systemd problem? What could be causing the 33 output lines to be suppressed? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1737394 Title: Systemd causing shutdown to hang Status in systemd package in Ubuntu: New Bug description: 1 down vote favorite I have Ubuntu 17.10 installed on a Dell XPS 15 using Nvidia proprietary drivers (384.98). The shutdown process can sometimes take up to ten minutes and sometimes not shutdown at all. I used a camera to record the shutdown messages as I couldn't see anything in the logs: wlp2s0: deauthenticating from 90:21:06:96:c2:d1 by local choice (Reason: 3=DEAUTH_LEAVING) systemd-shutdow: 33 output lines suppressed due to ratelimiting systemd-shutdown[1]: Sending SIGTERM to remaining processes... systemd-journald[332]: Received SIGTERM from PID 1 (systemd-shutdow). systemd-shutdown[1]: Sending SIGKILL to remaining processes... systemd-shutdown[1]: Unmounting file systems. systemd-shutdown[1]: Remounting '/' read-only with options 'errors=remount-ro,data=ordered'. EXT4-fs (nvme0n1p1): remounted. Opts: errors=remount-ro,data=ordered systemd-shutdown[1]: Remounting '/' read-only with options 'errors=remount-ro,data=ordered'. EXT4-fs (nvme0n1p1): remounted. Opts: errors=remount-ro,data=ordered systemd-shutdown[1]: All filesystems unmounted. systemd-shutdown[1]: Deactivating swaps. systemd-shutdown[1]: All swaps deactivated. systemd-shutdown[1]: Detaching loop devices. systemd-shutdown[1]: All loop devices detached. kvm: exiting hardware virtualization psmouse serio1: Failed to disable mouse on isa0060/serio1 reboot: Restarting system reboot: machine restart ACPI MEMORY or I/O RESET_REG. The major hang appears after wlp2s0 deauthenticates, and the first systemd-shutdow message takes up to 10 minutes to appear. Is this a systemd problem? What could be causing the 33 output lines to be suppressed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737394/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start
On next boot my system is online, but nbd-client failed: $ cat dmesg_net.txt | grep break [4.676982] systemd[1]: dbus.service: Job dbus.service/start deleted to break ordering cycle starting with NetworkManager.service/start [4.677730] systemd[1]: sockets.target: Job sockets.target/start deleted to break ordering cycle starting with NetworkManager.service/start [4.678408] systemd[1]: nbd-client.service: Job nbd-client.service/start deleted to break ordering cycle starting with NetworkManager.service/start -- 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/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: New Status in cloud-initramfs-tools package in Ubuntu: New Status in ipsec-tools package in Ubuntu: New Status in nbd package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: New Status in rpcbind package in Ubuntu: New Status in shorewall package in Ubuntu: New Status in shorewall6 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Status in xe-guest-utilities package in Ubuntu: New Status in aoetools source package in Xenial: New Status in avahi source package in Xenial: New Status in cloud-init source package in Xenial: New Status in cloud-initramfs-tools source package in Xenial: New Status in ipsec-tools source package in Xenial: New Status in nbd source package in Xenial: Triaged Status in network-manager source package in Xenial: New Status in nfs-utils source package in Xenial: New Status in open-iscsi source package in Xenial: New Status in rpcbind source package in Xenial: New Status in shorewall source package in Xenial: New Status in shorewall6 source package in Xenial: New Status in systemd source package in Xenial: New Status in util-linux source package in Xenial: New Status in xe-guest-utilities source package in Xenial: New Status in nbd package in Debian: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy nbd-client nbd-client: Installed: 1:3.8-4ubuntu0.1 Candidate: 1:3.8-4ubuntu0.1 Version table: *** 1:3.8-4ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following: Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated. - Bug with NFS-server and RPC-bind is indicated by messages: $ journalctl | grep -i break ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start
cloud-initramfs-tools is described in bug 1666573. -- 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/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: New Status in cloud-initramfs-tools package in Ubuntu: New Status in ipsec-tools package in Ubuntu: New Status in nbd package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: New Status in rpcbind package in Ubuntu: New Status in shorewall package in Ubuntu: New Status in shorewall6 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Status in xe-guest-utilities package in Ubuntu: New Status in aoetools source package in Xenial: New Status in avahi source package in Xenial: New Status in cloud-init source package in Xenial: New Status in cloud-initramfs-tools source package in Xenial: New Status in ipsec-tools source package in Xenial: New Status in nbd source package in Xenial: Triaged Status in network-manager source package in Xenial: New Status in nfs-utils source package in Xenial: New Status in open-iscsi source package in Xenial: New Status in rpcbind source package in Xenial: New Status in shorewall source package in Xenial: New Status in shorewall6 source package in Xenial: New Status in systemd source package in Xenial: New Status in util-linux source package in Xenial: New Status in xe-guest-utilities source package in Xenial: New Status in nbd package in Debian: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy nbd-client nbd-client: Installed: 1:3.8-4ubuntu0.1 Candidate: 1:3.8-4ubuntu0.1 Version table: *** 1:3.8-4ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following: Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated. - Bug with NFS-server and RPC-bind is indicated by messages: $ journalctl | grep -i break ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start
xe-guest-utilities is described in bug 1669755. ** Also affects: cloud-initramfs-tools (Ubuntu) Importance: Undecided Status: New -- 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/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: New Status in cloud-initramfs-tools package in Ubuntu: New Status in ipsec-tools package in Ubuntu: New Status in nbd package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: New Status in rpcbind package in Ubuntu: New Status in shorewall package in Ubuntu: New Status in shorewall6 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Status in xe-guest-utilities package in Ubuntu: New Status in aoetools source package in Xenial: New Status in avahi source package in Xenial: New Status in cloud-init source package in Xenial: New Status in cloud-initramfs-tools source package in Xenial: New Status in ipsec-tools source package in Xenial: New Status in nbd source package in Xenial: Triaged Status in network-manager source package in Xenial: New Status in nfs-utils source package in Xenial: New Status in open-iscsi source package in Xenial: New Status in rpcbind source package in Xenial: New Status in shorewall source package in Xenial: New Status in shorewall6 source package in Xenial: New Status in systemd source package in Xenial: New Status in util-linux source package in Xenial: New Status in xe-guest-utilities source package in Xenial: New Status in nbd package in Debian: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy nbd-client nbd-client: Installed: 1:3.8-4ubuntu0.1 Candidate: 1:3.8-4ubuntu0.1 Version table: *** 1:3.8-4ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following: Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated. - Bug with NFS-server and RPC-bind is indicated by messages: $ journalctl | grep -i break ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start
open-iscsi is described in bug 1453331. -- 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/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: New Status in cloud-initramfs-tools package in Ubuntu: New Status in ipsec-tools package in Ubuntu: New Status in nbd package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: New Status in rpcbind package in Ubuntu: New Status in shorewall package in Ubuntu: New Status in shorewall6 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Status in xe-guest-utilities package in Ubuntu: New Status in aoetools source package in Xenial: New Status in avahi source package in Xenial: New Status in cloud-init source package in Xenial: New Status in cloud-initramfs-tools source package in Xenial: New Status in ipsec-tools source package in Xenial: New Status in nbd source package in Xenial: Triaged Status in network-manager source package in Xenial: New Status in nfs-utils source package in Xenial: New Status in open-iscsi source package in Xenial: New Status in rpcbind source package in Xenial: New Status in shorewall source package in Xenial: New Status in shorewall6 source package in Xenial: New Status in systemd source package in Xenial: New Status in util-linux source package in Xenial: New Status in xe-guest-utilities source package in Xenial: New Status in nbd package in Debian: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy nbd-client nbd-client: Installed: 1:3.8-4ubuntu0.1 Candidate: 1:3.8-4ubuntu0.1 Version table: *** 1:3.8-4ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following: Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated. - Bug with NFS-server and RPC-bind is indicated by messages: $ journalctl | grep -i break ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start
ipsec-tools is described in bug 1574833. ** Also affects: shorewall (Ubuntu) Importance: Undecided Status: New ** Also affects: shorewall6 (Ubuntu) Importance: Undecided Status: New -- 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/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: New Status in cloud-initramfs-tools package in Ubuntu: New Status in ipsec-tools package in Ubuntu: New Status in nbd package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: New Status in rpcbind package in Ubuntu: New Status in shorewall package in Ubuntu: New Status in shorewall6 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Status in xe-guest-utilities package in Ubuntu: New Status in aoetools source package in Xenial: New Status in avahi source package in Xenial: New Status in cloud-init source package in Xenial: New Status in cloud-initramfs-tools source package in Xenial: New Status in ipsec-tools source package in Xenial: New Status in nbd source package in Xenial: Triaged Status in network-manager source package in Xenial: New Status in nfs-utils source package in Xenial: New Status in open-iscsi source package in Xenial: New Status in rpcbind source package in Xenial: New Status in shorewall source package in Xenial: New Status in shorewall6 source package in Xenial: New Status in systemd source package in Xenial: New Status in util-linux source package in Xenial: New Status in xe-guest-utilities source package in Xenial: New Status in nbd package in Debian: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy nbd-client nbd-client: Installed: 1:3.8-4ubuntu0.1 Candidate: 1:3.8-4ubuntu0.1 Version table: *** 1:3.8-4ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following: Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated. - Bug with NFS-server and RPC-bind is indicated by messages: $ journalctl | grep -i break ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start
shorewall is described in bug 1511869. -- 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/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: New Status in cloud-initramfs-tools package in Ubuntu: New Status in ipsec-tools package in Ubuntu: New Status in nbd package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: New Status in rpcbind package in Ubuntu: New Status in shorewall package in Ubuntu: New Status in shorewall6 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Status in xe-guest-utilities package in Ubuntu: New Status in aoetools source package in Xenial: New Status in avahi source package in Xenial: New Status in cloud-init source package in Xenial: New Status in cloud-initramfs-tools source package in Xenial: New Status in ipsec-tools source package in Xenial: New Status in nbd source package in Xenial: Triaged Status in network-manager source package in Xenial: New Status in nfs-utils source package in Xenial: New Status in open-iscsi source package in Xenial: New Status in rpcbind source package in Xenial: New Status in shorewall source package in Xenial: New Status in shorewall6 source package in Xenial: New Status in systemd source package in Xenial: New Status in util-linux source package in Xenial: New Status in xe-guest-utilities source package in Xenial: New Status in nbd package in Debian: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy nbd-client nbd-client: Installed: 1:3.8-4ubuntu0.1 Candidate: 1:3.8-4ubuntu0.1 Version table: *** 1:3.8-4ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following: Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated. - Bug with NFS-server and RPC-bind is indicated by messages: $ journalctl | grep -i break ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start
rpcbind is described in bug 1580523. ** Also affects: ipsec-tools (Ubuntu) Importance: Undecided Status: New -- 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/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: New Status in cloud-initramfs-tools package in Ubuntu: New Status in ipsec-tools package in Ubuntu: New Status in nbd package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: New Status in rpcbind package in Ubuntu: New Status in shorewall package in Ubuntu: New Status in shorewall6 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Status in xe-guest-utilities package in Ubuntu: New Status in aoetools source package in Xenial: New Status in avahi source package in Xenial: New Status in cloud-init source package in Xenial: New Status in cloud-initramfs-tools source package in Xenial: New Status in ipsec-tools source package in Xenial: New Status in nbd source package in Xenial: Triaged Status in network-manager source package in Xenial: New Status in nfs-utils source package in Xenial: New Status in open-iscsi source package in Xenial: New Status in rpcbind source package in Xenial: New Status in shorewall source package in Xenial: New Status in shorewall6 source package in Xenial: New Status in systemd source package in Xenial: New Status in util-linux source package in Xenial: New Status in xe-guest-utilities source package in Xenial: New Status in nbd package in Debian: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy nbd-client nbd-client: Installed: 1:3.8-4ubuntu0.1 Candidate: 1:3.8-4ubuntu0.1 Version table: *** 1:3.8-4ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following: Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated. - Bug with NFS-server and RPC-bind is indicated by messages: $ journalctl | grep -i break ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start
cloud-init is described in bug 1713104. ** Also affects: xe-guest-utilities (Ubuntu) Importance: Undecided Status: New -- 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/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: New Status in cloud-initramfs-tools package in Ubuntu: New Status in ipsec-tools package in Ubuntu: New Status in nbd package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: New Status in rpcbind package in Ubuntu: New Status in shorewall package in Ubuntu: New Status in shorewall6 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Status in xe-guest-utilities package in Ubuntu: New Status in aoetools source package in Xenial: New Status in avahi source package in Xenial: New Status in cloud-init source package in Xenial: New Status in cloud-initramfs-tools source package in Xenial: New Status in ipsec-tools source package in Xenial: New Status in nbd source package in Xenial: Triaged Status in network-manager source package in Xenial: New Status in nfs-utils source package in Xenial: New Status in open-iscsi source package in Xenial: New Status in rpcbind source package in Xenial: New Status in shorewall source package in Xenial: New Status in shorewall6 source package in Xenial: New Status in systemd source package in Xenial: New Status in util-linux source package in Xenial: New Status in xe-guest-utilities source package in Xenial: New Status in nbd package in Debian: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy nbd-client nbd-client: Installed: 1:3.8-4ubuntu0.1 Candidate: 1:3.8-4ubuntu0.1 Version table: *** 1:3.8-4ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following: Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated. - Bug with NFS-server and RPC-bind is indicated by messages: $ journalctl | grep -i break ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start
aoetools is affected via bug 1596178. ** Also affects: aoetools (Ubuntu) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in aoetools package in Ubuntu: New Status in avahi package in Ubuntu: Confirmed Status in cloud-init package in Ubuntu: New Status in cloud-initramfs-tools package in Ubuntu: New Status in ipsec-tools package in Ubuntu: New Status in nbd package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: New Status in rpcbind package in Ubuntu: New Status in shorewall package in Ubuntu: New Status in shorewall6 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Status in xe-guest-utilities package in Ubuntu: New Status in aoetools source package in Xenial: New Status in avahi source package in Xenial: New Status in cloud-init source package in Xenial: New Status in cloud-initramfs-tools source package in Xenial: New Status in ipsec-tools source package in Xenial: New Status in nbd source package in Xenial: Triaged Status in network-manager source package in Xenial: New Status in nfs-utils source package in Xenial: New Status in open-iscsi source package in Xenial: New Status in rpcbind source package in Xenial: New Status in shorewall source package in Xenial: New Status in shorewall6 source package in Xenial: New Status in systemd source package in Xenial: New Status in util-linux source package in Xenial: New Status in xe-guest-utilities source package in Xenial: New Status in nbd package in Debian: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy nbd-client nbd-client: Installed: 1:3.8-4ubuntu0.1 Candidate: 1:3.8-4ubuntu0.1 Version table: *** 1:3.8-4ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following: Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated. - Bug with NFS-server and RPC-bind is indicated by messages: $ journalctl | grep -i break ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717459] Re: Ubuntu Xenial: Job local-fs.target/start deleted to break ordering cycle starting with networking.service/start
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) 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/1717459 Title: Ubuntu Xenial: Job local-fs.target/start deleted to break ordering cycle starting with networking.service/start Status in systemd package in Ubuntu: Confirmed Bug description: It looks that there is a cyclic dependency in some of the systemd services: see log. The VM was created some hours ago using the latest packages. I'm not really sure if this is a problem with systemd - if not maybe somebody can point me to the buggy package. === Version Info === root@ubuntuvm:~# uname -a Linux ubuntuvm 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@ubuntuvm:~# dpkg -l | grep systemd ii libsystemd0:amd64 229-4ubuntu19 amd64systemd utility library ii systemd229-4ubuntu19 amd64system and service manager ii systemd-sysv 229-4ubuntu19 amd64system and service manager - SysV links root@ubuntuvm:~# dpkg -l | grep cloud-init ii cloud-init 0.7.9-233-ge586fe35-0ubuntu1~16.04.1 all Init scripts for cloud instances root@ubuntuvm:~# dpkg -l | grep lvm2 ii liblvm2app2.2:amd642.02.133-1ubuntu10 amd64LVM2 application library ii liblvm2cmd2.02:amd64 2.02.133-1ubuntu10 amd64LVM2 command library ii lvm2 2.02.133-1ubuntu10 amd64Linux Logical Volume Manager === LOG === Please note that 'opt' is one of the LVs. Depending on the boot this is replaced e.g. with 'home'. Sep 15 09:41:11 ubuntuvm systemd[1]: networking.service: Found ordering cycle on networking.service/start Sep 15 09:41:11 ubuntuvm systemd[1]: networking.service: Found dependency on local-fs.target/start Sep 15 09:41:11 ubuntuvm systemd[1]: networking.service: Found dependency on opt.mount/start Sep 15 09:41:11 ubuntuvm systemd[1]: networking.service: Found dependency on systemd-fsck@dev-mapper-sysvg\x2dopt_vol.service/start Sep 15 09:41:11 ubuntuvm systemd[1]: networking.service: Found dependency on cloud-init.service/start Sep 15 09:41:11 ubuntuvm systemd[1]: networking.service: Found dependency on networking.service/start Sep 15 09:41:11 ubuntuvm systemd[1]: networking.service: Breaking ordering cycle by deleting job local-fs.target/start Sep 15 09:41:11 ubuntuvm systemd[1]: local-fs.target: Job local-fs.target/start deleted to break ordering cycle starting with networking.service/start Sep 15 09:41:11 ubuntuvm systemd[1]: cloud-init-local.service: Found ordering cycle on cloud-init-local.service/start Sep 15 09:41:11 ubuntuvm systemd[1]: cloud-init-local.service: Found dependency on var.mount/start Sep 15 09:41:11 ubuntuvm systemd[1]: cloud-init-local.service: Found dependency on systemd-fsck@dev-mapper-sysvg\x2dvar_vol.service/start Sep 15 09:41:11 ubuntuvm systemd[1]: cloud-init-local.service: Found dependency on cloud-init.service/start Sep 15 09:41:11 ubuntuvm systemd[1]: cloud-init-local.service: Found dependency on networking.service/start Sep 15 09:41:11 ubuntuvm systemd[1]: cloud-init-local.service: Found dependency on network-pre.target/start Sep 15 09:41:11 ubuntuvm systemd[1]: cloud-init-local.service: Found dependency on cloud-init-local.service/start Sep 15 09:41:11 ubuntuvm systemd[1]: cloud-init-local.service: Breaking ordering cycle by deleting job cloud-init.service/start Sep 15 09:41:11 ubuntuvm systemd[1]: cloud-init.service: Job cloud-init.service/start deleted to break ordering cycle starting with cloud-init-local.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727687] Re: systemd boots system offline ("Breaking ordering cycle by deleting job network.target/stop")
Possibly duplicate of bug 1487679.
--
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/1727687
Title:
systemd boots system offline ("Breaking ordering cycle by deleting job
network.target/stop")
Status in systemd package in Ubuntu:
New
Bug description:
Steps to reproduce:
1. Install Ubuntu 16.04 LTS
2. Install LTSP server (dnsmasq as proxy DHCP and tftp; NBD, SSH)
3. Reboot.
4. Boot system
Expected results:
* system boots to online
Actual results:
* system boots offline; it's a security vulnerability as denial of service
Interesting messages from syslog:
Oct 19 15:25:56 server systemd[1]: network-online.target: Found ordering
cycle on network-online.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
network.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
NetworkManager.service/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
basic.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
paths.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
cups.path/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
sysinit.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
nbd-client.service/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Found dependency on
network-online.target/stop
Oct 19 15:25:56 server systemd[1]: network-online.target: Breaking ordering
cycle by deleting job network.target/stop
Oct 19 15:25:56 server systemd[1]: network.target: Job network.target/stop
deleted to break ordering cycle starting with network-online.target/stop
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu19
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
CurrentDesktop: MATE
Date: Thu Oct 26 13:50:49 2017
InstallationDate: Installed on 2016-04-21 (552 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic
root=UUID=26069a01-c072-4021-83c5-f6df23dc51d5 ro net.ifnames=0 biosdevname=0
quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/09/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FD
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: F2A55M-DS2
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.:bvrFD:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-DS2: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/systemd/+bug/1727687/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487679] Re: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start
Guys I can't completely understand why you are ignoring this bug. Today my system boot offline again: dmesg | grep break [4.634456] systemd[1]: sockets.target: Job sockets.target/start deleted to break ordering cycle starting with basic.target/start [4.634893] systemd[1]: acpid.path: Job acpid.path/start deleted to break ordering cycle starting with paths.target/start [4.635273] systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with NetworkManager-wait-online.service/start Does Ubuntu is really enterprise-grade OS? -- 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/1487679 Title: CRITICAL BUG: Breaking ordering cycle by deleting job NetworkManager.service/start Status in systemd: Fix Released Status in avahi package in Ubuntu: Confirmed Status in nbd package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Won't Fix Status in nfs-utils package in Ubuntu: Confirmed Status in open-iscsi package in Ubuntu: New Status in rpcbind package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Status in avahi source package in Xenial: New Status in nbd source package in Xenial: Triaged Status in network-manager source package in Xenial: New Status in nfs-utils source package in Xenial: New Status in open-iscsi source package in Xenial: New Status in rpcbind source package in Xenial: New Status in systemd source package in Xenial: New Status in util-linux source package in Xenial: New Status in nbd package in Debian: Fix Released Bug description: $ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 $ apt-cache policy nbd-client nbd-client: Installed: 1:3.8-4ubuntu0.1 Candidate: 1:3.8-4ubuntu0.1 Version table: *** 1:3.8-4ubuntu0.1 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ vivid-security/main amd64 Packages 100 /var/lib/dpkg/status 1:3.8-4 0 500 http://ch.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages I'm using the nbd-client to mount some raw disk images over the network but starting the nbd-client automatically during bootup does not happen due to the following: Aug 22 08:54:20 fractal kernel: [ 11.875885] systemd[1]: Found dependency on nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875890] systemd[1]: Breaking ordering cycle by deleting job nbd-client.service/start Aug 22 08:54:20 fractal kernel: [ 11.875891] systemd[1]: Job nbd-client.service/start deleted to break ordering cycle starting with basic.target/start Meaning after boot, I have to manually run `sudo ndb-client start` every time I want to access these images. Note that this is no diskless system, the images I mount via NBD do not contain the local system, they are totally unrelated. - Bug with NFS-server and RPC-bind is indicated by messages: $ journalctl | grep -i break ноя 06 22:49:57 norbert-vaio systemd[1]: network.target: Breaking ordering cycle by deleting job NetworkManager.service/start ноя 06 22:49:57 norbert-vaio systemd[1]: NetworkManager.service: Job NetworkManager.service/start deleted to break ordering cycle starting with network.target/start ноя 06 22:49:57 norbert-vaio systemd[1]: nfs-server.service: Breaking ordering cycle by deleting job rpcbind.socket/start ноя 06 22:49:57 norbert-vaio systemd[1]: rpcbind.socket: Job rpcbind.socket/start deleted to break ordering cycle starting with nfs-server.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1487679/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737046] Re: Razer Naga Chroma wheel tilt being remapped to vertical scroll
Reuben Lifshay, to clarify, what happens when you switch from libinput to evdev in the daily image? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1737046 Title: Razer Naga Chroma wheel tilt being remapped to vertical scroll Status in xorg package in Ubuntu: Incomplete Bug description: My Razer Naga Chroma's wheel tilt right and left (buttons 6, and 7) are being remapped to scroll up and down (buttons 4, and 5) as per xev. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 BootLog: Scanning for Btrfs filesystems Ubuntu: clean, 394556/11829248 files, 20977988/47286784 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Dec 7 14:25:33 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1303] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986: Acer, Inc Bus 001 Device 004: ID 1532:0053 Razer USA, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=4bf03301-9454-4893-8590-722b1fa2efa7 ro quiet splash crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04nRSA dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp2 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04nRSA:bd04/26/2017:svnSystem76:pnGalagoPro:pvrgalp2:rvnSystem76:rnGalagoPro:rvrgalp2:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.version: galp2 dmi.sys.vendor: System76 version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.80-1~xenial version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 7 14:21:19 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1737046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
