** Changed in: hal
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/92647
Title:
hal takes about 60 seconds to start up
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
** Changed in: hal
Importance: Medium => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/92647
Title:
hal takes about 60 seconds to start up
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Excellent, thanks for testing the backports.
** Changed in: hal (Ubuntu)
Status: In Progress => Fix Released
--
hal takes about 60 seconds to start up
https://bugs.launchpad.net/bugs/92647
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Having just stumbled across the backports repositories (
https://help.ubuntu.com/community/UbuntuBackports ) through the latest
Kubuntu koffice updates I can now confirm that the hal update in their
fixes my problems too!
Excellent work folks, my boot time is down over 20 seconds from 1:15
yesterd
Thank you for recent feisty-backports upload. I've had zero problems with new
hal.
This is probably "Fix Released" now.
--
hal takes about 60 seconds to start up
https://bugs.launchpad.net/bugs/92647
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
Updated from source package (as provided by Martin above) to Gutsy
version. So far no regressions.
--
hal takes about 60 seconds to start up
https://bugs.launchpad.net/bugs/92647
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I downloaded the debs for libhal, libhalstorage1, hal, and hal-info
packages for Gutsy directly from launchpad and installed (via dpkg). I
am also happy to report no noticeable side effects (or other weirdness).
I can also confirm a reduction in boot speed (5 seconds on my box) and
the desire to s
I'd be very interested to see Gutsy's hal appear in feisty-backports. I rebuilt
current hal and hal-info from gutsy's archive for feisty, and there's no delay
on bootup anymore.
I haven't spotted any regressions so far, but I'm not using any exotic gadgets
either. I'll post back the results afte
I downloaded, created the packages, and installed on my Feisty. No
problems, and boot time indeed got better. The enforced delay is gone.
No side effects, at least not visible.
--
hal takes about 60 seconds to start up
https://bugs.launchpad.net/bugs/92647
You received this bug notification becau
Hi Martin, thanks for the response!
I guess what I'm puzzled about is that looking at what has changed in
that part of the code of hald/linux/blockdev.c it appears that they have
removed the check to see if it matches the dm- pattern and consequent
debug message and usleep(). The comment before
For anyone who is interested to test hot new crack, I prepared hal 0.5.9
packages which work on current Feisty for me:
http://people.ubuntu.com/~pitti/packages/hal-gutsy/
They will be uploaded to gutsy as soon as it opens. NB that you need
hal-info_20070402-1_all.deb for the new hal package.
@Martin: if it helps any, I can test it.
--
hal takes about 60 seconds to start up
https://bugs.launchpad.net/bugs/92647
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
Hi Chris,
Chris Samuel [2007-04-17 11:44 -]:
> Is a fix going to get backported to Feisty or do we just have to put up
> with much slower boot times ?
I am afraid not, hal 0.5.9 has major architectural changes which are
inappropriate for feisty-updates. *However*, if we find some people
who t
Is a fix going to get backported to Feisty or do we just have to put up
with much slower boot times ?
--
hal takes about 60 seconds to start up
https://bugs.launchpad.net/bugs/92647
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
Jason, can you please file a separate bug against linux-source-2.6.20,
please, since it is a completely different problem?
Apparently fixed upstream, so this will get fixed in gutsy when we'll
move to hal 0.5.9.
** Changed in: hal (Ubuntu)
Status: Confirmed => In Progress
--
hal takes ab
yes, I've found that my problem is actually the kernel, 2.6.20 doesn't
play well with ACPI on quite a few systems, it shows it's head when I
modprobe battery,ac and thermal with longer than usual pauses, and then
really shows up with applications like kpowermanager, gkrellm, and hal.
--
hal takes
I think Jason is looking at a different problem, the slowdown I see is
purely down to HAL as I'm running on a desktop with no battery or
thermal ACPI modules loaded and the HAL message is quite explicit that
it is HAL itself waiting for 1 second per logical volume and the
upstream bug report shows
This seems to be a kernel problem, it takes a long time just to modprobe
battery and thermal as well.
--
hal takes about 60 seconds to start up
https://bugs.launchpad.net/bugs/92647
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
-
** Changed in: hal (upstream)
Status: Confirmed => Needs Info
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Same Problem here, waiting 1 sec for each device manager (evms) device.
** Attachment added: "hal.log from feisty: waiting for multiple evms partitions"
http://librarian.launchpad.net/7098430/hal.log
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
ubuntu-bugs m
Startup w/o acpi modules for batt and ac:
[EMAIL PROTECTED]:~# time /etc/init.d/dbus start
* Starting system message bus dbus
[ OK ]
* Starting Hardware abstraction layer hald
ACPI?
I noticed starting gkrellm today that it took an oddly long time to
startup so I straced it, it was hanging on batt and ac acpi for a long
time.
Then I started hal with --verbose=yes --use-syslog and restarted dbus,
hal also hung for a long time on those same acpi parts.
--
hal takes abou
Bootchart from Kubuntu Edgy immediately prior to upgrade to Feisty
showing a boot time of 1m 4s.
** Attachment added: "Edgy bootchart PNG - 20070324"
http://librarian.launchpad.net/6930772/edgy-20070324-1.png
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
ubun
I see the same thing here with Feisty Kubuntu (up to date), each of my
LVM's results in a 1 second wait:
"Waiting 1000ms to wait for device mapper to be ready"
So my boot time here has almost doubled from just over 1m to 1m 52s (+/-
3s) - a bit disappointing really as I upgrade thinking I'd see a
Bootchart from Kubuntu Feisty with current updates showing a boot time
of 1m 57s, over 50 seconds longer than Edgy.
** Attachment added: "Feisty bootchart PNG - 20070325"
http://librarian.launchpad.net/6930775/feisty-20070325-2.png
--
hal takes about 60 seconds to start up
https://launchpad.n
** Changed in: hal (upstream)
Status: Needs Info => Fix Released
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: hal (upstream)
Status: Unknown => Confirmed
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: hal (Ubuntu)
Importance: Undecided => Medium
Status: Needs Info => Confirmed
** Bug watch added: Freedesktop Bugzilla #10364
https://bugs.freedesktop.org/show_bug.cgi?id=10364
** Also affects: hal (upstream) via
https://bugs.freedesktop.org/show_bug.cgi?id=10364
Restarted hald in verbose mode. first timestamp is 09:31:43.595, last
timestamp is 09:32:32.162, so about 50 seconds.
There is a forced 1000 ms wait at blockdev (see timestamps 09:32:10.650
onward) for each device found; this piece of init takes about 20 seconds
to complete.
Have not yet looked f
Can you please get a hal debug output, as described on the second half
of https://wiki.ubuntu.com/DebuggingRemovableDevices, watch the log
output, and see where it hangs for so long? Since it usually starts in
some-three seconds, I guess it just hangs in a single operation instead
of being general
startup hal takes more than 30 seconds. On shutdown, for my surprise, it
was seamless, with absolutely no waits. This is today, yesterday it was
not behaving like this.
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
Similar here on a laptop with AMD64, but it is most visible on shutdown,
when I lose usplash when shutting down dbus & friends. Takes about a
minute to shutdown dbus.
On startup... I will check next boot.
--
hal takes about 60 seconds to start up
https://launchpad.net/bugs/92647
--
ubuntu-bugs
32 matches
Mail list logo