It appears no changelogs have been uploaded to the changelog server
since 4 May 2012.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001609
Title:
Changelogs not being uploaded to changelog server
*** This bug is a duplicate of bug 1001609 ***
https://bugs.launchpad.net/bugs/1001609
Bug #1001609 has been clarified to refer to all updates, so I think this
bug is probably a genuine duplicate.
Don't be confused by the two different kinds of web addresses. update-
manager uses
Confirm the bug is still there in Lucid after upgrade to firefox
12.0+build1-0ubuntu0.10.04.1.
So far I've used the launchpad bug report system for two different bugs.
On both occasions the bug was not fixed, but was marked as fixed, and we
were told to open a new bug report when we pointed out
If anyone is still interested, I can confirm the bug still exists in
Lucid after the latest update to firefox 10.0.2+build1-0ubuntu0.10.04.1.
I believe this is not a returning bug. It was incorrectly marked as
fixed by Launchpad Janitor in reply #27.
--
You received this bug notification
I am still experiencing this bug on Lucid. I am using firefox
9.0.1+build1-0ubuntu0.10.04.2, which is the same version as in Launchpad
Janitor's post above, so I can't agree that this should be classified as
Fix Released.
--
You received this bug notification because you are a member of Ubuntu
Hi Clint, thanks for the reply. I think that either I have made a
mistake and the bug is really fixed, or reply #27 is mistaken and the
bug was not fixed by the update.
Perhaps the problem is that I have somehow not installed the update. The
output of dpkg -l firefox shows
I add this information in case it is useful to anyone: the latest 9.04
update to kernel 2.6.28-19 has fixed it for me.
--
grub error 24 with Jaunty beta
https://bugs.launchpad.net/bugs/353071
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I'm not sure (I don't completely understand the bug-tracking system),
but I think the status of this bug is currently invalid (for Linux) or
fix-released (for xorg-server), and consequently no-one is likely to
try to fix it. Since the released fix from last year only works for some
people and
I am also seeing this problem with a clean install of 9.04 / Jaunty.
The filesystem is (and always has been) ext3.
The problem only occurs with kernels 2.6.28-16 and onwards: I find I can
boot successfully using 2.6.26-15 and earlier.
** Changed in: grub (Ubuntu)
Status: Invalid =
I still have this problem, but as far as I am aware I am not using
Xinerama.
At least, there is no mention of Xinerama in my xorg.conf. Does this mean I
am not using Xinerama, or is it possible I am using it without realising it?
Is it possible there are causes of this problem other than
I have found the same thing in Dapper and Feisty (both fully patched as
of 2007-10-01).
On Dapper:
~/beethoven$ ls -l beet1b*
-rw-rw-r-- 1 alex alex 821768448 2005-08-04 22:45 beet1b.end.wav
-rw-rw-r-- 1 alex alex 214700 2005-08-04 22:40 beet1b.trunc.wav
-rw-rw-r-- 1 alex alex 2321768448
No, for me it always happens when I'm actively using the computer. In
fact, it mostly seems to happen following some rapid mouse clicking.
I bet focus-follows-pointer is a necessary condition to trigger the bug.
That would explain why lots of other people haven't noticed it. f-f-p is
probably a
I've noticed a workaround. Pressing Alt-Tab a few times seems to cure
it, which is quite a relief.
By the way, I'm using focus-follows-pointer
(System-Preferences-Windows, Select windows when the mouse moves over
them). I'm wondering if everyone who experiences this bug has focus-
I've got what I think is the same problem, as mentioned at
http://ubuntuforums.org/showthread.php?t=255898
The pointer is movable, but it can't be used to click in anything, so you are
usually stuck with having to restart X. On one occasion I managed to cure it by
logging in via a remote
14 matches
Mail list logo
