I have seen problems like this with large files on multiple fs's and
ultimately it was a RAM problem. Scott, can you run memtester and/or
memtest86 at bootup to verify that you don't have bad RAM? Is your CPU
overclocked? CPU errors can also be detected with burn* programs
(cpuburn package). A
It was a poor decision to release Jaunty with this version of the
driver. (Though I don't know if you had any choice from upstream)
Jaunty also has massive speed problems in i.e. xournal which are all the
driver's fault. There's some commentary on freedesktop about the crappy
state of this
I confirm on this chipset:
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory
Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (rev 0c)
00:02.1 Display controller: Intel Corporation
I confirm on GM965/GL960. Note that this has nothing to do with DRI. the
symptoms described occur both with DRI enabled and with it disabled. Note also
it has nothing to do with tvtime -- it affects all xv apps (totem, vlc,
mplayer, etc). You can enable TexturedVideo via
Option
not a tvtime bug, it's an intel driver (xserver-xorg-video-intel) bug.
** Changed in: tvtime (Ubuntu)
Status: New = Invalid
--
[i865] [Jaunty] - Can not start tvtime (since DRI is disabled)
https://bugs.launchpad.net/bugs/367546
You received this bug notification because you are a member
This bug is indeed fixed by the updated 2.7.0 driver at:
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/
However you MUST used TexturedVideo (again, the default anyway) so remove any
XvPreferOverlay option from your xorg.conf. When this option is false, it
causes a different bug and X
This bug is fixed by the updated 2.7.0 driver at:
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates/
However you MUST used TexturedVideo (again, the default anyway) so remove any
XvPreferOverlay option from your xorg.conf. When this option is false, it
causes a different bug and X crash.
Then this would appear to be an 865/965 difference. I posted here
because bug #371275 is marked as a dup, and I have the symptoms of that
bug. I don't get the message DRI is disabled because it fails to run
without freezing on i810 and i865G chips (because I have a GM965).
--
[i865] [Jaunty] -
I confirm João's comment above. With the official jaunty release
2.6.3-0ubuntu9, video players crash when directed to use xv. Telling
gstreamer not to use xv works around it.
In my case, video in vlc/mplayer/totem works fine initially, but if one
forces a repaint of the screen, X will crash.
This bug is still present in Jaunty and libgnomecanvas 2.26.
Unfortunately, the patch I removed from 2.20 to fix it is no longer
present in 2.26. It looks like the libgnomecanvas people made the
situation worse and incorporated the bug upstream.
The symptom is that what is drawn lags
On further investigation, it seems this was caused by the dastardly
iowait kernel bug:
http://bugzilla.kernel.org/show_bug.cgi?id=12309
I'm sure that one is in launchpad somewhere but I couldn't find it.
Trackerd was running in the background right after the upgrade, and
because the kernel
In case anyone else looks here, the related launchpad bugs are:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/131983 (trackerd
makes system crawl)
https://bugs.launchpad.net/ubuntu/+source/linux-
source-2.6.22/+bug/131094 (because of a kernel bug)
--
[regression, intrepid] redraw
I hit this bug today (again) in upgrading from a jaunty alpha to the
current jaunty. The symptom is:
(1)mcelr...@tardis:initramfs-tools sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-2.6.28-11-generic
W:copy_exec: Not copying /lib/lvm-200/lvm to $DESTDIR/sbin/lvm, which
** Changed in: lvm2 (Ubuntu)
Sourcepackagename: linux = lvm2
--
package linux-image-2.6.28-8-generic 2.6.28-8.25 failed to install/upgrade:
subprocess post-installation script returned error exit status 2
https://bugs.launchpad.net/bugs/334237
You received this bug notification because you are
Interesting...as it turns out, my battery finally got delivered for the
dock. I've been avoiding removing it from the dock since I got it and
carrying the dock around. But I just tried suspend/resume both in and
out of the dock, and they both work. Perhaps someone is interested in
the messages
This bug is still in Intrepid. Let's fix it?
I ripped out the debian/patches/04_lcd_filter.dpatch and recompiled.
This fixes the bug both in resizing windows and other apps (like
firefox) painting some text incorrectly. As described above, it only
happens with VRGB subpixel smoothing.
Why is
The package with the bug is:
6f827fc1fffcbfa480dc548bb82b003a
libgnomecanvas2-0_2.20.1.1-1ubuntu3_i386.deb
(that's the md5sum). I just re-downloaded it from the mirrors e.g.
http://mirrors.kernel.org/ubuntu/pool/main/libg/libgnomecanvas/
and double checked. (i386 arch)
The package I
Fix is in nautilus
** Changed in: nautilus (Ubuntu)
Sourcepackagename: gnome-volume-manager = nautilus
--
USB automount lost on hardy upgrade
https://bugs.launchpad.net/bugs/267151
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Run gconf-editor and navigate to the key
/apps/nautilus/preferences/media_automount and
/apps/nautilus/preferences/media_automount_open and set them both to
true. Then it will auto-mount and auto-open the folder in a nautilus
window. viola!
It seems you need to restart nautilus (logout and log
Absolutely positive about my versioning. I did an 'apt-get source
libgnomecanvas' which gets libgnomecanvas_2.20.1.1-1ubuntu3, and built
it by hand, with and without that patch which is a part of this package.
The ubuntu-compiled package that was installed by default in intrepid
definitely has
This is not fixed in intrepid for me.
It is however sensitive to the zoom level. In xournal, maximize by
clicking the set zoom button, then select page height.
The bug I see is that drawn lines appear a long time behind the stylus,
and the bug gets worse as you move toward the lower right
Confirmed with 8.10 and ath9k. The wireless often roams to (none),
which totally drops the connection. I can cause it to reassociate with
an AP by using 'iwconfig ath0 ap MAC'. And about 2 minutes later it
will roam back to (none). Very frustrating.
It seems to me like there is some code in
Testing your patch on MacBook Pro 3.1 Santa Rosa, I get the following
kernel messages:
Sep 17 19:02:38 futura kernel: [ 181.920006] applesmc: no version for
struct_module found: kernel tainted.
Sep 17 19:02:38 futura kernel: [ 181.922477] applesmc: Apple MacBook Pro
detected:
Sep 17 19:02:38
A few minutes later, another message:
Sep 17 19:09:54 futura kernel: [ 531.365060] applesmc: command failed:
10 - c
--
applesmc: wait status failed: c != 8
https://bugs.launchpad.net/bugs/102270
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
See my dmesg attached to this bug:
http://launchpadlibrarian.net/10268555/dmesg.log for messages on this
laptop before your patch.
--
applesmc: wait status failed: c != 8
https://bugs.launchpad.net/bugs/102270
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I just experienced this problem.
Through the md: array md0 already has disks! error. Through the spam,
if you wait 60s (or whatever the timeout is), you will be dropped to the
initramfs shell. You can't see it though through the already has
disks error 100 times per second. But, I typed 'mdadm
The 2.6.24 kernel you mention has no impact on this bug. I can upload
the dmesg if you like, but there's nothing essentially new in there.
The error messages are the same.
--
applesmc: wait status failed: c != 8
https://bugs.launchpad.net/bugs/102270
You received this bug notification because
I think this is caused entirely by trying to read hardware that isn't present.
The applesmc driver does not have a comprehensive up-to-date list of apple
hardware. In particular on my MacBook Pro (v3, Santa Rosa), the kernel message
is generated by trying to read its outputs:
cat
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/10268573/lspci-vvnn.log
--
applesmc: wait status failed: c != 8
https://bugs.launchpad.net/bugs/102270
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
** Attachment added: version.log
http://launchpadlibrarian.net/10268549/version.log
--
applesmc: wait status failed: c != 8
https://bugs.launchpad.net/bugs/102270
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
** Attachment added: dmesg.log
http://launchpadlibrarian.net/10268555/dmesg.log
--
applesmc: wait status failed: c != 8
https://bugs.launchpad.net/bugs/102270
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
Yes, this problem still persists in 7.10. I think it may be related to
a regular hang in the OS interface, where keyboard input is not accepted
and the screen is not updated for several seconds.
** Attachment added: uname-a.log
http://launchpadlibrarian.net/10268548/uname-a.log
--
applesmc:
0.9.7-3 does not fix this problem.
The debbugs #401637 fixes only the spelling error in the error message,
but does not fix this bug (#70525). The error message still occurs, and
settings cannot be saved with the gsynaptics package.
--
gsynaptics-init won't load settings
The name of the attribute causing the error is (apparently)
CoastingSpeed. Note no Threshold or Threashold or any other
spelling at the end, just CoastingSpeed.
After changing this in gsynaptics.c, it works properly and can save and
restore settings with gsynaptics-init. (finally!)
This is for
Not fixed in 0.9.7-3 in Feisty.
** Changed in: gsynaptics (Ubuntu)
Status: Fix Released = Confirmed
--
gsynaptics-init won't load settings
https://bugs.launchpad.net/bugs/70525
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
35 matches
Mail list logo
