** Changed in: unity-settings-daemon (Ubuntu)
Assignee: uklas (uklasius) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
unity-settings-daemon crashed with SIGSEGV
** Changed in: unity-settings-daemon (Ubuntu)
Assignee: (unassigned) => uklas (uklasius)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
unity-settings-daemon crashed with SIGSEGV
I installed a new kernel (version 4.8). It seems to solve this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
unity-settings-daemon crashed with SIGSEGV in
I am seeing the same issue with Linux Mint 18.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
unity-settings-daemon crashed with SIGSEGV in
up_exported_daemon_get_lid_is_closed()
I've now replaced the whole PC and kept the old harddrive. But this bug
remains even in the new system. Again unplugging my USB DVB tuner is the
workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just looking at my latest .crash file, it's definitely the same crash. And now
from:
libupower-glib3:amd64 0.99.4-2ubuntu0.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, but now the fault has returned. Even with upower
0.99.4-2ubuntu0.3
The only thing that works is for me to unplug the USB DVB tuner for
boot-up.
** Changed in: upower (Ubuntu Xenial)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member
This bug was fixed in the package upower - 0.99.4-2ubuntu0.3
---
upower (0.99.4-2ubuntu0.3) xenial-proposed; urgency=medium
* Fix up_client_new() returning an invalid object (that causes crashes on
any operation) when upowerd is not (yet) started. (LP: #1546641)
*
Got the bug back on xenial. Applied the proposed fix 0.99.4-2ubuntu0.3
and rebooted three times. The bug has not returned. All fixed, thanks.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Just got back from holiday and tried upgrading trusty to xenial again...
My first attempt hit this bug again. However then I found that
unplugging my USB DVB tuner solved it. So now I'm finally able to keep
xenial installed.
Next step was to plug the USB DVB tuner back in and test the above
This problem popped up on my Intel NUC today when I rebooted due to an
application crash (guvcview). I have no idea how or why, as this machine
has been going fine with Xubuntu 16.04 x64 since it was released.
I tried the packages which have been proposed and it does partially
correct the
Hello william, or anyone else affected,
Accepted upower into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/upower/0.99.4-2ubuntu0.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
I uploaded a xenial upower update to the SRU review queue now.
** Tags added: hw-specific
** Description changed:
https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8
Ubuntu 16.04 crashes immediately on login. Default settings not applied
and appearance is a bit
usb errors are related with
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1437492
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
unity-settings-daemon crashed with SIGSEGV in
This bug was fixed in the package upower - 0.99.4-3
---
upower (0.99.4-3) unstable; urgency=medium
* UpKbdBacklight: Don't cache the brightness level, always read
it from sysfs. (LP: #1583861)
* Fix up_client_new() returning an invalid object (that causes crashes on
any
After two (faster) boot, the crash did not occured in my case.
(The default theme was loaded instead of my preferences, as it could be
expected #40 , but reloging in my session reloaded my theme correctly)
Dmesg still indicates that unity-settings raises a segfault (part of the
log just in case)
Hi, I just tested the version on Martin's PPA.
The unity-settings-daemon did not crashed at startup on my rig with this
version of upower, and my theme loaded correctly.
(I will test a second and a third reboot just to be sure)
There is still an usb error appearing in dmesg that i need to
Could anyone who is affected please test my PPA, so that we can go ahead
with that part of the fix for 16.04 LTS and yakkety?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
I can confirm, that this bug can be related to libimobiledevice. I
installed to software without getting it to work under ubuntu 15.04 and
never removed it. After upgrading to 16.04 I got described problems,
which could be solved by removing libimobiledevice.
--
You received this bug
finally there is a fix from upstream kernel
https://git.kernel.org/cgit/linux/kernel/git/next/linux-
next.git/patch/include/linux/usb.h?id=feb26ac31a2a5cb88d86680d9a94916a6343e9e6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Many thanks Martin.
Trawling through the linux-usb and distro kernel mailing list archives
shows that the kernel blocking problem has been around for some time and
discussed at length.
What it seems to boil down to is this:
I put the patches for upower into my PPA for xenial:
https://launchpad.net/~pitti/+archive/ubuntu/ppa . These should stop the
crashes, and instead the UI should now show default values (which are
most certainly wrong). This can only be fixed with a kernel fix to make
upowerd working.
However,
upower patches landed upstream now.
** Changed in: upower (Ubuntu Yakkety)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
I sent patches to the upstream upower bug that improve the behaviour
when connecting to upowerd on D-Bus fails. However, libupower already
behaved in the current way forever, so this is nothing new in Xenial.
Thus the patches will also only help so far: they should avoid the
segfault, but you'll
Already done in comment #32 :)
** Also affects: upower via
https://bugs.freedesktop.org/show_bug.cgi?id=95350
Importance: Unknown
Status: Unknown
** Changed in: upower (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: upower (Ubuntu Yakkety)
Status:
Please:
1. Report to (https://bugs.freedesktop.org/enter_bug.cgi).
2. Paste the new report link here.
3. Set this bug status back to "confirmed".
Thank you.
** Changed in: upower (Ubuntu Xenial)
Status: Confirmed => Incomplete
** Changed in: upower (Ubuntu Yakkety)
Status:
Hi all,
I also encountered this issue. What happened for me is I installed
glib-2.47.92, after the completion of the install my terminal didn't work. Then
I rebooted the system and then I faced this same exact crash (crash
unity-settings-daemon)
So I removed glib-2.47.92 and then I restarted
https://wiki.ubuntu.com/Kernel/Bugs has details on how to file kernel
bugs with useful details
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
unity-settings-daemon crashed with
Those having slow system start/usb enumeration issues should report a
kernel bug as well, fixing upower is going to resolve the segfault but
not the kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
the issue seems an upower on, reported upstream on
https://bugs.freedesktop.org/show_bug.cgi?id=95350 with a simple
testcase
** Bug watch added: freedesktop.org Bugzilla #95350
https://bugs.freedesktop.org/show_bug.cgi?id=95350
--
You received this bug notification because you are a member
So whether it be broken/missing libs or bad USB device enumeration
causing upowerd to be either not available or slow to start, it would
seem unity-settings-daemon could at least be improved to be robust
enough not to segfault if upowerd is not present.
In the meantime, I was able to solve the
I have been facing this issue for a while now.
Some details of my system are as follows:
System:Host: sitspak Kernel: 4.4.0-22-generic x86_64 (64 bit) Desktop:
Unity 7.4.0
Distro: Ubuntu 16.04 xenial
Machine: System: Hewlett-Packard (portable) product: HP ZBook 15 G2 v:
Both packages mentioned above are a part of libimobiledevice (enabled on
upower builds that detect iOSdevices). Both have been replaced by newer
versions. I haven't yet had time to track down why upowerd is linking
the older version.
--
You received this bug notification because you are a member
After trying to launch upowerd manually, I found that two packages were
missing: libusbmuxd2 and libplist2. These are no longer in the Wily
repository. I found and installed both libraries and my problems with
upower and unity-settings-daemon were fixed. Fonts look correct, media
keys are working,
Can confirm that I get the same error as jontyl when clicking on the
Power item in system settings.
Disabling lightdm and manually starting it after booting the computer
does not seem to impact the bug for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Em 03/05/2016 07:47, Rick Harris escreveu:
> One last thing...ice in comment #12 said:
> "Some people say it has to do with a ASMedia USB Controller"
>
> Have found that USB enumeration failure can cause a bottleneck in
> systemd getting the upower.service unit to finally start.
>
> You'll know if
the bug must have something to do with a boot error.
when I got this bug after next reboot the system hangs for 2 min on post with
error code 99 and
this error dissapears only if I shut down the power completly.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm seeing this on a Sony Vaio VPCSB.
I'm also getting a problem with System Settings which may be related.
Clicking on Power, the System Settings window freezes and then
disappears. If I run unity-control-center from a terminal it prints the
following as it dies:
libupower-glib-WARNING **:
One last thing...ice in comment #12 said:
"Some people say it has to do with a ASMedia USB Controller"
Have found that USB enumeration failure can cause a bottleneck in
systemd getting the upower.service unit to finally start.
You'll know if the system is hit with this as it'll be much slower to
Thanks Rick. I proposed that might be the cause last week but pitti said
it wasn't possible. Maybe it is...
** Changed in: upower (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: upower (Ubuntu Yakkety)
Importance: Undecided => Critical
--
You received this bug
Looks to be a race condition where the session (and so unity-settings-daemon)
is started before systemd has finished starting the upower.service unit.
u-s-d tries to query the state of power and segfaults when upowerd hasn't
finished initialising to be able respond.
>From syslog:
17:14:31
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upower (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: upower (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
This issue occurs on my lenovo laptop when I install nvidia drivers and then
plug in a second monitor.
If I do not plug in a second monitor this issue never appears for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
... which makes this more like a bug in upower.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
unity-settings-daemon crashed with SIGSEGV in
up_exported_daemon_get_lid_is_closed()
It appears up_client is not NULL. But up_client->priv->proxy is NULL
** Also affects: upower (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/1546641
This check was introduced in https://git.gnome.org/browse/gnome-
settings-daemon/commit/?id=d491ebf63, so this needs to get backported.
** Changed in: unity-settings-daemon (Ubuntu Yakkety)
Status: Confirmed => Triaged
** Changed in: unity-settings-daemon (Ubuntu Xenial)
Status:
It's not just that one line, it seems the lid_is_present internal
variable is missing completely from u-s-d.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
unity-settings-daemon
** Changed in: unity-settings-daemon (Ubuntu Xenial)
Importance: Undecided => Critical
** Changed in: unity-settings-daemon (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/power
/gsd-power-manager.c#n2589 checks whether the computer has a lid before
it queries the status for it. But unity-settings-daemon apparently did
not get that fix yet as per the StacktraceSource.txt attachment:
3323:
Some people say it has to do with a ASMedia USB Controller.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
unity-settings-daemon crashed with SIGSEGV in
It seems to be loosely tied to the motherboard/BIOS. I have two Dell
9020 desktops, although they weirdly have different motherboards and
different POST appearance. Only one of them experiences this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
we need someone to fix this.
here are somne more informations from me :
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1570558
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
400 additional crash reports for this since last night...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
unity-settings-daemon crashed with SIGSEGV in
** Description changed:
- Do not Know. Last thing done: work screenlets, update, upgrade, dist-
- upgrade, reboot.
+ Ubuntu 16.04 crashes immediately on login. Default settings not applied
+ and appearance is a bit ugly (incorrect font hinting, in-window menus
+ etc).
+
+ ---
ProblemType:
Duplicate bug 1557940 from errors.ubuntu.com shows 3080 users affected and
climbing. Me too...
https://errors.ubuntu.com/problem/8ca9c548fc4e2fc1d4bf827bbd85c72df59313f8
** Changed in: unity-settings-daemon (Ubuntu)
Importance: Medium => Critical
--
You received this bug notification
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1546641
Title:
unity-settings-daemon crashed with SIGSEGV in
57 matches
Mail list logo
