Public bug reported:
Description:Ubuntu 20.04.3 LTS
Release:20.04
ubuntu-restricted-extras:
Installed: 67
Candidate: 67
Version table:
*** 67 500
500 http://ca.archive.ubuntu.com/ubuntu focal/multiverse amd64 Packages
100 /var/lib/dpkg/status
In up-to-date
I had a version of this bug.
- starting from 18.04 LTS, with all package updates
- software-updater didn't offer 20.04 (surprised me this many months
after 20.04 was released)
- followed https://ubuntu.com/blog/how-to-upgrade-from-ubuntu-18-04-lts-
to-20-04-lts-today
- all went well until
Oops:
The problem has gone away. I'm not sure why. Things that I did:
- updated thunderbird (that didn't fix the problem by itself -- I did
that before posting #2)
- did a software update on the server (Fedora 32). But that doesn't
explain the problem since the problem arose WITHOUT a
I had a problem much like this.
- in 2020 January.
- Ubuntu 18.04
- broke when I updated Thunderbird from 1:52.7.0+build1-0ubuntu1
- fixed when I rolled it back and pinned it.
With recent updates, even 1:52.7.0+build1-0ubuntu1 failed in a way that
seems the same.
I then updated to the latest
I'm getting this too. /var/log/syslog gets this:
Feb 17 11:17:01 redback console-kit-daemon[3481]: GLib-CRITICAL: Source
ID 373 was not found when attempting to remove it
>From reading this launchpad entry, I infer that it is a bug in each
application that generates this. So perhaps my message
It might be useful to look at these Fedora bz entries. Not sure.
https://bugzilla.redhat.com/show_bug.cgi?id=1046935
https://bugzilla.redhat.com/show_bug.cgi?id=1069403
** Bug watch added: Red Hat Bugzilla #1046935
https://bugzilla.redhat.com/show_bug.cgi?id=1046935
** Bug watch added: Red
Just happened to me again. After an upgrade to
Linux version 3.2.0-58-generic (buildd@allspice) (gcc version 4.6.3
(Ubuntu/Linaro 4.6.3-1ubuntu5) ) #88-Ubuntu SMP Tue Dec 3 17:37:58 UTC 2013
$ sudo dkms status
[sudo] password for hugh:
nvidia-304, 304.88, 3.2.0-53-generic, x86_64: installed
I have experienced this problem on my Ubuntu 12.04.3 LTS system.
Here's an extract from dmesg output:
[ 30.521761] NVRM: API mismatch: the client has the version 304.108, but
[ 30.521763] NVRM: this kernel module has the version 304.88. Please
[ 30.521764] NVRM: make sure that this kernel
I think I hit this too.
Very puzzling because I first I used the GUI without invoking it from a
terminal. It worked for a while and then silently went away. Not even
an oil slick.
When I invoked it from a terminal (sudo update-manager -d) it had this
Signal 0 message (which makes no sense to me
How can I nominate this for Precise? Quantal? Raring? I've
experienced the symptoms with each (not all the same).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791833
Title:
Dell ST2220T Monitor
Yeah, it does seem slow.
I'm installing 13.04 on my Acer Revo (Intel Atom) box. It already has
DOS, Fedora 19, and 13.04 (I'm installing another 13.04 to track down a
bug). Before installation even asks where to install, it does a grub-
mount, burning just under 2 minutes of CPU (I was watching
@Jose #56:
lsusb does as you say. There is a bit more with -v. Identical on
Fedora 19.
I don't see the dmesg errors that you see.
I said that touch was working with 12.10 to some extent (I didn't test
much).
Well, it isn't working on 13.04. The first and maybe second click
work but after
This but persists: it is in 12.04 LTS with all current updates applied.
There are several problems. The first one is that K3b incorrectly
reports the problem. wodim fails with an I/O error, well into burning:
Track 01: 10 of 625 MB written (fifo 100%) [buf 91%] 10.2x.
Errno: 5 (Input/output
I'm using Firefox 22.0 on Fedora 19. I tried to log into a site typing
a lowercase name. Auto completion offered both the lower case and
initial caps version. But nothing I tried would let me get the
lowercase name (tab, mouse click (on choices, or on other part of form),
arrow key).
Jesse on
For some unknown reason, this problem showed up on my system recently
(XFCE / Ubuntu 12.04.2 LTS system with all updates).
Deleting ~/.config/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml and
logging in again didn't fix it for me. (See #7)
That file contains property name=ThemeName
Still broken in 12.04 LTS. Surely it is time to support Long Term
Support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1038093
Title:
Fedora17 and ArchLinux dont appear in GRUB menu
To manage
I updated for 10.04 LTS AMD64 = 12.04 LTS AMD64 in the last few days.
Cheese went from working to failing in the way described above:
At launch, it took 100% CPU and did not even show a window.
This was true with and without my HP USB webcam plugged in.
I wanted to give a useful traceback but the
Addendum to #10: guvcview works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/963920
Title:
Cheese doesn't start, hangs with 100% CPU
To manage notifications about this bug go to:
@Jefrey Walton
I agree: it is amazing that this is not fixed. Especially when the status is
Fix Released.
But there is an easy manual work-around: before running update-grub,
mount the non-Ubuntu Linux boot partitions. Then os-prober finds them!
--
You received this bug notification because
This bug is NOT fixed.
I just updated my up-to-date 10.04 system to 12.04.
I'm hitting this bug now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/863741
Title:
apt doesn't want to replace
Although Update Manager cannot deal with the problem, this seems to fix it:
sudo apt-get install rpcbind
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/863741
Title:
apt doesn't want to replace
I don't know in what sense the Fix [is] Released.
I just updated my 12.04 and 12.10 systems and, after the updates, they
still exhibited the bug.
Please explain.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm getting a particularly frustrating variant of this problem with
firefox 17.0 on 64-bit Fedora 17 Gnome.
I get a stack of these cookie confirmation dialog boxes and I wish to
click allow for Session on each of them. The top of the stack won't
take a click! If I drag the FF window, some of
See also https://bugzilla.mozilla.org/show_bug.cgi?id=633763 Cookie
confirmation dialogs should be tab-modal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/833952
Title:
cookie dialogues can pile up
Touch on ST2220T works with 12.10 but not 12.04. Since 12.04 is LTS, I
respectfully request that the fix be backported.
I'm not sure what multitouch support is supposed to look like, so I
don't know if it works with the ST2220T under 12.10.
--
You received this bug notification because you are
Romano: +1
12.04 is LTS: supported of some more years.
Furthermore, Mythbuntu only supports LTS, and the proprietary driver is
necessary for home theatre applications.
So: this needs to be fixed for 12.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1033538
Title:
k9copy calls kdesu but kdesu password window never appears
To manage notifications about this bug go to:
Public bug reported:
k9copy should be run as a regular user but it needs superuser privileges
for some reasons. It apparently invokes a kdelib routine kdesu to
escalate its privilege. In my case, the main k9window becomes
unresponsive, awaiting kdesu's result. But there is no kdesu window for
A little more data from another run.
Here's what ps laxgwf shows while kdesu is waiting vainly for a
password.
0 1000 2562 2510 20 0 835828 50804 n_tty_ Sl+ pts/2 0:03 |
\_ k9copy
4 0 2575 2562 20 0 53220 1992 n_tty_ Ss+ pts/4 0:00 |
A work-around:
When googling for one of the messages, I found this thread (in Italian,
which I don't understand): http://www.linuxmind-
italia.org/index.php?topic=11584.0. The last message seems to say that
things worked after he deleted .kde.
I renamed ~/.kde so it would not be found by KDE.
** Patch added: the difference between the old .kde (failure) and the new .kde
(success)
https://bugs.launchpad.net/ubuntu/+source/k9copy/+bug/1033538/+attachment/3250583/+files/dot-kde.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
see https://bugs.freedesktop.org/show_bug.cgi?id=46557
Work around: pass mem=2g to kernel (from grub)
** Bug watch added: freedesktop.org Bugzilla #46557
https://bugs.freedesktop.org/show_bug.cgi?id=46557
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
This Maverick bug looks a lot like
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/859539
(Oneiric).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/722019
Title:
Failed to install the
This bug affects me.
I invoked usb-creator-gtk without knowing that was its name: I used
Startup Disk Creator from the Dash Home thing on my Unity desktop
(Oneiric + updates). It would be wise to keep names consistent.
The thing failed after 10 minutes of copying files to the thumb drive.
This
** Attachment added: message from usb-creator-gtk installation failed: Failed
to install the bootloader; Quit
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/859539/+attachment/2662361/+files/Screenshot%20at%202012-01-08%2001%3A21%3A22.png
--
You received this bug notification
It is extremely confusing and stupid that authenticating to policykit
(or whatever puts this up) has no effect on the outcome. Failure has
already happened.
** Attachment added: policy kit(?) popup. usb-creator has ALREADY given up,
so authenticating here doesn't help.
This Oneiric bug looks a lot like
https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/722019
(Maveric).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/859539
Title:
usb-creator-gtk fails to
Hmm. Still fails for me with --allow-system-internal.
This time I ran from the command line:
usb-creator-gtk --iso=Ubuntu11.10/ubuntu-11.10-desktop-i386.iso
--allow-system-internal
No logging appeared on stderr (or stdout for that matter).
The command did not complete until I had entered the
I experience this bug in 11.10 + updates for AMD64. There are other sightings
on the web:
https://lists.ubuntu.com/archives/ubuntu-uk/2011-December/032588.html
https://forums.virtualbox.org/viewtopic.php?f=3t=46554
I don't know if this is a unity-greeter bug or a bug in acpid's
See also https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/792242
power button shuts down immediatly (no warning)
This seems to be a different manifestation of what is likely the same
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@ Martin Pitt #23
Is your proposed fix to nvidia-common supposed to fix jockey's handling
of installing proprietary AMD drivers (fglrx)? That seems rather
counter-intuitive.
I have a fresh AMD64 installation of Oneiric, plus all updates (but no
-proposed). Jockey fails with the message sorry
Public bug reported:
There are many bugs fixed between simple-scan 1.0.3 (the latest version
released for Lucid) and the current version, 3.2.0.
I've used the version in
https://launchpad.net/~robert-ancell/+archive/simple-scan (2.32.0.1-0ubuntu1)
but it too has serious bugs fixed in 3.2.0.
Since 10.04 LTS is still supported, could you backport the fixed version
of Simple Scan to 10.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/741628
Title:
simple-scan creates broken PDF's
To
From reports in various fora, this bug is common.
http://phoronix.com/forums/showthread.php?31961-Notes-on-Acer-Aspire-One-522
http://ubuntuforums.org/showthread.php?t=1680348
A workaround has been found: unload the wired ethernet module before
entering the WPA password. Works for me.
** Also affects: linux
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785569
Title:
Ubuntu 11.04 freeze on Acer AO 522
To manage notifications about this
This bug is similar to 785569
Be very clear whether your wireless card is Broadcom BCM 4313 or some
Atheros chipset. This bug is for BCM4313.
I found that I could crash with either the BRCM80211 driver or the WL
driver. This makes me think that the problem is with the atl1c driver
(part of the
Also see bug 775034
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785569
Title:
Ubuntu 11.04 freeze on Acer AO 522
To manage notifications about this bug go to:
Another workaround: If you add PXE netbooting at the front of the BIOS
boot options, somehow the wired interface gets set up in a way that
prevents the atl1c and WL drivers from causing our problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have an ao522. In my case, the problem is with the wireless support.
When I connect to my wireless, shortly after (immediately or sometimes
after a delay) the system locks up hard. No X updates (clock on desktop
does not advance). No response to keyboard or mouse or soft poweroff.
This is a
I don't understand the Won't Fix. This bug shows up in Lucid LTS
which is still supported. See the status near the top Nominated for
Lucid by Amano.
It definitely shows up in Lucid, even with recent updates.
How could creating a clone of this bug report help anything?
--
You received this
If you read enough of this bz entry, you will see that it cannot be
fixed by a new Adobe Flash. Proof: I have the problem but don't have
Flash installed.
My best guess is that this is a GTK bug. You will see hints of this if
you read the whole bz entry. Or just look for GTK.
--
You received
@Nigel:
Your BIOS has chosen to set up the MTRRs in a way that cannot be fixed by the
kernel (or mtrr-uncover) without changing the memory caching ranges.
The BIOS uses overlapping ranges. That won't work when the system wants to
change uncachable to write-combining for an X driver.
The kernel
@sylvain Bourdette:
Is the message still in dmesg output in Maverick?
--
Error probing SMB2 boot message on nVidia ION chipset (Acer Aspire Revo,
ASrock ION 330, ASUS netbooks...)
https://bugs.launchpad.net/bugs/443113
You received this bug notification because you are a member of Ubuntu
Bugs,
I experienced this gparted failure with the 10.10 i386 live-cd. I could
work around it with the .deb in message number 58.
--
gparted crash at start: glibmm-ERROR **
https://bugs.launchpad.net/bugs/617885
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have an Acer Revo R1600 with one of these wireless devices. Out of
the box, Lucid's driver didn't work. To fix it, I created an empty file
in as described in #12 and elsewhere. It works for me.
I don't have the machine at hand to check exactly what I did, but I do
have the output of dmesg.
This is a real bug. It affects me in Lucid 10.04 LTS. It did not
affect me in 8.04 LTS.
Some Radeon 7000 VE cards have two VGA connectors and some have one VGA
and one DVI connector. The current code assumes tow VGA.
A fix has been checked in upstream:
How different is an RT2860 driver from an RT3090 driver? Is it better
to use the built-into-lucid 2860 driver or try to install Markus' 3090
package?
BTW, Markus' PPA doesn't work for Lucid even if the .deb does. It needs
a populated lucid directory.
--
Ralink RT3090 Wireless Not Supported in
I see no value in insults.
I hit this problem. It is real. This launchpad entry helped me work
around the problem. I expect never to hit it again. I'm here to help
make things better for other Ubuntu users.
My disk drive has never been used in RAID and yet dmraid detected that it had.
How
See this bug that has been determined (correctly, I think) to be not a
dmraid bug https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/543008
My particular experience was quite a surprise and wasted a lot of time.
Some details are in that bug report.
dmraid decided that my (only) disk was part
I added to
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/573618
--
Ubiquity can't find the sata hard disk (promise 376 chip)
https://bugs.launchpad.net/bugs/543008
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I experienced this too when trying to install Ubuntu 10.04 i386
(released version).
My computer is an old eMachine, with the original disk. It has never
been RAIDed. Heck, the machine doesn't have the appropriate controller
and has never had a second drive.
I had a difficult time figuring out
I think that Flash provokes the bug more often than other things, but I
don't think that this is a Flash bug. Read my comment #92.
My desktop is Fedora 11. I get these crashes regularly if I leave a lot
of tabs open for a long time. I don't have Flash installed on the
system. I don't know if
I assume that this is the wrapper: www.cbc.ca/video/swf/UberPlayer.swf
I don't know much about flash. I did a swfdump (from swftools) on it.
I got a set of warnings:
Warning: Invalid jump instruction jump from 60 to 143 (120)
Warning: Invalid jump instruction jump from 118 to 128 (125)
Warning:
For what it's worth, I just had this hit me again but on Fedora 11 with
Firefox 3.5.8 on x86-64. Note: I don't have Flash on the system. The
fact that it is Fedora should not be important since this is an upstream
bug.
Removing the warning does not remove the bug, it just obscures it.
If the
I don't think that the bug is related to Flash: I get it without having
Flash on my system. I do think that Flash makes everything worse :-)
Again, I point to this bug report:
http://bugs.freedesktop.org/show_bug.cgi?id=21583
Unfortunately, that report has been diluted by a bunch of Cairo
Public bug reported:
Binary package hint: mythbuntu-gdm-theme
On Ubuntu 9.10 + mythbuntu on AMD64 with all current updates:
My disk is filling up with messages logged in /var/log/gdm/:0-greeter.log.
These messages are repeated:
Window manager warning: Screen 0 on display :0.0 already has a
Micah said it's only a warning, so nothing bad should happen.
Please read comment 67. This diagnostic is a warning of bad things
going on. They will eventually bite you unless you restart FireFox.
--
Gdk-WARNING **: XID collision, trouble ahead
https://bugs.launchpad.net/bugs/401823
You
I don't think that suppressing the warning message fixes the underlying
bug. This is a rather deep bug. Have a look at
http://bugs.freedesktop.org/show_bug.cgi?id=21583
--
(firefox:24993): Gdk-WARNING **: XID collision, trouble ahead - overeager XID
caching
re mtrr-uncover: I updated it to deal with a change to kernel header
asm/mtrr.h that hijacked a symbol that I had used.
The link is now ftp://ftp.cs.utoronto.ca/pub/hugh/mtrr-uncover-2009august14.tgz
Best advice: look in that directory for the newest version, indicated by the
filename.
--
ilna: I notice that error now on my Fedora 11. I'm too lazy to check,
but it looks as if the kernel header changed and hijacked a symbol that
I had been using.
quick fix: issue this shell command in the mtrr directory
sed -i -e 's/\mtrr_type\/_dhr/g' mtrr-uncover.c
Then make again.
I am a
ilna:
Glad to hear that the kernel's clean up code worked. Could you post the
/proc/mtrr contents when cleanup is not enabled? I'd like to see what
it is fixing.
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB RAM and with Memory Remapping
This version of mtrr-uncover should compile cleanly with the new asm/mtrr.h
header file.
ftp://ftp.cs.utoronto.ca/pub/hugh/mtrr-uncover-2009august14.tgz
Thanks, ilna, for pointing out the problem.
--
MTRR is not properly setup on Intel Northbridge Chipset (P35, X38, X48) with
more than 3GB
I tried to use apport-collect but it required more access rights than I
am willing to give it.
Please read #3 -- #1 is confusing.
This bug still exists in 9.04. It also exists in Fedora 11. It is in
upstream (I'm sure, by code inspection).
Note: I said that MTRRs with length =4GiB were not
** Attachment added: /var/log/dpkg.log.4.gz
http://launchpadlibrarian.net/29269295/dpkg.log.4.gz
--
package linux-image-2.6.27-9-generic 2.6.27-9.19 failed to install/upgrade:
subprocess post-installation script returned error exit status 3
https://bugs.launchpad.net/bugs/316644
You
This was not a distribution or release upgrade. It was just an upgrade
within 8.10. So there is nothing in /var/log/dist-upgrade/
I will attach /var/log/apt/term.4.gz, a logrolled version of term that
covers this period. Unfortunately, it ended abruptly, and is
incomplete. This was not caused
As far as I can tell from this thread, the best current answer of
Jaunty+MythTV users with ATI video cards was given here
https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/341898/comments/87
That was six weeks ago. Is there going to be an update to fix the
underlying problem in the near
I'm now using Ubuntu 9.04 on my x61t.
GLXgears now reports varying amounts in the range 900 to 1150 without
any mucking with MTRRs. That suggests that the Intel X video driver now
uses the PAT mechanism. Good!
The MTRRs are still overlapping.
I had to change mtrr-uncover to deal with a
Public bug reported:
Binary package hint: ubiquity
I installed the 9.04 beta AMD64 on my Thinkpad x61t.
Using advanced on one of the screens (I forget which one), I specified
that grub's boot record should be installed on /dev/sda9 (the only
choice besides /dev/sda) (I admit that I don't
Is there a new version to try for Intrepid?
--
bluetooth mouse will not connect
https://bugs.launchpad.net/bugs/310893
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
*** This bug is a duplicate of bug 310893 ***
https://bugs.launchpad.net/bugs/310893
On my Thinkpad x61t, running 64-bit Intrepid, my bluetooth mouse will no longer
pair.
I use the bluetooth applet.
The device seearch sees the device Rocketfix Bluetooth Mouse
When I select it and press
lessoffensive:
No, I have not tested the patch.
I'm actually experiencing the problem on Fedora 10 (my main desktop). I
use Ubuntu on some computers but not long enough to experience this
problem.
I am also concerned that the patch isn't in a final form yet. If I
remember correctly, the
I have a thinkpad x61t with an intel video chipset. I have installed 4G of RAM.
I am running Intrepid with 64-bit kernel 2.6.27-11-generic.
The Intel X driver works but cannot set the frame buffer to write combining.
glxgears reports 450 FPS.
If I run mtrr-uncover (see above) and restart X,
See the libxcb project bugzilla entry
https://bugs.freedesktop.org/show_bug.cgi?id=20254
See the firefox project bugzilla entry
https://bugzilla.mozilla.org/show_bug.cgi?id=458092
--
firefox-3.0b5 received an X Window System error: 'BadIDChoice'
https://bugs.launchpad.net/bugs/220628
You
*** This bug is a duplicate of bug 220628 ***
https://bugs.launchpad.net/bugs/220628
** This bug has been marked a duplicate of bug 220628
firefox-3.0b5 received an X Window System error: 'BadIDChoice'
--
repeated crash BadIDChoice on hardy
https://bugs.launchpad.net/bugs/255195
You
Is there a fix for Intrepid? I'm trying to install Mythbuntu 8.10 and
have hit this problem. I duplicated the problem with Ubuntu 8.10.
(For what it is worth, Fedora 10 has this problem too.)
--
install failure (regression) with ProSavageDDR graphics chipset
George Lesica: your message appeared in the kernel log (dmesg) whereas
the message reported in the first report is from the xorg log. I think
that the message in the xorg log might vary between video drivers. The
one in kernel log should be consistent.
I'm surprised that you have this problem
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/21150512/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/21150513/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/21150514/Dependencies.txt
**
Public bug reported:
Binary package hint: linux-image-generic
update manager was installing a lot of packages. The installation of
this package failed.
I have not yet tried to reboot.
Here is the output of uname -a (reflecting the previous kernel):
Linux redaver 2.6.27-7-generic #1 SMP Tue Nov
With regard to my earlier comment (
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.24/+bug/224404/comments/42
):
I have updated the mtrr-uncover a few times. Look for the newest appropriately
named tarball in the ftp directory: ftp://ftp.cs.utoronto.ca/pub/hugh/
--
For what it is worth, I've been experiencing this for some time on
64-bit Fedora 9. And I don't have any plugin for Flash.
It isn't reproducible. It happens every few days. I'm having trouble
using gdb on Firefox so I don't have much diagnostic information to add.
GDB keeps stopping the
see https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/255195
--
firefox crashed
https://bugs.launchpad.net/bugs/116189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
denisius.sion in #58 (probably 3 messages up, but I cannot tell until
after I post) seems to have an MTRR problem.
This message means that the kernel is refusing to change the type of an MTRR as
the driver is telling it to do:
[ 16.285745] mtrr: type mismatch for fb00,80 old: write-back
I've written the program. It works on my one system. Who knows if it
works anywhere else.
Fetch it from ftp://ftp.cs.utoronto.ca/pub/hugh/mtrr-uncover-
2008sept18.tgz
Untar it. cd into the new directory. Type make. Read the manpage man
./ mtrr-uncover.8
Run the command (just a test!)
2.6.27 has been ported to Hardy (a good thing: Hardy is LTS).
Unfortunately, it doesn't quite work because v86d is needed. See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/236937/comments/3
I've written an experimental userland program to rejig MTRRs. Read
about it here:
I'm trying to write a program to rejig MTRR settings to avoid this
problem. More details to follow if it works.
It would help me if people would post the contents of /proc/mtrr for
their systems. If you have a BIOS setting that avoids the problem,
please post /proc/mtrr for both. It would also
I see v86d is problematic:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/246269
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/189621
Before Hardy can move to 2.6.27 this will need to be solved.
(I'm on AMD64, if that matters.)
--
dmi_save_oem_strings_devices: out of memory
This bug affects Hardy when the 2.6.27 kernel is installed from
http://kernel.ubuntu.com/pub/next/2.6.27-rc3/{all,hardy}
I installed this because of the response to 236937.
Is there any .deb containing v86d made available for Hardy?
--
Switched from vesafb to uvesafb, but uvesafb can't work
I wish your message had explained where to find the .debs and a
procedure to install them.
I fetched things from
http://kernel.ubuntu.com/pub/next/2.6.27-rc3/{all,hardy} and installed
them.
The out of memory message is now gone -- thanks.
Reading the dmesg output, I now see several disturbing
[I got some help from BenC and mjg59 on freenode's #ubuntu-kernel]
It turns out that the kernel's IOCTL code just bails (returns an all-0
struct) if the MTRR size field is =4G. There is no room in the size
field of struct mtrr_gentry (defined in /usr/include/asm/mtrr.h).
See case
Public bug reported:
The kernel's Documentation/x86/mtrr.txt
or Documentation/mtrr.txt
describes the ioctl interface to the MTRRs.
The sample code for printing out the MTRRs (mtrr-show.c) fails to
print many of the values. I think that this is a bug in the ioctl
implementation, not the
1 - 100 of 124 matches
Mail list logo