** Changed in: hal
Importance: Unknown = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/361689
Title:
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when
assembling
** Changed in: hal
Importance: Critical = Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/361689
Title:
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when
assembling
Ahhh! Is this bug back?
The server I was having a problem with is 1000 miles away from me now
and I rebooted it and it didn't come back up. Thinking back a few hours,
I remember that update-manager installed a HAL update.
N! I need my server and this is going to force me into weeks
Didn't mean to sound upset at anyone in my previous post. I know that
Chris did an awesome job with the first patch. I'm just upset and
looking for a support group :-)
The sooner we can get a permanent fix for this issue, the sooner I can
get a good night's sleep.
Please, anyone who is capable,
This bug hasn't regressed, as the recent HAL update was completely
unrelated, and didn't even touch any code AFAICT. If you're experiencing
any issues, it's defaintely not related to this bug, even if you are
experiencing a HAL crash.
You should open a new bug report, preferably by submitting a
Oli Wade [2009-06-17 9:41 -]:
After applying this update I am having trouble with my X server. There
are the following errors in the log:
(EE) config/hal: NewInputDeviceRequest failed (8)
Do you think it could be a side effect?
The hal update didn't change anything wrt. input
It happened after a reboot - I blamed this update due to the hal in
the error message.
I've downgraded (sudo apt-get install hal/jaunty libhal1/jaunty libhal-
storage1/jaunty) but the problem remained through several reboots until
I did a shutdown and then poweron.
Therefore I suspect some
Oli Wade [2009-06-18 8:56 -]:
Therefore I suspect some part(s) of the hardware might have been in a
weird state and there is nothing wrong with the update.
OK, thanks for checking!
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid devices
After applying this update I am having trouble with my X server. There
are the following errors in the log:
(EE) config/hal: NewInputDeviceRequest failed (8)
(EE) config/hal: NewInputDeviceRequest failed (8)
(EE) config/hal: NewInputDeviceRequest failed (8)
(EE) config/hal:
This bug was fixed in the package hal - 0.5.12~rc1+git20090403-0ubuntu2
---
hal (0.5.12~rc1+git20090403-0ubuntu2) jaunty-proposed; urgency=low
* debian/patches/50_no_crash_on_md_blockdev.patch:
- When adding a block device, don't assume that the parent
has storage
The patch from jaunty-proposed WORKS for me! Thank you!
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid devices
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Patch also worked for me on AMD64. Thanks, Chris.
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid devices
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: verification-done
** Tags removed: verification-needed
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid devices
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Accepted hal into jaunty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: hal (Ubuntu Jaunty)
Here's a debdiff for the Jaunty update
** Attachment added: hal_0.5.12~rc1+git20090403-0ubuntu2.debdiff
http://launchpadlibrarian.net/27508055/hal_0.5.12%7Erc1%2Bgit20090403-0ubuntu2.debdiff
** Changed in: hal (Ubuntu Jaunty)
Status: In Progress = Triaged
--
hald crashed with
** Also affects: hal (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Tags added: regression-release
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid devices
https://bugs.launchpad.net/bugs/361689
You received this bug notification because
** Changed in: hal (Ubuntu Jaunty)
Importance: Undecided = Medium
** Changed in: hal (Ubuntu Jaunty)
Status: New = In Progress
** Changed in: hal (Ubuntu Jaunty)
Assignee: (unassigned) = Chris Coulson (chrisccoulson)
--
hald crashed with SIGSEGV in
All,
Has everyone else been able to work around this issue, or is it just me?
Since my jaunty update, I can't get mouse or keyboard with mdadm
installed.
I was hoping someone would tell me what to do about the libblkid1
dependency in Chris's hal update---at least on amd64---but no traffic
here
Spoke too soon. After installing both Chris's fixed hal and the
libblkid1 update above, my AMD64 system failed to boot, pausing about
1/5 of the way through. If I hit Alt-Ctl-Del, I could get the boot to
resume but with my / mounted read-only. I suspect something is wrong
with the libblkid1
Yes, I have the same problem.
From my quick investigation, the problem was when the findfs binary was called
and it was stuck on that binary execution.
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid devices
https://bugs.launchpad.net/bugs/361689
You
Eric, thanks for confirming. Is your system AMD64 or i386?
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid devices
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Please don't do silly things like install libblkid from karmic - that's
totally unsupported and is likely to break your machine.
Everyone is at UDS at the moment but I'll see if this could be
considered for a SRU when everyone gets back.
--
hald crashed with SIGSEGV in
It's not something I would have thought of on my own, but it appears to
be a dependency in the amd .deb hal package you posted above:
r...@saturn:/home/ded/Downloads# dpkg -i
hal_0.5.12+git20090512-0ubuntu2_amd64.deb
(Reading database ... 94344 files and directories currently installed.)
my system is AMD64.
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid devices
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Chris et. al.,
OK, I get it now. karmic is the next release---my bad, just an end user
here.
Still, is there some repository that has version 2.15 of libblkid1 for
jaunty? Would someone please post a link or the sources entry for such
a repository? Looks like Chris's fix to hal needs it from
excuse my ignorance, but do we have any idea when that fix will be available
when I update my system?
shouldn't the severity be high as it breaks any installation that is using raid
afaik? shouldn't that issue be listed in the release note (i would not have
upgraded if I had known..).
I've
Same deal here, except that the fixed hal .deb depends on version 2.15
of libblkid1 which is not available, at least on amd64, in the
repositories either.
My system is now working (after some painful googling with links) after
applying the following:
Update seems to be in repository already, waiting for the index to be updated.
These builds can be downloaded @
http://nl3.archive.ubuntu.com/ubuntu/pool/main/h/hal/hal_0.5.12+git20090512-0ubuntu2_i386.deb
So... may I suggest the new hald build be uploaded to the jaunty
repository?
I've spent the last 3 hours debugging what seemed to be a DBus problem,
but turned out to be this. Then I needed to pull the fix from karmic
because the fix is not available in the jaunty repo.
--
hald crashed with
** Changed in: hal
Status: Confirmed = Fix Released
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid devices
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I committed the fix upstream, thanks Chris!
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid devices
https://bugs.launchpad.net/bugs/361689
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
This bug was fixed in the package hal - 0.5.12+git20090512-0ubuntu2
---
hal (0.5.12+git20090512-0ubuntu2) karmic; urgency=low
* debian/patches/50_no_crash_on_md_blockdev.patch:
- When adding a block device, don't assume that the parent
has storage capability. This fixes a
Also confirmed, problem appeared after creating mdadm raidset and
reboot.
Chris' build fixed my problem as well
Thanks!
** Attachment added: lshal.log
http://launchpadlibrarian.net/26722920/lshal.log
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid
Adding my voice to the chorus - same problem.
Haven't tried the patch yet (I'm away from the box right now), but will
ASAP. I agree that there should be consideration of increasing
importance if that's still appropriate.
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when
** Summary changed:
- hald segfault when using a raid volume
+ hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid devices
--
hald crashed with SIGSEGV in hotplug_event_begin_add_blockdev when assembling
mdraid devices
https://bugs.launchpad.net/bugs/361689
35 matches
Mail list logo
