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 inst
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
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 =
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
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.launc
$ 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 o
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
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) libimobil
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/bi
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.
Un
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/Se
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
gconftoo
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 notifica
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
*** 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 b
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:/
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 s
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
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 o
*** 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
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 exter
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,
** 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
Deskt
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 bec
** 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 B
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 q
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
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
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.laun
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',
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
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 s
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.
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 lo
Here the gpm.log for the situation, taken with gnome-power-manager
--verbose 2>&1 | 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 y
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, whic
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-pow
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 g
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 subscribe
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 g
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-m
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-m
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 subscri
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 g
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
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
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
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 d
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 assigne
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
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-ext
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
d
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 w
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.
-
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
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
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
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 => Confirm
** 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 suspen
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 consol
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 receive
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.
--
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 Ubu
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
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 famil
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://
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
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: N
*** 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 be
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/li
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 uninsta
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
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 ma
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
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@lis
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:
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/
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
d
I used Edgy. Bug 59054 looks related, however there is no empty iso
created anywhere and no error "unknown error while creating the image"
shown.
--
Lack of warning message when low on diskspace
https://launchpad.net/bugs/76731
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://
Public bug reported:
Binary package hint: nautilus-cd-burner
There should be a warning message that there is not enough filespace available
when trying to write an iso file.
This bug has been reported upstream (#388142 in bugzilla.gnome.org -
http://bugzilla.gnome.org/show_bug.cgi?id=388142)
**
80 matches
Mail list logo
