however 4.4.4 from https://edge.launchpad.net/~kubuntu-
ppa/+archive/ppa/ still shows the same problem :-(
--
Kmail cannot send to groups
https://bugs.launchpad.net/bugs/580242
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I can confirm this problem.
The page linked in the first post suggests this is fixed in KDE 4.4.3.
--
Kmail cannot send to groups
https://bugs.launchpad.net/bugs/580242
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Hi,
A note for those who are dissatisfied with the progress on this bug.
It seems likely that these usb problems could actually be caused by
numerous different glitches in different usb controllers or devices.
Don't expect one single fix to address all these problems
simultaneously; I guess
*** This bug is a duplicate of bug 88746 ***
https://bugs.launchpad.net/bugs/88746
It looks different to #88746. You mention you have one USB drive that
works, and one that does not; can you confirm this happens even if there
are inserted into the same USB port. That would definitely make it
Ive been checking whether it is sufficient to disable autosuspend for a
few specific devices on the nforce2 board, hoping to package an easier
fix as a udev rule. In short, its not possible. I haven't been able to
determine the full pattern, but I definitely also need to disable
autosuspend on the
I previously reported that USB devices were not working on my nforce2
system when connected via hub after a dapper to hardy upgrade. I had
tried the suggested workarounds here and nothing helped *except*
blacklisting ehci_hcd, So Ive been living with usb 1 speeds for a month
:-( But now I have a
FWIW I'm seeing this too. Also on nforce2 chipset. Recently upgraded
from Dapper which did not show this problem.
--
ehci_hcd module causes I/O errors in USB 2.0 devices
https://bugs.launchpad.net/bugs/88746
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For anyone else affected by this, there is a workaround here:
http://ubuntuforums.org/showthread.php?t=422490
--
Segmentation fault in jpeg plugin
https://bugs.launchpad.net/bugs/46234
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
I think this was once fixed by an update, but a subsequent hal update
means dapper is still suffering from this bug. Workaround on dapper is
downgrading hal.
No idea about edgy...
--
Latest hal update breaks USB stick mounting in kubuntu dapper kde 3.5.5
https://bugs.launchpad.net/bugs/72869
Problem confirmed here too. I have been using the
/etc/dbus-1/system.d/hal.conf workaround since upgrading to kde 355.
I can also confirm the downgrade fixes the problem.
--
Latest hal update breaks USB stick mounting in kubuntu dapper kde 3.5.5
https://launchpad.net/bugs/72869
--
ubuntu-bugs
have a fix for the broken Dapper too?
This is now fixed on Dapper for me.
--
Changes to imlib2 in recent security update causes digikam breakage
https://launchpad.net/bugs/70278
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Confirmed fixed in edgy, and 355 on dapper
--
Ugly mount point name used for removable media
https://launchpad.net/bugs/48104
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
Public bug reported:
Digikam worked great in dapper using the packages for kde-353.
Since installing kde-355 on dapper I am seeing some problems using
Digikam's internal viewer/editor. The first photo opened is displayed
well. Pressing the 'previous' toolbar button also works, however
pressing
Public bug reported:
Binary package hint: kdebase
Using safely remove on a usb memory stick causes the desktop icon to
disappear immediately, without waiting for any cached writes to
complete.
I have observed this behaviour in both edgy and dapper with kde-355,
with two different memory sticks.
Public bug reported:
Binary package hint: unattended-upgrades
The unattended-upgrades package needs manual configuration after it is
installed. Unattended upgrades are disabled by default, even once this
package is installed.
I suggest adding to /etc/apt/apt.conf.d/50unattended-upgrades
Aha! I only just noticed that unattended-upgrades is part of the default
ubuntu and xubuntu install. I therefore agree the current configuration
file defaults make sense.
It is NOT part of the default install of Kubuntu. Changing that would be
a better wishlist item.
--
unattended-upgrades
Public bug reported:
Binary package hint: unattended-upgrades
The unattended-upgrades package needs manual configuration after it is
installed. Unattended upgrades are disabled by default, even once this
package is installed.
I suggest adding to /etc/apt/apt.conf.d/50unattended-upgrades
bootchart here (but remove the XXX):
http://www.tarind.com/dapXXXper-20060701-1.png
--
hardware clock overrides time set by ntpdate on boot
https://launchpad.net/bugs/51502
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: adept
Adept-notifier currently works identically for all users. This is
counterproductive for
users who do not manage the computer, are not in the admin group, and cannot
sudo. if an update is needed it displays the warning icon which encourages
(I am an occasional spambayes developer)
This behaviour is by design. future versions are likely to offer other
storage options which do not have this problem (possibly based on zodb).
Short-term solutions include:
a. Configure procmail to use a lock file, and use a wrapper script
around
20 matches
Mail list logo
