I don't have easy access to this machine any more, so further updates
will not be likely.
I guess this was more of a feature request than it was a bug.
--
Modem monitor - inadequate status feedback
https://launchpad.net/bugs/46169
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
It would be good if command line parameters were editable in this
properties window.
--
Property contextual menu on item...
https://launchpad.net/bugs/11324
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This bug is not just for SMB shares, but for mounted file systems in
general.
I've added a similar comment upstream.
--
emblems from the sidebar are updated when clicked, should be set right at
startup
https://launchpad.net/bugs/35411
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I just re-installed and decided to switch to ubuntu instead for a bit of
change. Next time I have to re-install, I'll consider Kubuntu then, but
so far I'm happy with the gnome counterpart.
--
dist-upgrade wants to delete almost kde packages while migrating from breezy to
dapper
Ubuntu- Dapper with updates
Printer - Canon Pixma IP4200
Drivers - Pixma IP4200
Connection- usb://Canon/iP4200
Resolution- 600x600 DPI
Remaining Settings - defaults
(No third party printing packages installed at all)
Summary
- colour printing seems to be of a very
Public bug reported:
Subject: Totem crashes when the visualisation size is changed
Distribution: Ubuntu 6.06 (dapper)
Package: totem
Severity: Normal
Version: GNOME2.14.2 1.4.1
Gnome-Distributor: Ubuntu
Synopsis: Totem crashes when the visualisation size is changed
Bugzilla-Product: totem
After the screen saver came on, I cannot now reproduce the problem.
I'm starting to suspect that the problem is either to do with the
drivers for the ATI card I have or with OpenGL as the problem was
originally observed after the machine was hung by the screen saver and
required a hard reboot.
There wasn't anything that looked useful in /var/log/syslog.
My parents now have the computer, and they have noticed the problem on
several occasions. The workaround is to do a re-boot.
Either way, some extra information in the dialog would provide some much
needed feedback to the user not only
