[Bug 1526345] Re: *bird themes break adress autocompletion in thunderbird
> Could you confirm that this is no longer a problem and that we can close the ticket? Yep, no problem anymore. ** Changed in: shimmer-themes (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526345 Title: *bird themes break adress autocompletion in thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shimmer-themes/+bug/1526345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 601897] Re: Retention policy "Delete all but the most recent xx messages" deletes most recent messages.
This is indeed no longer a problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/601897 Title: Retention policy "Delete all but the most recent xx messages" deletes most recent messages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/601897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623385] Re: Suspend on lid close can not be configured individually for battery/AC
*** This bug is a duplicate of bug 1471979 *** https://bugs.launchpad.net/bugs/1471979 ** This bug has been marked a duplicate of bug 1471979 Laptop lid setting on AC ignored -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623385 Title: Suspend on lid close can not be configured individually for battery/AC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1623385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686084] Re: x11vnc on zesty terminates with **stack smashing detected** error
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686084 Title: x11vnc on zesty terminates with **stack smashing detected** error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11vnc/+bug/1686084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475620] Re: grub-common does not unset "recordfail" on hibernate when using systemd
** Tags added: artful bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475620 Title: grub-common does not unset "recordfail" on hibernate when using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1475620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532180] Re: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-change for https://
This issue is fixed in bionic due to the switch to amarok 2.9.0 (which contains respective commits). ** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532180 Title: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API- change for https:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1532180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743314] Re: Complete system freeze while resuming from hibernation
The issue remains when using the proposed kernel 4.13.0-29-generic. It does not happen with the mainline kernels 4.13.16 and 4.14.13. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743314 Title: Complete system freeze while resuming from hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743314] [NEW] Complete system freeze while resuming from hibernation
Public bug reported: Since the update to kernel 4.13.0-25-generic hibernation is broken: the system freezes while resuming somewhat after having loaded the hibernation image. Reverting to the previous kernel (4.13.0-21-generic) allows to resume without any problems. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-25-generic 4.13.0-25.29 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kiran 1152 F pulseaudio /dev/snd/controlC0: kiran 1152 F pulseaudio CurrentDesktop: XFCE Date: Mon Jan 15 08:45:32 2018 HibernationDevice: RESUME=UUID=5ea8b83e-6f6f-4e44-98f6-45ade2c2d6c3 InstallationDate: Installed on 2013-11-16 (1520 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) IwConfig: p2p1 no wireless extensions. lono wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=UUID=4fee8160-326f-4688-a0d9-22e158e70f45 ro quiet RelatedPackageVersions: linux-restricted-modules-4.13.0-25-generic N/A linux-backports-modules-4.13.0-25-generic N/A linux-firmware 1.169.1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-12-01 (44 days ago) dmi.bios.date: 07/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-G dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743314 Title: Complete system freeze while resuming from hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686084] Re: x11vnc on zesty terminates with **stack smashing detected** error
** Tags added: artful zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686084 Title: x11vnc on zesty terminates with **stack smashing detected** error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11vnc/+bug/1686084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664389] Re: Power manager setting not applied
> ... When laptop lid is closed: switch off display. Did you configure different actions for battery/AC? If so, you probably ran into this bug: https://bugs.launchpad.net/ubuntu/+source/xfce4 -power-manager/+bug/1623385 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664389 Title: Power manager setting not applied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1664389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676484] Re: digikam 5.4 lacks audio/video support due to unavailable QtAV libraries
** Tags added: artful ** Summary changed: - digikam 5.4 lacks audio/video support due to unavailable QtAV libraries + digikam > 5.3 lacks audio/video support due to unavailable QtAV libraries -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676484 Title: digikam > 5.3 lacks audio/video support due to unavailable QtAV libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1676484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532180] Re: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-change for https://
Corresponding report on the debian bug tracker: https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=851945 ** Bug watch added: Debian Bug tracker #851945 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851945 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532180 Title: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API- change for https:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1532180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475620] Re: grub-common does not unset "recordfail" on hibernate when using systemd
Attached an alternative service file which unsets recordfail directly via grub-editenv. ** Attachment added: "grub-unset-recordfail.service" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1475620/+attachment/4864149/+files/grub-unset-recordfail.service ** Tags added: zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475620 Title: grub-common does not unset "recordfail" on hibernate when using systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1475620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676484] [NEW] digikam 5.4 lacks audio/video support due to unavailable QtAV libraries
Public bug reported: Since version 5.4 digikam uses the QtAV framework[1] to handle audio/video files[2]. Since qtav is currently not packaged in ubuntu (nor in debian, although there is an ITP [3]) digikam is unable to handle any audio or video files. This is a regression because video/audio playback did work (mostly) in previous versions. [1] http://www.qtav.org/ [2] https://www.digikam.org/node/764 [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737016 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: digikam 4:5.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 27 16:53:02 2017 InstallationDate: Installed on 2016-09-25 (183 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: digikam UpgradeStatus: Upgraded to zesty on 2017-03-27 (0 days ago) ** Affects: digikam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Description changed: Since version 5.4 digikam uses the QtAV framework[1] to handle audio/video files[2]. Since qtav is currently not packaged in ubuntu (nor in debian, although there is an ITP [3]) digikam is unable to handle any audio or video files. This is a regression because video/audio playback did work (mostly) in previous versions. - [1] http://www.qtav.org/ [2] https://www.digikam.org/node/764 - [ITP] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737016 + [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737016 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: digikam 4:5.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Mar 27 16:53:02 2017 InstallationDate: Installed on 2016-09-25 (183 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: digikam UpgradeStatus: Upgraded to zesty on 2017-03-27 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676484 Title: digikam 5.4 lacks audio/video support due to unavailable QtAV libraries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1676484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532180] Re: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-change for https://
** Tags added: zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532180 Title: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API- change for https:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1532180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655659] [NEW] Qt5Agg backend can't be used
Public bug reported: The current version from yakkety (1.5.2~rc2-1) does not work with pyqt5. Trying to plot to the Qt5Agg backend raises the following error: QObject::connect: Cannot connect NavigationToolbar2QT::message(QString) to (null)::_show_message() Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/matplotlib/pyplot.py", line 3146, in plot ax = gca() File "/usr/lib/python3/dist-packages/matplotlib/pyplot.py", line 928, in gca return gcf().gca(**kwargs) File "/usr/lib/python3/dist-packages/matplotlib/pyplot.py", line 578, in gcf return figure() File "/usr/lib/python3/dist-packages/matplotlib/pyplot.py", line 527, in figure **kwargs) File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_qt5agg.py", line 43, in new_figure_manager return new_figure_manager_given_figure(num, thisFig) File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_qt5agg.py", line 51, in new_figure_manager_given_figure return FigureManagerQT(canvas, num) File "/usr/lib/python3/dist-packages/matplotlib/backends/backend_qt5.py", line 465, in __init__ self.toolbar.message.connect(self._show_message) TypeError: connect() failed between NavigationToolbar2QT.message[str] and _show_message() This bug is fixed upstream and was backported to 1.5.x (https://github.com/matplotlib/matplotlib/pull/6854). It is also fixed in debian testing (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=835455). ** Affects: matplotlib (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/1655659 Title: Qt5Agg backend can't be used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matplotlib/+bug/1655659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 573524] Re: mtpfs : "Transport endpoint is not connected"
** Tags added: trusty yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/573524 Title: mtpfs : "Transport endpoint is not connected" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtpfs/+bug/573524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1377585] Re: Very slow listing and scrolling a PTP connected photo directory.
I believe this is related to thumbnail handling. It seems that thunar recreates the thumbnails on every scroll event. So if one disables 'Show thumbnails' in the preferences, scrolling is very fast. This behavior is also found for mtp connections. Upstream report: https://bugzilla.xfce.org/show_bug.cgi?id=12111 ** Bug watch added: Xfce Bugzilla #12111 https://bugzilla.xfce.org/show_bug.cgi?id=12111 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377585 Title: Very slow listing and scrolling a PTP connected photo directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1377585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623385] Re: Suspend on lid close can not be configured individually for battery/AC
Upstream report: https://bugzilla.xfce.org/show_bug.cgi?id=12756 ** Bug watch added: Xfce Bugzilla #12756 https://bugzilla.xfce.org/show_bug.cgi?id=12756 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623385 Title: Suspend on lid close can not be configured individually for battery/AC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1623385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623385] Re: Suspend on lid close can not be configured individually for battery/AC
As suspected its caused by the light-locker integration. More specifically by xfpm_update_logind_handle_lid_switch in xfpm-settings.c: logind-handle-lid-switch = true when: lock_on_suspend == true and (lid_switch_on_ac == suspend or lid_switch_on_battery == suspend) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623385 Title: Suspend on lid close can not be configured individually for battery/AC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1623385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623385] Re: Suspend on lid close can not be configured individually for battery/AC
This also happens on yakkety (well, its same version). In both cases it requires the 'Lock screen when system is going to sleep' option to be set. ** Tags added: xenial yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623385 Title: Suspend on lid close can not be configured individually for battery/AC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1623385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532180] Re: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-change for https://
** Tags added: yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532180 Title: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API- change for https:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1532180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618903] Re: System crashes after resume from hibernate
I should mention I'm running v4.8-rc3 from mainline. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618903 Title: System crashes after resume from hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618903] Re: System crashes after resume from hibernate
20d uptime, about 100 hibernate/resume cycles and no crash, so its definitively fixed in later kernels. ** Tags added: kernel-fixed-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618903 Title: System crashes after resume from hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1475620] Re: hibernate / resume works, but triggers recordfail & grub menu
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475620 Title: hibernate / resume works, but triggers recordfail & grub menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1475620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1623385] [NEW] Suspend on lid close can not be configured individually for battery/AC
Public bug reported: Xfce power-manager allows to configure individual actions for the lid close event for battery and AC mode. However, if one is set to suspend the system suspends always despite it might be configured otherwise for the current state. I believe this happens because xfpm unconditionally removes the handle- lid-switch inhibitor. Instead xfpm should check the power mode (battery/AC) and only remove the inhibitor if it is actually configured to do so for the current power mode. Of course this check must be repeated on every change of the power mode. Test case: On eg. AC mode set the lid close action for battery mode to suspend and for AC mode to eg. lock screen. systemd-inhibit --list shows that the handle-lid-switch inhibitor is removed. Closing the lid in AC mode consequently lets logind handle the event, which defaults to suspend. I get this on all up-to-date xubuntu 16.04 installations. ** Affects: xfce4-power-manager (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/1623385 Title: Suspend on lid close can not be configured individually for battery/AC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1623385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618903] [NEW] System crashes after resume from hibernate
Public bug reported: kernels 4.4 crash reliably after almost every resume from hibernate. One system log I could save reported: Aug 31 15:24:37 yo sshd[2620]: Server listening on :: port 810. Aug 31 15:24:40 yo kernel: general protection fault: [#2] SMP Aug 31 15:24:40 yo kernel: Modules linked in: binfmt_misc usblp joydev input_leds eeepc_wmi intel_rapl asus_wmi x86_pkg_temp_thermal sparse_ Aug 31 15:24:40 yo kernel: CPU: 3 PID: 3355 Comm: xfsettingsd Tainted: G D 4.4.0-36-generic #55-Ubuntu Aug 31 15:24:40 yo kernel: Hardware name: ASUS All Series/B85M-G, BIOS 2501 07/22/2015 Aug 31 15:24:40 yo kernel: task: 880211bfa940 ti: 88021197 task.ti: 88021197 Aug 31 15:24:40 yo kernel: RIP: 0010:[] [] down_write+0x1f/0x40 Aug 31 15:24:40 yo kernel: RSP: 0018:880211973dd0 EFLAGS: 00010246 Aug 31 15:24:40 yo kernel: RAX: 00e700e60028 RBX: 00e700e60028 RCX: Aug 31 15:24:40 yo kernel: RDX: 0001 RSI: 81a11c80 RDI: 00e700e60028 Aug 31 15:24:40 yo kernel: RBP: 880211973dd8 R08: 88021fb9a920 R09: 8800c2fe5d48 Aug 31 15:24:40 yo kernel: R10: 88021fdf6000 R11: R12: 8800c9b78960 Aug 31 15:24:40 yo kernel: R13: 8800c2fe5d48 R14: 00e700e60028 R15: 00e700e6 Aug 31 15:24:40 yo kernel: FS: 7fafccda9a80() GS:88021fb8() knlGS: Aug 31 15:24:40 yo kernel: CS: 0010 DS: ES: CR0: 80050033 Aug 31 15:24:40 yo kernel: CR2: 560ce357cad8 CR3: 000214802000 CR4: 001406e0 Aug 31 15:24:40 yo kernel: DR0: DR1: DR2: Aug 31 15:24:40 yo kernel: DR3: DR6: fffe0ff0 DR7: 0400 Aug 31 15:24:40 yo kernel: Stack: Aug 31 15:24:40 yo kernel: 8800c97ec000 880211973eb8 8107fc4f 10cc8d00 Aug 31 15:24:40 yo kernel: 7fafccda9d50 01200011 8800c2fe5278 Aug 31 15:24:40 yo kernel: 8800c2fe5280 8800c2fe5268 8800c97ec068 8802111fb128 Aug 31 15:24:40 yo kernel: Call Trace: Aug 31 15:24:40 yo kernel: [] copy_process+0x14ff/0x1ae0 Aug 31 15:24:40 yo kernel: [] _do_fork+0x80/0x360 Aug 31 15:24:40 yo kernel: [] SyS_clone+0x19/0x20 Aug 31 15:24:40 yo kernel: [] entry_SYSCALL_64_fastpath+0x16/0x71 Aug 31 15:24:40 yo kernel: Code: 1f 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb e8 ae dd ff ff 48 ba 01 00 00 00 Aug 31 15:24:40 yo kernel: RIP [] down_write+0x1f/0x40 Aug 31 15:24:40 yo kernel: RSP Aug 31 15:24:41 yo kernel: ---[ end trace 864859008364d4cd ]--- Aug 31 15:24:44 yo systemd[3136]: Time has been changed Currently I've removed the intel xorg package to exclude some gpu crashes, but this does not seem to have any influence, so I guess it is really a kernel bug. Previous kernels under trusty resumed flawlessly up to 4.2 (lts-wily), 4.4 (lts-xenial) also produced system hangs after resume. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-36-generic 4.4.0-36.55 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kiran 3378 F pulseaudio /dev/snd/controlC0: kiran 3378 F pulseaudio CurrentDesktop: XFCE Date: Wed Aug 31 15:32:06 2016 HibernationDevice: RESUME=UUID=5ea8b83e-6f6f-4e44-98f6-45ade2c2d6c3 InstallationDate: Installed on 2013-11-16 (1019 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) IwConfig: lono wireless extensions. p2p1 no wireless extensions. MachineType: ASUS All Series ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=4fee8160-326f-4688-a0d9-22e158e70f45 ro quiet RelatedPackageVersions: linux-restricted-modules-4.4.0-36-generic N/A linux-backports-modules-4.4.0-36-generic N/A linux-firmware1.157.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-08-20 (10 days ago) dmi.bios.date: 07/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-G dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/22/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-G:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are
[Bug 1618903] Re: System crashes after resume from hibernate
I've tested 4.4.x and 4.6.7 from mainline. Crashes happen much less frequent, but still happen. Attached is a dmesg log from 4.6.7. ** Attachment added: "dmesg_resume_crash_4.6.7.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618903/+attachment/4731588/+files/dmesg_resume_crash_4.6.7.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618903 Title: System crashes after resume from hibernate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532180] Re: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-change for https://
I've tested the patch against the xenial amarok package (2:2.8.0-0ubuntu9) and it solves the issue for it too. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to amarok in Ubuntu. https://bugs.launchpad.net/bugs/1532180 Title: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API- change for https:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1532180/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1532180] Re: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-change for https://
The attached patch fixes the issue for trusty. Since there were only minimal updates to amarok for xenial, it probably works for it too. Its basically a backport of the following upstream commits: http://commits.kde.org/amarok/8c15258b28870b6d9990b24f87ce913e2049bac8 http://commits.kde.org/amarok/15d68755dc5dcf549386a4d50d8a15ebfbea ** Patch added: "wikipedia_applet.patch" https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1532180/+attachment/4688193/+files/wikipedia_applet.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532180 Title: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API- change for https:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1532180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526345] Re: *bird themes break adress autocompletion in thunderbird
This is fixed in thunderbird 45.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526345 Title: *bird themes break adress autocompletion in thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shimmer-themes/+bug/1526345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1531902] Re: Stopping cups-browsed.service may stall shutdown/reboot
I could not reproduce it either since a while (thats, why I didn't sent any debug logs). So I concur, that it got fixed by some update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1531902 Title: Stopping cups-browsed.service may stall shutdown/reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1531902/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575708] Re: Firefox 46 works only with fresh profile
New version of firetray (0.6.1) should fix this issue (for now). ** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575708 Title: Firefox 46 works only with fresh profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1575708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575708] Re: Firefox 46 works only with fresh profile
Ok, this is somehow extensions related. Starting with --safe-mode results in a working version. In my case I pinned it down to the firetray addon. Since it is unmaintained, I guess this is a won't fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575708 Title: Firefox 46 works only with fresh profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1575708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575708] [NEW] Firefox 46 works only with fresh profile
Public bug reported: A freshly updated firefox (to 46) does not work anymore if there is already a firefox profile. Basically everything is broken: sessions, menus even browsing by typing in a web address. As a work around (sort of), one can delete the profile (~/.mozilla) and start fresh ... and lose all settings, extensions etc. Or downgrade until this is fixed. I get this issue on two machines running a fully updated xubuntu trusty. ** Affects: firefox (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/1575708 Title: Firefox 46 works only with fresh profile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1575708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568352] Re: "/sys/block/sd(X)/removable" erroneously indicates "removable" for fixed drives
According to a redhat bug report (https://bugzilla.redhat.com/show_bug.cgi?id=1310682) it was introduced by a kernel update from 4.3 to 4.4. So I've testet 4.3.6 from mainline and it is not effected. Btw. you probably get this on a live system too and for all hdds (since root is on the flash drive). This can have quite an impact, because some DEs automatically mount all removable drives (e.g. kde). If one of your hdd partitions contains a hypernated system, your in for a lot of fscking and/or ro mounted partitions on next resume. ** Bug watch added: Red Hat Bugzilla #1310682 https://bugzilla.redhat.com/show_bug.cgi?id=1310682 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568352 Title: "/sys/block/sd(X)/removable" erroneously indicates "removable" for fixed drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568352] Re: "/sys/block/sd(X)/removable" erroneously indicates "removable" for fixed drives
Tested with latest mainline v4.6-rc4-wily, issue still persists. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568352 Title: "/sys/block/sd(X)/removable" erroneously indicates "removable" for fixed drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568352] [NEW] "/sys/block/sd(X)/removable" erroneously indicates "removable" for fixed drives
Public bug reported: This seems to happen only to additional hdd (not the one with the root partition). gnome-disks and some file manager report those drives as ejectable. This might be fixed by the following patch http://git.kernel.org/cgit/linux/kernel/git/stable/stable- queue.git/diff/queue-4.4/ata-ahci-don-t-mark-hotplugcapable-ports-as- external-removable.patch?id=4e362751dc079531ef2b95bcd5c71e12f78e1ae6 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kiran 1110 F pulseaudio CurrentDesktop: XFCE Date: Sat Apr 9 20:03:18 2016 HibernationDevice: RESUME=UUID=ebcf26a9-f63a-4b55-ad87-31f7b1f3feb6 InstallationDate: Installed on 2016-03-31 (9 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) MachineType: LENOVO 2767WSD PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=a0309315-a77b-4d81-8a2c-b603b5ab7acd ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 2767WSD 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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn2767WSD:pvrThinkPadT400:rvnLENOVO:rn2767WSD:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2767WSD dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568352 Title: "/sys/block/sd(X)/removable" erroneously indicates "removable" for fixed drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1568352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532180] Re: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API-change for https://
Fedora fixed this in June 2015. If a read their solution correctly ( https://pkgs.fedoraproject.org/cgit/rpms/amarok.git/commit/?id=fa50109140fa4482bbd1ced79ed4daf440f568ee), it's just a matter of pulling in the upstream commit mentioned in the op. ** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532180 Title: Amaroks Wikipedia applet does not work anymore, due to Wikimedias API- change for https:// To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1532180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521586] Re: Frame shadow of gtk3 application is not transparent for mouse clicks
I should mention, that I get this issue only with enabled compositing in the wm. In my case with xfwm or mutter (cf. attached screenshot). ** Attachment added: "window_border_grabbing.png" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1521586/+attachment/4624541/+files/window_border_grabbing.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521586 Title: Frame shadow of gtk3 application is not transparent for mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1521586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521586] Re: Frame shadow of gtk3 application is not transparent for mouse clicks
So, its not the shadow actually, which would have been weird in the first place. But some apps (I would say gtk3, csd; eg. gnome-calculator, gnome-software) show a different behavior concerning window border grabbing (for resizing). Windows, which can be resized, change the cursor the discussed area next to the window border and can be resized. This behavior is probably also applied to windows, which can not be resized, like gnome-calculator or the indicator menus. Thus leading to the several pixel wide region near window borders, where mouse clicks are not interpreted as, well, clicks. If the border grabbing margin is intentional (although it leads to an inconsistent behavior between different apps), then it should be disabled for windows, which are not resizeable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521586 Title: Frame shadow of gtk3 application is not transparent for mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1521586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521586] Re: Frame shadow of gtk3 application is not transparent for mouse clicks
This affects gtk3 indicator in Xubuntu (xfwm or mutter as wm). Usually the black borders in the attached screenshot are transparent shadows, but it represents exactly the area which is sometimes not clickable. To reproduce: * click a gtk3 indicator * hover over the expanded indicator menu * try to click the indicator or any neighbors => only clicks in the upper ~1/3 of the button show a reaction, the lower 2/3 do nothing. The same thing happens with some gtk3 window shadows, e.g. the gnome calculator: Underlying windows cannot be brought into focus near the window border in the shadow area. ** Attachment added: "black_border_indicator_plugin_no_compositing.jpg" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1521586/+attachment/4618533/+files/black_border_indicator_plugin_no_compositing.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1521586 Title: Frame shadow of gtk3 application is not transparent for mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1521586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533206] Re: Blueman-applet crash on login: DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out
In my case this happens, when the bluetooth hardware wasn't initialized by kernel, e.g. it was toggled off by hardware switch (maybe software off might work as well). In such case /sys/class/bluetooth is not created, which prevents the bluetooth.service to start: systemctl status bluetooth ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: inactive (dead) Condition: start condition failed at So 2016-02-14 12:37:00 CET; 4s ago ConditionPathIsDirectory=/sys/class/bluetooth was not met This means that bluetoothd is not running and thus does not provide the org.bluez dbus service, which in turn is what blueman is complaining about. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533206 Title: Blueman-applet crash on login: DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1533206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] Re: Hibernate causes an unmounted hard drive in sleep mode to spin up
*** This bug is a duplicate of bug 524407 *** https://bugs.launchpad.net/bugs/524407 For the sake of completeness, the point is, that we're talking about a hdd with no mounted partitions. As far as I understand it, any data, which might be in memory needs to be flushed before unmounting (after all you don't loose data when disconnecting an unmounted usb flash drive). Anyhow, this is definitively a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/524407, which contains also a reference to an upstream report. So marking this one accordingly. ** This bug has been marked a duplicate of bug 524407 hibernating wakes up sleeping harddrives -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532180] [NEW] Amaroks Wikipedia applet does not work anymore
Public bug reported: Amaroks wikipedia applet stopped showing any information. According to the upstream bug report (https://bugs.kde.org/show_bug.cgi?id=349313) this is caused by a change in wikipedias api, which requires now a ssl connection. This means, that all amarok versions currently available on ubuntu are affected. The same bug report mentions a commit http://commits.kde.org/amarok/284342b48dc32341c3553fd2b0ee5069d75b58f9 which (partially) fixes the issue by making it possible to enable ssl for the applet. It might be worth backporting if possible. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: amarok 2:2.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Jan 8 13:25:04 2016 InstallationDate: Installed on 2015-09-22 (107 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150825) SourcePackage: amarok UpgradeStatus: Upgraded to xenial on 2015-10-30 (70 days ago) ** Affects: amarok (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532180 Title: Amaroks Wikipedia applet does not work anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1532180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526345] Re: *bird themes break adress autocompletion in thunderbird
Theres also an upstream bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1151764 So maybe its an issue with thunderbird (xfwm4 was also suggested). However, since some themes do work, adjusting the others may be the easiest way to fix this. ** Bug watch added: Mozilla Bugzilla #1151764 https://bugzilla.mozilla.org/show_bug.cgi?id=1151764 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526345 Title: *bird themes break adress autocompletion in thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shimmer-themes/+bug/1526345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1526345] [NEW] *bird themes break adress autocompletion in thunderbird
Public bug reported: When using the greybird or bluebird theme, the adress autocompletion list of thunderbirds compositor window is reduced to few pixel height, starting with the second key stroke (cf. attached image). Since the numix and orion theme work, I suspect it is an issue within the *bird themes. I get this with trustys shimmer-themes (1.7.3-0ubuntu1) as well as with xenials (2.0.2-0ubuntu1). ** Affects: shimmer-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Autocomplete should show a list of about 7 items." https://bugs.launchpad.net/bugs/1526345/+attachment/4535105/+files/tb_autocomplete_cropped.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1526345 Title: *bird themes break adress autocompletion in thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shimmer-themes/+bug/1526345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1521586] [NEW] Frame shadow of gtk3 application is not transparent for mouse clicks
Public bug reported: The shadow region of Gtk3 apps drawing their own frame shadow (CSD) is not transparent for mouse events. E.g. when such an app is in front of a browser window, a link in the browser can only be clicked/hovered at distance from the window border, which is larger than the shadow thickness. This may be related to #1518661. ** Affects: gtk+3.0 (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/1521586 Title: Frame shadow of gtk3 application is not transparent for mouse clicks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1521586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1520573] Re: libgtk-3-0 (3.18.5-1ubuntu1) breaks CSD rendering in gnome-shell
*** This bug is a duplicate of bug 1518661 *** https://bugs.launchpad.net/bugs/1518661 ** This bug has been marked a duplicate of bug 1518661 Apps with HeaderBar have margin outside window -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1520573 Title: libgtk-3-0 (3.18.5-1ubuntu1) breaks CSD rendering in gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1520573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1518661] Re: Apps with HeaderBar have margin outside window
Version 3.18.5-1ubuntu2 from proposed fixes this issue partially. In order to work, the window manager needs to support compositing, otherwise we now get a black margin outside the window (cf. attached screenshot). ** Attachment added: "margin_without_compositing.png" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1518661/+attachment/4527891/+files/margin_without_compositing.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1518661 Title: Apps with HeaderBar have margin outside window To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1518661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1349879] Re: powering off an usb3 device causes kernel to resume immediately after suspend
Tested again with latest mainline kernel (4.4.0-040400rc2-generic): Still the same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349879 Title: powering off an usb3 device causes kernel to resume immediately after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1394193] Re: 114 instances of indicator-sound-service running
*** This bug is a duplicate of bug 1322275 *** https://bugs.launchpad.net/bugs/1322275 ** This bug has been marked a duplicate of bug 1322275 lightdm sessions started by dm-tool lock (or a session locker) never get closed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1394193 Title: 114 instances of indicator-sound-service running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1394193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed
Another workaround, at least for those not requiring the a11y-indicator (accessibility menu for visual impaired): removing the a11y-indicator from the lightdm session, seems to prevent the start of the sound- indicator. Hence the sound-indicator does not block the termination of lightdm session, hence the lightdm session vanishes after login. The indicators started by lightdm are configured in the corresponding 'lightdm-*-greeter.conf' file (for xubuntu its '/etc/xdg/xdg- xubuntu/lightdm/lightdm-gtk-greeter.conf') in the line 'show- indicators='. Deleting the built-in ~a11y solved the issue for me. For a proper solution, one would have to investigate, why the sound- indicator is blocking the clean termination of the lightdm session. Maybe its some sort of reincarnation of https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk- greeter/+bug/1290575. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322275 Title: lightdm sessions started by dm-tool lock (or a session locker) never get closed To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1322275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
... nominate it to be logged as Confirmed in the 'Trusty' series if it's still not fixed there. Can someone (who has the permission) nominate this for trusty? Trusty will be around for a while and there is right now no real workaround (or fix for that matter). So it should be at least documented. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 880533]
Build thunar from current master (6010f71). Trash status works fine and I haven't found any regressions so far. Admittedly I've looked primarily at the 'empty trash after first start'-issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/880533 Title: Thunar and Trash Applet report that Trash is empty when it is not To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/880533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 880533]
(In reply to Harald Judt from comment #15) Created attachment 6252 [details] fix-loading-the-trash-bin-status-at-startup-bug-9513.patch This is probably a better version of the patch. Instead of putting the checks into thunar_file_get, which could be called quite often for folders that contain a lot of files, put it into the main function which gets called only once per thunar instance. Applied the second version of the patch and it fixes the issue for me. No side effects so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/880533 Title: Thunar and Trash Applet report that Trash is empty when it is not To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/880533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 880533]
(In reply to Harald Judt from comment #11) Is this still an issue? If it is, please reopen. Yes, it is. Thunar build from git (afe91e9). As Thaddaeus Tintenfisch said in #10, it works fine, *if* xfdesktop is configured to show the trash icon on the desktop. For all desktop configurations not enabling the desktop trash icon, thunar shows always an empty trash on startup after a fresh login. So do all further thunar instances started later. To get the correct status, one must delete a file/folder or close all open thunar windows. The next thunar window will then show the correct status. Btw. my workaround for this issue is to create a autostart entry calling gvfs-ls trash /dev/null. So my guess is, that calling gvfs-ls trash initializes something thunar is relying on to determine the trash status. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/880533 Title: Thunar and Trash Applet report that Trash is empty when it is not To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/880533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432222] Re: system does not power off after going into hibernation
This issue seems to be fixed since the last kernel update from 3.19.0-10 to 3.19.0-12. While with 3.19.0-10 I can still reproduce it, with 3.19.0-12 it doesn't happen anymore. So for my part it is fixed now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/143 Title: system does not power off after going into hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432222] Re: system does not power off after going into hibernation
Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.16 stable kernel[0]. Just to clarify: I've reported this bug for the vivid kernel, currently 3.19.0. So I'm not sure, if it helps to test 3.16? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/143 Title: system does not power off after going into hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] Re: Hibernate causes an unmounted hard drive in sleep mode to spin up
b3nmore, does this also happen when the computer shuts down? Yes, its basically the same for shutdown and hibernation: At the very end of the shutdown/hibernation process, when one would expect the system to power off, the drive spins up and then the system powers off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] Re: Hibernate causes an unmounted hard drive in sleep mode to spin up
** Tags added: kernel-bug-exists-upstreamkernel-bug-exists- upstream-4.0-rc3 ** Tags removed: kernel-bug-exists-upstreamkernel-bug-exists-upstream-4.0-rc3 ** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.0-rc3 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432222] [NEW] system does not power off after going into hibernation
Public bug reported: My laptop does not power off anymore after going into hibernation. Instead I have to power off manually by holding the power button for some seconds. Resuming from hibernation does work reliably however. This is regression, since it works perfectly with the utopic kernel (currently 3.16.0.31.24). To be more precise, the standard 'platform' mode causes this issue: echo platform /sys/power/disk echo disk /sys/power/state When using the 'shutdown' mode the system powers off correctly: echo shutdown /sys/power/disk echo disk /sys/power/state ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-9-generic 3.19.0-9.9 [modified: boot/vmlinuz-3.19.0-9-generic] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kiran 1458 F pulseaudio CurrentDesktop: XFCE Date: Sat Mar 14 19:36:16 2015 HibernationDevice: RESUME=UUID=ebcf26a9-f63a-4b55-ad87-31f7b1f3feb6 InstallationDate: Installed on 2015-03-14 (0 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150313) MachineType: LENOVO 2767WSD PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=f0d3de75-e584-48c4-a3af-7b73dd5eb495 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-9-generic N/A linux-backports-modules-3.19.0-9-generic N/A linux-firmware1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 2767WSD 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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn2767WSD:pvrThinkPadT400:rvnLENOVO:rn2767WSD:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2767WSD dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/143 Title: system does not power off after going into hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1432222] Re: system does not power off after going into hibernation
While at it, I've tested kernel 4.0-rc3 from mainline and with that one it works again, even in 'platform' mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/143 Title: system does not power off after going into hibernation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] IwConfig.txt
apport information ** Attachment added: IwConfig.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345426/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] Re: Hibernate causes an unmounted hard drive in sleep mode to spin up
Last apport-collect was on utopic, but this is still an issue with vivid (kernel 3.19). Btw this might be a dup of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/524407 ** Tags added: apport-collected vivid ** Description changed: I've got a hdd for backups, which most of the time is unmounted and sleeping (spun down). When going into hibernation it spins up shortly before the computer powers off. This is somehow annoying because it's noisy, elongates the power off process and is completely senseless. Syslog shows: kernel: [ ...] Synchronizing SCSI cache for all my hdd when going into hibernation. Thats the only hint I've got so far whats causing the wakeup. This happens in oneiric and precise (pm-utils 1.4.1-8ubuntu1 and 1.4.1-9). Btw it does not happen when suspending. --- ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kiran 1939 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 14.10 HibernationDevice: RESUME=UUID=ebcf26a9-f63a-4b55-ad87-31f7b1f3feb6 InstallationDate: Installed on 2015-01-11 (0 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141006) MachineType: LENOVO 2767WSD Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=61673c3e-2e9d-4a30-8126-9f0f6e9280da ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 RelatedPackageVersions: linux-restricted-modules-3.16.0-28-generic N/A linux-backports-modules-3.16.0-28-generic N/A linux-firmware 1.138.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: utopic Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 2767WSD 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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn2767WSD:pvrThinkPadT400:rvnLENOVO:rn2767WSD:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2767WSD dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO + --- + ApportVersion: 2.16.2-0ubuntu3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: kiran 1524 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 15.04 + HibernationDevice: RESUME=UUID=ebcf26a9-f63a-4b55-ad87-31f7b1f3feb6 + InstallationDate: Installed on 2015-03-14 (0 days ago) + InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150313) + MachineType: LENOVO 2767WSD + Package: linux (not installed) + PccardctlIdent: + Socket 0: +no product info available + PccardctlStatus: + Socket 0: +no card + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=f0d3de75-e584-48c4-a3af-7b73dd5eb495 ro quiet splash + ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 + RelatedPackageVersions: + linux-restricted-modules-3.19.0-9-generic N/A + linux-backports-modules-3.19.0-9-generic N/A + linux-firmware1.143 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: vivid + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 3.19.0-9-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/17/2012 + dmi.bios.vendor: LENOVO + dmi.bios.version: 7UET94WW (3.24 ) + dmi.board.name: 2767WSD + 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:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn2767WSD:pvrThinkPadT400:rvnLENOVO:rn2767WSD:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.name: 2767WSD + dmi.product.version: ThinkPad T400 + dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 980307] Lspci.txt
apport information ** Attachment added: Lspci.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345427/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] ProcModules.txt
apport information ** Attachment added: ProcModules.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345432/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345430/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] PulseList.txt
apport information ** Attachment added: PulseList.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345433/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345431/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345425/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] CRDA.txt
apport information ** Attachment added: CRDA.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345424/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] WifiSyslog.txt
apport information ** Attachment added: WifiSyslog.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345435/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] Lsusb.txt
apport information ** Attachment added: Lsusb.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345428/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] AlsaInfo.txt
apport information ** Attachment added: AlsaInfo.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345423/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345429/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980307] UdevDb.txt
apport information ** Attachment added: UdevDb.txt https://bugs.launchpad.net/bugs/980307/+attachment/4345434/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980307 Title: Hibernate causes an unmounted hard drive in sleep mode to spin up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/980307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313682] Re: Can't hide entries sourced from /usr/share/applications/kde4/
Still an issue with menulibre 2.0.6 and vivid. The attached patch should map the original subdirectory structure to the user directory. ** Patch added: util_subdir.patch https://bugs.launchpad.net/ubuntu/+source/menulibre/+bug/1313682/+attachment/4332503/+files/util_subdir.patch ** Also affects: menulibre 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/1313682 Title: Can't hide entries sourced from /usr/share/applications/kde4/ To manage notifications about this bug go to: https://bugs.launchpad.net/menulibre/+bug/1313682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
I ran some tests, which I recall having caused problems in the past. With the latest patch (b529706) applied, the two main issues (unwanted suspend/blank screen) are basically resolved now for *all* test cases (except maybe f) 1/2). There are small differences for the various configuration options, which I'll list for each test case. IMO the ideal case would be, that the 'unlock dialog appears directly'. However sometimes the user must interfere manually a second time or wait additional time [1]. 1) --no-lock-on-lid 2) --lock-on-lid Test cases directly triggered by lid close: a) xfpm lid action: lock i) auto lock: never 1) delay OR manual interference (depends on close time) 2) unlock dialog appears directly (depends on close time) ii) auto lock: ss activates (after autolock kicks in) 1) delay OR manual interference 2) unlock dialog appears directly iii) auto lock: ss deactivates (after autolock kicks in) 1) delay OR manual interference 2) unlock dialog appears directly b) xfpm lid action: suspend 1) unlock dialog appears directly 2) unlock dialog appears directly c) xfpm lid action: hibernate 1) manual interference required 2) manual interference required Test cases auto lock, lid stays open (xfpm lid action: lock): d) auto lock: ss activates 1) unlock dialog appears directly 2) unlock dialog appears directly e) auto lock: ss deactivates 1) manual interference required 2) manual interference required Test cases auto lock, but lid gets closed *after* the screen was locked (xfpm lid action: lock): f) auto lock: ss activates 1) system suspends, manual interference required 2) system suspends, manual interference required g) auto lock: ss deactivates 1) manual interference required 2) manual interference required [1] I would call them usability issues, because the user has to take additional action although he already requested the unlock dialog by e.g opening the lid etc. So nothing really dramatic, but the user interaction required to get to the unlock screen heavily depends on situation and isn't consistent (and maybe discussed elsewhere). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416810] Re: indicator-messages should depent (or recommend) libmessaging-menu0
The problem is that, at least with xubuntu (xfce indicator plugin), the messaging menu never appears in the panel, unless libmessaging-menu0 gets installed, although applications using it are installed (e.g. thunderbird). But of course this can also be resolved be letting thunderbird recommend (or suggests) libmessaging-menu0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416810 Title: indicator-messages should depent (or recommend) libmessaging-menu0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1416810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315558]
(In reply to André Miranda from comment #7) Check the image attached on bug 11233, here it's *not* being rendered correctly. Well, finally we've found an image to reproduce this bug. Yeah, that one isn't rendered correctly either with 0.6.3. But strangely enough only directly after opening it with ristretto. When I cycle through the images in the same folder, its rendered correctly when I hit it again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315558 Title: Ristretto cannot read GIF properly To manage notifications about this bug go to: https://bugs.launchpad.net/ristretto/+bug/1315558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315558]
Created attachment 5978 ristretto rendering a gif incompletely and filling in some old data (In reply to André Miranda from comment #5) I guess this image is good enough for testing purposes: http://commons.wikimedia.org/wiki/File:Lexington_original_configuration_orig. gif Here it takes ~7 seconds to open, but no rendering issues again. Well, then something got (partially) fixed in this respect since 0.6.3. Here it renders only the first few lines. I've attached another screen shot of ristretto after loading the animated one from #3, the huge one from #5 and than the large one from #2. It shows, that parts of the not rendered part is filled with some data of the 1st image. Kind of a mem alloc error? Hope that helps to pin down the root cause of this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315558 Title: Ristretto cannot read GIF properly To manage notifications about this bug go to: https://bugs.launchpad.net/ristretto/+bug/1315558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
Just as reference: attached log is from light-locker --debug --lock-on- lid, I commented the triggering actions. Only difference to previous log are lines 92 and 93. ** Attachment added: ll_debug-lock_on_lid https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+attachment/4323960/+files/ll_debug-lock_on_lid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
I've tested light-locker version 1.6.0-0ubuntu1 on vivid with the staging repository enabled (although the light-locker from vivid currently supersedes the staging one). Good news first: the system does not suspend anymore when it is configured to lock only (case 1 from #50). It does not suspend even when explicitly locking on lid close (--lock-on-lid). Shouldn't this reproduce the old behavior? Bad news: the screen stays still switched off after unlocking (case 2 from #50). I couldn't see any differences between lock-on-lid and no- lock-on-lid (cf. attached debug logs). And I'm not sure why this still happens. Maybe the switch is too fast to activate the screen on the original session first. If our analysis is correct so far, we would need to activate the screen on the session where it got deactivated first and than do the switch. Attached log is from light-locker --debug --no-lock-on-lid, I commented the triggering actions. ** Attachment added: ll_debug-no_lock_on_lid https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+attachment/4323959/+files/ll_debug-no_lock_on_lid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
Ah, I used a modified logind.conf for the tests in #55/#56. It had HandleLidSwitch=ignore, so thats probably the reason, why the system didn't suspend. When using an unmodified logind.conf, i.e. all options commented out, the system suspends regardless of which option (--lock-on-lid/--no-lock- on-lid) I use. Odd exception: sometimes the first try after reboot does not suspend; again independent of the used option. So my guess is, that we still have some vt switching while the lid is closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416810] [NEW] indicator-messages should depent (or recommend) libmessaging-menu0
Public bug reported: indicator-messages does not work without libmessaging-menu0, hence there should be some sort of dependency. ** Affects: indicator-messages (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/1416810 Title: indicator-messages should depent (or recommend) libmessaging-menu0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1416810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
Yes, we know this. The logjnd-handle-lid-switch property is being used as fix for the blank screen bug. If logind handles the lid event, it will send two separate signals which control light-locker (lock session before suspend, switch to unlock screen on resume). Ah, I suspected something of the kind. Here is a summary of the issues (as I understand it): The vt switching by light-locker (or rather lightdm) is the root cause for two issues, which were attributed to xfpm, but have nothing to do with xfpm: 1) system suspends in certain situations, although xfpm is configured not to suspend in those situations 2) in certain situations the screen stays switched off after unlocking Besides the trivial case for 1), cf. comment #48, both issues arise, if the lid is closed when the vt switch happens. If we call the user session vt1 and the unlock screen session vt2, the event chains look (approximately) as followed: 1) lid close on vt1 - xfpm blocks logind and executes as configured - screen locks and switches to vt2 - vt2 has no logind inhibitor log - logind suspends the system. 2) lid close on vt1 - xserver (?) switches the screen off for vt1 - screen locks and switches to vt2 - user wants to unlock - screen gets switched on on current active sesion, i.e vt2 - authentication - switch to vt1 - turned off screen, because on vt1 it was never switched on again If this analysis is correct, we have two approaches to solve both issues: a) adapt light-locker to never make a vt switch while the lid is closed. That would be something like making late-locking a general behavior. b) adapt light-locker (or maybe even lightdm) to tackle each problem on its own. E.g. the unlock screen session needs an inhibitor lock too and possibly turn on the screen of the session it switches to after unlocking. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
... the logind-handle-lid-switch property can be changed on-the-fly. Judging from the code, the logind-handle-lid-switch property causes xfpm to ignore the lid switch event, if set to true. That means, that if you want to set the action for the lid close event in xfpm (that is, that xfpm reacts on such an event), this property must not be set to true. Else logind will handle the event and executes what ever is defined in logind.conf. IMO this property should be removed, its confusing and xfpm has the ability to handle lid switch events. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
We need to understand how the systemd inhibit mechanism works and why it is not applied system-wide. I've asked at the systemd-devel list, if they want to keep this behavior (after all, it is a design decision): http://lists.freedesktop.org/archives/systemd- devel/2015-January/027255.html. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
Apropos vt switch, I believe, thats the root cause of this issue and the blank-after-unlock bug. If we have a vt switch (e.g. sleep 20 loginctl activate cX in the examples above) *after* the lid was closed, then the system suspends; maybe because the new session has no inhibitor lock. When the lid is open, the screen gets turned on for the new active session. When we switch back to the original session, the screen turns off, because on this sessions it was deactivated, but never reactivated. I've tested this behavior on text vt's and there is the same retroactive suspend reaction of a closed lid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
The case utopic 2a (or trusty 1a) is basically the same as above, only that the actual lock time depends on how the lock-after-screensaver-time of light-locker is configured. Again a test, that keeps xfpm out of the picture: - killall xfce4-power-manager - systemd-inhibit --what=handle-lid-switch --who=me --why=test --mode=block sleep 1000 - light-locker --lock-after-screensaver=1 - sleep 20 xset dpms force off - close lid Result: 20 sec. nothing, light-locker registers the screen blanking and locks the screen, if the lid is closed the system suspends. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
O.k., so light-locker calls lightdm to lock the seat. So we can skip light-locker in the tests above and use e.g. dm-tool lock. That means, that it is lightdm, which seems to override the inhibitor lock for the lid handle upon locking. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
Btw. running above tests only with dm-tool (no xfpm and no light-locker) shows, that the screen stays switched off in the same situation as with the 'infamous blank-screen-after-unlock bug' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
... rerun the test case from comment #40, but also activate the late locking feature of light-locker: This does work. It is expected to work, since the lock command is called after the lid is open again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
b3nmore, please add HandleLidSwitch=ignore to your logind.conf and rerun the test cases which are mentioned in my previous comment. Running utopic 2b with HandleLidSwitch=ignore: result: lock + blank-screen-after-unlock bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
Why does the system suspend in test case trusty 1b and utopic 2b? The screen should be only locked and neither logind nor xfce4-power- manager should trigger suspend. Neither does (cf. #30, its the same for utopic 2b), at least not in combination with other screen lockers. I've tested i3lock and the system does exactly as configured in xfpm. So the questions is more specifically: why does the system suspend in those cases, *if* we use light-locker as locking application? I've tried to dig into this issue, and this is what I've got so far: - if set to lock sreen, xfpm calls xflock4 - if light-locker is running, xflock4 calls light-locker-command -l - running light-locker --debug shows in this case (i.e. lid triggered): gs-listener-dbus.c: obj_path=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager method=PrepareForSleep destination=(null) - when calling xflock4 manually, xflock4 calls light-locker-command -l - running light-locker --debug shows now: gs-listener-dbus.c: obj_path=/org/freedesktop/login1/session/c2 interface=org.freedesktop.login1.Session method=Lock destination=(null) This means, that somehow in the combination xfpm + light-locker (and only in this combination) a suspend call is sent to (?) logind (and therefor a PrepareForSleep-Signal is emitted). I've been unable to identify, where the suspend call comes from. Just to make this clear: xfpm is setup to inhibit systemd/logind's lid handling and to lock the screen on lid close: xfpm + i3lock - no suspend xflock4 + light-locker - no suspend xfpm + light-locker - suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
The last test of the previous comment seems to imply, that we get the unwanted suspending only, if light-locker locks the screen *while* the lid is closed. Heres a test to verify this and takes xfpm out of the whole mess (on utopic): - killall xfce4-power-manager - systemd-inhibit --what=handle-lid-switch --who=me --why=test --mode=block sleep 1000 This blocks any action logind may take upon lid close (for 1000 sec.), i.e. one can close the lid and nothing happens. - sleep 20 light-locker-command -l - close the lid Result: 20 sec. happens nothing (you can even open/close the lid several times). If the lid is closed when light-locker-command -l runs, the system suspends. I would guess, that light-locker lifts the block of the 'handle-lid- switch' and, if the lid is closed, theres still a lid close event pending, which than gets executed (or something of the kind). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
Unfortunately I've to revise the results for trusty 1a and utopic 2a resp.. There is a delay of ~5 sec. before the system suspends (in the other cases its suspends immediately, hence my misinterpretation). So they should be: result: 5sec. nothing + suspend + lock + blank-screen-after-unlock bug I've verified, that we get different timings for utopic 2a/2b (or trusty 1a/1b) by adding a 'sleep 20' at the start of the xflock4 script. in that case utopic 2a suspends after 5 sec., utopic 2b after 20 sec. And with the modified xflock4, we can do another variation of utopic 2 b: - close lid and wait 15 sec. - nothing happens - open lid - screen gets turned on - wait 5 sec. more - light-locker locks the screen, but does *not* suspend - after unlocking screen just gets turned on -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
I did the same tests for trusty: The behavior is basically the same, only the xfce4-power-manager/logind-handle-lid-switch xfconf-key is handled oppositional (probably due to http://git.xfce.org/xfce/xfce4 -power-manager/commit/?id=f62e82256cb2a45b4f044b7d603017952f7dd63e). Let's try to summarize all findings: trusty case 1) xfce4-power-manager/logind-handle-lid-switch = true - blank-screen bug with light-locker - debug trace: xfpm_manager_inhibit_sleep_systemd(): [...] handle-lid-switch a) lid close action: nothing - result: nothing b) lid close action: lock - result: suspend + lock + blank bug trusty case 2) xfce4-power-manager/logind-handle-lid-switch = false - light-locker works - debug trace: xfpm_manager_inhibit_sleep_systemd(): [...] a) lid close action: nothing - result: suspend + lock b) lid close action: lock - result: suspend + lock utopic case 1) xfce4-power-manager/logind-handle-lid-switch = true - light-locker works - debug trace: xfpm_manager_inhibit_sleep_systemd(): [...] a) lid close action: nothing - result: suspend + lock b) lid close action: lock - result: suspend + lock utopic case 2) xfce4-power-manager/logind-handle-lid-switch = false - blank-screen bug with light-locker - debug trace: xfpm_manager_inhibit_sleep_systemd(): [...] handle-lid-switch a) lid close action: nothing - result: nothing b) lid close action: lock - result: suspend + lock + blank bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307545] Re: Power Manager settings are ignored when closing laptop lid
The log file from comment #19 shows that xfwm4-power-manager does not inhibit sleep on lid close (the key handle-lid-switch is missing for Inhibiting systemd sleep). From the analysis above I would guess, that it is either trusty case 2 or utopic case 1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307545 Title: Power Manager settings are ignored when closing laptop lid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-power-manager/+bug/1307545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
