may be a duplicate of 552058 which is on i915 chipset
--
mouse pointer disappears when screen is turned off and on
https://bugs.launchpad.net/bugs/560804
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Confirming on my IBM Thinkpad X41 running 10.4
also seen reported on bug 560804 which is similar or same behavior on
Intel Corporation 82852/855GM Integrated Graphics Device
--
[915GM] Mouse cursor disappears when laptop lid closed
https://bugs.launchpad.net/bugs/552058
You received this bug
Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed.
--
MASTER storing ALSA mixer element values during shutdown hangs
nondeterministically due to internal alsa-plugins pulse check
https://bugs.launchpad.net/bugs/274995
You received this
Public bug reported:
Binary package hint: snort
package snort 2.7.0-19ubuntu1 failed to be uninstalled: subprocess pre-
removal script returned error exit status 123
This report was initiated by the crash-reporting process. I am adding
the following information manually.
Used Synaptic Package
** Attachment added: Screenshot - Synaptic Package Manager console window
following error message
http://launchpadlibrarian.net/20323448/Screenshot-Changes%20applied.png
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/20323455/Dependencies.txt
** Attachment added:
I am attaching a second Screenshot - Synaptic Package Manager console
window following error message which is the scrolled-down view. I also
notice that there seems to be some DpkgTerminalLog.txt info from a
previous session, but today's information also appears toward the bottom
of that log.
Proposed change for ubiquity/scripts/install.py -- I am not on the dev
team so someone needs to review/sponsor this change. This would solve
the issue for future new installs. This does not solve the issue for
the currently installed base.
=== modified file 'scripts/install.py'
---
question answered, several examples provided
** Changed in: netcfg (Ubuntu)
Status: Incomplete = Confirmed
--
ipv6 /etc/hosts missing localhost hostname
https://bugs.launchpad.net/bugs/301430
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
I think this bug lives in ubuntu-installer/ubiquity/
currently line 1525 /scripts/install.py (revision 2954)
1515hosts = open(os.path.join(self.target, 'etc/hosts'),
'w')
1516997 print hosts, 127.0.0.1\tlocalhost
15171772if domain:
1518
+ ***Important summary for those experiencing this bug***
+ Kernel versions where this bug is fixed:
+ 1) 2.6.27-10 from intrepid-proposed
CORRECT
+ Kernel versions where this bug is NOT fixed (if you are running one of these,
please upgrade to known working kernel):
+ 1) 2.6.27-7 from intrepid
@Jens -- whatever DNS server you are using while connected to VPN
probably doesn't quickly return an answer for a query for
localhost, while your non-VPN DNS does. alsa-utils 1.0.17-0ubuntu3
should avoid it in all cases. Also, see below.
@kungmidas -- when I change my DNS to some bogus
Hi Steve,
I'm glad you identified the right package. It was difficult for me to
figure out what actually initially creates /etc/hosts!
What was in your /etc/hosts, if not this?
Exactly what you posted, except for the localhost entry in the ::1 line.
This condition is common across two fresh
).
Thanks for your help and congrats on getting bug 274995 fixed!
Robb Topolski
--
MASTER storing ALSA mixer element values during shutdown hangs
nondeterministically due to internal alsa-plugins pulse check
https://bugs.launchpad.net/bugs/274995
You received this bug notification because you
Laurent, I replied https://bugs.launchpad.net/ubuntu/+source/alsa-
utils/+bug/274995/comments/275 on the alsa-utils issue.
--
ipv6 /etc/hosts missing localhost hostname
https://bugs.launchpad.net/bugs/301430
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
Hi Laurent,
That's odd that the 274995 proposed fix doesn't solve the issue. Do you
have more than 2 machines?
Did you follow the steps mentioned in
https://wiki.ubuntu.com/Testing/EnableProposed to upgrade? Did alsa-
utils update to 1.0.17-0ubuntu3 (the proposed fix) or are you using
Looks like the -9 security update fixed a number of concerning-looking
issues. Is that why our fix wasn't in it?
I tried reapplying the patch from comment 52 into the (-9 directories
instead of -7) and wound up with a system with no wireless devices.
(Fortunately that process left me with .ko~
They're ba-ack.
With a patch at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52
and later a 2.6.27-8 kernel update in backports (mentioned later in bug
286285), I was avoiding kernel panics on 802.11n networks. Now with
2.6.27-9, the panics are back.
also
mention that it is a different issue near resolution and the crackling
sound is not fixed by it.
Thanks!
Robb Topolski
--
ALSA hangs on shutdown - Intrepid Ibex on Dell Inspiron 1525
https://bugs.launchpad.net/bugs/294160
You received this bug notification because you are a member of Ubuntu
facilities
have a facility
identifier of 7, therefore news.local and 56.local are equivalent in
syslog.conf.)
endQuote
Thanks
Robb Topolski
** Affects: sysklogd (Ubuntu)
Importance: Undecided
Status: New
--
undocumented logaudit facility, how to log unknown
Hi Dov, I'm glad you posted. It seems I've made the bug Gods angry --
it won't show itself on my system tonight, and I can't figure out why.
I hate when that happens.
I tried killing pulseaudio while logged in to an X session, and it
still hung while shutting down.
Right.
Killing pulseaudio
I'll buy the beer if this is a BIOS bug.
Bug 295136 (aschuring) is the most succinct test case I've seen on this.
That bug is a duplicate but shows what is going on. It should not be
ignored.
Key observations:
---Quote---
After dist-upgrading to intrepid, Ubuntu appears to hang when shutting
@Luke,
My quick test --
There was the same hang with your new file as written (without the
variable being exported).
THERE WAS NO HANG with
export PULSE_INTERNAL=0
but there was a hang if the variable was not exported.
-- Robb
PS: (reproducing tip for developers and experienced users -- do
@Daniel Chen,
Hi Daniel, you're over my head a little bit. Can you tell me in easier
terms what you'd like me to try and I'll be happy to try it.
@Any,
What does the PULSE_INTERNAL variable do? Was that a potential fix or
just a diagnostic test?
--
MASTER storing ALSA mixer element values
Please reevaluate -- see comment 226
** Changed in: pulseaudio (Ubuntu)
Status: Invalid = New
--
MASTER storing ALSA mixer element values during shutdown hangs
nondeterministically if non-loopback network interfaces are still up
https://bugs.launchpad.net/bugs/274995
You received this
Please reevaluate -- see comment 226
** Changed in: alsa-utils (Ubuntu)
Status: Invalid = New
--
MASTER storing ALSA mixer element values during shutdown hangs
nondeterministically if non-loopback network interfaces are still up
https://bugs.launchpad.net/bugs/274995
You received this
I am going to try and change the invalid status for pulseaudio and
alsa-tools.
alsa-tools, pulseaudio -- please re-evaluate. The primary issue seems
to be that the alsa-tools are trying to find a pulseaudio daemon that is
no longer running after the user has chosen to shutdown or reboot. It
name in
the ::1 line.
Users who manually add the localhost hostname to the ::1 line in
/etc/hosts also avoid this wait. My guess is that users who disable
IPV6 after installing will also avoid this wait for timeout.
Robb Topolski
--
MASTER storing ALSA mixer element values during shutdown hangs
Thanks for agreeing with me, aschuring. :-) However, the change for
126140 certainly won't benefit you so my previous advice of wait and
hope no longer makes sense for some.
This is a cascade of bugs and behaviors.
In bug 295136, FlagMan said, If pulseaudio is the default sound sink
and you are
** This bug is no longer a duplicate of bug 274995
MASTER storing ALSA mixer element values during shutdown hangs
nondeterministically if non-loopback network interfaces are still up
--
Intrepid Ibex hangs when shutting down or restarting...
https://bugs.launchpad.net/bugs/288863
You
*** This bug is a duplicate of bug 274995 ***
https://bugs.launchpad.net/bugs/274995
** This bug has been marked a duplicate of bug 274995
MASTER storing ALSA mixer element values during shutdown hangs
nondeterministically if non-loopback network interfaces are still up
--
acpi seems to
*** This bug is a duplicate of bug 274995 ***
https://bugs.launchpad.net/bugs/274995
This bug 288863 as originally reported is probably a duplicate of bug
274995. However, the symptom of having to shut down using the power
button even after waiting 5+ more minutes is NOT a symptom of 274995.
*** This bug is a duplicate of bug 274995 ***
https://bugs.launchpad.net/bugs/274995
** This bug has been marked a duplicate of bug 274995
MASTER storing ALSA mixer element values during shutdown hangs
nondeterministically if non-loopback network interfaces are still up
--
amixer
This was tipped by aschuring in bug 295136 with Flagman's explanation --
here's another workaround:
STEP A. sudo gedit /etc/hosts
STEP B. Change the first line in the IPv6 section
from
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
to
# The
@aschuring,
can anyone confirm whether they have a search ... statement in
/etc/resolv.conf,
and whether removing that statement fixes the delays?
I did not have a search statement there, but I can see where having one
could lengthen the situation.
--
MASTER storing ALSA mixer element
Even though they have a lot in common, I'm convinced these issues have
two different root causes, but I'm also hopeful that the change for bug
126140 will also avoid ours (bug 274995).
Bug 126140 is about certain PCs that remain powered up at the end of
their shutdown sequence. Anyone remember
*** This bug is a duplicate of bug 274995 ***
https://bugs.launchpad.net/bugs/274995
I concur that this is not a duplicate, FWIW.
My read of this (288863) bug is that the failure mode is that the
computer fails to shut down, the last thing displayed is acpid
exiting.
The hang in 274995
@aldebx re
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/103
What is your failure symptom after the suspend or hibernation?
--
kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100
https://bugs.launchpad.net/bugs/286285
You received this bug
Okay, that helps explain why the rc.0 one alone did nothing for me --
I'm usually rebooting! ;-/
So the workaround is to do both --
sudo ln -s /etc/init.d/NetworkManager /etc/rc0.d/K40NetworkManager
sudo ln -s /etc/init.d/NetworkManager /etc/rc6.d/K40NetworkManager
Great job! That's a temporary
IMPORTANT CORRECTION -- please ignore my prior message, it contained a
major mistake -- this is the corrected version
Okay, that helps explain why the rc.0 one alone did nothing for me --
I'm usually rebooting! ;-/
So the workaround is to do both --
sudo ln -s /etc/init.d/NetworkManager
ATM, I'm able to avoid the delay by going to System - Preferences -
Sessions and clearing the checkbox next to Gnome Login Sound.
--
Delayed Intrepid Login
https://bugs.launchpad.net/bugs/291467
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Accepted -- it must be something else that I did. Sorry for the false
alarm.
--
Delayed Intrepid Login
https://bugs.launchpad.net/bugs/291467
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
*** This bug is a duplicate of bug 274995 ***
https://bugs.launchpad.net/bugs/274995
** This bug has been marked a duplicate of bug 274995
MASTER storing ALSA mixer element values during shutdown hangs
nondeterministically if non-loopback network interfaces are still up
--
Intrepid Ibex
Just a couple of notes on this.
1. For those with working ALSA sounds, but ALSA hangs on shutdowns
lasting about 2.5 minutes, I believe our bug fix is mentioned
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.27.5 --
released November 7th. (I don't know how soon we will see it through
Jakub,
What was the date/time when the system locked up? You'll want to check
your logs matching up those times to help figure out why the kernel
panicked.
As to the printout you provided, those look like routine firewall logs.
To get help with turning that off, see
linux-image-2.6.27-8-generic is looking good.
Beware that this doesn't yet have linux-restricted-modules or
-backports-modules available, these will follow in a bit.
Worth repeating.
I tried to apply only linux-image-2.6.27-8-generic and Synaptic let me
do so without complaint. I booted
*** This bug is a duplicate of bug 286285 ***
https://bugs.launchpad.net/bugs/286285
Bug#295781 does not appear to be a duplicate of bug#286285, which had a
root cause and is patched in wifi code.
--
logs (syslog, messages, kern.log) flooded on new 8.10 installation - no wlan
Okay, I think I'm reading that the 845G is blacklisted from compiz, thus
dodging the bug(s) causing the hang. The status here, however, is Fix
Released. Is that right? Seems there is still an actual bug out there
to be hunted.
--
Intrepid Compiz hangs on login for i830MG and i845 video cards
Dylan, you've most probably got the correct bug report.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52
has a patch that will ease the issue.
There is an update forthcoming in the proposed repository, but so far
nobody has reported on it (it was still missing as of my last
Hi Rocko,
The problem you are describing is
https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990 and
a patch was available for that problem.
But it gets better.
The patch at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/52
includes the patch from
*** This bug is a duplicate of bug 136813 ***
https://bugs.launchpad.net/bugs/136813
** This bug has been marked a duplicate of bug 136813
(Gutsy) help button does not work in gnome-appearance-properties
--
Help-button in gnome-appearance-properties doesn't do anything
Not FIXED in 8.10/Gnome 2.24 see
http://bugzilla.gnome.org/attachment.cgi?id=122030 in
http://bugzilla.gnome.org/show_bug.cgi?id=473181
--
(Gutsy) help button does not work in gnome-appearance-properties
https://bugs.launchpad.net/bugs/136813
You received this bug notification because you are a
Thank you Antonio. That helps assure me that the results I'm seeing
apply to the patch. As also reported above, I now can't shutdown
cleanly without hitting the wifi switch. I'm not certain whether this
is a new behavior or heightened awareness of an existing issue.
for clarity's sake,
11
Tom,
I got the kern.log entry mentioned at
https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/276990/comments/92
which is the patched (comment 85) behavior of that bug. The news is that
I didn't use that patch, I used the patch from comment 52 in this bug.
The patch at
Tom (comment 93),
Please see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/286285/comments/63
for some info.
--Robb
--
iwlagn causes kernel panic on 802.11n wifi
https://bugs.launchpad.net/bugs/276990
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tom, if I use apt-get to remove backports and then try the patch, is
that a clean test?
--
kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100
https://bugs.launchpad.net/bugs/286285
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I removed backports, rebooted, then installed the patch per Tom's
instructions, rebooted, and now I've rebooted several times.
I cannot reproduce the original problem. However, I can't shut down
without hitting the wifi killswitch.
18:45 Shut down from Gnome
18:46 Hanging... hanging... (and
56 matches
Mail list logo
