Public bug reported:
In id3tag.h, the type id3_ucs4_t is typedef'd as an unsigned long.
Clearly this type needs to be a 32 bit unsigned int but an unsigned long
is 64 bit on a 64 bit system. Changing the typedef to read
typedef uint32_t id3_ucs4_t;
and #including stdint.h fixes the problem.
After seeing comment #6 I tried
CLUTTER_VBLANK=none quadrapassel
and it works! Full speed restored.
My video details are in comment #5
--
quadrapassel and gnome shell very slow and unusable probably a clutter issue
https://bugs.launchpad.net/bugs/572465
You received this bug notification because
I see this bug too on Lucid 32 bit. Quadrapassel is unplayably slow, taking
around 5 seconds to respond to control.
lspci output for video:
VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller [8086:2a02] (rev 0c)
Subsystem: Hewlett-Packard
The last kernel upgrade (I think it was 2.6.31-21) installed without
problem so I'd say whatever the problem was has been fixed.
--
Boot failure after kernel upgrade, unable to mount root fs
https://bugs.launchpad.net/bugs/517638
You received this bug notification because you are a member of
I was able to solve the problem by simply reinstalling the kernel
package but after another kernel update it's broken again so there seems
to be a problem with the kernel install process. Is there something I
can check for to find out what hasn't installed correctly?
--
Boot failure after kernel
The kernel panic error message reads:
VFS: Unable to mount root fs on unknown-block(8,2)
--
Boot failure after kernel upgrade, unable to mount root fs
https://bugs.launchpad.net/bugs/517638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If I boot using the recovery mode grub menu entry I get to see a bit
more. Before the kernel panic I get:
RAMDISK: gzip image found at block 0
uncompression error
List of all partitions:
0800312571224 sda driver: sd
08012096451 sda1
0802 310472190 sda2
0b00 1048575 sr0 driver: sr
No
Public bug reported:
After applying a kernel upgrade with Update Manager my system no longer
boots. The boot process dies quickly with a kernel panic stating that it
was unable to mount the root fs. I have to select the previous kernel
from the GRUB menu to get a working system.
Note that the
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/38796375/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/38796377/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/38796378/ArecordDevices.txt
Some more observations. I've noticed that the memory usage of the sol
process grows slowly over time, starting at 33M virtual 16M resident and
rising to 44M virtual 26M resident just before crashing.
Also, I just had it crash in a slightly different way. After running sol
for a while I switch to
I also get this crash quite predictably, any time I play AisleRiot Solitaire
for much over 30 minutes.
I've compiled the relevant packages
(xorg-server-1.6.4,xserver-xorg-video-intel-2.9.0) with optimization turned off
and got a full backtrace of the crash (attached). The relevant bit of lspci:
I get the same problem. I managed to get a backtrace by attaching gdb.
Running latest Karmic 32 bit, on an HP/Compaq 6710b w/Intel GM965
graphics.
** Attachment added: GDB Backtrace
http://launchpadlibrarian.net/35745505/backtrace.txt
--
x crashes while drag-and-drop on aislerot app
I've now got a full backtrace by attaching gdb. Hope this helps.
#0 0x009db6ff in fbBlt (srcLine=0xacd92480, srcStride=16, srcX=0,
dstLine=0x147f, dstStride=16, dstX=0, width=17,
height=45, alu=3, pm=value optimized out, bpp=1, reverse=0, upsidedown=0)
at ../../fb/fbblt.c:213
I've seen a similar looking crash several times. Seems to happen mostly when
playing Solitaire, dragging cards around.
Current Karmic 32 bit, Intel 965GM
Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x8133d6b]
1: /usr/bin/X(xf86SigHandler+0x55) [0x80c7d35]
2: [0x64d400]
3:
Have the same problem on HP Compaq 6710b. With two full batteries
connected (1 internal, 1 external), discharge estimate time is much the
same as with one full battery. This is on a fully updated Jaunty.
--
gutsy gnome-power-manager shows incorrect time remaining with two batteries
conencted
15 matches
Mail list logo
