[Bug 1189095] [NEW] gedit IBUS-WARNING - The owner of .. /.config/ibus/bus is not root!
Public bug reported: This is ubuntu-bug report and further info is meant to be added to another bug, but Launchpad could not find it by even a part of its title (odd name must have thown it): https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1125944 - (gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus is not root! Issue occured for me in very specific circumstances: attempt to run two sudo gedit commands running simultaneously. The second failed with the error: (gedit:3214): IBUS-WARNING **: The owner of /home/username/.config/ibus/bus is not root! It failed in the sense that gedit did not open. It may have been significant that a related command was already running in another terminal (xfce4-terminal 0.6.1) window: sudo iptables -L iptables_rules_.txt This comand takes a while to chug through its output. So gedit, or whatver, was already occupied. While that was happening, I had issued another sudo gedit command in another terminal window: sudo gedit /etc/firewall.bash It was that comand reported the above-quoted error. The failed sudo gedit command was resissued after the first had finished. Gedit opened the (new) file this time. It appeared, in other words, to have worked. It nevertheless repeated the error: (gedit:3301): IBUS-WARNING **: The owner of /home/username/.config/ibus/bus is not root!. The file meanwhile, was edited and saved without a problem. Xubuntu 13.04 i686 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gedit 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun Jun 9 08:41:29 2013 InstallationDate: Installed on 2012-11-28 (192 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: Upgraded to raring on 2013-05-14 (25 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1189095 Title: gedit IBUS-WARNING - The owner of .. /.config/ibus/bus is not root! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1189095/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1173510] Re: gvfsd-http crash rhythmbox streamming
*** This bug is a duplicate of bug 1153934 *** https://bugs.launchpad.net/bugs/1153934 When adding a new radio stream to Rhythmbox, the new stream will not play until gvfsd-http is killed. If Rhythmbox is restarted no stream will play until gvfsd-http is killed again. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1173510 Title: gvfsd-http crash rhythmbox streamming To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1173510/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1153934] Re: Some radio streams which used to play OK don't play after updating to rhythmbox 2.98 or higher due a gvfs bug
When adding a new radio stream to Rhythmbox, the new stream will not play until gvfsd-http is killed. If Rhythmbox is restarted no stream will play until gvfsd-http is killed again. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1153934 Title: Some radio streams which used to play OK don't play after updating to rhythmbox 2.98 or higher due a gvfs bug To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1153934/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189102] [NEW] Nautilus is left behind the opened window as the app haven't been started
Public bug reported: I drop a folder over the VLC icon in the Unity laucher. VLC started and the audio files in the folder started playing. However, if you click the Nautilus launcher icon, the program is started again as if it hasn't been started before. If you minimize all the other windows (the VLC one and the new Nautilus one), you'll find out that the first Nautilus window (with the folder which contained the audio files) is actually there. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-23.34-generic 3.8.11 Uname: Linux 3.8.0-23-generic i686 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: i386 Date: Sun Jun 9 11:26:44 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1437x899+65+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'218' InstallationDate: Installed on 2013-06-04 (4 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release i386 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 raring third-party-packages -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1189102 Title: Nautilus is left behind the opened window as the app haven't been started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1189102/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 982889] Re: X trying to start before plymouth has finished using the drm driver
Either this fix isn't complete or I have a similar problem. On my fast hardware (a Clevo W370ET with SSD and a quad core i7) I observe the same effects. Even after updating to latest versions I get the fault. I'm running raring (XUbuntu 13.04). I observe at 50% of booting a black screen with a blinking cursor and a mousepointer. I can switch to a terminal console and by entering the command sudo service lightdm restart I get a running graphical session. Also the workaround at comment #5, inserting a sleep 1 in lightdm.conf does help. But I doesn't like the idea of solving a race condition by inserting some sleep. Especially on a fast booting ssd notebook. Should I open a new bug report or should I continue tis one? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/982889/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189111] [NEW] gimp 2.8 crashed in Ubuntu when using gradients
Public bug reported: Hello. when using Gimp 2.8.4-1ubuntu1 on Ubuntu 13.04, and when trying to change the gradients with Glossy effects, Gimp is crashing. here is what i got in the terminal: 08344e0e664864cc2ede53d-le32d4.cache-3gimp: terminated: Aborted /usr/lib/gimp/2.0/plug-ins/script-fu: fatal error: GIMP crashed (script-fu:7724): LibGimp-WARNING **: script-fu: gimp_flush(): error: Broken pipe this bug is fixed in the upstream: https://bugzilla.gnome.org/show_bug.cgi?id=696240 but it is not fixed in Ubuntu until now. any help? thanks. ** Affects: gimp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1189111 Title: gimp 2.8 crashed in Ubuntu when using gradients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1189111/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189115] [NEW] Sound control lacks surround upmix tick and default card choice
Public bug reported: There should be ability to disable upmix from stereo to surround (i.e. 5.1) sound in gnome-control-center. I needed to manually change it in /etc/pulse/daemon.conf : enable-remixing = no The secod issue In the sound control app there is no choice of default sound card like in Windows. Now I have like 3 sound card Intel Ivy bridge embedded, Creative X-Fi USB, not to mention soundcard over HDMI/Display Port. When I turn my thinkpad the sound comes from X-Fi, but the volume control is still on Intel card ! It works this way since I remember. I would help in developing, just need the clue where to start :-) Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu24.1 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Sun Jun 9 10:38:12 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2012-10-25 (227 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, user) LANG=pl_PL.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: Upgraded to raring on 2013-04-09 (60 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.6bzr13.04.05-0ubuntu1.1 gnome-control-center-unity 1.2daily13.04.09-0ubuntu1 indicator-datetime 12.10.3daily13.03.26-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed raring -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1189115 Title: Sound control lacks surround upmix tick and default card choice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1189115/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189122] [NEW] google accounts cannot be added in online accounts
Public bug reported: whenever i try to add my google account to the online accounts in the ubuntu system settings, i get Error:invalid_request Invalid response_type: codeaccess_type=offlineapproval_prompt=force ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu27 ProcVersionSignature: Ubuntu 3.9.0-4.9-generic 3.9.4 Uname: Linux 3.9.0-4-generic i686 ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Sun Jun 9 15:17:44 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-05-21 (19 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130101) MarkForUpload: True ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_IN:en LANG=en_IN SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu2 gnome-control-center-signon 0.1.7~daily13.06.05.1-0ubuntu1 gnome-control-center-unity 1.3daily13.05.30-0ubuntu1 indicator-datetime 12.10.3daily13.06.07-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1189122 Title: google accounts cannot be added in online accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1189122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189111] Re: gimp 2.8 crashed in Ubuntu when using gradients
Thank you for reporting this bug. We will have to wait for the next GIMP version to include it. Please feel free to report any other bugs in Ubuntu you encounter. ** Bug watch added: GNOME Bug Tracker #696240 https://bugzilla.gnome.org/show_bug.cgi?id=696240 ** Also affects: gimp via https://bugzilla.gnome.org/show_bug.cgi?id=696240 Importance: Unknown Status: Unknown ** Summary changed: - gimp 2.8 crashed in Ubuntu when using gradients + Gimp 2.8 crashed in Ubuntu when using gradients ** Changed in: gimp (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1189111 Title: Gimp 2.8 crashed in Ubuntu when using gradients To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/1189111/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 47029] Re: Should always re-query xsane plugin at startup
No I mark it as confirmed because it happens to several users. Thank you for reporting. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/47029 Title: Should always re-query xsane plugin at startup To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/47029/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 47029] Re: Should always re-query xsane plugin at startup
Thank you Sven Neumann I'm marking this as xsane bug. ** Changed in: gimp (Ubuntu) Status: Confirmed = Invalid ** Also affects: xsane (Ubuntu) Importance: Undecided Status: New ** Changed in: xsane (Ubuntu) Status: New = Confirmed ** Changed in: xsane (Ubuntu) Status: Confirmed = Incomplete ** Changed in: xsane (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/47029 Title: Should always re-query xsane plugin at startup To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/47029/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189111] Re: Gimp 2.8 crashed in Ubuntu when using gradients
** Changed in: gimp Status: Unknown = Fix Released ** Changed in: gimp Importance: Unknown = Critical -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1189111 Title: Gimp 2.8 crashed in Ubuntu when using gradients To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/1189111/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 990908] Re: Won't honor Do Nothing when Lid is Closed
I see this too. I'm running Ubuntu 13.10 (Saucy) on a MacBookPro9,1. In the power settings I have When the lid is closed: Do nothing, but the machine suspends every time I close the lid. And unfortunately when I open the lid it can't wake from suspend (see bug #1186818), forcing me to reboot. -- 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/990908 Title: Won't honor Do Nothing when Lid is Closed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/990908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 995840] Re: When laptop lid is closed screen locks even if it should not
I believe this is a duplicate of bug #990908 ('Won't honor Do Nothing
when Lid is Closed'). As described in that bug, the computer suspends
when the lid is closed even though you've selected Do Nothing in the
power preferences.
--
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/995840
Title:
When laptop lid is closed screen locks even if it should not
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/995840/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 736606] Re: Do Nothing option not available for lid closing in Power settings
In the current development version of Ubuntu (13.10 Saucy) the power settings do offer a choice When the lid is closed: Do nothing. So I'm marking this as fixed. (The behavior is broken, but that's a different issue; see bug #990908.) ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed = Fix Released -- 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/736606 Title: Do Nothing option not available for lid closing in Power settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/736606/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 990908] Re: Won't honor Do Nothing when Lid is Closed
This bug is a duplicate of bug #1180513 (lid close actions are ignored laptop always suspends) in the gnome-settings-daemon project. These days gnome-settings-daemon actually handles power-related events such as suspend/resume (gnome-power-mangaer is historical). -- 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/990908 Title: Won't honor Do Nothing when Lid is Closed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/990908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 433500] Re: gvfsd memory leak
*** This bug is a duplicate of bug 760344 *** https://bugs.launchpad.net/bugs/760344 ** This bug has been marked a duplicate of bug 760344 gvfsd-http not closing tcp connections -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/433500 Title: gvfsd memory leak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/433500/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1158529] Re: gvfsd-http memory leaks
*** This bug is a duplicate of bug 760344 *** https://bugs.launchpad.net/bugs/760344 ** This bug has been marked a duplicate of bug 760344 gvfsd-http not closing tcp connections -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1158529 Title: gvfsd-http memory leaks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1158529/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1161317] Re: gvfsd-http could handle high traffic better
Isn't this a duplicate of bug #760344 ? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1161317 Title: gvfsd-http could handle high traffic better To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1161317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 760344] Re: gvfsd-http not closing tcp connections
Not sure if bug #1161317 is a duplicate of this or simply related. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/760344 Title: gvfsd-http not closing tcp connections To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/760344/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 990908] Re: Won't honor Do Nothing when Lid is Closed
*** This bug is a duplicate of bug 1180513 *** https://bugs.launchpad.net/bugs/1180513 ** This bug has been marked a duplicate of bug 1180513 lid close actions are ignored laptop always suspends -- 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/990908 Title: Won't honor Do Nothing when Lid is Closed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/990908/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1180513] Re: lid close actions are ignored laptop always suspends
That's actually a bit surprising, I thought this was a regression due to the logind transition. But as the effect is the same, I'll make it a duplicate. -- 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/1180513 Title: lid close actions are ignored laptop always suspends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1180513/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189122] Re: google accounts cannot be added in online accounts
*** This bug is a duplicate of bug 1189120 *** https://bugs.launchpad.net/bugs/1189120 ** This bug has been marked a duplicate of bug 1189120 When I try to add a Google account, the site return an error -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1189122 Title: google accounts cannot be added in online accounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1189122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189166] [NEW] Naming newly created folder or document with AltGr key doesn't work as expected
Public bug reported: To reproduce the bug: 1. open nautilus 2. choose New Folder 3. press AltGr key Result: default new folder name (Untitled Folder) is enforced (AltGr works like enter). It should allow to enter special characters instead. If you choose again already created Untitled Folder and than try to rename it, AltGr key works as expected. It seems that only freshly created folders and files are affected. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Sun Jun 9 16:55:13 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1002x515+204+65' b'org.gnome.nautilus.window-state' b'sidebar-width' b'160' InstallationDate: Installed on 2013-05-01 (38 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: alt altgr amd64 apport-bug files folder nautilus new raring third-party-packages ** Description changed: To reproduce the bug: 1. open nautilus 2. choose New Folder 3. press AltGr key Result: default new folder name (Untitled Folder) is enforced (AltGr works like enter). It should allow to enter special characters instead. - If you choose again already created Untitled Folder and than try rename - it, AltGr key works as expected. It seems that only freshly created - folders and files are affected. + If you choose again already created Untitled Folder and than try to + rename it, AltGr key works as expected. It seems that only freshly + created folders and files are affected. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Sun Jun 9 16:55:13 2013 GsettingsChanges: - b'org.gnome.nautilus.window-state' b'geometry' b'1002x515+204+65' - b'org.gnome.nautilus.window-state' b'sidebar-width' b'160' + b'org.gnome.nautilus.window-state' b'geometry' b'1002x515+204+65' + b'org.gnome.nautilus.window-state' b'sidebar-width' b'160' InstallationDate: Installed on 2013-05-01 (38 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1189166 Title: Naming newly created folder or document with AltGr key doesn't work as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1189166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1174313] Re: Account creation window is empty
Sry 4 double Command but i forgot i can only see the abort Button, no done Button. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1174313 Title: Account creation window is empty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1174313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189166] Re: Naming newly created folder or document with AltGr key doesn't work as expected
** Description changed: + Naming newly created folder or document with AltGr key doesn't work as expected. To reproduce the bug: 1. open nautilus 2. choose New Folder 3. press AltGr key Result: default new folder name (Untitled Folder) is enforced (AltGr works like enter). It should allow to enter special characters instead. If you choose again already created Untitled Folder and than try to rename it, AltGr key works as expected. It seems that only freshly created folders and files are affected. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Sun Jun 9 16:55:13 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1002x515+204+65' b'org.gnome.nautilus.window-state' b'sidebar-width' b'160' InstallationDate: Installed on 2013-05-01 (38 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1189166 Title: Naming newly created folder or document with AltGr key doesn't work as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1189166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189169] [NEW] GDM 3.8.1.1 (Saucy) depends on dconf-tools
Public bug reported: As noted here http://ubuntuforums.org/showthread.php?t=2152255 GDM 3.8.1.1 depends on dconf-tools when it should depend on dconf-editor, as dconf-tools is a transitional package, for help installing the new split packages dconf-cli and dconf-editor. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1189169 Title: GDM 3.8.1.1 (Saucy) depends on dconf-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1189169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189169] Re: GDM 3.8.1.1 (Saucy) depends on dconf-tools
Thanks for reporting this bug and helping to make Ubuntu better. According to Debian, gdm actually needs dconf-cli instead: http://anonscm.debian.org/viewvc/pkg-gnome?view=revisionrevision=38363 We'll still have ubuntu-gnome-desktop depend on dconf-editor though. I don't know if Ubuntu itself will continue to include dconf-editor or not by default. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1189169 Title: GDM 3.8.1.1 (Saucy) depends on dconf-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1189169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189169] Re: GDM 3.8.1.1 (Saucy) depends on dconf-tools
** Changed in: gdm (Ubuntu) Importance: Undecided = Low ** Changed in: gdm (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/1189169 Title: GDM 3.8.1.1 (Saucy) depends on dconf-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1189169/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 853994] Re: g-c-c User Accounts should be built with webcam support
Cheese MIR filed at bug 1189180 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/853994 Title: g-c-c User Accounts should be built with webcam support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/853994/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 624076] Re: (gedit:4985): GtkSourceView-WARNING **: Could not find word to remove in buffer...
** Changed in: gtksourceview Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtksourceview2 in Ubuntu. https://bugs.launchpad.net/bugs/624076 Title: (gedit:4985): GtkSourceView-WARNING **: Could not find word to remove in buffer... To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/624076/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1188970] Re: mouse pointer shows wait icon repetitively while leaking memory
==23183== 3,145,783 bytes in 1 blocks are indirectly lost in loss record 21,633 of 21,637 ==23183==at 0x4C2CD7B: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==23183==by 0x8B13CF0: g_malloc (gmem.c:159) ==23183==by 0x5302FC8: gtk_selection_data_set (gtkselection.c:1269) ==23183==by 0x5303E68: gtk_selection_data_set_pixbuf (gtkselection.c:1643) ==23183==by 0x564DC8: gimp_clipboard_send_buffer (gimpclipboard.c:895) ==23183==by 0x868461F: g_closure_invoke (gclosure.c:777) ==23183==by 0x8695EFF: signal_emit_unlocked_R (gsignal.c:3584) ==23183==by 0x869DD10: g_signal_emit_valist (gsignal.c:3328) ==23183==by 0x869E4B8: g_signal_emit_by_name (gsignal.c:3424) ==23183==by 0x530311A: gtk_selection_invoke_handler (gtkselection.c:2986) ==23183==by 0x5304A0E: _gtk_selection_request (gtkselection.c:2391) ==23183==by 0x529D928: _gtk_marshal_BOOLEAN__BOXED (gtkmarshalers.c:86) ==23183== ==23183== 3,686,059 (540,276 direct, 3,145,783 indirect) bytes in 1 blocks are definitely lost in loss record 21,634 of 21,637 ==23183==at 0x4C2ABB4: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==23183==by 0x103A9C42: ??? ==23183==by 0x103AA31F: ??? ==23183==by 0x8138C04: babl_extension_load_dir_list (in /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0.109.1) ==23183==by 0x7B80FAE: gegl_post_parse_hook (gegl-init.c:520) ==23183==by 0x8B196C7: g_option_context_parse (goption.c:2009) ==23183==by 0x481691: main (main.c:396) ==23183== ==23183== 4,323,201 bytes in 298 blocks are possibly lost in loss record 21,635 of 21,637 ==23183==at 0x4C2CD7B: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==23183==by 0x8B13CF0: g_malloc (gmem.c:159) ==23183==by 0x787C24: temp_buf_new (temp-buf.c:67) ==23183==by 0x696D67: gimp_brush_load_brush (gimpbrush-load.c:296) ==23183==by 0x69D7FE: gimp_brush_pipe_load (gimpbrushpipe-load.c:213) ==23183==by 0x6B6B70: gimp_data_factory_load_data (gimpdatafactory.c:878) ==23183==by 0x68F6128: gimp_datafiles_read_directories (gimpdatafiles.c:130) ==23183==by 0x6B6A34: gimp_data_factory_load_data_recursive (gimpdatafactory.c:816) ==23183==by 0x68F6128: gimp_datafiles_read_directories (gimpdatafiles.c:130) ==23183==by 0x6B6985: gimp_data_factory_data_load (gimpdatafactory.c:358) ==23183==by 0x6B74AC: gimp_data_factory_data_init (gimpdatafactory.c:239) ==23183==by 0x68BFE4: gimp_restore (gimp.c:952) ==23183== ==23183== 1,338,746,784 bytes in 400 blocks are definitely lost in loss record 21,636 of 21,637 ==23183==at 0x4C2CD7B: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==23183==by 0x8B13CF0: g_malloc (gmem.c:159) ==23183==by 0x5302FC8: gtk_selection_data_set (gtkselection.c:1269) ==23183==by 0x5303E68: gtk_selection_data_set_pixbuf (gtkselection.c:1643) ==23183==by 0x564DC8: gimp_clipboard_send_buffer (gimpclipboard.c:895) ==23183==by 0x868461F: g_closure_invoke (gclosure.c:777) ==23183==by 0x8695EFF: signal_emit_unlocked_R (gsignal.c:3584) ==23183==by 0x869DD10: g_signal_emit_valist (gsignal.c:3328) ==23183==by 0x869E4B8: g_signal_emit_by_name (gsignal.c:3424) ==23183==by 0x530311A: gtk_selection_invoke_handler (gtkselection.c:2986) ==23183==by 0x5304A0E: _gtk_selection_request (gtkselection.c:2391) ==23183==by 0x529D928: _gtk_marshal_BOOLEAN__BOXED (gtkmarshalers.c:86) ==23183== ==23183== 3,223,406,980 bytes in 940 blocks are possibly lost in loss record 21,637 of 21,637 ==23183==at 0x4C2CD7B: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==23183==by 0x8B13CF0: g_malloc (gmem.c:159) ==23183==by 0x5302FC8: gtk_selection_data_set (gtkselection.c:1269) ==23183==by 0x5303E68: gtk_selection_data_set_pixbuf (gtkselection.c:1643) ==23183==by 0x564DC8: gimp_clipboard_send_buffer (gimpclipboard.c:895) ==23183==by 0x868461F: g_closure_invoke (gclosure.c:777) ==23183==by 0x8695EFF: signal_emit_unlocked_R (gsignal.c:3584) ==23183==by 0x869DD10: g_signal_emit_valist (gsignal.c:3328) ==23183==by 0x869E4B8: g_signal_emit_by_name (gsignal.c:3424) ==23183==by 0x530311A: gtk_selection_invoke_handler (gtkselection.c:2986) ==23183==by 0x5304A0E: _gtk_selection_request (gtkselection.c:2391) ==23183==by 0x529D928: _gtk_marshal_BOOLEAN__BOXED (gtkmarshalers.c:86) ==23183== ==23183== LEAK SUMMARY: ==23183==definitely lost: 1,339,420,631 bytes in 2,085 blocks ==23183==indirectly lost: 3,225,583 bytes in 3,718 blocks ==23183== possibly lost: 3,251,798,234 bytes in 69,592 blocks ==23183==still reachable: 6,079,382 bytes in 29,012 blocks ==23183== suppressed: 0 bytes in 0 blocks ==23183== ==23183== For counts of detected and suppressed errors, rerun with: -v ==23183== Use --track-origins=yes to see where uninitialised values come from ==23183== ERROR SUMMARY: 12975 errors from 8244 contexts (suppressed:
Re: [Bug 580961] Re: unzip fails to deal correctly with filename encodings
ppa has only raring version of packages, not precise/quantal 2013/6/8 robert leleu robert.jean.le...@wanadoo.fr didn't work for me here is the end of the update cmd Lecture des listes de paquets... Fait W: Une erreur s'est produite lors du contrôle de la signature. Le dépôt n'est pas mis à jour et les fichiers d'index précédents seront utilisés. Erreur de GPG : http://ppa.launchpad.net quantal Release : Les signatures suivantes ne sont pas valables : BADSIG B22A95F88110A93A Launchpad PPA for Bumlebee Project W: Impossible de récupérer http://ppa.launchpad.net/bumblebee/stable/ubuntu/dists/quantal/Release W: Impossible de récupérer http://ppa.launchpad.net/md-xytop/unzip/ubuntu/dists/quantal/main/source/Sources 404 Not Found W: Impossible de récupérer http://ppa.launchpad.net/md-xytop/unzip/ubuntu/dists/quantal/main/binary-amd64/Packages 404 Not Found W: Impossible de récupérer http://ppa.launchpad.net/md-xytop/unzip/ubuntu/dists/quantal/main/binary-i386/Packages 404 Not Found W: Le téléchargement de quelques fichiers d'index a échoué, ils ont été ignorés, ou les anciens ont été utilisés à la place. la 07/06/2013 23:22, Vitaly skribis (esperanto estas la unua internacia lingvo) And here is ppa with fixed unzip: https://launchpad.net/~md-xytop/+archive/unzip -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings Status in File Roller: Confirmed Status in The Linux Mint Distribution: Triaged Status in Ubuntu Japanese Kaizen Project: Fix Committed Status in unzip - free software .zip unarchiver: Unknown Status in “unzip” package in Ubuntu: Triaged Status in “unzip” source package in Natty: Won't Fix Status in “unzip” package in Debian: Confirmed Status in Gentoo Linux: Won't Fix Status in “unzip” package in Mandriva: Unknown Status in “unzip” package in openSUSE: Fix Released Bug description: Binary package hint: unzip This is a fairly annoying bug that's been around and known at least since 2005. It's very visible as it will very often make exchange of zip files with Windows users impossible, for example. As such, it gathered it's fair share of me too and how dare you haven't fixed this yet!!111! comments. Problem description: zip/unzip and the specification fall short when dealing with non-ASCII filenames not encoded in UTF-8 test case: do an unzip -l on the file http://tinyurl.com/2aofpxs and witness the question marks affected programs: the problem is in unzip itself, but affects GUI like xarchiver, file-roller, etc. that rely on unzip for the decompression suggested solutions (most are workarounds, not proper fixes): a) reintroduce patch for codepage-based zip filenames: bug 477755, http://tinyurl.com/2aqdbqg (Ubuntu blueprint) b) unzip filename according to locale: bug 203609 c) Ubuntu JP has a patch, probably not generally applicable, bug 269482 d) Russian altlinux distro uses natspec lib and patched zip binary natspec was mentioned in bug 477755 comment #2 and may indeed be a proper fix, needs closer inspection (I haven't really looked, yet. As discussed in https://bugzilla.gnome.org/show_bug.cgi?id=306403 there is no failsafe, straight-forward way to fix this in all cases. Nonetheless, the current situation can and should be improved. There's some good ideas floating around. It needs somebody to pull and wrap them together. It's unfortunate the FOSS community so far hasn't been able to fix this rather visible problem. I'm opening this ticket as a master bug and clean slate to document the issue and current status. Please don't ruin it by making above-mentioned unhelpful comments, they actually slow things down! Please don't nominate for a release. Unless you're a dev and can provide a patch, you should think VERY carefully to do anything but 1) subscribe yourself to this ticket 2) mark this bug as affecting you 3) tell me via mail about other bugs you think are a duplicate of this one, discussing the same problem 1) to 3) will showcase to the devs how many people are affected and that is the only real chance we have for somebody to take a serious look. Me too comments do the opposite, so again, please don't do it. To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/580961/+subscriptions -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (34667). https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/580961/+subscriptions -- desktop-bugs mailing list
[Bug 157306] Re: greyed options in right click context menu
** Changed in: nautilus Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/157306 Title: greyed options in right click context menu To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/157306/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 987986] Re: Cannot browse files via bluetooth on Android device
Still not resolved??? Kamil, are you working on it??? This bug is a bug bummer for an OS that's trying to take over desktops/laptops. -vg -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/987986 Title: Cannot browse files via bluetooth on Android device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/987986/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580961] Re: unzip fails to deal correctly with filename encodings
thanks the raring ppa worked for my mint 14 (quantal?) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (34667). https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/580961/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 951916] Re: gnome-sudoku crashed with ImportError in /usr/lib/python2.7/dist-packages/gnome_sudoku/main.py: cannot import name LaunchpadIntegration
Installing gir1.2-launchpad-integration-3.0 allows gnome-sudoku to start on Ubuntu 12.04. python-launchpad-integration wasn't sufficient. Even ubuntu-desktop doesn't include gir1.2-launchpad-integration-3.0 in its dependency chain, only a Recommends via software-center. Anyway, either add the dependency or change the patched-in code in main.py to omit that menu item if the library can't be imported. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-games in Ubuntu. https://bugs.launchpad.net/bugs/951916 Title: gnome-sudoku crashed with ImportError in /usr/lib/python2.7/dist- packages/gnome_sudoku/main.py: cannot import name LaunchpadIntegration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/951916/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1180513] Re: lid close actions are ignored laptop always suspends
Martin, thanks for looking into this. By the way, is gnome-settings- daemon 3.8 expected to land in Saucy? -- 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/1180513 Title: lid close actions are ignored laptop always suspends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1180513/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 951916] Re: gnome-sudoku missing dependency for patched-in LaunchpadIntegration. Won't run.
** Summary changed: - gnome-sudoku crashed with ImportError in /usr/lib/python2.7/dist-packages/gnome_sudoku/main.py: cannot import name LaunchpadIntegration + gnome-sudoku missing dependency for patched-in LaunchpadIntegration. Won't run. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-games in Ubuntu. https://bugs.launchpad.net/bugs/951916 Title: gnome-sudoku missing dependency for patched-in LaunchpadIntegration. Won't run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/951916/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1075196] Re: Rhythmbox never starts minimized
** Description changed: Hi! I'm on Quantal (12.10). What I expected: - If I lunch rhythmbox (2.97-1ubuntu6) from Dash, from Alt+F2, from terminal ecc it should show the main window. + If I launch rhythmbox (2.97-1ubuntu6) from Dash, from Alt+F2, from terminal ecc it should show the main window. If i start it from the sound menu (by clicking the Play button, not the application name) it should start and start playing without showing me the main window. What I obtain: - There's no actually a way to start rhythmbox minimized. + There's no actual way to start rhythmbox minimized. In old versions there was an option --hide to launch it without showing the main window. In newer versions there should be a gsetting key that remember the last state (minimized, normal, maximized). In the last verion it's simply impossible to launch it minimized. Way to replicate this: Open rhythmbox, then closed it (Ctrl+Q), then push Play in sound Menu. It does not start playing and, instead show the main window. -- 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/1075196 Title: Rhythmbox never starts minimized To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1075196/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1099550] Re: gvfsd-archive crashed with SIGSEGV in mount_failed()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1099550 Title: gvfsd-archive crashed with SIGSEGV in mount_failed() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1099550/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164855] Re: evolution-calendar-factory crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 1154822 *** https://bugs.launchpad.net/bugs/1154822 ** This bug has been marked a duplicate of bug 1154822 evolution-calendar-factory crashed with SIGABRT: double free or corruption -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1164855 Title: evolution-calendar-factory crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1164855/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1165195] Re: evolution-calendar-factory crashed with SIGABRT in raise()
*** This bug is a duplicate of bug 1154822 *** https://bugs.launchpad.net/bugs/1154822 ** This bug has been marked a duplicate of bug 1154822 evolution-calendar-factory crashed with SIGABRT: double free or corruption -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1165195 Title: evolution-calendar-factory crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1165195/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1170647] Re: Nautilus opens new window instead of restoring the minimized window
Just now I noticed that with directories mounted on /media (via a direct invokation of udisks in a script) nautilus works as expected. Well, at least for me, at least right now. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1170647 Title: Nautilus opens new window instead of restoring the minimized window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1170647/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1176885] Re: Nautilus opened as root user crashes when trying to view properties of file/folder owned by normal user: ERROR:nautilus-properties-window.c:1836:schedule_owner_change_timeout: asse
** Changed in: nautilus Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1176885 Title: Nautilus opened as root user crashes when trying to view properties of file/folder owned by normal user: ERROR:nautilus-properties- window.c:1836:schedule_owner_change_timeout: assertion failed: (NAUTILUS_IS_FILE (file)) To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1176885/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 723001] Re: no screensaver capability
The aforementioned links are now obsolete. The page is at https://help.ubuntu.com/community/Photos/Slideshows. ** Description changed: Binary package hint: shotwell - Obviously there is screensaver capability else this bug would have been reported now, but at the least there is something missing from the documentation that needs to be fixed to instruct me better how to get it working. + https://help.ubuntu.com/community/Photos/Slideshows + + Obviously there is screensaver capability; else, this bug would have + been reported now, but at the least there is something missing from the + documentation that needs to be fixed to instruct me better how to get it + working. + Using Shotwell 0.7.2 under Ubuntu 10.10. Documentation says to select the Shotwell Photos screensaver theme under System-Preferences-Screensaver. This option is not available (though F-spot photos and Pictures folder are). Documentation also says in order to change the tag used for the screensaver to select screensaver under edit-preferences in Shotwell. There is no screensaver tab, button or option (only display, library location and external editors) - See attached screenshots. + + *See attached screenshots. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: shotwell 0.7.2-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic i686 Architecture: i386 Date: Tue Feb 22 10:11:56 2011 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1) ProcEnviron: - LANG=en_US.utf8 - SHELL=/bin/bash + LANG=en_US.utf8 + SHELL=/bin/bash SourcePackage: shotwell ** Tags removed: apport-bug i386 maverick ** Tags added: wiki -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/723001 Title: no screensaver capability To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/723001/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 723001] Re: no screensaver capability
The only possible method of picture screensavers is F-spot, not Shotwell. It still seems a screensaver feature for Shotwell hasn't been implemented to this day. ** Changed in: ubuntu-docs (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/723001 Title: no screensaver capability To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/723001/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 310231] Re: Error cannot parse incoming data when browing or pushing files
This bug still exist and just like for sparrowt: this is triggered by character in the file name. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/310231 Title: Error cannot parse incoming data when browing or pushing files To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/310231/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 907452] Re: Shouldn't let you desactivate the only admin user
** Changed in: gnome-control-center Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/907452 Title: Shouldn't let you desactivate the only admin user To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/907452/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 424956] Re: nautilus crashed with SIGABRT in raise()
I was accesing files on an Iphone via USB and got this crash. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/424956 Title: nautilus crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/424956/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189318] [NEW] xchat-gnome crashed with SIGSEGV in gtk_xtext_append_indent()
Public bug reported: Don't know what this crash is about. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xchat-gnome 1:0.30.0~git20110821.e2a400-0.2ubuntu8 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 CrashCounter: 1 Date: Sun Jun 9 23:32:04 2013 ExecutablePath: /usr/bin/xchat-gnome InstallationDate: Installed on 2013-04-25 (45 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: xchat-gnome SegvAnalysis: Segfault happened at: 0x440753 gtk_xtext_append_indent+195: mov (%r15),%rdi PC (0x00440753) ok source (%r15) (0x636172726f62206f) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: xchat-gnome StacktraceTop: gtk_xtext_append_indent () ?? () conversation_panel_print () fe_print_text () PrintText () Title: xchat-gnome crashed with SIGSEGV in gtk_xtext_append_indent() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: xchat-gnome (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace raring ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1189318 Title: xchat-gnome crashed with SIGSEGV in gtk_xtext_append_indent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1189318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189317] [NEW] xchat-gnome crashed with SIGSEGV in g_object_newv()
*** This bug is a duplicate of bug 1155798 *** https://bugs.launchpad.net/bugs/1155798 Public bug reported: Some chat-rooms opened and this crash happened. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xchat-gnome 1:0.30.0~git20110821.e2a400-0.2ubuntu8 ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13 Uname: Linux 3.8.0-25-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Sun Jun 9 23:28:39 2013 ExecutablePath: /usr/bin/xchat-gnome InstallationDate: Installed on 2013-04-25 (45 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: xchat-gnome SegvAnalysis: Segfault happened at: 0x7f1b2cb1cadb g_object_newv+139: mov 0x8(%rax),%r13 PC (0x7f1b2cb1cadb) ok source 0x8(%rax) (0x2073616c6c697469) not located in a known VMA region (needed readable region)! destination %r13 ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: xchat-gnome StacktraceTop: g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: xchat-gnome crashed with SIGSEGV in g_object_newv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: xchat-gnome (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash raring ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1189317 Title: xchat-gnome crashed with SIGSEGV in g_object_newv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1189317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189317] Re: xchat-gnome crashed with SIGSEGV in g_object_newv()
*** This bug is a duplicate of bug 1155798 *** https://bugs.launchpad.net/bugs/1155798 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1155798, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1189317/+attachment/3699465/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1189317/+attachment/3699467/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1189317/+attachment/3699469/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1189317/+attachment/3699470/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1189317/+attachment/3699471/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1189317/+attachment/3699472/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1189317/+attachment/3699473/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1155798 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1189317 Title: xchat-gnome crashed with SIGSEGV in g_object_newv() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1189317/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1189318] Re: xchat-gnome crashed with SIGSEGV in gtk_xtext_append_indent()
*** This bug is a duplicate of bug 970867 *** https://bugs.launchpad.net/bugs/970867 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #970867, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1189318/+attachment/3699475/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1189318/+attachment/3699477/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1189318/+attachment/3699479/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1189318/+attachment/3699480/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1189318/+attachment/3699481/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1189318/+attachment/3699482/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1189318/+attachment/3699483/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 970867 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to xchat-gnome in Ubuntu. https://bugs.launchpad.net/bugs/1189318 Title: xchat-gnome crashed with SIGSEGV in gtk_xtext_append_indent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xchat-gnome/+bug/1189318/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
** Branch linked: lp:~robert-ancell/lightdm/xauth-no-g_file_set_contents -- 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/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1180513] Re: lid close actions are ignored laptop always suspends
Adam Dingle [2013-06-09 22:48 -]: By the way, is gnome-settings- daemon 3.8 expected to land in Saucy? I asked Sebastien; if the desktop team gets around to it, yes, but updating to it requires updating of a whole lot of other components, and that's not the focus for this cycle. -- 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/1180513 Title: lid close actions are ignored laptop always suspends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1180513/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 951916] Re: gnome-sudoku missing dependency for patched-in LaunchpadIntegration. Won't run.
The lpi patch is gone from gnome-games's source tree in Saucy, so at some point this bug disappeared. It still affects 12.04 LTS, but won't affect future releases. ** Changed in: gnome-games (Ubuntu) Status: New = Confirmed ** Summary changed: - gnome-sudoku missing dependency for patched-in LaunchpadIntegration. Won't run. + gnome-sudoku missing dependency for patched-in LaunchpadIntegration. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-games in Ubuntu. https://bugs.launchpad.net/bugs/951916 Title: gnome-sudoku missing dependency for patched-in LaunchpadIntegration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/951916/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 984785] Re: .goutputstream files polluting $HOME
Fix committed into lp:lightdm at revision 1675, scheduled for release in lightdm, milestone Unknown ** Changed in: lightdm Status: Triaged = Fix Committed -- 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/984785 Title: .goutputstream files polluting $HOME To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 951916] Re: gnome-sudoku missing dependency for patched-in LaunchpadIntegration.
I updated the title again, the won't run part of the bug description is the symptom if you hit this bug, but that only happens when you either install gnome-sudoku on a lean install that doesn't include the recommends: packages of ubuntu-desktop, or if you strip stuff out of a desktop install. A kubuntu-desktop doesn't pull in gir1.2-launchpad-integration-3.0, even with recommends, so installing this on a default kubuntu system would fail. I didn't want to raise undue alarm about it not working out of the box for most people, since it's fixed for later releases anyway. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-games in Ubuntu. https://bugs.launchpad.net/bugs/951916 Title: gnome-sudoku missing dependency for patched-in LaunchpadIntegration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/951916/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
