I eventually decided that the display device on the laptop where I was
having this problem was probably faulty. I replaced that laptop with a
very similar one (the principle difference being an ATI x1400 instead of
an x1300), and I haven't had this problem since. For what that's worth.
--
Screen
I eventually decided that the display device on the laptop where I was
having this problem was probably faulty. I replaced that laptop with a
very similar one (the principle difference being an ATI x1400 instead of
an x1300), and I haven't had this problem since. For what that's worth.
--
KMS & r
I eventually decided that the display device on the laptop where I was
having this problem was probably faulty. I replaced that laptop with a
very similar one (the principle difference being an ATI x1400 instead of
an x1300), and I haven't had this problem since. For what that's worth.
--
Xorg 10
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/48028288/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/48028289/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/48028290/Dependencies.txt
** A
Public bug reported:
Binary package hint: xorg
For the last couple of days, my laptop has been "freezing" after 0-10
minutes. Today I tried to SSH in and discovered that X was running at
100% on one CPU. Output of top:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
You can avoid losing your report by refreshing the "Timeout error" page
every couple of minutes until it works.
--
Ubuntu bug reporting is too hard
https://bugs.launchpad.net/bugs/574339
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Here's the other bug: https://bugs.launchpad.net/bugs/573983 . I don't
know that they're related, but they're both display regressions that
appeared at or around the same update.
--
Screen corruption with compiz since Lucid release
https://bugs.launchpad.net/bugs/573929
You received this bug noti
Oh, here are what look to me like the relevant bits of syslog. I can
attach the whole thing if you'd like.
** Attachment added: "syslog_excerpt"
http://launchpadlibrarian.net/47360089/syslog_excerpt
--
KMS & radeon in Lucid renders X unusable, but only since about April 26
https://bugs.launch
** Attachment added: "kms_bug.JPG"
http://launchpadlibrarian.net/47358719/kms_bug.JPG
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/47347803/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/47347804/CurrentDmesg.txt
** Attachment
Public bug reported:
Binary package hint: xorg
I used the Lucid beta for a few weeks with no problems. Last Wednesday
(4/26), however, I did an upgrade, and when I rebooted there was a
serious problem with X. The symptom is that the screen only displays the
Lucid background image, but shifted up
** Attachment added: "screenshots.tar"
http://launchpadlibrarian.net/47345486/screenshots.tar
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/47334396/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/47334397/CurrentDmesg.txt
** Att
Public bug reported:
I really like compiz. I did a fresh Lucid install, and now when I turn
it on my screen is corrupted.
I'm attaching a couple of screenshots of the corruption I'm talking
about. Here is some more information:
I'm using a Thinkpad T60 with a Radeon Mobility X1300.
I've been us
I was seeing this bug in the betas, too. Last night (because of another
issue, with X not loading and a bunch of radeon errors) I did a clean
install of Lucid, and disabled KMS (to fix my weird X errors; I didn't
know it was related to the wireless), and I haven't seen the bug yet
this morning.
--
** Attachment added: "AlsaDevices.txt"
http://launchpadlibrarian.net/38391601/AlsaDevices.txt
** Attachment added: "AplayDevices.txt"
http://launchpadlibrarian.net/38391602/AplayDevices.txt
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/38391603/BootDmesg.txt
** Att
Public bug reported:
Failed to hibernate when the battery was accidentally drained.
ProblemType: KernelOops
Annotation: This occured during a previous hibernate and prevented it from
resuming properly. The resume processing hung very near the end and will have
appeared to have completed normal
** Visibility changed to: Public
--
gnome-terminal assert failure:
Vte:ERROR:/build/buildd/vte-0.22.2/./src/ring.c:532:_vte_ring_remove: assertion
failed: (_vte_ring_contains (ring, position))
https://bugs.launchpad.net/bugs/486501
You received this bug notification because you are a member of
Public bug reported:
Binary package hint: f-spot
Today I installed the Facebook export extension. I didn't get any error
when I did this, but when I went to export photos I found that the
"Export To" menu item in F-Spot was disabled (grayed out). I have tried
disabling and reenabling the Facebook
I'm seeing the same problem. I'd also like to join the chorus of voices
curious about how we know it's a Mathematica bug, rather than a
Gnome/Hardy/X bug. I'm 100% ready to believe that it's true, but it
would be nice to hear the evidence. Especially because, if someone is
going to point the Wolfra
18 matches
Mail list logo
