> 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
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
*** 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.
** 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:
** 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 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
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:
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
** 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
> ... 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
** 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
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,
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
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
** 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
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):
** 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:
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:
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.
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
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.
** 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
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
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
** 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:
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
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
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"
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
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
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
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:
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
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
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 ...
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
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.
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-
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
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"
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
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
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
●
*** 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
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
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
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
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
*** 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
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"
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
*** 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
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,
... 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
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
(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
(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
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
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
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
** 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 =
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
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
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:
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
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:
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
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
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:
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.
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
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
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
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:
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:
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
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:
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
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
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
(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
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
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
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
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-
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
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
... 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
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.
--
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
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
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
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
... 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
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
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 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
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 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
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
1 - 100 of 309 matches
Mail list logo
