An update, since I posted the original bug report... I'm now running
Ubuntu 11.04, and still having the same problems that everyone else is
experiencing.
I'm running the full xorg-edgers PPA, so I am running radeon
6.14.99+git20110504 and mesa 7.11.0+git20110504, with the latest
standard Natty
(In reply to comment #40)
I never gave it much thought, but thinking about it, this seems suspicious to
me as I am pretty sure that this device has only 64MB of VRAM.
I'm using an X1400 here, with 128MB of vram. I'm not sure if that is
helpful or not.
Here's some extra info for the fire, and
An update, since I posted the original bug report... I'm now running
Ubuntu 11.04, and still having the same problems that everyone else is
experiencing.
I'm running the full xorg-edgers PPA, so I am running radeon
6.14.99+git20110504 and mesa 7.11.0+git20110504, with the latest
standard Natty
(In reply to comment #40)
I never gave it much thought, but thinking about it, this seems suspicious to
me as I am pretty sure that this device has only 64MB of VRAM.
I'm using an X1400 here, with 128MB of vram. I'm not sure if that is
helpful or not.
Here's some extra info for the fire, and
An update, since I posted the original bug report... I'm now running
Ubuntu 11.04, and still having the same problems that everyone else is
experiencing.
I'm running the full xorg-edgers PPA, so I am running radeon
6.14.99+git20110504 and mesa 7.11.0+git20110504, with the latest
standard Natty
(In reply to comment #40)
I never gave it much thought, but thinking about it, this seems suspicious to
me as I am pretty sure that this device has only 64MB of VRAM.
I'm using an X1400 here, with 128MB of vram. I'm not sure if that is
helpful or not.
Here's some extra info for the fire, and
An update, since I posted the original bug report... I'm now running
Ubuntu 11.04, and still having the same problems that everyone else is
experiencing.
I'm running the full xorg-edgers PPA, so I am running radeon
6.14.99+git20110504 and mesa 7.11.0+git20110504, with the latest
standard Natty
(In reply to comment #40)
I never gave it much thought, but thinking about it, this seems suspicious to
me as I am pretty sure that this device has only 64MB of VRAM.
I'm using an X1400 here, with 128MB of vram. I'm not sure if that is
helpful or not.
Here's some extra info for the fire, and
This is an issue that prevents automated installation of Convirture
ConVirt 2.0, who have partnered with Canonical on KVM virtualization.
Is there a workaround?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is still an issue in Ubuntu Server 11.04.
Isn't it a relatively common use case for /var to be on its own
partition on a server?
Either fix the ureadahead behavior, or eliminate it from the server
builds entirely. Most server admins don't care much about boot speed,
but they do care about
Due to this bug, Apache Solr (enterprise search) cannot be installed via
the repo packages on Ubuntu Server without installing a huge number of
desktop dependencies, including a wide array of media codecs and other
cruft. This is actually an issue for us on a production Lucid server.
Please fix
This bug is still present in 11.04 64-bit. The card reader worked fine
several versions back... in 9.10 if I remember correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/486332
Title:
Delkin
Odd behavior is still present in Natty. I use the Logitech MX-5500
Revolution combo, and the bluetooth dongle does not show up as a
Bluetooth device by default in Natty at all, though the keyboard/mouse
do work by default in Logitech's fallback mode which connects the
devices as pseudo-wired when
Additional info:
With default Natty configuration in /lib/udev/rules.d/70-hid2hci.rules,
I get the following three devices reported by lsusb:
Bus 005 Device 025: ID 046d:c71c Logitech, Inc.
Bus 005 Device 024: ID 046d:c71b Logitech, Inc.
Bus 005 Device 023: ID 046d:0b06 Logitech, Inc.
After
Is there any confirmation on which other dock applet libraries are
affected?
Earlier it was mentioned that GtkStatusIcon doesn't exhibit this
behavior, the specifics of which I don't fully grasp if it is actually
*only* a gnome-panel issue as speculated here.
I can confirm though, that
This bug was marked Fix Committed in 2009 but the current repo
packages in all current Ubuntu repos are still 1.1.12, which was last
updated in August of 2007.
When will 1.1.14 be published to the repos?
The upstream changelog (
http://jfs.cvs.sourceforge.net/*checkout*/jfs/jfsutils/NEWS )
** Changed in: jfsutils (Ubuntu)
Status: New = Confirmed
** Summary changed:
- Unrecoverable error writing M to /dev/sdf1. CANNOT CONTINUE.
+ fsck.jfs error due to obsolete jfsutils package: Unrecoverable error writing
M to /dev/sdf1. CANNOT CONTINUE.
--
fsck.jfs error due to obsolete
Thanks Tormod... and thanks for your help on this issue! Sorry for
subscribing you proactively, I didn't know an easier way to put it in
front of your eyeballs without your direct email. Alex Deucher is
involved as well, on the upstream report, though he seems to suspect
some sort of underlying
I will let the radeon devs know in the upstream bug report... it's here
if anyone is interested:
https://bugs.freedesktop.org/show_bug.cgi?id=28106
** Bug watch added: freedesktop.org Bugzilla #28106
http://bugs.freedesktop.org/show_bug.cgi?id=28106
--
Kernel crash when switching off wlan
** Also affects: xserver-xorg-driver-ati via
http://bugs.freedesktop.org/show_bug.cgi?id=28106
Importance: Unknown
Status: Unknown
--
Kernel crash when switching off wlan after wlan hangup (iwl3945)
https://bugs.launchpad.net/bugs/555286
You received this bug notification because
This seems to be due to the same problem as this bug with radeon KMS and
wireless:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/564376
Not sure if I should mark duplicate, since the expression is slightly
different, but I will add the radeon driver project as an also
affects.
--
Does the issue still occur with radeon KMS disabled? I suspect this may
be related to similar problems other users are having, the common
denominator in those cases seems to be Radeon video with KMS enabled by
default. I have linked the bug reports upstream on those issues, but it
would be
Adding radeon driver as affected project, linking to upstream bug
report.
** Bug watch added: freedesktop.org Bugzilla #28106
http://bugs.freedesktop.org/show_bug.cgi?id=28106
** Also affects: xserver-xorg-driver-ati via
http://bugs.freedesktop.org/show_bug.cgi?id=28106
Importance:
Adding the radeon driver project to this, and linking to upstream bug
report on freedesktop.org.
** Bug watch added: freedesktop.org Bugzilla #28106
http://bugs.freedesktop.org/show_bug.cgi?id=28106
** Also affects: xserver-xorg-driver-ati via
** Bug watch added: freedesktop.org Bugzilla #28106
http://bugs.freedesktop.org/show_bug.cgi?id=28106
** Changed in: xserver-xorg-driver-ati
Importance: Undecided = Unknown
** Changed in: xserver-xorg-driver-ati
Status: New = Unknown
** Changed in: xserver-xorg-driver-ati
Remote
I posted on the Phoronix forums to try to attract some of the radeon
driver devs to this problem directly, and linked to this bug report for
their reference. Several of the radeon developers participate there, so
I thought it might help.
Phoronix thread here:
** Summary changed:
- Lucid - iwl3945 drops connection on youtube but not with mainline
+ Lucid - radeon kms causes iwl3945 to drop connection on youtube but not with
mainline
** Also affects: xserver-xorg-driver-ati
Importance: Undecided
Status: New
--
Lucid - radeon kms causes
In addition, the language support dependency causes OpenOffice.org to be
installed by default on Ubuntu Server, which makes no sense at all.
There's no GUI... why install OO.org and X11 dependencies and etc on a
server?
--
Package should not depend on Open Office Writer
oops... may have jumped the gun on that. the box I'm working on may
have had standard Ubuntu desktop installed by mistake rather than the
server version...
--
Package should not depend on Open Office Writer
https://bugs.launchpad.net/bugs/68464
You received this bug notification because you are
Confirming behavior under Jaunty 64-bit. Logged in to server remotely
via NX (ssh) and cannot unlock the panel in users-admin. Is this a
policy setting?
--
cannot Unlock Users Settings
https://bugs.launchpad.net/bugs/310742
You received this bug notification because you are a member of Ubuntu
**Removed duplicate status
This is NOT a duplicate of #318465. That is a different unit (MX5000)
with a different USB Bluetooth dongle. The issue is also quite
different.
** This bug is no longer a duplicate of bug 318465
Logitech MX5000 doesn't connect via bluetooth under ubuntu
--
This is not a duplicate of #318465. That is a different keyboard with a
different USB Bluetooth dongle.
The quick way to fix this until bluez is updated upstream is to switch
HID2HCI_ENABLED=1 to HID2HCI_ENABLED=0 in /etc/default/bluetooth.
** This bug is no longer a duplicate of bug 318465
This is NOT a bug.
The USB Bluetooth dongle for the Logitech MX5500 Revolution is a fully
functional Bluetooth hub as well as having a failover mode for slave
USB keyboard/mouse emulation. It is not just a connector for the
keyboard/mouse like many other such dongles, it is a fully functional
This is NOT a bug. The Logitech USB dongle for the MX5500 Revolution is
a fully functional Bluetooth hub. Keyboard and Mouse need to be
connected as discrete Bluetooth devices in the normal way, and will then
persist across reboots with full functionality.
** Changed in: hal (Ubuntu)
This is NOT a bug.
The USB Bluetooth dongle for the higher end Logitech keyboard/mouse
combos is a fully functional Bluetooth hub as well as having a
failover mode for slave USB keyboard/mouse emulation. It is not just a
connector for the keyboard/mouse like many other such dongles, it is a
fully
This is NOT a bug. The Logitech USB dongle for these units is a fully
functional Bluetooth hub. Keyboard and Mouse need to be connected as
discrete Bluetooth devices in the normal way, and will then persist
across reboots with full functionality.
** Changed in: linux (Ubuntu)
Status: New =
Mous16 is absolutely right about the inconvenience issue... also, the
fact that paired bluetooth devices are not being auto-reconnected when
power cycled is something that should definitely be considered a bug. I
am now getting the same behavior on system reboots, which it did not
used to do.
Hi Arthur,
You're absolutely right... there is a bluetooth problem currently and
the pairings do not persist correctly across reboots, but it is a
different problem from the one described in the original bug report
here. The problem you're running into is the same one that I am, that
the bluez
After this fix to GTK, my system performance is ABYSMALLY slow. At
least a 60% overall UI performance hit. Running Nvidia 180.29 (standard
Jaunty repo packages) and the new fixed GTK as mentioned previously.
Is anyone else experiencing significant performance reduction?
Multitasking is almost
Confirming here on Jaunty 32bit i386. Dropping to recovery console and
running updates fixed login problem, but verifying Igor's comment above
that system performance is SIGNIFICANTLY lower. Functionality is
restored with new GTK but there is a large performance hit. Hopefully
that will be
Confirming that this bug still exists. Verified on Ubuntu 8.10, using
the Canonical repo-packaged ATI Catalyst 8.10 (fglrx) on ATI Radeon 9600
AGP.
--
Mythfrontend doesn't render correctly on ATI driver
https://bugs.launchpad.net/bugs/254285
You received this bug notification because you are a
The problem seems to have fixed itself. Some enterprising soul must
have fixed the glitch.
--
upgrade hangs after ldconfig deferred processing
https://bugs.launchpad.net/bugs/280478
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Per Eric Julien's suggestion (thanks Eric!) I added the ServerLayout
section to xorg.conf and it seemed to fix my problem. Running nvidia-
settings as root was still necessary.
It seems that having an (empty) ServerLayout section in xorg.conf by
default, and requiring nvidia-settings to run as
After setting TwinView and applying successfully, reboot results in
return to single screen mode.
Running sudo nvidia settings from console returns:
ERROR: Invalid display device CRT-1 specified on line 21 of configuration file
'/home/user/.nvidia-settings-rc' (the currently enabled
Xorg.conf attached:
** Attachment added: xorg.conf
http://launchpadlibrarian.net/18769656/xorg.conf
--
nvidia-settings crashes when user clicks Save To X Configuration File
https://bugs.launchpad.net/bugs/286424
You received this bug notification because you are a member of Ubuntu
Bugs,
I renamed .nvidia-settings-rc to make it visible, per your suggestion.
The app no longer errors on first run but the crash behavior when Save
to X Configuration File is still present. TwinView display settings do
not persist over a reboot.
--
nvidia-settings crashes when user clicks Save To X
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/18731901/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/18731902/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/18731903/Disassembly.txt
** Attachment
Same issue here. Verifying on Ubuntu 8.10 beta, kernel
2.6.27-3-generic. Intel P4 machine.
--
upgrade hangs after ldconfig deferred processing
https://bugs.launchpad.net/bugs/280478
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
48 matches
Mail list logo
