Sorry, I was waiting to get a chance to try again, but the time never
came. The last time I used that machine with an external monitor, on the
Hardy branch just before its release, it "sort of" worked, but I still
had to xrandr the laptop panel off in order to get the full resolution
on the externa
Also applies to "no candidate version" packages. I suspect the package
list gets checked through twice instead of once.
--
Hardy aptitude prints duplicate "already installed" packages
https://bugs.launchpad.net/bugs/205915
You received this bug notification because you are a member of Ubuntu
Bugs
Public bug reported:
[EMAIL PROTECTED] ~ $ sudo aptitude -v install hdparm sdparm
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
hdparm
Workaround found:
"Virtual 1600 1200" in xorg.conf (possibly avoidable)
xrandr --output LVDS --off
xrandr -s 1600x1200
The first command disables the internal monitor, allowing the second
command to raise the resolution. KDE, Fluxbox, etc. require restart to
see the new resolution, but GNOME seems
It seems that nuking ~/.purple leads to a correctly generated prefs.xml
on the next startup. So this bug is "fixed" if you only started using
Pidgin after the Gutsy release. Otherwise it might be a nice note to
publish.
--
Pidgin's settings aren't saved on Gutsy
https://bugs.launchpad.net/bugs/14
More clarity on my case, seen on every machine I have installed Ubuntu
Gutsy Beta on.
* Attempt to set "Initiate Window Resize" to Button3 instead of
Button2
The request is completely ignored, nothing changes and no warning of
replacing Initiate Window Menu is given.
* Attempt to clear or ch
Public bug reported:
Boot or install Gutsy snapshot on Dell Latitude D600 with attached
external monitor (specifically, Dell 2001FP).
Laptop panel is 1400x1050, external monitor is 1600x1200. Card is a
Radeon 9000 Mobility, supported 'fully' by the open ati driver.
GDM, KDM, GNOME, all use the 1
Public bug reported:
Binary package hint: pidgin
Pidgin plugins are disabled on start. DIscovered using "Message
Notification" plugin.
Procedure:
* Enable a plugin via Tools > Plugins
* Configure that plugin
* Quit Pidgin
* Open Pidgin
The plugin is disabled, but its configuration is intact.