Turns out this 'feature' is configurable in GConf.
Run gconf-editor and un-set the following:
/apps/update-manager/summary_before_name
That doesn't remove the bug, however, because there is no compelling
argument to be made for ever showing summaries before names. Doing so
only breaks every
Public bug reported:
Following recent updates, the /var/run/motd file is being updated
properly, but the data contained within is not. This refers
specifically to the data udpated by the following scripts:
/usr/lib/update-notifier/update-motd-cpu-checker
Verification that /var/run/motd is actually being regenerated with
outdated information:
it@milpat:~$ sudo rm /var/run/motd
it@milpat:~$ logout
Connection to milpat closed.
dmcgarry@emigre:~/devel/goofalicious/src/Goofalicious$ ssh milpat
Linux milpat 2.6.32-4-pve #1 SMP Thu Oct 21 09:35:29 CEST
Two examples of why this is bad UI behaviour:
1) The heading for the Google Chrome browser is 'The browser from
Google'. No actual reference to the name, and unnecessarily verbose.
2) The entry for subversion is 'Advanced Version Control System'. Again,
no name, and hopelessly imprecise. Worse,
Demonstration of why this is a bug:
http://scriptorum.imagicity.com/2010/12/07/ui-follies/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/655998
Title:
Update Manager Listing should NOT use
Public bug reported:
Binary package hint: update-manager
The use of package descriptions (instead of package names) in the Update
Manager package listings represents a significant and needless reduction
in usability.
There is no scenario in which a description of a package to be upgraded
works
Given that I'm still seeing these symptoms on an up-to-date Lucid
installation, I'm assuming there's been no movement on this.
Can anyone suggest a more elegant work-around than 'log in and out a few
times until things work again'?
--
Active VT tracking can fail at startup
Suggest you re-open, as it's reliably happening to me on an up-to-date
Lucid system (i386).
** Changed in: gdm (Ubuntu)
Status: Invalid = Incomplete
--
G_VALUE_HOLDS_BOOLEAN (value)' failed
https://bugs.launchpad.net/bugs/540774
You received this bug notification because you are a member
Seeing the same problem while performing a clean install of Lucid on a
5.0 TB LVM (IBM RAID). As Grub is being installed, it informs the user
that 'You have chosen not to install grub on any device', trying to
go back or replying 'No' to the question 'Do you want to continue
without installing
Er - what was I saying about unreliable witnesses?
That last post was, uh, unreliable. Ignore that attachment.
--
Some modules are not automatically loaded after dist-upgrade from 5.10 to 6.06
beta
https://launchpad.net/bugs/41144
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
However I'm saying that all of the evidence you have supplied indicates
the system is working perfectly and you haven't provided a single piece
of evidence that it isn't.
I have done. It's called testimony. 8^)
I agree that *almost always* the witnesses are not as reliable as the
physical
I'll confirm K's report and views.
The 'breakage' I reported above resulted from grub not updating the boot
menu to default to the most recent kernel, which caused me to boot to
the 2.6.12-10-386 kernel instead.
Whatever the problem was, it was transient.
--
Some modules are not automatically
Whatever udev may be showing is trumped by the fact that my stylus,
sound card and other USB devices did not work until I added the relevant
lines in /etc/modules. Given that it happened *immediately* after
updating from Breezy to Dapper, it seems reasonable to assume a change
in that upgrade
Sorry, something must have got messed up. Internet here in Vanuatu is
pretty flaky most of the time
--
Some modules are not automatically loaded after dist-upgrade from 5.10 to 6.06
beta
https://launchpad.net/bugs/41144
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The problem is not that missing file, we do not use modutils in Ubuntu
Yep, I realised that after the fact. I tried to get confirmation on how
/etc/modules gets populated on IRC (including #ubuntu-bugs) and the
lists, but no one was available to answer that.
Attaching /var/log/udev as requested.
It looks like the problem is from a missing file...
@emigre:~$ dpkg -S /sbin/update-modules
diversion by module-init-tools from: /sbin/update-modules
diversion by module-init-tools to: /sbin/update-modules.modutils
module-init-tools: /sbin/update-modules
@emigre:~$ dpkg -S
see recent comments in Bug 41144 for a possible work-around. (It
resolved all the hot-plug issues raised here for my wacom graphire USB
tablet.)
--
Lack of support for hotplugging and Dapper kernel
https://launchpad.net/bugs/38336
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I think even we need to be careful about making functionality
assumptions based on USER-AGENT. I can think of a few scenarios where
the example you provide would be counter-productive. The most obvious
one is someone trying to learn more before upgrading. As a corrolary to
that, I run my personal
If the content of h.u.c is not dynamically generated, then there are
strong technical reasons to avoid this kind of functionality. The most
significant of these is that the HTTP-USER-AGENT header is an arbitrary
tag, and is subject to change without notice. The content of h.u.c. is
in constant
I've confirmed this on two separate upgrades from 5.10 to 6.06. I've got
dapper-security and dapper-updates enabled as well, so we can assume
that the problem still exists as of today.
Testing a work-around now. Will post details if results merit.
--
Some modules are not automatically loaded
Manually editing the /etc/modules to include
snd-intel8x0
Gets sound working again.
Note that adding the following modules also seems to resolve (or at
least render moot) issues (Bug #38336, Bug #41381 and some of Bug
#40473) concerning wacom tablets as well:
uhci_hcd
ehci_hcd
usbcore
21 matches
Mail list logo