** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/29158205/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/29158206/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/29158207/Disassembly.txt
** Attachm
The failed retrace thing doesn't look like fun. I installed the
libmms0-dbgsym, gstreamer0.10-plugins-bad-dbgsym &
libgstreamer0.10-0-dbgsym packages and got a backtrace from gdb, which
I'm attaching.
Totem frequently did not crash when run under gdb; I had to rerun it
several times before the cr
I was able to get totem to play the NASA wmv stream after many crashes.
So: it does work sometimes without gdb. It definitely appears to be
timing-related.
--
totem crashed with SIGSEGV
https://bugs.launchpad.net/bugs/400391
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
When using the lilo.conf vga= parameter, 'vga=' doesn't turn up in the
kernel command line. Further, lilo won't allow putting 'vga=' into the
kernel command line directly via 'append' or 'literal'.
This means that it's not possible to use vesafb with with lilo -- the
usplash
I'm seeing this too -- running anything from the Run dialog causes
gnome-panel to crash. Turning assistive technologies off makes the
problem go away.
--
Panel crashes on the 'run application' dialog when assistive technologies are
enabled
https://launchpad.net/bugs/50273
--
ubuntu-bugs mailin
I am also seeing this (on Karmic). Sometimes "still readable" is a
stretch.
It goes away if antialiasing is disabled. Bitmap fonts are unaffected.
GTK and QT widgets are affected, as is the web content in a firefox
window. The web content in chromium nightlies from
http://ppa.launchpad.net/chro
I've verified that the crash does not happen if gnome-terminal is not
set to use a bitmap font. I've also reproduced the crash in GIMP: open
the font selector for the text tool-> crash.
** Visibility changed to: Public
--
pango upgrade causes gnome-terminal to SIGSEGV
https://bugs.launchpad.net
Public bug reported:
# export LIBGL_DEBUG=verbose
# glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 1.6.4 i915 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so
libGL error: dlopen /usr/lib/dri/i915_dri.so failed (/usr/lib/dri/i915_dri.so:
cannot open shared object fi
This is i386. I had version 6.5.1~20060817-0ubuntu4 -- this got updated
to 6.5.2-3ubuntu1 today and the the file is there as you say.
I'm not seeing any problems with this anymore either. Thank you.
--
/usr/lib/dri/i915_dri.so missing (feisty)
https://launchpad.net/bugs/86870
--
ubuntu-bugs
@Mr. Daley:
"Luke, you are proposing to add a special case to the Services dialog
for avahi"
You are proposing to special-case the avahi-daemon initscript. I won't
speculate as to why.
I have demonstrated that this behavior is very common in Debian, and so in
Ubuntu, and I don't see that you h
Bah, there are many precedents in Debian and Ubuntu for this behavior.
Making /etc/init.d/avahi-daemon ignore the system setting in
/etc/default because people are too lazy or stupid to read the
initscript is dumb when many other packages work this way, including
many in universe (that won't be sim
"Ubuntu is supposed to be for everyone and many people wouldn't be able
to figure this out."
If you can't figure this out, you oughtn't be fiddling around with the
SysV init scripts. They're not for everyone. Things should "just
work", without needing to mess with the initscripts. Once you do,
Any movement on this?
It'd be nice to submit a fix for this to the mainline kernel within the
three week window after 2.6.20 is released (RSN).
--
Kernel panic - not syncing: IO-APIC + timer doesn't work!
https://launchpad.net/bugs/54621
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Do you get any error messages if you export LIBGL_DEBUG=verbose before
running glxinfo? They'd show up in the terminal window, not the logs.
--
no direct rendering on dapper with i810 chipset (855GM)
https://launchpad.net/bugs/42049
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
This still doesn't work in Gutsy:
| The UTS Release version in include/linux/utsrelease.h
| "2.6.23-ge8b8c977-dirty"
| does not match current version:
| "2.6.23-ge8b8c977-dirty-ge8b8c977-dirty-dirty"
| Please correct this.
| make: *** [install/linux-image-2.6.23-ge8b8c977-dirty-ge8b
I can confirm that backing out the above patch and rebuilding the
package makes GNOME work again on my PowerPC G3.
Please re-open this bug.
The "open" bit of this bug refers to the need to figure out why Altivec
detection is broken, so that it can be re-enabled without breaking G3s.
Ubuntu's prob
Public bug reported:
Binary package hint: cupsys-driver-gutenprint
The output of `dpkg -L cupsys-driver-gutenprint` indicated that dpkg
thinks /usr/share/cups/model/gutenprint should exist, but it is not
present even after purging the package (needed --force-depends) and
reinstalling it.
The sym
I am seeing this as well. It's a fair bet this is
https://bugs.launchpad.net/ubuntu/+source/synergy/+bug/91540 turning up
again.
--
Ubuntu 8.04 synergy lagging
https://bugs.launchpad.net/bugs/196792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I'm seeing this too, with 1.0.11~git-20060105-2 (i.e. feisty).
I strace'd mount(8), and see that mount prints that warning just after
failing to locate the file /var/run/rpc.idmapd.pid. The warning seems
to be spurious -- rpc.idmapd is running, and I'm seeing the correct
owners on the mounted NFS
Public bug reported:
Binary package hint: synergy
A synergy_1.3.1-4ubuntu1 client (the current in intrepid) fails to
connect to a server running gutsy (synergy_1.3.1-2ubuntu2). Synergy
works fine if I install the gutsy package on the intrepid client. It
also works if I install the 1.3.1-4 packa
** Attachment added: ".pcap of failed connect of synergy client"
http://launchpadlibrarian.net/16237650/handshake_failed.pcap
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: "Output of `synergyc -f -d DEBUG2 {server.name}`"
http://launchpadlibrarian.net/16237663/synergy-debug2.txt
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
B
** Attachment added: "strace of failed synergyc connect"
http://launchpadlibrarian.net/16237671/synergy_strace.txt
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Okay, it looks like the .pcap I attached doesn't include the last two
packets I described in the original report -- i.e. the last two packets
are from the connection timing out, and the two packets I once saw after
Ctrl-\'ing the client aren't in there. Maybe they weren't sent this
time (though I
...and I should have said hardy, not gutsy, in all instances above.
I'm walking away from the keyboard now. ;-)
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
This bug has been triaged; the cause of the bug seems to be known.
Yes, the root cause of this bug can introduce lags and general desktop
unresponsiveness in other applications. It's a kernel scheduler option
that's known to the (upstream) developers to cause scheduling problems
and which has unf
*** This bug is a duplicate of bug 412152 ***
https://bugs.launchpad.net/bugs/412152
** This bug has been marked a duplicate of bug 412152
gnome-disk-utility nags me too much that my disk is failing
--
Thinkpad x40: palimpsest reports disk as failing when it isn't
https://bugs.launchpad.n
*** This bug is a duplicate of bug 412152 ***
https://bugs.launchpad.net/bugs/412152
** This bug has been marked a duplicate of bug 412152
gnome-disk-utility nags me too much that my disk is failing
--
Palimpsest disk utility found bad sector but the disk is healthy
https://bugs.launchpad
I've been able to verify that Chromium does not use RENDER acceleration
for antialiased fonts for web content; I asked one of the developers.
That would seem to explain why it doesn't show up for Chromium web
content (as stated in my previous comment).
I believe this is a bug in EXA RENDER acceler
This issue is no longer present in Karmic. I skipped Jaunty, so I can't
speak for that release, but this is potentially closeable.
--
kernel-package doesn't work if CONFIG_LOCALVERSION_AUTO is set
https://bugs.launchpad.net/bugs/77649
You received this bug notification because you are a member o
This issue is gone in Karmic. I skipped Jaunty, so I cannot speak for
that release, though I suspect it is fixed there too. This report is
potentially closeable.
--
2.6.24-8 Introduces Network Issue
https://bugs.launchpad.net/bugs/194029
You received this bug notification because you are a memb
Can anyone verify is this bug is still present? My G3-based Mac has
died of old age.
If not. yay! Please close this bug.
If so, then it's time to officially drop support for the G3, whatever
the value of Ubuntu PPC "support" may be.
Maybe that's already been done; it so, I apologize. Please c
Public bug reported:
Binary package hint: synergy
A synergy_1.3.1-4ubuntu1 client (the current in intrepid) fails to
connect to a server running gutsy (synergy_1.3.1-2ubuntu2). Synergy
works fine if I install the gutsy package on the intrepid client. It
also works if I install the 1.3.1-4 packa
** Attachment added: ".pcap of failed connect of synergy client"
http://launchpadlibrarian.net/16237650/handshake_failed.pcap
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: "Output of `synergyc -f -d DEBUG2 {server.name}`"
http://launchpadlibrarian.net/16237663/synergy-debug2.txt
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
B
** Attachment added: "strace of failed synergyc connect"
http://launchpadlibrarian.net/16237671/synergy_strace.txt
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Okay, it looks like the .pcap I attached doesn't include the last two
packets I described in the original report -- i.e. the last two packets
are from the connection timing out, and the two packets I once saw after
Ctrl-\'ing the client aren't in there. Maybe they weren't sent this
time (though I
...and I should have said hardy, not gutsy, in all instances above.
I'm walking away from the keyboard now. ;-)
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
This still doesn't work in Gutsy:
| The UTS Release version in include/linux/utsrelease.h
| "2.6.23-ge8b8c977-dirty"
| does not match current version:
| "2.6.23-ge8b8c977-dirty-ge8b8c977-dirty-dirty"
| Please correct this.
| make: *** [install/linux-image-2.6.23-ge8b8c977-dirty-ge8b
Public bug reported:
When using the lilo.conf vga= parameter, 'vga=' doesn't turn up in the
kernel command line. Further, lilo won't allow putting 'vga=' into the
kernel command line directly via 'append' or 'literal'.
This means that it's not possible to use vesafb with with lilo -- the
usplash
I'm seeing this too -- running anything from the Run dialog causes
gnome-panel to crash. Turning assistive technologies off makes the
problem go away.
--
Panel crashes on the 'run application' dialog when assistive technologies are
enabled
https://launchpad.net/bugs/50273
--
ubuntu-bugs mailin
Bah, there are many precedents in Debian and Ubuntu for this behavior.
Making /etc/init.d/avahi-daemon ignore the system setting in
/etc/default because people are too lazy or stupid to read the
initscript is dumb when many other packages work this way, including
many in universe (that won't be sim
"Ubuntu is supposed to be for everyone and many people wouldn't be able
to figure this out."
If you can't figure this out, you oughtn't be fiddling around with the
SysV init scripts. They're not for everyone. Things should "just
work", without needing to mess with the initscripts. Once you do,
@Mr. Daley:
"Luke, you are proposing to add a special case to the Services dialog
for avahi"
You are proposing to special-case the avahi-daemon initscript. I won't
speculate as to why.
I have demonstrated that this behavior is very common in Debian, and so in
Ubuntu, and I don't see that you h
Any movement on this?
It'd be nice to submit a fix for this to the mainline kernel within the
three week window after 2.6.20 is released (RSN).
--
Kernel panic - not syncing: IO-APIC + timer doesn't work!
https://launchpad.net/bugs/54621
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Do you get any error messages if you export LIBGL_DEBUG=verbose before
running glxinfo? They'd show up in the terminal window, not the logs.
--
no direct rendering on dapper with i810 chipset (855GM)
https://launchpad.net/bugs/42049
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
I'm seeing this too, with 1.0.11~git-20060105-2 (i.e. feisty).
I strace'd mount(8), and see that mount prints that warning just after
failing to locate the file /var/run/rpc.idmapd.pid. The warning seems
to be spurious -- rpc.idmapd is running, and I'm seeing the correct
owners on the mounted NFS
Public bug reported:
# export LIBGL_DEBUG=verbose
# glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 1.6.4 i915 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so
libGL error: dlopen /usr/lib/dri/i915_dri.so failed (/usr/lib/dri/i915_dri.so:
cannot open shared object fi
This is i386. I had version 6.5.1~20060817-0ubuntu4 -- this got updated
to 6.5.2-3ubuntu1 today and the the file is there as you say.
I'm not seeing any problems with this anymore either. Thank you.
--
/usr/lib/dri/i915_dri.so missing (feisty)
https://launchpad.net/bugs/86870
--
ubuntu-bugs
This bug has been triaged; the cause of the bug seems to be known.
Yes, the root cause of this bug can introduce lags and general desktop
unresponsiveness in other applications. It's a kernel scheduler option
that's known to the (upstream) developers to cause scheduling problems
and which has unf
Public bug reported:
When using the lilo.conf vga= parameter, 'vga=' doesn't turn up in the
kernel command line. Further, lilo won't allow putting 'vga=' into the
kernel command line directly via 'append' or 'literal'.
This means that it's not possible to use vesafb with with lilo -- the
usplash
I'm seeing this too -- running anything from the Run dialog causes
gnome-panel to crash. Turning assistive technologies off makes the
problem go away.
--
Panel crashes on the 'run application' dialog when assistive technologies are
enabled
https://launchpad.net/bugs/50273
--
ubuntu-bugs mailin
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/29158205/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/29158206/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/29158207/Disassembly.txt
** Attachm
The failed retrace thing doesn't look like fun. I installed the
libmms0-dbgsym, gstreamer0.10-plugins-bad-dbgsym &
libgstreamer0.10-0-dbgsym packages and got a backtrace from gdb, which
I'm attaching.
Totem frequently did not crash when run under gdb; I had to rerun it
several times before the cr
I was able to get totem to play the NASA wmv stream after many crashes.
So: it does work sometimes without gdb. It definitely appears to be
timing-related.
--
totem crashed with SIGSEGV
https://bugs.launchpad.net/bugs/400391
You received this bug notification because you are a member of Ubuntu
B
I am seeing this as well. It's a fair bet this is
https://bugs.launchpad.net/ubuntu/+source/synergy/+bug/91540 turning up
again.
--
Ubuntu 8.04 synergy lagging
https://bugs.launchpad.net/bugs/196792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I can confirm that backing out the above patch and rebuilding the
package makes GNOME work again on my PowerPC G3.
Please re-open this bug.
The "open" bit of this bug refers to the need to figure out why Altivec
detection is broken, so that it can be re-enabled without breaking G3s.
Ubuntu's prob
Public bug reported:
Binary package hint: cupsys-driver-gutenprint
The output of `dpkg -L cupsys-driver-gutenprint` indicated that dpkg
thinks /usr/share/cups/model/gutenprint should exist, but it is not
present even after purging the package (needed --force-depends) and
reinstalling it.
The sym
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/29158205/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/29158206/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/29158207/Disassembly.txt
** Attachm
The failed retrace thing doesn't look like fun. I installed the
libmms0-dbgsym, gstreamer0.10-plugins-bad-dbgsym &
libgstreamer0.10-0-dbgsym packages and got a backtrace from gdb, which
I'm attaching.
Totem frequently did not crash when run under gdb; I had to rerun it
several times before the cr
I was able to get totem to play the NASA wmv stream after many crashes.
So: it does work sometimes without gdb. It definitely appears to be
timing-related.
--
totem crashed with SIGSEGV
https://bugs.launchpad.net/bugs/400391
You received this bug notification because you are a member of Ubuntu
B
I am also seeing this (on Karmic). Sometimes "still readable" is a
stretch.
It goes away if antialiasing is disabled. Bitmap fonts are unaffected.
GTK and QT widgets are affected, as is the web content in a firefox
window. The web content in chromium nightlies from
http://ppa.launchpad.net/chro
I've verified that the crash does not happen if gnome-terminal is not
set to use a bitmap font. I've also reproduced the crash in GIMP: open
the font selector for the text tool-> crash.
** Visibility changed to: Public
--
pango upgrade causes gnome-terminal to SIGSEGV
https://bugs.launchpad.net
*** This bug is a duplicate of bug 412152 ***
https://bugs.launchpad.net/bugs/412152
** This bug has been marked a duplicate of bug 412152
gnome-disk-utility nags me too much that my disk is failing
--
Thinkpad x40: palimpsest reports disk as failing when it isn't
https://bugs.launchpad.n
*** This bug is a duplicate of bug 412152 ***
https://bugs.launchpad.net/bugs/412152
** This bug has been marked a duplicate of bug 412152
gnome-disk-utility nags me too much that my disk is failing
--
Palimpsest disk utility found bad sector but the disk is healthy
https://bugs.launchpad
I've been able to verify that Chromium does not use RENDER acceleration
for antialiased fonts for web content; I asked one of the developers.
That would seem to explain why it doesn't show up for Chromium web
content (as stated in my previous comment).
I believe this is a bug in EXA RENDER acceler
This issue is no longer present in Karmic. I skipped Jaunty, so I can't
speak for that release, but this is potentially closeable.
--
kernel-package doesn't work if CONFIG_LOCALVERSION_AUTO is set
https://bugs.launchpad.net/bugs/77649
You received this bug notification because you are a member o
This issue is gone in Karmic. I skipped Jaunty, so I cannot speak for
that release, though I suspect it is fixed there too. This report is
potentially closeable.
--
2.6.24-8 Introduces Network Issue
https://bugs.launchpad.net/bugs/194029
You received this bug notification because you are a memb
Can anyone verify is this bug is still present? My G3-based Mac has
died of old age.
If not. yay! Please close this bug.
If so, then it's time to officially drop support for the G3, whatever
the value of Ubuntu PPC "support" may be.
Maybe that's already been done; it so, I apologize. Please c
Public bug reported:
Binary package hint: synergy
A synergy_1.3.1-4ubuntu1 client (the current in intrepid) fails to
connect to a server running gutsy (synergy_1.3.1-2ubuntu2). Synergy
works fine if I install the gutsy package on the intrepid client. It
also works if I install the 1.3.1-4 packa
** Attachment added: ".pcap of failed connect of synergy client"
http://launchpadlibrarian.net/16237650/handshake_failed.pcap
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: "Output of `synergyc -f -d DEBUG2 {server.name}`"
http://launchpadlibrarian.net/16237663/synergy-debug2.txt
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
B
** Attachment added: "strace of failed synergyc connect"
http://launchpadlibrarian.net/16237671/synergy_strace.txt
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Okay, it looks like the .pcap I attached doesn't include the last two
packets I described in the original report -- i.e. the last two packets
are from the connection timing out, and the two packets I once saw after
Ctrl-\'ing the client aren't in there. Maybe they weren't sent this
time (though I
...and I should have said hardy, not gutsy, in all instances above.
I'm walking away from the keyboard now. ;-)
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
I am seeing this as well. It's a fair bet this is
https://bugs.launchpad.net/ubuntu/+source/synergy/+bug/91540 turning up
again.
--
Ubuntu 8.04 synergy lagging
https://bugs.launchpad.net/bugs/196792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I can confirm that backing out the above patch and rebuilding the
package makes GNOME work again on my PowerPC G3.
Please re-open this bug.
The "open" bit of this bug refers to the need to figure out why Altivec
detection is broken, so that it can be re-enabled without breaking G3s.
Ubuntu's prob
Public bug reported:
Binary package hint: cupsys-driver-gutenprint
The output of `dpkg -L cupsys-driver-gutenprint` indicated that dpkg
thinks /usr/share/cups/model/gutenprint should exist, but it is not
present even after purging the package (needed --force-depends) and
reinstalling it.
The sym
This still doesn't work in Gutsy:
| The UTS Release version in include/linux/utsrelease.h
| "2.6.23-ge8b8c977-dirty"
| does not match current version:
| "2.6.23-ge8b8c977-dirty-ge8b8c977-dirty-dirty"
| Please correct this.
| make: *** [install/linux-image-2.6.23-ge8b8c977-dirty-ge8b
@Mr. Daley:
"Luke, you are proposing to add a special case to the Services dialog
for avahi"
You are proposing to special-case the avahi-daemon initscript. I won't
speculate as to why.
I have demonstrated that this behavior is very common in Debian, and so in
Ubuntu, and I don't see that you h
Public bug reported:
# export LIBGL_DEBUG=verbose
# glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 1.6.4 i915 (screen 0)
libGL: OpenDriver: trying /usr/lib/dri/i915_dri.so
libGL error: dlopen /usr/lib/dri/i915_dri.so failed (/usr/lib/dri/i915_dri.so:
cannot open shared object fi
This is i386. I had version 6.5.1~20060817-0ubuntu4 -- this got updated
to 6.5.2-3ubuntu1 today and the the file is there as you say.
I'm not seeing any problems with this anymore either. Thank you.
--
/usr/lib/dri/i915_dri.so missing (feisty)
https://launchpad.net/bugs/86870
--
ubuntu-bugs
I'm seeing this too, with 1.0.11~git-20060105-2 (i.e. feisty).
I strace'd mount(8), and see that mount prints that warning just after
failing to locate the file /var/run/rpc.idmapd.pid. The warning seems
to be spurious -- rpc.idmapd is running, and I'm seeing the correct
owners on the mounted NFS
Any movement on this?
It'd be nice to submit a fix for this to the mainline kernel within the
three week window after 2.6.20 is released (RSN).
--
Kernel panic - not syncing: IO-APIC + timer doesn't work!
https://launchpad.net/bugs/54621
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Do you get any error messages if you export LIBGL_DEBUG=verbose before
running glxinfo? They'd show up in the terminal window, not the logs.
--
no direct rendering on dapper with i810 chipset (855GM)
https://launchpad.net/bugs/42049
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
Bah, there are many precedents in Debian and Ubuntu for this behavior.
Making /etc/init.d/avahi-daemon ignore the system setting in
/etc/default because people are too lazy or stupid to read the
initscript is dumb when many other packages work this way, including
many in universe (that won't be sim
"Ubuntu is supposed to be for everyone and many people wouldn't be able
to figure this out."
If you can't figure this out, you oughtn't be fiddling around with the
SysV init scripts. They're not for everyone. Things should "just
work", without needing to mess with the initscripts. Once you do,
This bug has been triaged; the cause of the bug seems to be known.
Yes, the root cause of this bug can introduce lags and general desktop
unresponsiveness in other applications. It's a kernel scheduler option
that's known to the (upstream) developers to cause scheduling problems
and which has unf
Public bug reported:
Binary package hint: synergy
A synergy_1.3.1-4ubuntu1 client (the current in intrepid) fails to
connect to a server running gutsy (synergy_1.3.1-2ubuntu2). Synergy
works fine if I install the gutsy package on the intrepid client. It
also works if I install the 1.3.1-4 packa
** Attachment added: ".pcap of failed connect of synergy client"
http://launchpadlibrarian.net/16237650/handshake_failed.pcap
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs
** Attachment added: "Output of `synergyc -f -d DEBUG2 {server.name}`"
http://launchpadlibrarian.net/16237663/synergy-debug2.txt
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
B
** Attachment added: "strace of failed synergyc connect"
http://launchpadlibrarian.net/16237671/synergy_strace.txt
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Okay, it looks like the .pcap I attached doesn't include the last two
packets I described in the original report -- i.e. the last two packets
are from the connection timing out, and the two packets I once saw after
Ctrl-\'ing the client aren't in there. Maybe they weren't sent this
time (though I
...and I should have said hardy, not gutsy, in all instances above.
I'm walking away from the keyboard now. ;-)
--
synergy-1.3.1-4ubuntu1 (intrepid) fails to connect
https://bugs.launchpad.net/bugs/250869
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
*** This bug is a duplicate of bug 412152 ***
https://bugs.launchpad.net/bugs/412152
** This bug has been marked a duplicate of bug 412152
gnome-disk-utility nags me too much that my disk is failing
--
Thinkpad x40: palimpsest reports disk as failing when it isn't
https://bugs.launchpad.n
*** This bug is a duplicate of bug 412152 ***
https://bugs.launchpad.net/bugs/412152
** This bug has been marked a duplicate of bug 412152
gnome-disk-utility nags me too much that my disk is failing
--
Palimpsest disk utility found bad sector but the disk is healthy
https://bugs.launchpad
I've been able to verify that Chromium does not use RENDER acceleration
for antialiased fonts for web content; I asked one of the developers.
That would seem to explain why it doesn't show up for Chromium web
content (as stated in my previous comment).
I believe this is a bug in EXA RENDER acceler
This issue is no longer present in Karmic. I skipped Jaunty, so I can't
speak for that release, but this is potentially closeable.
--
kernel-package doesn't work if CONFIG_LOCALVERSION_AUTO is set
https://bugs.launchpad.net/bugs/77649
You received this bug notification because you are a member o
This issue is gone in Karmic. I skipped Jaunty, so I cannot speak for
that release, though I suspect it is fixed there too. This report is
potentially closeable.
--
2.6.24-8 Introduces Network Issue
https://bugs.launchpad.net/bugs/194029
You received this bug notification because you are a memb
Can anyone verify is this bug is still present? My G3-based Mac has
died of old age.
If not. yay! Please close this bug.
If so, then it's time to officially drop support for the G3, whatever
the value of Ubuntu PPC "support" may be.
Maybe that's already been done; it so, I apologize. Please c
1 - 100 of 2196 matches
Mail list logo
