This bug was fixed in the package fwupd - 0.8.1-3
---
fwupd (0.8.1-3) unstable; urgency=medium
* Backport upstream commit to make valgrind optional (Closes: #856344)
* Backport upstream commit to make /boot/efi optional to start
fwupd.service.
-- Mario Limonciello
Forget about comment #25, can't access "mail.google.com" from a
particular wifi network (eduroam), maybe there is a new bug there but I
will investigate further.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Does this bug affect the access to google accounts? After updating to
zeisty, I can access "www.google.com", but "mail.googl.com", for
instance, times out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: fwupd (Ubuntu Zesty)
Assignee: zawheinhtet (zawheinhtet) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663548
Title:
fwupd crashed with SIGSEGV in _int_malloc()
** Changed in: fwupd (Ubuntu Zesty)
Assignee: (unassigned) => zawheinhtet (zawheinhtet)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663548
Title:
fwupd crashed with SIGSEGV in _int_malloc()
** Also affects: fwupd (Ubuntu Zesty)
Importance: High
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663548
Title:
fwupd crashed with SIGSEGV in _int_malloc()
To manage
I spent some more time with this today and concluded that it is systemd
confinement that is causing a majority of this headache. The stuff that
was happening with crashes was just the tip. There were further
problems with refreshing not working, flashing not working too.
I believe this commit
Mario,
Just tried your commits (on top of the Debian pkg) and they seem to fix
the crash for me. I tried on an XPS 13 9350 and on a random desktop
machine. The problem also happened for me in a VM. I didn't try that
patch in there, but that might be a good way for you to try the error
path.
I
Ok, the workaround with commenting out PrivateUsers=yes from
/lib/systemd/system/fwupd.service worked here, too, on the 17.04 on the
Lenovo Thinkpad x230.
fuwpd is not crashing anymore. But i dont really know what the
consequences of this workaround are.
--
You received this bug notification
having the same issue on a Lenovo Thinkpad x230
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663548
Title:
fwupd crashed with SIGSEGV in _int_malloc()
To manage notifications about this bug go
@laney
Thanks for digging into that. I think that's definitely a part that
should be solved, but at least in the interim I believe this can be
avoided in fwupd too by only running this code on supported systems.
Can you please check if
I filed https://github.com/dell/libsmbios/pull/13 which is now waiting
for review
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663548
Title:
fwupd crashed with SIGSEGV in _int_malloc()
To manage
as this crash was originally reported via apport I revert it back to bag
for the fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663548
Title:
fwupd crashed with SIGSEGV in _int_malloc()
To
As this crash was originally reported by apport I revert it back to a
bug report
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663548
Title:
fwupd crashed with SIGSEGV in _int_malloc()
To manage
** Changed in: fwupd (Ubuntu)
Status: Invalid => Triaged
** Description changed:
- ...
+ possible *workaround*
+ Comment out PrivateUsers=yes from /lib/systemd/system/fwupd.service
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: fwupd 0.8.0-1
ProcVersionSignature:
Bug #1663548
How can I destroy the bug? What do I need to do?
** Changed in: fwupd (Ubuntu)
Status: Triaged => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/fwupd/+question/465720
--
You received this bug notification because you are a member of
Commenting out NoNewPrivileges=yes in /lib/systemd/system/fwupd.service
does not fix the issue.
Commenting out PrivateUsers=yes from /lib/systemd/system/fwupd.service
fixes it for me!
So is this an appropriate workaround? What is the root of this issue?
--
You received this bug notification
If you comment out the NoNewPrivileges=yes in
/usr/lib/systemd/system/fwupd.service -- does this now start normally?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663548
Title:
fwupd crashed with
I see this too. For me it goes away if I comment out PrivateUsers=yes
from /lib/systemd/system/fwupd.service.
** 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.
19 matches
Mail list logo
