Redirecting all trash to ~/.local/share/Trash/files does not fully solve
the problem
Correct implementation of trash will require:
1) Integration of all trash in all volumes, not just home
2) Displaying of original file names, not mangled ones
3) Display of metadata from Trash/info: delete date,
I should be more careful with my wording -- 3 and 4 are really just
obvious next-step features given the metadata required by the trash
spec.
Achieving 1 will get you feature parity with the gnome trash applet and
should be enough work. You will probably also have to generate the
metadata files
Jerson,
Sika has posted a working fix for this issue. In the launch script,
/usr/bin/keytouchd-launch, repacing the lines to kill keytouchd by pid
with killall keytouchd-launch will reliably terminate both processes on
logout without hanging.
Sika's corrected keytouchd-launch:
This appears to be normal behavior. If a drive doesn't unmount
correctly before disconnecting it or turning off the computer (ie a
power outage, forced power-off, or literally pulling the plug) then
there could be errors in the file system. The error message during
boot is just a notification
I'm seeing similar behavior on a Dell Inspiron 1520. The brightness
down button functions normally, but brightness up has no effect. The
brightness meter appears, and the progress bar quickly increments and
decrements back to the same position.
xev shows four keypress events with code 212 in
Still present in latest Gutsy kernel 2.6.22-12. I can't do anything to
get snd_hda_intel to load.
--
Intel HDA Sound device doesn't work in gutsy
https://bugs.launchpad.net/bugs/119266
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
I can confirm a reproducible lockup related to K3B 1.0 on my Edgy
system. I also happen to have an LG burner and am running gnome. In my
case, immediately following successfully burning a DVD (with the write
successful message displayed) the system locks (completely unresponsive;
ctrl+alt+F1
***Typo in previous post:
This problem did not exist when running 6.10/Edgy on this machine and
has only appeared after an upgrade to Ubuntu 7.04/Feisty.
--
k3b causes system freeze
https://bugs.launchpad.net/bugs/110484
You received this bug notification because you are a member of Kubuntu
The deb package seems to be 404. I can temporarily host it if need be
if somebody can send me the file.
--
Support for Intel 965 (GMA X3000) doesn't work
https://launchpad.net/bugs/62135
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
