[Bug 692791] Re: Installing then removing evolution leaves unused packages behind
I do think apt does the right thing. On Precise I did: $ sudo apt-get install evolution $ sudo apt-get purge evolution $ sudo apt-get autoremove Note that purge/remove will only remove the package and packages that are directly dependent on it, e.g. evolution-plugins. Packages that have been installed as a requirement for the soon to be removed package (evolution) are marked auto and will get removed with 'autoremove' if no dependent package on it is found. I mark the bug invalid. ** Changed in: apt (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/692791 Title: Installing then removing evolution leaves unused packages behind To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/692791/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 923290] Re: iPod support missing
Question 179930 seems related. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/923290 Title: iPod support missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/923290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 923290] [NEW] iPod support missing
Public bug reported: I've upgraded from 10.04 LTS to Precise during alpha. When I insert my iPod via USB, Rhythmbox does not include the device. dmesg contains the mass storage hints: [16728.907724] scsi 5:0:0:0: Direct-Access AppleiPod 1.62 PQ: 0 ANSI: 0 [16728.910789] sd 5:0:0:0: Attached scsi generic sg2 type 0 [16731.210723] sd 5:0:0:0: [sdb] 117210240 512-byte logical blocks: (60.0 GB/55.8 GiB) [16731.211908] sd 5:0:0:0: [sdb] Write Protect is off [16731.211917] sd 5:0:0:0: [sdb] Mode Sense: 68 00 00 08 [16731.213022] sd 5:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [16731.232603] sdb: sdb1 sdb2 [16731.239508] sd 5:0:0:0: [sdb] Attached SCSI removable disk [17004.792832] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [17004.795422] SGI XFS Quota Management subsystem [17004.801213] JFS: nTxBlock = 8192, nTxLock = 65536 [17004.811684] NTFS driver 2.1.30 [Flags: R/O MODULE]. [17004.828214] QNX4 filesystem 0.2.3 registered. [17004.853791] Btrfs loaded Music-Check new devices does not reveal anything. It worked well on 10.04 LTS. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/923290 Title: iPod support missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/923290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 923290] Re: iPod support missing
Launching rhythmbox from the command line with -d reveals this upon check new devices: (11:30:45) [0x8732ca0] [rb_removable_media_manager_add_volume] rb-removable-media-manager.c:682: Unhandled media (11:30:45) [0x8732ca0] [dump_volume_identifiers] rb-removable-media-manager.c:637: unix-device = /dev/sdb2 (11:30:45) [0x8732ca0] [dump_volume_identifiers] rb-removable-media-manager.c:637: uuid = 1580-415E (11:30:45) [0x8732ca0] [dump_volume_identifiers] rb-removable-media-manager.c:637: label = TORSTEN'S I found device path /dev/sdb2 for mount /media/TORSTEN'S I found ID_MEDIA_PLAYER tag apple_ipod for device /dev/sdb2 device information (system database) information read from system device database model: iPod vendor: Apple filesystem uuid: 1580-415E drive type: (none) requires eject: true access protocols: storage ipod output formats: audio/mpeg audio/aac audio/x-wav audio/x-aiff input formats: (none) playlist formats: (none) playlist path: (none) audio folders: (none) folder depth: -1 /media/TORSTEN'S I is already a mount point override file /media/TORSTEN'S I/.is_audio_player not found on mount /media/TORSTEN'S I (11:30:45) [0x8732ca0] [rb_removable_media_manager_add_mount] rb-removable-media-manager.c:757: Unhandled media Complete log is attached. ** Attachment added: rhythmbox.log https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/923290/+attachment/2699331/+files/rhythmbox.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/923290 Title: iPod support missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/923290/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 923297] [NEW] No indicator support
Public bug reported: On precise Rhythmbox does not display any indicator. When closing the window via the window manager music continues playing without giving the user any hint how to stop it. One needs to open rhythmbox again and then use music-quit to stop the playback. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/923297 Title: No indicator support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/923297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 839744] Re: package libglib2.0-0 2.29.16-0ubuntu3 [modified: usr/share/doc/libglib2.0-0/changelog.Debian.gz] failed to install/upgrade: ErrorMessage: './usr/share/doc/libglib2.0-0/changelog.Debia
$ ls -l /usr/share/doc/libglib2.0-0/changelog.Debian.gz -rw-r--r-- 1 root root 1669 2011-09-19 08:32 /usr/share/doc/libglib2.0-0/changelog.Debian.gz Note that now both packages are installed: ii libglib2.0-0 2.29.92-0ubuntu1 GLib library of C routines ii libglib2.0-0:i3862.29.92-0ubuntu1 GLib library of C routines -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/839744 Title: package libglib2.0-0 2.29.16-0ubuntu3 [modified: usr/share/doc/libglib2.0-0/changelog.Debian.gz] failed to install/upgrade: ErrorMessage: './usr/share/doc/libglib2.0-0/changelog.Debian.gz' is different from the same file on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/839744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 732867] Re: gnome-display-properties monitor layout not saved when re-docking (and display port)
The attached python script utilizes pyudev (available from Natty onward) to wait for docking events and then calls gnome-settings-daemon ApplyConfiguration method. It's a slight improvement over the udev rules hackery before. Would be interesting to hear if this approach resolves the original issue or not. ** Attachment added: docking-event.py https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/732867/+attachment/2413187/+files/docking-event.py -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/732867 Title: gnome-display-properties monitor layout not saved when re-docking (and display port) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/732867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 732867] Re: gnome-display-properties monitor layout not saved when re-docking (and display port)
I can reproduce this problem on a Lenovo T61 with a docking station, the monitor layout setting is not used. However, when I call ApplyConfiguration via dbus, then the correct setting is applied: dbus-send --type=method_call --print-reply --session --dest=org.gnome.SettingsDaemon /org/gnome/SettingsDaemon/XRANDR org.gnome.SettingsDaemon.XRANDR.ApplyConfiguration -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/732867 Title: gnome-display-properties monitor layout not saved when re-docking (and display port) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/732867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 732867] Re: gnome-display-properties monitor layout not saved when re-docking (and display port)
Calling gsd_xrandr_manager_apply_configuration (mgr, error); unconditionally from plugins/xrandr/gsd-xrandr-manager.c handle_fn_f7 will restore the existing configuration as well. But fn-f7 cycling through display modes stops working, as the existing configuration will always take precedence. Unfortunately I don't think gnome-settings-daemon has any idea that the system is being docked. So only conditionally calling apply_configuration from gsd-xrandr-manager.c handle_fn_f7 will most likely not work. Is there any other place in the system that is run only when a system is being docked? From there we could call ApplyConfiguration via dbus. Alternatively the fn-f7 modes should contain the saved configuration, the configurations are generated upon docking in generate_fn_f7_configs: g_ptr_array_add (array, gnome_rr_config_new_current (screen)); g_ptr_array_add (array, make_clone_setup (screen)); g_ptr_array_add (array, make_xinerama_setup (screen)); g_ptr_array_add (array, make_laptop_setup (screen)); g_ptr_array_add (array, make_other_setup (screen)); g_ptr_array_add (array, gnome_rr_config_new_stored (screen, NULL)); /* NULL-GError - if this can't read the stored config, no big deal */ -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/732867 Title: gnome-display-properties monitor layout not saved when re-docking (and display port) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/732867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 732867] Re: gnome-display-properties monitor layout not saved when re-docking (and display port)
I followed the path of calling ApplyConfiguration from a script upon
docking, and while it is not pretty, it basically works:
# cat /etc/udev/rules.d/80-thinkpad-T61.rules
KERNEL==dock.0, ATTR{docked}==1, RUN+=/usr/local/bin/dock.sh 1
KERNEL==dock.0, ATTR{docked}==0, RUN+=/usr/local/bin/dock.sh 0
# cat /usr/local/bin/dock.sh
#!/bin/sh
LOG=/tmp/dock.$$
echo Called dock.sh with $@, proceeding ${LOG}
if [ $1 -eq 1 ]; then
DISPLAY=:0.0
export DISPLAY
sudo -u ubuntu dbus-send --type=method_call --print-reply --session
--dest=org.gnome.SettingsDaemon /org/gnome/SettingsDaemon/XRANDR
org.gnome.SettingsDaemon.XRANDR.ApplyConfiguration 21 ${LOG}
fi
echo Done docking ${LOG}
Is this path worth pursuing or is this approach out of question for fixing the
problem?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/732867
Title:
gnome-display-properties monitor layout not saved when re-docking (and
display port)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/732867/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 732867] Re: gnome-display-properties monitor layout not saved when re-docking (and display port)
Unfortunately upower 0.9.1 on Ubuntu 10.04 LTS does not have up_client_get_is_docked. The earliest upower that has it is in Natty. Backporting this to Lucid seems like a task, due to dependencies: dpkg-checkbuilddeps: Unmet build dependencies: debhelper (= 8) libusb-1.0-0-dev (= 1.0.0) libimobiledevice-dev (= 0.9.7) libgirepository1.0-dev (= 0.9.12) gobject-introspection (= 0.9.12-4~) gir1.2-glib-2.0 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/732867 Title: gnome-display-properties monitor layout not saved when re-docking (and display port) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/732867/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 620693] Re: Screen not locked when turned off
I did some more structured testing this morning and on 20 occasions the screen was always locked. However, /apps/gnome-power- manager/lock/use_screensaver_settings was set to false, not to true as in step 2b. I'll retest with use_screensaver_settings set to true. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/620693 Title: Screen not locked when turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/620693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 620693] Re: Screen not locked when turned off
10 more tests also resulted in screen being locked. For the record, here are the gconf keys: gconftool-2 --get /apps/gnome-power-manager/lock/use_screensaver_settings true gconftool-2 --get /apps/gnome-screensaver/lock_enabled true gconftool-2 --get /desktop/gnome/session/idle_delay 5 gconftool-2 --get /apps/gnome-power-manager/timeout/sleep_display_ac 60 Is there anything missing from my testing? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/620693 Title: Screen not locked when turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/620693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 620693] Re: Screen not locked when turned off
For me it sometimes locks the screen, sometimes it doesn't. From my testing I could so far not detect any patterns. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/620693 Title: Screen not locked when turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/620693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 839744] Re: package libglib2.0-0 2.29.16-0ubuntu3 [modified: usr/share/doc/libglib2.0-0/changelog.Debian.gz] failed to install/upgrade: ErrorMessage: './usr/share/doc/libglib2.0-0/changelog.Debia
*** This bug is a duplicate of bug 835625 *** https://bugs.launchpad.net/bugs/835625 ** This bug has been marked a duplicate of bug 835625 apt may try to unpack a foreign-arch multiarch library before the native package is at a multiarch version, prohibited by dpkg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/839744 Title: package libglib2.0-0 2.29.16-0ubuntu3 [modified: usr/share/doc/libglib2.0-0/changelog.Debian.gz] failed to install/upgrade: ErrorMessage: './usr/share/doc/libglib2.0-0/changelog.Debian.gz' is different from the same file on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/839744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 839744] Re: package libglib2.0-0 2.29.16-0ubuntu3 [modified: usr/share/doc/libglib2.0-0/changelog.Debian.gz] failed to install/upgrade: ErrorMessage: './usr/share/doc/libglib2.0-0/changelog.Debia
Happened to me during an upgrade from 11.04 as well. Disabling multiarch works around the problem that glib2.0 i386 wants to overwrite the amd64 changelog file. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/839744 Title: package libglib2.0-0 2.29.16-0ubuntu3 [modified: usr/share/doc/libglib2.0-0/changelog.Debian.gz] failed to install/upgrade: ErrorMessage: './usr/share/doc/libglib2.0-0/changelog.Debian.gz' is different from the same file on the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/839744/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 586528] Re: keyboard doesn't work after screensaver shuts down the monitor
Does the work around of minimizing and maximizing the applications always work? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/586528 Title: keyboard doesn't work after screensaver shuts down the monitor -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 705791] Re: 10.04, Multi Monitor: gnome-screensaver does not show login dialog after resume in docking station with lid closed.
I just reproduced the problem with a T61 and a docking station using Natty, following the sequence in the bug description. 1) Laptop is placed in a docking station 2) gnome-display-properties has been used to disable the internal laptop screen and only use the external display, this is stored in the gnome monitors.xml 3) Laptop is undocked 4) Laptop is suspended 5) Laptop is placed in docking station and resumes Expected result: gnome-screensaver displays a login prompt. Actual result: gnome-screensaver has to be killed from the console to gain access to the session. ** Summary changed: - 10.04, Multi Monitor: gnome-screensaver does not show login dialog after resume in docking station with lid closed. + T-61 Multi Monitor: gnome-screensaver does not show login dialog after resume in docking station with lid closed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/705791 Title: T-61 Multi Monitor: gnome-screensaver does not show login dialog after resume in docking station with lid closed -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740805] [NEW] [10.04] Black screen on external display when resuming with lid closed in docking station
Public bug reported: Binary package hint: gnome-screensaver Steps to reproduce: 1) Boot outside of docking station, login 2) Suspend, close the lid 3) Put laptop in docking station 4) Resume with lid closed via docking station power button Expected behaviour: Login dialogue is displayed on external display Actual behaviour: External display stays black; ssh login to the system and killing gnome-screensaver restores access to the session. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/740805 Title: [10.04] Black screen on external display when resuming with lid closed in docking station -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 740805] Re: [10.04] Black screen on external display when resuming with lid closed in docking station
*** This bug is a duplicate of bug 705791 *** https://bugs.launchpad.net/bugs/705791 ** This bug has been marked a duplicate of bug 705791 10.04, Multi Monitor: gnome-screensaver does not show login prompt with one disabled. * You can subscribe to bug 705791 by following this link: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/705791/+subscribe -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/740805 Title: [10.04] Black screen on external display when resuming with lid closed in docking station -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 705791] Re: 10.04, Multi Monitor: gnome-screensaver does not show login prompt with one disabled.
Another way to reproduce, from the soon to be duplicate marked bug: Steps to reproduce: 1) Boot outside of docking station, login 2) Suspend, close the lid 3) Put laptop in docking station 4) Resume with lid closed via docking station power button Expected behaviour: Login dialogue is displayed on external display Actual behaviour: External display stays black; ssh login to the system and killing gnome-screensaver restores access to the session. ** Summary changed: - 10.04, Multi Monitor: gnome-screensaver does not show login prompt with one disabled. + 10.04, Multi Monitor: gnome-screensaver does not show login dialog after resume in docking station with lid closed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/705791 Title: 10.04, Multi Monitor: gnome-screensaver does not show login dialog after resume in docking station with lid closed. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 705791] [NEW] 10.04, Multi Monitor: gnome-screensaver does not show login prompt with one disabled.
Public bug reported: Binary package hint: gnome-screensaver In the following scenario no login prompt after a resume from suspend is shown: 1) Laptop is placed in a docking station 2) gnome-display-properties has been used to disable the internal laptop screen and only use the external display, this is stored in the gnome monitors.xml 3) Laptop is undocked 4) Laptop is suspended 5) Laptop is placed in docking station and resumes Expected result: gnome-screensaver displays a login prompt. Actual result: gnome-screensaver has to be killed from the console to gain access to the session. ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. https://bugs.launchpad.net/bugs/705791 Title: 10.04, Multi Monitor: gnome-screensaver does not show login prompt with one disabled. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 673082] [NEW] 10.04: Print in black/white instead of color
Public bug reported: Binary package hint: eog For a printer there are two print queues, one for black/white, one for colour. eog always prints in black/white to the color print queue. If the setting on 'Advanced' is changed to stop using 'gray scale', this is also true for the black/white print queue, e.g. from then on it will print in color. This happens on Ubuntu 10.04 LTS. ** Affects: eog (Ubuntu) Importance: Undecided Status: New -- 10.04: Print in black/white instead of color https://bugs.launchpad.net/bugs/673082 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 673082] Re: 10.04: Print in black/white instead of color
** Attachment added: D347.ppd https://bugs.launchpad.net/ubuntu/+source/eog/+bug/673082/+attachment/1728055/+files/D347.ppd -- 10.04: Print in black/white instead of color https://bugs.launchpad.net/bugs/673082 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 673082] Re: 10.04: Print in black/white instead of color
printers.conf from the system. ** Attachment added: printers.conf https://bugs.launchpad.net/ubuntu/+source/eog/+bug/673082/+attachment/1728054/+files/printers.conf -- 10.04: Print in black/white instead of color https://bugs.launchpad.net/bugs/673082 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 673082] Re: 10.04: Print in black/white instead of color
** Attachment added: D347-C.ppd https://bugs.launchpad.net/ubuntu/+source/eog/+bug/673082/+attachment/1728056/+files/D347-C.ppd -- 10.04: Print in black/white instead of color https://bugs.launchpad.net/bugs/673082 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 595985] Re: Triggers suspend on undocking
On Mon, 2010-07-12 at 14:01 +, Martin Pitt wrote: I. e. I do not quite agree to 3) System suspends (rightfully). Isn't that rather unexpected? It's certainly for me. It's controlled via gconf, apps/gnome-power-manager/actions/event_when_closed_battery A work around for this problem is to disable this trigger. One thing that confuses me is that the verbose log reports a lid-down event after undocking. I assume you did not actually close it, but it was closed all the time, and then you opened it? This could be bug 481312 which was recently fixed upstream (see https://bugzilla.gnome.org/show_bug.cgi?id=622026). Correct, it was placed in the docking station with lid closed. I can test this in two weeks when I'm back home again (with a dock). Great, if there's anything for me to test in between, let me know. -- Triggers suspend on undocking https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] Re: Two suspends when opening lid
The attached patch removes the AC power disconnect event, which fixes this problem, though introduces another one ** Patch added: ac-adapter-removed-event-gone.patch http://launchpadlibrarian.net/51229985/ac-adapter-removed-event-gone.patch -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 595985] Re: Two suspends when opening lid
I found /apps/gnome-power-manager/action/event_when_closed_battery that seems to have the same effect as my patch, albeit less invasive. Thanks for the reminder! -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] Re: Two suspends when opening lid
A work around might be to inhibit gnome-power manager for a few seconds when resuming. -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 595985] Re: Two suspends when opening lid
The following dbus-send command is a first attempt. It does not inhibit right now, but I believe the path is right: dbus-send --print-reply --dest='org.gnome.SessionManager' /org/gnome/SessionManager org.gnome.SessionManager.Inhibit string:torsten uint32:0 string:Just a test uint32:15 -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 595985] Re: Two suspends when opening lid
The dbus-send command cannot work due to the fact that dbus-send exits and Inhibitor cleans up thereafter. -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] Re: Two suspends when opening lid
I tried the following python script called from resume, but it gnome-
power-manager simply waits for the inhibited time and then the system
will sleep:
==
#!/usr/bin/env python
import dbus
import time
session_bus = dbus.SessionBus()
proxy = session_bus.get_object('org.gnome.SessionManager',
'/org/gnome/SessionManager')
proxy.Inhibit(torsten, dbus.UInt32(0), Just a test, dbus.UInt32(15))
# Nasty way to remove the inhibt, we just exit after 120 seconds
time.sleep(120)
==
The same happens when calling kill -STOP and kill -CONT after a period
of time on gnome-power-manager. The signal seems to be already in the
queue and will be processed whenever g-p-m continues to run.
--
Two suspends when opening lid
https://bugs.launchpad.net/bugs/595985
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] Re: Two suspends when opening lid
Here the gpm.log for the situation, taken with gnome-power-manager --verbose 21 | tee ~/gpm.log ** Attachment added: gpm.log http://launchpadlibrarian.net/51114828/gpm.log -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] Re: Two suspends when opening lid
Grepping for suspend in gpm.log I see these two lines: - suspending, reason: The lid has been closed, and the ac adapter removed (and gconf is okay). - suspending, reason: The lid has been closed on battery power. The later reason seems to be unjustified as the lid was open, especially when looking at the time stamps. -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] [NEW] Two suspends when opening lid
Public bug reported: Binary package hint: gnome-power-manager When booting the system with lid closed in a docking station, and then removing it from the docking station the system goes to sleep. When opening the lid the system goes to sleep again. Steps to reproduce 1) Boot with lid closed in docking station 2) Remove laptop with lid closed from docking station 3) System suspends (rightfully) 4) Opening the lid causes the system to resume 5) System suspends again (wrong) --- Architecture: i386 DistroRelease: Ubuntu 10.04 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No MachineType: LENOVO 6463WFX Package: gnome-power-manager 2.30.0-0ubuntu1 PackageArchitecture: i386 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic-pae root=/dev/mapper/VolGroup00-rootlv ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=de_DE.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-22.36-generic-pae 2.6.32.11+drm33.2 Tags: lucid UdevDb: Error: [Errno 2] No such file or directory Uname: Linux 2.6.32-22-generic-pae i686 UnreportableReason: This is not a genuine Ubuntu package UserGroups: dmi.bios.date: 05/11/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC6WW (2.26 ) dmi.board.name: 6463WFX dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC6WW(2.26):bd05/11/2009:svnLENOVO:pn6463WFX:pvrThinkPadT61:rvnLENOVO:rn6463WFX:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6463WFX dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected ** Tags added: apport-collected ** Description changed: Binary package hint: gnome-power-manager When booting the system with lid closed in a docking station, and then removing it from the docking station the system goes to sleep. When opening the lid the system goes to sleep again. Steps to reproduce 1) Boot with lid closed in docking station 2) Remove laptop with lid closed from docking station 3) System suspends (rightfully) 4) Opening the lid causes the system to resume 5) System suspends again (wrong) + --- + Architecture: i386 + DistroRelease: Ubuntu 10.04 + GnomeSessionIdleInhibited: No + GnomeSessionInhibitors: None + GnomeSessionSuspendInhibited: No + MachineType: LENOVO 6463WFX + Package: gnome-power-manager 2.30.0-0ubuntu1 + PackageArchitecture: i386 + ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-22-generic-pae root=/dev/mapper/VolGroup00-rootlv ro quiet splash + ProcEnviron: + PATH=(custom, no user) + LANG=de_DE.utf8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-22.36-generic-pae 2.6.32.11+drm33.2 + Tags: lucid + UdevDb: Error: [Errno 2] No such file or directory + Uname: Linux 2.6.32-22-generic-pae i686 + UnreportableReason: This is not a genuine Ubuntu package + UserGroups: + + dmi.bios.date: 05/11/2009 + dmi.bios.vendor: LENOVO + dmi.bios.version: 7LETC6WW (2.26 ) + dmi.board.name: 6463WFX + dmi.board.vendor: LENOVO + dmi.board.version: Not Available + dmi.chassis.asset.tag: No Asset Information + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Not Available + dmi.modalias: dmi:bvnLENOVO:bvr7LETC6WW(2.26):bd05/11/2009:svnLENOVO:pn6463WFX:pvrThinkPadT61:rvnLENOVO:rn6463WFX:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: + dmi.product.name: 6463WFX + dmi.product.version: ThinkPad T61 + dmi.sys.vendor: LENOVO -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] BootDmesg.txt
apport information ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/50547469/BootDmesg.txt -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] CurrentDmesg.txt
apport information ** Attachment added: CurrentDmesg.txt http://launchpadlibrarian.net/50547470/CurrentDmesg.txt -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] Dependencies.txt
apport information ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/50547472/Dependencies.txt -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] DevkitPower.txt
apport information ** Attachment added: DevkitPower.txt http://launchpadlibrarian.net/50547474/DevkitPower.txt -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] GConfNonDefault.txt
apport information ** Attachment added: GConfNonDefault.txt http://launchpadlibrarian.net/50547475/GConfNonDefault.txt -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] Lspci.txt
apport information ** Attachment added: Lspci.txt http://launchpadlibrarian.net/50547477/Lspci.txt -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] Lsusb.txt
apport information ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/50547478/Lsusb.txt -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] ProcCpuinfo.txt
apport information ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/50547479/ProcCpuinfo.txt -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] ProcInterrupts.txt
apport information ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/50547480/ProcInterrupts.txt -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] ProcModules.txt
apport information ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/50547481/ProcModules.txt -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] UdevLog.txt
apport information ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/50547482/UdevLog.txt -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 595985] gnome-power-bugreport.txt
apport information ** Attachment added: gnome-power-bugreport.txt http://launchpadlibrarian.net/50547483/gnome-power-bugreport.txt -- Two suspends when opening lid https://bugs.launchpad.net/bugs/595985 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 58352] Re: evolution-data-server Uses 100% CPU on disk-full.
I confirm Santiago's reporting, on Lucid evolution-data-center seems to take 100% CPU all the time. -- evolution-data-server Uses 100% CPU on disk-full. https://bugs.launchpad.net/bugs/58352 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515465] Re: g-p-m acts when switching to console and back to x when lid is closed
The attached source checks via xrandr if an external display is connected (named VGA or DVI). It does not work with drivers that don't provide xrandr interface, e.g. the binary driver from nvidia. ** Attachment added: detect-external-display.c http://launchpadlibrarian.net/41102727/detect-external-display.c -- g-p-m acts when switching to console and back to x when lid is closed https://bugs.launchpad.net/bugs/515465 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515465] Re: g-p-m acts when switching to console and back to x when lid is closed
Attached is the Makefile. Please let me know if this is the right direction for resolving the issue. ** Attachment added: Makefile http://launchpadlibrarian.net/41102756/Makefile -- g-p-m acts when switching to console and back to x when lid is closed https://bugs.launchpad.net/bugs/515465 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 539180] Re: Session keyring stored on disk in plain text
This problem was detected by Dominik Fischer. -- Session keyring stored on disk in plain text https://bugs.launchpad.net/bugs/539180 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515465] Re: g-p-m acts when switching to console and back to x when lid is closed
It is not completely clear to me how to use xrandr to detect multiple displays. On the command line it looks like the following will see if an external display is connected: $ xrandr | grep connected | grep -v disconnected | egrep VGA|DVI -- g-p-m acts when switching to console and back to x when lid is closed https://bugs.launchpad.net/bugs/515465 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515465] Re: g-p-m acts when switching to console and back to x when lid is closed
The attached patch prevents a system from going to sleep when lid is closed and it is docked. It contains a lot of debug output, just in case. ** Patch added: 19-fix-docking.patch http://launchpadlibrarian.net/40808957/19-fix-docking.patch -- g-p-m acts when switching to console and back to x when lid is closed https://bugs.launchpad.net/bugs/515465 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 515465] Re: g-p-m acts when switching to console and back to x when lid is closed
Checking for a display could be done with xrandr. I'll have a look at it. -- g-p-m acts when switching to console and back to x when lid is closed https://bugs.launchpad.net/bugs/515465 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 445481] Re: emulation category in games section?
Sounds like it is the gnome-menus package then, reassigning this bug. ** Package changed: apt (Ubuntu) = gnome-menus (Ubuntu) ** Changed in: gnome-menus (Ubuntu) Status: Incomplete = New -- emulation category in games section? https://bugs.launchpad.net/bugs/445481 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515465] Re: g-p-m acts when switching to console and back to x
** Description changed: ** Description changed: Binary package hint: gnome-power-manager I have configured g-p-m to go into suspend to ram when closing the LID on a Laptop running Lucid.. - Now when switching from X to a virtual console and then back to X the - laptop goes into suspend2ram. + If the system is in a docking station and started with the lid closed, the following problem occurs: + Now when switching from X to a virtual console and then back to X the laptop goes into suspend2ram. The expected result is that the laptop does not go into suspend2ram. I found this on a Lucid system: gnome-power-manager 2.29.1-0ubuntu2 -- g-p-m acts when switching to console and back to x https://bugs.launchpad.net/bugs/515465 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515465] Re: g-p-m acts when switching to console and back to x when lid is closed
Setting the bug to confirmed after seeing it on two different systems. ** Summary changed: - g-p-m acts when switching to console and back to x + g-p-m acts when switching to console and back to x when lid is closed ** Changed in: gnome-power-manager (Ubuntu) Status: Incomplete = Confirmed -- g-p-m acts when switching to console and back to x when lid is closed https://bugs.launchpad.net/bugs/515465 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515465] Re: g-p-m acts when switching to console and back to x when lid is closed
After killing gnome-power-manager the problem disappears. -- g-p-m acts when switching to console and back to x when lid is closed https://bugs.launchpad.net/bugs/515465 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515465] Re: g-p-m acts when switching to console and back to x
This seems to be fixed in 2.29.2-0ubuntu2, at least I cannot reproduce the problem on a Thinkpad T61. ** Changed in: gnome-power-manager (Ubuntu) Status: New = Invalid ** Changed in: gnome-power-manager (Ubuntu) Status: Invalid = Incomplete -- g-p-m acts when switching to console and back to x https://bugs.launchpad.net/bugs/515465 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 400329] Re: Lowercase v key not working in gnome terminal
It might be a local configuration problem. When you add another user to the system, is the same problem appearing there? ** Changed in: gnome-terminal (Ubuntu) Status: New = Incomplete -- Lowercase v key not working in gnome terminal https://bugs.launchpad.net/bugs/400329 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 176544] Re: gnome-power-manager: (user) suspend failed on Toshiba Portege R500
This solution works for me too, thanks John. -- gnome-power-manager: (user) suspend failed on Toshiba Portege R500 https://bugs.launchpad.net/bugs/176544 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 115256] Re: f-spot crashes when exporting pictures to directory
The problem does not happen for me on Hardy when starting f-spot with sloppy locks enabled for xcb: $ LIBXCB_ALLOW_SLOPPY_LOCK=1 f-spot -- f-spot crashes when exporting pictures to directory https://bugs.launchpad.net/bugs/115256 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 176544] Re: gnome-power-manager: (user) suspend failed on Toshiba Portege R500
The attached report is for Hardy, all available updates applied (2008-03-03). I'll attach dmesg output next. ** Attachment added: gnome-power-bugreport http://launchpadlibrarian.net/12379641/gnome-power-bugreport -- gnome-power-manager: (user) suspend failed on Toshiba Portege R500 https://bugs.launchpad.net/bugs/176544 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 176544] Re: gnome-power-manager: (user) suspend failed on Toshiba Portege R500
Following the process described on wiki.ubuntu.com/DebuggingKernelSuspend the attached dmesg was generated. Not sure if the included magic number is really relevant: [9.702287] Magic number: 0:810:724 After a reboot I get another Magic number: [9.052404] NET: Registered protocol family 1 [9.052442] Using IPI No-Shortcut mode [9.052477] registered taskstats version 1 [9.052616] Magic number: 0:466:876 [9.052659] hash matches device ptyx0 [9.052790] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [9.052792] EDD information not available. [9.053123] Freeing unused kernel memory: 364k freed ** Attachment added: dmesg.txt http://launchpadlibrarian.net/12379714/dmesg.txt -- gnome-power-manager: (user) suspend failed on Toshiba Portege R500 https://bugs.launchpad.net/bugs/176544 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 176544] Re: gnome-power-manager: (user) suspend failed on Toshiba Portege R500
Output of $ sudo report-hw is attached. ** Attachment added: report-hw.r500 http://launchpadlibrarian.net/12379720/report-hw.r500 -- gnome-power-manager: (user) suspend failed on Toshiba Portege R500 https://bugs.launchpad.net/bugs/176544 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 190237] Re: Type to test settings not recognizing layout
This is on Hardy: % dpkg -l gnome-control-center Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii gnome-control- 1:2.21.90-0ubu utilities to configure the GNOME desktop -- Type to test settings not recognizing layout https://bugs.launchpad.net/bugs/190237 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 190237] [NEW] Type to test settings not recognizing layout
Public bug reported: Binary package hint: gnome-control-center When adding a second layout it cannot be tested in the 'Type to test settings:' entry, every key pressed is interpreted with the original layout. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- Type to test settings not recognizing layout https://bugs.launchpad.net/bugs/190237 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 70046] Re: gnome-settings-daemon won't start, crashes
*** This bug is a duplicate of bug 61381 *** https://bugs.launchpad.net/bugs/61381 Has this problem been fixed by any of the more recent updates to gnome- control-center? -- gnome-settings-daemon won't start, crashes https://bugs.launchpad.net/bugs/70046 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 90423] Re: Apps not always removed from GNOME menus after uninstall [feisty]
I cannot reproduce your problem. 'dpkg -i frostwire-4.13.1.5-11.i586.deb' followed by an 'apt-get remove frostwire' did remove the entry in Applications-Internet. ** Changed in: gnome-menus (Ubuntu) Status: Unconfirmed = Rejected -- Apps not always removed from GNOME menus after uninstall [feisty] https://launchpad.net/bugs/90423 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 90423] Re: Apps not always removed from GNOME menus after uninstall [feisty]
Yes, the menu entry is there after the package is installed and is gone when removing the package. -- Apps not always removed from GNOME menus after uninstall [feisty] https://launchpad.net/bugs/90423 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87336] Printing via evince from smb vfs
Public bug reported: When connecting to a samba share via Places-Connect to Server and opening a pdf file with evince, it will not print on a connected printer. It prints when either a range is specified or when printing to a file is selected. This behaviour does not occur on Feisty. ** Affects: gnome-vfs2 (Ubuntu) Importance: Low Status: Confirmed ** Description changed: When connecting to a samba share via Places-Connect to Server and opening a pdf file with evince, it will not print on a connected printer. It prints when either a range is specified or when printing to - a file is selected. + a file is selected. This behaviour does not occur on Feisty. ** Tags added: edgy evince -- Printing via evince from smb vfs https://launchpad.net/bugs/87336 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87336] Re: Printing via evince from smb vfs
Confirmed on three different computers running edgy with latest updates. ** Changed in: gnome-vfs2 (Ubuntu) Importance: Undecided = Low Status: Unconfirmed = Confirmed -- Printing via evince from smb vfs https://launchpad.net/bugs/87336 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87336] Re: Printing via evince from smb vfs
Printing a pdf from a samba share mounted by smbmount works. -- Printing via evince from smb vfs https://launchpad.net/bugs/87336 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87336] Re: Printing via evince from smb vfs
The printing worked for me on Feisty. I could only reproduce the print problem from evince with files made available by gnomevfs via nautilus, this is why I filed the bug against gnomevfs rather than evince. -- Printing via evince from smb vfs https://launchpad.net/bugs/87336 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 87336] Re: Printing via evince from smb vfs
Yes, I consider the bug fixed in Feisty. For Edgy the above given work- arounds of either printing to a file or selecting the complete range are working. -- Printing via evince from smb vfs https://launchpad.net/bugs/87336 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066] Re: Unable to load any usable fontset
Try the following: When a file ~/.gnome2/share/fonts/fonts.dir exists, move it out of the way (e.g. mv ~/.gnome2/share/fonts/fonts.dir ~/.gnome2-share-fonts-fonts.dir-gone) and see if xdvi works. -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2066] Re: Unable to load any usable fontset
Forgot to add the following: Please end your session and start a new one. If this does not work, does 'xset fp rehash' work? -- Unable to load any usable fontset https://launchpad.net/bugs/2066 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
