[Bug 1725032] [NEW] tmux failed to start, missing library
Public bug reported: Just upgraded Ubuntu from 17.04 to 17.10. tmux fails to start and the dynamic linker reports: tmux: error while loading shared libraries: libevent-2.0.so.5: cannot open shared object file: No such file or directory It looks like the tmux binary was linked against libevent 2.0 but ubuntu 17.10 only provides 2.2. ** Affects: tmux (Ubuntu) Importance: Undecided Status: New ** Description changed: - Just upgraded from 17.04 to 17.10. + Just upgraded Ubuntu from 17.04 to 17.10. tmux fails to start and the dynamic linker reports: tmux: error while loading shared libraries: libevent-2.0.so.5: cannot open shared object file: No such file or directory - It looks like the tmux binary was linked against 2.0 but ubuntu 17.10 - only provides 2.2. + It looks like the tmux binary was linked against libevent 2.0 but ubuntu + 17.10 only provides 2.2. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725032 Title: tmux failed to start, missing library To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1725032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626371] Re: cdc_ether fills kernel log
Reproduces with 4.9.0-997.201611212212 from http://kernel.ubuntu.com /~kernel-ppa/mainline/drm-intel-next/2016-11-22/ here too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626371 Title: cdc_ether fills kernel log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626371/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598759] Re: incomplete apparmor definition for ntpd
I'm the initial OP. What am I supposed to do here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598759 Title: incomplete apparmor definition for ntpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1598759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598759] [NEW] incomplete apparmor definition for ntpd
Public bug reported: On this plain install of Xenial apparmor complains about ntpd: [ 19.379152] audit: type=1400 audit(1467623330.386:27): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 20.379299] audit: type=1400 audit(1467623331.386:28): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 22.426246] audit: type=1400 audit(146762.434:29): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 22.771326] audit: type=1400 audit(146762.782:30): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 [ 23.568548] audit: type=1400 audit(1467623334.574:31): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/dbus/system_bus_socket" pid=4513 comm="ntpd" requested_mask="wr" denied_mask="wr" fsuid=121 ouid=0 Adding the following line to /etc/apparmor.d/usr.sbin.ntpd fixes the problem: #include ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Summary changed: - missing apparmor definition for ntpd + incomplete apparmor definition for ntpd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598759 Title: incomplete apparmor definition for ntpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1598759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597654] Re: Xorg crashed with SIGABRT during system resume after suspend
Ok now we have a problem. The "Apport retracing service" bot has removed all the attachments containing the details of how to investigate this bug, and nothing was produced as a result. What do we do now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597654 Title: Xorg crashed with SIGABRT during system resume after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1597654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597654] Re: Xorg crashed with SIGABRT during system resume after suspend
The bug you just linked to is invalid. ** This bug is no longer a duplicate of private bug 1557346 ** Tags added: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597654 Title: Xorg crashed with SIGABRT during system resume after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1597654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597654] Re: Xorg crashed with SIGABRT during system resume after suspend
*** This bug is a duplicate of bug 1557346 *** https://bugs.launchpad.net/bugs/1557346 Note: this crash happens *every time* after resume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597654 Title: Xorg crashed with SIGABRT during system resume after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1597654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597654] [NEW] Xorg crashed with SIGABRT during system resume after suspend
*** This bug is a duplicate of bug 1557346 *** https://bugs.launchpad.net/bugs/1557346 Public bug reported: Information attached. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: xserver-xorg-core 2:1.18.3-1ubuntu6 Uname: Linux 4.7.0-994-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 Date: Wed Jun 29 20:10:47 2016 ExecutablePath: /usr/lib/xorg/Xorg InstallationDate: Installed on 2016-03-13 (108 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () xf86VTEnter () WakeupHandler () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to yakkety on 2016-05-22 (38 days ago) UserGroups: ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash yakkety ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597654 Title: Xorg crashed with SIGABRT during system resume after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1597654/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585587] Re: Missing unix.ko in 4.6 initrd prevents LVM boot
Workaround: add "unix" and "unix_diag" to /etc/initramfs-tools/modules. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585587 Title: Missing unix.ko in 4.6 initrd prevents LVM boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1585587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585587] Re: Missing support for Unix domain sockets during boot in 4.6
Found in Ubuntu 16.10 ** Also affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Missing support for Unix domain sockets during boot in 4.6 + Missing unix.ko in 4.6 initrd prevents LVM boot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585587 Title: Missing unix.ko in 4.6 initrd prevents LVM boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1585587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585587] [NEW] Missing unix.ko in 4.6 initrd prevents LVM boot
Public bug reported: Somehow recently the default kernel config for kernel 4.6 was changed from CONFIG_UNIX=y to CONFIG_UNIX=m. This however prevents systems with full disk encryption to start properly, as the lvm encryption tools require unix sockets during set-up in the initrd. The proper fix would either be to restore CONFIG_UNIX=y or to force the unix.ko module to always be included (and loaded) in the initrd. The latter is likely to be the better approach, thus filing this against initramfs-tools. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585587 Title: Missing unix.ko in 4.6 initrd prevents LVM boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1585587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1556602] Re: LVM in 16.04 cannot mount LVM Cached Volumes created in 15.10
The suggested workaround in https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1556602/comments/8 did not work for me. What did work however was to build a modified lvm2 package using the aforementioned patch, then boot from external media, install the modified lvm2 on the externally booted ubuntu, then mount the system's main fs using the modified lvm, then install the modified lvm2 again this time on the system's fs using chroot. This process is cumbersome and I wish ubuntu would include this patch by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1556602 Title: LVM in 16.04 cannot mount LVM Cached Volumes created in 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1556602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1566759] Re: Full system lockup after attaching external monitor
The issue persists with kernel 4.6-rc4. However it disappears (fixed?) with the intel nightly drivers as of April 16th 2016 (from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm- intel-nightly/2016-04-16-wily/ ). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566759 Title: Full system lockup after attaching external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1566759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1566759] [NEW] Full system lockup after attaching external monitor
Public bug reported: Running on a recently acquired Lenovo Yoga 260. How to reproduce: 1. plug external screen 2. activate/configure monitor (either using GUI or xrandr) 3. set relative position of ext monitor to something else than the default (e.g. above or below) 4. move cursor from laptop screen to external screen 5. move cursor back from extrernal screen to laptop screen At this point a full system freeze occurs. Cannot switch to console, no kernel error (crashkernel does not activate), no trace in dmesg/Xorg.log etc. Even remote ssh sessions onto the computer freeze, so no extra information can be gathered this way. The lock-up does not occur if any of the steps above are omitted: - no issue if the external monitor is not activated - no issue if the relative position is not changed - no issue if the mouse cursor stays on the laptop screen where it was initially - no issue if the mouse cursor iis moved from the laptop screen to the external screen and stays there **Also the issue does not occur if the external monitor is already plugged before boot, and the resolution and position is only set once upon Xorg start-up**. In other words it is possible to use an external monitor as long as 1) it is plugged before boot 2) the Xorg conf contains explicit entries to set the resolution and position. The issue can be reproduced reliably on both a fresh 15.10 install, any stock Ubuntu kernel, and the mainline PPA kernels (up to and including the latest 4.6-rc2). Also reproduces reliably with both the base intel drivers shipped with 15.10 and those provided by Intel's linux- installer. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 Uname: Linux 4.6.0-040600rc2-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Apr 6 11:31:13 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since before I upgraded GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2237] InstallationDate: Installed on 2016-03-13 (23 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20FD0004US ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.6.0-040600rc2-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash intel_idle.max_cstate=1 crashkernel=384M-:200M SourcePackage: xorg Symptom: display Title: Xorg freeze UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N1GET34W (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FD0004US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1GET34W(1.11):bd11/05/2015:svnLENOVO:pn20FD0004US:pvrThinkPadYoga260:rvnLENOVO:rn20FD0004US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FD0004US dmi.product.version: ThinkPad Yoga 260 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.65+git20151026.c745e541-0ubuntu0ricotz~wily version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.4-1intel1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4-1intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.99+git20150521.d64a13eb-0ubuntu0ricotz version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151202.da9ad388-0ubuntu0sarvatt version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20150926.1ff13a92-0ubuntu0sarvatt xserver.bootTime: Wed Apr 6 11:25:42 2016 xserver.configfile: None xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1 xserver.video_driver: intel ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze third-party-packages ubuntu wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566759 Title: Full system lockup after attaching external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1566759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1566759] Re: Full system lockup after attaching external monitor
Another note: The current dmesg reports an intel driver warning: Apr 06 11:25:40 hostname kernel: WARNING: CPU: 1 PID: 6 at /home/kernel/COD/linux/drivers/gpu/drm/i915/intel_pm.c:3572 skl_update_other_pipe_wm+0x16c/0x180 [i915] followed by a stack trace. This is likely to be irrelevant to the issue: this only started to appear after upgrading to intel-provided drivers. This warning was not present just after installing Ubuntu 15.10. However the issue reported in this bug report was happening both before and after the intel driver upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566759 Title: Full system lockup after attaching external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1566759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1566759] Re: Full system lockup after attaching external monitor
Note that although the debug files mention that the kernel was booted with "intel_idle.max_cstate=1 " the issue reproduces with or without this parameter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566759 Title: Full system lockup after attaching external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1566759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
