FTR, 4.15.0-62 seems *much* better than 4.15.0-60. With 4.15.0-60 this
system was kernel panic restarting every 75-90 minutes; now it's been up
since I installed 4.15.0-62, over 5 hours ago:
-=- cut here -=-
ewen@naosr620:~$ uname -r
4.15.0-62-generic
ewen@naosr620:~$ uptime
16:09:54 up 5:26,
FTR, I think this is the fix in -62:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?h=master-
next=b502cfeffec81be8564189e5498fd3f252b27900
and it appears to be the only change from -60 to -62:
-=- cut here -=-
ewen@naosr620:~$ zcat
These symptoms sound very much like
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447 (I found
the bug I'm commenting on while searching for additional links about the
issue in 1842447). There's a -62 kernel in proposed updates which
hopefully contains the fix for this bug. See
I agree with Taher (in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/comments/15),
this bug seems to impact a lot of systems (my colo host was kernel panic
restarting about every 75-90 minutes, all weekend). It has a NAT
firewall on it (for the hosted VMs), but no Docker/Wireguard,
FTR, system did boot to working network interfaces with the above
configuration (including pre-up/sleep lines). I'm not sure if there
were warnings issued as the default Ubuntu last action on boot is to
clear all boot messages in favour of displaying the login prompt at the
top of the screen :-(
Even with the apparently fixed version, this "does not work after ifdown
bond0/ifup bond0 cycle" appears to persist:
-=- cut here -=-
ewen@nas06:~$ cat /etc/issue
Ubuntu 14.04.4 LTS \n \l
ewen@nas06:~$ dpkg -l | grep ifenslave
ii ifenslave2.4ubuntu1.2
I ran into what looked like this problem (on Ubuntu 14.04 LTS, with the
postgrey 1.34-1.2 package).
After a bunch of debugging it turned out that neither "service postgrey
stop" nor "service postgrey restart" were actually _stopping_ the
postgrey daemon, which meant it never started with the new
lucid-updates appears to be official updates, so with 2.6.32-23-generic
fixing the problem and being in lucid-updates it seems to be fixed in an
official update. So yes, I think closing the bug with fixed in linux-
image 2.6.32-23-generic is appropriate. (It'd be nice to know
precisely which
Prompted by Dennis's comment, I thought I'd be a bit scientific about
this, and (a) retested with the packages already installed on my HP
NC6220 (behaves as described in bug -- after first suspend audio can be
heard through headphones, but not built in speakers), (b) ensure that I
had the latest
This bug also affects me on a HP NC6220 laptop, with a fresh install of
Ubuntu Linux 10.04 (Lucid).
It appears to be a reversion of the fix in bug #15
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/15), from 2007
(Fiesty, Gutsty). Prior to that fix the internal speakers stopped
patch -r (r == reverse) will unapply a patch. In this case given
there's only one line changed it's actually easier just to edit the file
in a text editor and uncomment the line that was commented out. If
you're new to linux you may find the rest of the steps challenging too,
and might be better
Tested with Hardy Alpha 4 (x86 Desktop). The Gnome configuration (apps
-gnome-power-manager-timeout) still stores the difference between the
screen saver time and the power management time, as in Gutsy. However I
wasn't able to trigger the behaviour of the X11 DPMS off timeout being
set to a
I think I've figured out how to trigger it.
The computer in question is a laptop, with an external CRT connected via
a docking station some of the time -- and all the times the DPMS Off:
value has been incorrectly set, the laptop has been docked with the CRT
connected.
In order to trigger it I
Resetting status to New since there is now (hopefully) a way for others
to reproduce it.
** Changed in: gnome-power-manager (Ubuntu)
Status: Invalid = New
--
[Gutsy] Display sleep sets wrong DPMS off time
https://bugs.launchpad.net/bugs/190537
You received this bug notification because
I've just attempted to reproduce it now, with the same results as you
(ie, the DPMS off time isn't being set as it was previously). I
wondered whether it had something to do with either s2ram, or adding a
monitor on resume (eg, docking with an external monitor) but neither of
those seem to be
lspci -vvnn on HP NC6220 laptop attached, as requested.
** Attachment added: lspci -vvnn on HP NC6220
http://launchpadlibrarian.net/11928656/hp-nc6220-lspci-vvnn.txt
--
No Sound after Resume on some HP Laptops
https://bugs.launchpad.net/bugs/15
You received this bug notification because
** Description changed:
Binary package hint: gnome-power-manager
In Ubuntu Gutsy (7.10) with gnome-power-manager (2.20.0-0ubuntu6), the
System-Preferences-Power Management slider for Put display to sleep
when inactive for shows values that start with the value set in
I suspect the 11 minutes minimum is coming from your
system-preferences-screensaver being set to 11 minutes; the figure
reported in the gnome power manager dialog seems to be offset by the
screensaver amount (even though it doesn't seem to be implemented like
that); I've reported a separate bug
Public bug reported:
Binary package hint: gnome-power-manager
In Ubuntu Gutsy (7.10) with gnome-power-manager (2.20.0-0ubuntu6), the
System-Preferences-Power Management slider for Put display to sleep
when inactive for shows values that start with the value set in
System-Preferences-Screensaver
Attached screenshot showing:
- Screen Saver preference time of 8 minutes (480 seconds)
- Power Manager display off time of 14 minutes (840 seconds)
- gnome configuration apps-gnome-power-manager-timeout-sleep_display_ac
value of 6 minutes (360 seconds; 14 minutes - 8 minutes = 6 minutes)
- X DPMS
** Description changed:
Binary package hint: gnome-power-manager
In Ubuntu Gutsy (7.10) with gnome-power-manager (2.20.0-0ubuntu6), the
System-Preferences-Power Management slider for Put display to sleep
when inactive for shows values that start with the value set in
This might seem really obvious, but you did make (the opposite of)
change listed in this comment:
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/15/comments/1
before you built the modules, right? Ie, you have to uncomment the
line:
pci_set_power_state(pci,
I can confirm that on a HP NC6220 after resume with the -generic Ubuntu
Gutsy kernel (2.6.22-14.47) the internal speakers are mute (but playback
to external speakers and/or headphones is fine).
After reverting the patch mentioned earlier in this bug, at comment:
Ah, yes, I'd forgotten I'd done that:
mkdir .tmp_versions
(somewhere after cd'ing into the directory with the source and before
running make)
After you run the mkdir you can just run make again, and it'll
continue from where it left off.
Apologies for the confusion.
Ewen
--
No
I can confirm that the Firefox package 1.5.dfsg+1.5.0.9-0ubuntu0.6.06.1
no longer crashes when presented with the Mailman admin form where there
is a saved password. Thanks for pushing out updated packages.
Ewen
--
Dapper: Regression: Firefox 1.5.0.9: Saved passwords causes crash with Mailman
I've now modified the patch from Mozilla Bugzilla (linked earlier in
this bug) to apply to Firefox 1.5.0.9 (as shipped with Ubuntu) and
recompiled the Firefox package with the patch (which takes about 2
hours, and 1GB of disk space), and appear to have a non-broken version
of Firefox that is able
I've retitled the bug to make it clearer that (a) it's a regression, (b)
it only affects Ubuntu Dapper, and (c) it's only the Firefox 1.5.0.9
security update which is affected. At this point I don't think we need
any more it doesn't crash for me, but I'm using some other browser
version reports.
In the hope that this will bring the bug to the firefox/security
maintainers attention, I've changed the status to confirmed given (a)
the number of bugs which have been marked as a duplicate of this bug,
and (b) that several people have reported they can reproduce the bug.
It would be nice to
As suggested by Peter Cherriman (https://launchpad.net/~pjcherriman) in
comment:
https://launchpad.net/ubuntu/+source/firefox/+bug/77859/comments/3
I've installed the firefox-dbg package (ie, debug symbols), and
regenerated the core dump and run gdb over it. Like him I see:
Source for affected function that is segfaulting:
void
nsPasswordManager::AttachToInput(nsIDOMHTMLInputElement* aElement)
{
nsCOMPtrnsIDOMEventTarget targ = do_QueryInterface(aElement);
nsIDOMEventListener* listener = NS_STATIC_CAST(nsIDOMFocusListener*, this);
I managed to find the source to firefox-1.5.dfsg+1.5.0.8 on a mirror
(http://mirror.xmu.edu.cn/archive.ubuntu.com/ubuntu/pool/main/f/firefox/;
it's already expired out of security.ubuntu.com and archive.ubuntu.com).
Diff between firefox-1.5.dfsg+1.5.0.8 and firefox-1.5.dfsg+1.5.0.9
reveals that a
Found the patch that got lost:
Mozilla Bugzilla 235336:
https://bugzilla.mozilla.org/show_bug.cgi?query_format=specificorder=relevance+descbug_status=__open__id=235336
(was obvious once I guessed that bz == Bugzilla not Baz/Bazzar
or similar.)
And the relevant patch:
Public bug reported:
Binary package hint: firefox
The latest security update for Firefox for Ubuntu Dapper (6.06), version
1.5.dfsg+1.5.0.9-0ubuntu0.6.06, now causes Firefox to crash repeatedly
when using a saved password field on a Mailman admin login screen. This
did not happen with the
Issolated test case:
http://www.naos.co.nz/tmp/ubuntu/firefox/mailman-signon-page.html
Steps to reproduce is slightly different here, I think because there's
no real form processing behind it. To reproduce:
1. Go to URL
2Enter some string to be the password, eg test (it doens't matter,
34 matches
Mail list logo
