[Desktop-packages] [Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]
Hi, I added Eoan series to the bug report as it hasn't been fixed there. (The bug had been automatically marked as Fix Released after the Focal update) ** Also affects: mutter (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Focal) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Also affects: gnome-shell (Ubuntu Focal) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Won't Fix ** Changed in: mutter (Ubuntu Eoan) Status: New => Triaged ** Changed in: gnome-shell (Ubuntu Eoan) Status: New => Won't Fix ** Changed in: mutter (Ubuntu Eoan) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1848119 Title: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in gnome-shell source package in Eoan: Won't Fix Status in mutter source package in Eoan: Triaged Status in gnome-shell source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Released Status in gnome-shell package in Fedora: Confirmed Bug description: [ Impact ] Gnome shell fills the journal with errors as soon as a view is closed from the overview Ubuntu 19.10 on Xorg gnome-shell 3.34.1-1ubuntu1 [ Test case ] 1) Open terminal and watch journalct -f /usr/bin/gnome-shell 2) Open a window (i.e Files) 3) Close Files in the activities overview 4) gnome-shell spanws errors in the journal. Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 0x55aead0b5360 == Oct 14 23:25:38 titan gnome-shell[9919]: #0 55aeae6f3910 i resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15) Oct 14 23:25:38 titan gnome-shell[9919]: #1 7ffd96c5e360 b self-hosted:975 (7f438c12dee0 @ 392) [ Regression potential ] Key focus might not work properly in some shell elements, in particular the focus be owned by multiple actors or by none of them. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 767040] Re: Firefox doesn't use overlay scrollbars
This is not considered a bug because overlay scrollbars are gone, they are not used in Ubuntu anymore, and therefore cannot be applied to Firefox. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/767040 Title: Firefox doesn't use overlay scrollbars Status in Mozilla Firefox: Won't Fix Status in overlay-scrollbar: Won't Fix Status in firefox package in Ubuntu: Won't Fix Bug description: Binary package hint: firefox The Firefox 4 browser in 11.04 doesn't use Unitys scrollbars (the light ones with the up/down button showing as soon as you move the mouse pointer over it). Instead, it uses standard scrollbars. I believe this is an inconsistency in the UI, as other programs (e.g. Nautilus) show them correctly. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: firefox 4.0+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: nvidia wl Architecture: i386 Date: Wed Apr 20 12:55:44 2011 EcryptfsInUse: Yes FirefoxPackages: firefox 4.0+nobinonly-0ubuntu3 flashplugin-installer 10.2.159.1ubuntu1 adobe-flashplugin N/A icedtea-plugin 1.1~20110406-0ubuntu2 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330) ProcEnviron: LANGUAGE=de:C:en LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/767040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1339607] Re: Unencrypted private keys are insecure message is vague and unhelpful
Actually, I was wrong. Forget my last message. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1339607 Title: Unencrypted private keys are insecure message is vague and unhelpful Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Set up a wireless connection with WPA security and an unencrypted private key. 2. Make sure Network Manager will connect as soon as the wireless network is available. 2. Reboot the computer. What happens: Network manager will connect to the network during boot. If it completes before login, you are presented with the following message: Unencrypted private keys are insecure The selected private key does not appear to be protected by a password. This could allow your security credentials to be compromised. Please select a password-protected private key. (You can password-protect your private key with openssl) This message is really uninformative and unhelpful for many reasons: * It does not tell me which program/key is the problem. Initially I though that the problem had to do with one of my SSH keys. I had to grep the message in /usr/bin in order to understand who was showing it. * It does not tell why exactly unencrypted keys are insecure. In fact, someone might say they aren't. * It does not tell how to encrypt them. You can password-protect your private key with openssl does not mean anything, even to a person who knows what OpenSSL is. TL;DR: you are warned about a problem which does not exist, without being told what it is and how to solve it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.8-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.13.0-31.55-generic 3.13.11.4 Uname: Linux 3.13.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 9 10:51:28 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-23 (258 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.169.169.254 dev wlan0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 10.169.169.0/24 dev wlan0 proto kernel scope link src 10.169.169.100 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager-applet UpgradeStatus: Upgraded to trusty on 2014-03-25 (105 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1339607/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1339607] Re: Unencrypted private keys are insecure message is vague and unhelpful
This message is no longer appearing since I upgraded to vivid. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1339607 Title: Unencrypted private keys are insecure message is vague and unhelpful Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Set up a wireless connection with WPA security and an unencrypted private key. 2. Make sure Network Manager will connect as soon as the wireless network is available. 2. Reboot the computer. What happens: Network manager will connect to the network during boot. If it completes before login, you are presented with the following message: Unencrypted private keys are insecure The selected private key does not appear to be protected by a password. This could allow your security credentials to be compromised. Please select a password-protected private key. (You can password-protect your private key with openssl) This message is really uninformative and unhelpful for many reasons: * It does not tell me which program/key is the problem. Initially I though that the problem had to do with one of my SSH keys. I had to grep the message in /usr/bin in order to understand who was showing it. * It does not tell why exactly unencrypted keys are insecure. In fact, someone might say they aren't. * It does not tell how to encrypt them. You can password-protect your private key with openssl does not mean anything, even to a person who knows what OpenSSL is. TL;DR: you are warned about a problem which does not exist, without being told what it is and how to solve it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.8-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.13.0-31.55-generic 3.13.11.4 Uname: Linux 3.13.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 9 10:51:28 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-23 (258 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.169.169.254 dev wlan0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 10.169.169.0/24 dev wlan0 proto kernel scope link src 10.169.169.100 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager-applet UpgradeStatus: Upgraded to trusty on 2014-03-25 (105 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1339607/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1339607] [NEW] Unencrypted private keys are insecure message is vague and unhelpful
Public bug reported: Steps to reproduce: 1. Set up a wireless connection with WPA security and an unencrypted private key. 2. Make sure Network Manager will connect as soon as the wireless network is available. 2. Reboot the computer. What happens: Network manager will connect to the network during boot. If it completes before login, you are presented with the following message: Unencrypted private keys are insecure The selected private key does not appear to be protected by a password. This could allow your security credentials to be compromised. Please select a password-protected private key. (You can password-protect your private key with openssl) This message is really uninformative and unhelpful for many reasons: * It does not tell me which program/key is the problem. Initially I though that the problem had to do with one of my SSH keys. I had to grep the message in /usr/bin in order to understand who was showing it. * It does not tell why exactly unencrypted keys are insecure. In fact, someone might say they aren't. * It does not tell how to encrypt them. You can password-protect your private key with openssl does not mean anything, even to a person who knows what OpenSSL is. TL;DR: you are warned about a problem which does not exist, without being told what it is and how to solve it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.8-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.13.0-31.55-generic 3.13.11.4 Uname: Linux 3.13.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 9 10:51:28 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-23 (258 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) IpRoute: default via 10.169.169.254 dev wlan0 proto static 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 10.169.169.0/24 dev wlan0 proto kernel scope link src 10.169.169.100 metric 9 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager-applet UpgradeStatus: Upgraded to trusty on 2014-03-25 (105 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1339607 Title: Unencrypted private keys are insecure message is vague and unhelpful Status in “network-manager-applet” package in Ubuntu: New Bug description: Steps to reproduce: 1. Set up a wireless connection with WPA security and an unencrypted private key. 2. Make sure Network Manager will connect as soon as the wireless network is available. 2. Reboot the computer. What happens: Network manager will connect to the network during boot. If it completes before login, you are presented with the following message: Unencrypted private keys are insecure The selected private key does not appear to be protected by a password. This could allow your security credentials to be compromised. Please select a password-protected private key. (You can password-protect your private key with openssl) This message is really uninformative and unhelpful for many reasons: * It does not tell me which program/key is the problem. Initially I though that the problem had to do with one of my SSH keys. I had to grep the message in /usr/bin in order to understand who was showing it. * It does not tell why exactly unencrypted keys are insecure. In fact, someone might say they aren't. * It does not tell how to encrypt them. You can password-protect your private key with openssl does not mean anything, even to a person who knows what OpenSSL is. TL;DR: you are warned about a problem which does not exist, without being told what it is and how to solve it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.8-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.13.0-31.55-generic 3.13.11.4 Uname: Linux 3.13.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jul 9
[Desktop-packages] [Bug 1164036] Re: Software Center Paypal empty page
** Also affects: software-center Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1164036 Title: Software Center Paypal empty page Status in Ubuntu Software Center: New Status in “software-center” package in Ubuntu: Confirmed Bug description: Hi! When i try to buy a software with PayPal, the Go button does not work or it redirect me to an empty page. OS: Xubuntu (12.04) LTS To manage notifications about this bug go to: https://bugs.launchpad.net/software-center/+bug/1164036/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 983449] Re: [Upstream] LibreOffice clears clipboard contents on exit
*** This bug is a duplicate of bug 11334 *** https://bugs.launchpad.net/bugs/11334 ** This bug has been marked a duplicate of bug 11334 MASTER Copy-Paste doesn't work if the source is closed before the paste -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/983449 Title: [Upstream] LibreOffice clears clipboard contents on exit Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 1) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.3-0ubuntu1 Candidate: 1:3.5.3-0ubuntu1 Version table: *** 1:3.5.3-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.5.2-2ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages apt-cache policy gedit gedit: Installed: 3.4.1-0ubuntu1 Candidate: 3.4.1-0ubuntu1 Version table: *** 3.4.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in a blank Writer document is type hello, copy, close Writer, and attempt to paste in gedit and it does. However, one may perform the same action in reverse successfully. WORKAROUND: Copy and paste before closing LibreOffice. WORKAROUND: https://wiki.ubuntu.com/ClipboardPersistence#Workaround:_Clipboard_Managers ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14 Uname: Linux 3.2.0-23-generic-pae i686 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu1 Architecture: i386 Date: Mon Apr 16 21:18:14 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) ProcEnviron: LANGUAGE=en_IE:en TERM=xterm PATH=(custom, no user) LANG=en_IE.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/983449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1186676] Re: gksu handles quoted strings wrongly
** Description changed: + Reported upstream: https://savannah.nongnu.org/bugs/index.php?40023 + To reproduce (based on http://askubuntu.com/a/288506/10371): Compare the first five commands: echo 'foo\ bar' sudo echo 'foo\ bar' gksudo -- echo 'foo\ bar' gksudo --su-mode -- echo 'foo\ bar' gksu --sudo-mode -- echo 'foo\ bar' To this: gksu -- echo 'foo\ bar' The last command prints foo bar rather than foo\ bar (excluding the quotes). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gksu 2.0.2-6ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun Jun 2 09:35:52 2013 InstallationDate: Installed on 2012-06-22 (344 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: gksu UpgradeStatus: Upgraded to raring on 2013-05-04 (28 days ago) ** Changed in: gksu (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gksu in Ubuntu. https://bugs.launchpad.net/bugs/1186676 Title: gksu handles quoted strings wrongly Status in “gksu” package in Ubuntu: Triaged Bug description: Reported upstream: https://savannah.nongnu.org/bugs/index.php?40023 To reproduce (based on http://askubuntu.com/a/288506/10371): Compare the first five commands: echo 'foo\ bar' sudo echo 'foo\ bar' gksudo -- echo 'foo\ bar' gksudo --su-mode -- echo 'foo\ bar' gksu --sudo-mode -- echo 'foo\ bar' To this: gksu -- echo 'foo\ bar' The last command prints foo bar rather than foo\ bar (excluding the quotes). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gksu 2.0.2-6ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-22.33-generic 3.8.11 Uname: Linux 3.8.0-22-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Sun Jun 2 09:35:52 2013 InstallationDate: Installed on 2012-06-22 (344 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: gksu UpgradeStatus: Upgraded to raring on 2013-05-04 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1186676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1206624] Re: Typo in a fortune
** Tags removed: patch-forwarded-debian ** Tags added: patch-accepted-debian -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fortune-mod in Ubuntu. https://bugs.launchpad.net/bugs/1206624 Title: Typo in a fortune Status in “fortune-mod” package in Ubuntu: Triaged Status in “fortune-mod” package in Debian: Fix Committed Bug description: emnity instead of enmity in a fortune; patch attached. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fortunes 1:1.99.1-4 ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46 Uname: Linux 3.2.0-49-generic i686 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: i386 Date: Tue Jul 30 19:57:13 2013 Dependencies: fortunes-min 1:1.99.1-4 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_ZA:en TERM=xterm PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: fortune-mod UpgradeStatus: Upgraded to precise on 2012-06-29 (396 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fortune-mod/+bug/1206624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1206624] Re: Typo in a fortune
Hi and thanks for your contribution. The fortune-mod package is maintained in Debian, and I recommend reporting this bug (and the patch) there. See https://wiki.ubuntu.com/Debian/Bugs for tips on how to do it. ** Changed in: fortune-mod (Ubuntu) Importance: Undecided = Low ** Changed in: fortune-mod (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fortune-mod in Ubuntu. https://bugs.launchpad.net/bugs/1206624 Title: Typo in a fortune Status in “fortune-mod” package in Ubuntu: Triaged Bug description: emnity instead of enmity in a fortune; patch attached. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fortunes 1:1.99.1-4 ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46 Uname: Linux 3.2.0-49-generic i686 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: i386 Date: Tue Jul 30 19:57:13 2013 Dependencies: fortunes-min 1:1.99.1-4 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_ZA:en TERM=xterm PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: fortune-mod UpgradeStatus: Upgraded to precise on 2012-06-29 (396 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fortune-mod/+bug/1206624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1206624] Re: Typo in a fortune
** Bug watch added: Debian Bug tracker #718361 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718361 ** Also affects: fortune-mod (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718361 Importance: Unknown Status: Unknown ** Tags added: patch patch-forwarded-debian ** Tags removed: running-unity ** Tags added: bitesize -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fortune-mod in Ubuntu. https://bugs.launchpad.net/bugs/1206624 Title: Typo in a fortune Status in “fortune-mod” package in Ubuntu: Triaged Status in “fortune-mod” package in Debian: Unknown Bug description: emnity instead of enmity in a fortune; patch attached. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fortunes 1:1.99.1-4 ProcVersionSignature: Ubuntu 3.2.0-49.75-generic 3.2.46 Uname: Linux 3.2.0-49-generic i686 ApportVersion: 2.0.1-0ubuntu17.3 Architecture: i386 Date: Tue Jul 30 19:57:13 2013 Dependencies: fortunes-min 1:1.99.1-4 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_ZA:en TERM=xterm PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash SourcePackage: fortune-mod UpgradeStatus: Upgraded to precise on 2012-06-29 (396 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fortune-mod/+bug/1206624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 52654] Re: Evolution will not use GNOME proxy settings of http_proxy environment variable to access Exchange via WebDAV
From the upstream bug [https://bugzilla.gnome.org/show_bug.cgi?id=307589#c25]: evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago. evolution-exchange is now deprecated and not under active development anymore. It is unlikely that there will be any further active development. Closing this report as WONTFIX as part of Bugzilla Housekeeping. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again. ** Changed in: evolution-data-server (Ubuntu) Status: Triaged = Won't Fix ** Changed in: evolution-data-server (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-exchange in Ubuntu. https://bugs.launchpad.net/bugs/52654 Title: Evolution will not use GNOME proxy settings of http_proxy environment variable to access Exchange via WebDAV Status in Evolution Exchange - Exchange Plugin for Exchange: Won't Fix Status in “evolution-data-server” package in Ubuntu: Won't Fix Status in “evolution-exchange” package in Ubuntu: Invalid Bug description: Binary package hint: evolution-exchange Subject line says it all. As far as I know, Evolution does use the Gnome proxy settings for images inside emails, but does not for proxies, and when I tried using the syntax http://proxy.server:port/my.exchange.site/exchange it did not work either. I know that the proxy is working because if I set it in the Gnome proxy settings and then use Places/Connect to Server and use the WebDEV protocl I can connect just fine and browse through my email directories. At first I thought of this as a new feature, but really it is a bug because Evolution, as any GNOME application, should be following GNOME settings for everything, not just selectively choosing what HTTP requests it uses the proxy for. I feel like this would be a one or two line fix in the code, and I would love to use the version of evoloution that supports HTTP proxying properly :) Thanks Misha To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-exchange/+bug/52654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 373170] Re: Easier filter creation
** Changed in: evolution (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned) ** Changed in: evolution (Ubuntu) Status: Triaged = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/373170 Title: Easier filter creation Status in The Evolution Mail Calendaring Tool: Won't Fix Status in “evolution” package in Ubuntu: Won't Fix Bug description: Binary package hint: evolution Currently to create a filter you have two way: 1. Edit - Message Filters; 2. right-click on a message and select Create Rule From Message - Filter based on .* However when you have to create too many filters it is an hard thing to do and it takes too much time. A better way to do that may be this: 1. say that you need to create a filter to move certain mails in an another folder; 2. move the mails to that folder; 3. in the future mails with similar subject, content or headers will be moved automatically in this folder, like Bogofilter or SpamAssassin do. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/373170/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected
Dear Heinz Boettjer, Please refer to https://help.ubuntu.com/community/ReportingBugs for instructions on how to open a new bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected Status in “culmus” package in Ubuntu: Fix Released Status in “fonts-arphic-ukai” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-nanum-coding” package in Ubuntu: Fix Released Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Fix Released Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “culmus” source package in Quantal: Fix Released Status in “fonts-arphic-ukai” source package in Quantal: Fix Released Status in “fonts-arphic-uming” source package in Quantal: Fix Released Status in “fonts-baekmuk” source package in Quantal: Fix Released Status in “fonts-droid” source package in Quantal: Fix Released Status in “fonts-nanum” source package in Quantal: Fix Released Status in “fonts-nanum-coding” source package in Quantal: Fix Released Status in “fonts-sil-andika” source package in Quantal: Fix Released Status in “fonts-tlwg” source package in Quantal: Fix Released Status in “fonts-unfonts-core” source package in Quantal: Fix Released Status in “fonts-unfonts-extra” source package in Quantal: Fix Released Status in “language-selector” source package in Quantal: Fix Released Status in “libreoffice” source package in Quantal: Confirmed Status in “ttf-wqy-zenhei” source package in Quantal: Fix Released Status in “fonts-arphic-ukai” package in Debian: New Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: Fix Released Status in “fonts-droid” package in Debian: Fix Released Status in “fonts-nanum” package in Debian: Fix Released Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: Fix Released Status in “fonts-unfonts-extra” package in Debian: Fix Released Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf, line 11: Having multiple values in test isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf [Test Case] 1) Install the fonts in question 2) Open a terminal 3) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal [Regression Potential] In case of a regression, the font in question can be affected. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/culmus/+bug/1034928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1126760] Re: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup()
** Attachment removed: CoreDump.gz https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1126760/+attachment/3530977/+files/CoreDump.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1126760 Title: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup() Status in “transmission” package in Ubuntu: Confirmed Bug description: Just closing transmission when this happened. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: transmission-gtk 2.76-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Fri Feb 15 15:57:54 2013 ExecutablePath: /usr/bin/transmission-gtk InstallationDate: Installed on 2012-11-06 (101 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcCmdline: transmission-gtk magnet:?xt=urn:btih:7BAB191F959953BF1D763368E0556E34A1910FB5dn=professional+javascript+for+web+developers+3rd+ed+bbstr=1 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff5646bf5a0 curl_multi_cleanup+176: mov %rax,(%rdi) PC (0x7ff5646bf5a0) ok source %rax ok destination (%rdi) (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: transmission StacktraceTop: curl_multi_cleanup () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 ?? () ?? () start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 clone () from /lib/x86_64-linux-gnu/libc.so.6 Title: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup() UpgradeStatus: Upgraded to raring on 2012-11-21 (86 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1126760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1128392] Re: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1128392 Title: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup() Status in “transmission” package in Ubuntu: New Bug description: This happens on quit. No data seems to get corrupted. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: transmission-gtk 2.76-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 CheckboxSubmission: 23d4ad9b5457fd302024f47052e863ca CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Sun Feb 17 21:41:17 2013 ExecutablePath: /usr/bin/transmission-gtk InstallationDate: Installed on 2011-10-17 (489 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True ProcCmdline: transmission-gtk SegvAnalysis: Segfault happened at: 0x7fc64d0515a0 curl_multi_cleanup+176: mov %rax,(%rdi) PC (0x7fc64d0515a0) ok source %rax ok destination (%rdi) (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: transmission StacktraceTop: curl_multi_cleanup () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 ?? () ?? () start_thread (arg=0x7fc63a5f0700) at pthread_create.c:311 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Title: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup() UpgradeStatus: Upgraded to raring on 2013-02-13 (4 days ago) UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1128392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1126760] Re: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup()
*** This bug is a duplicate of bug 1128392 *** https://bugs.launchpad.net/bugs/1128392 Hi Jason and thanks for your report. You have marked this report as public, even if it contained some sensible information, such as the CoreDump (which I have promptly removed) and the ProcCmdline. I'm marking this bug as private, to avoid further disclosure, however it's possible that some web archives have copied and stored the contents of this page. Please, next time do not mark bugs as public if they are not reviewed by a bug triager. Some bug reports (especially the ones with CoreDumps) may contain many sensible information, including email addresses and passwords. ** Information type changed from Public to Private ** This bug has been marked a duplicate of bug 1128392 transmission-gtk crashed with SIGSEGV in curl_multi_cleanup() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1126760 Title: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup() Status in “transmission” package in Ubuntu: Confirmed Bug description: Just closing transmission when this happened. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: transmission-gtk 2.76-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Fri Feb 15 15:57:54 2013 ExecutablePath: /usr/bin/transmission-gtk InstallationDate: Installed on 2012-11-06 (101 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) MarkForUpload: True ProcCmdline: transmission-gtk magnet:?xt=urn:btih:7BAB191F959953BF1D763368E0556E34A1910FB5dn=professional+javascript+for+web+developers+3rd+ed+bbstr=1 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7ff5646bf5a0 curl_multi_cleanup+176: mov %rax,(%rdi) PC (0x7ff5646bf5a0) ok source %rax ok destination (%rdi) (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: transmission StacktraceTop: curl_multi_cleanup () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 ?? () ?? () start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 clone () from /lib/x86_64-linux-gnu/libc.so.6 Title: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup() UpgradeStatus: Upgraded to raring on 2012-11-21 (86 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1126760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1128392] Re: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup()
*** This bug is a duplicate of bug 1124508 *** https://bugs.launchpad.net/bugs/1124508 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1128392 Title: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup() Status in “transmission” package in Ubuntu: Confirmed Bug description: This happens on quit. No data seems to get corrupted. ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: transmission-gtk 2.76-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 CheckboxSubmission: 23d4ad9b5457fd302024f47052e863ca CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Sun Feb 17 21:41:17 2013 ExecutablePath: /usr/bin/transmission-gtk InstallationDate: Installed on 2011-10-17 (489 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True ProcCmdline: transmission-gtk SegvAnalysis: Segfault happened at: 0x7fc64d0515a0 curl_multi_cleanup+176: mov %rax,(%rdi) PC (0x7fc64d0515a0) ok source %rax ok destination (%rdi) (0x) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: transmission StacktraceTop: curl_multi_cleanup () from /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 ?? () ?? () start_thread (arg=0x7fc63a5f0700) at pthread_create.c:311 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Title: transmission-gtk crashed with SIGSEGV in curl_multi_cleanup() UpgradeStatus: Upgraded to raring on 2013-02-13 (4 days ago) UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1128392/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1124508] Re: Transmission crashes on exit [curl_multi_cleanup error]
** Also affects: curl (Ubuntu) Importance: Undecided Status: New ** Changed in: curl (Ubuntu) Status: New = Triaged ** Changed in: curl (Ubuntu) Importance: Undecided = Medium ** Changed in: transmission (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1124508 Title: Transmission crashes on exit [curl_multi_cleanup error] Status in Curl - transfer files with URL syntax: New Status in “curl” package in Ubuntu: Triaged Status in “transmission” package in Ubuntu: Invalid Bug description: Lubuntu 13.04 Transmission 2.76 ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: transmission-gtk 2.76-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 CasperVersion: 1.330 Date: Wed Feb 13 20:51:27 2013 ExecutablePath: /usr/bin/transmission-gtk LiveMediaBuild: Lubuntu 13.04 Raring Ringtail - Alpha i386 (20130213) MarkForUpload: True ProcCmdline: transmission-gtk ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=ru_RU.UTF-8 SHELL=/bin/bash SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: transmission UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/curl/+bug/1124508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1125060] [NEW] Opening 'Settings › Appareance' involves losing workspace size settings
Public bug reported: Steps to reproduce: 1. Set your hsize and vsize to a non default value: gsettings set org.compiz.core:/org/compiz/profiles/unity/plugins/core/ hsize 3 gsettings set org.compiz.core:/org/compiz/profiles/unity/plugins/core/ vsize 3 2. Check that the number of workspaces has increased. 3. Open 'System Settings' and go to 'Appareance': gnome-control-center background 4. Check the number of workspaces. What should happen? Nothing. The workspaces should be still 3×3=9. What happens instead? hsize and vsize are reset to their default value (2×2=4). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 CheckboxSubmission: 23d4ad9b5457fd302024f47052e863ca CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Thu Feb 14 11:26:09 2013 InstallationDate: Installed on 2011-10-17 (485 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to raring on 2013-02-13 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.2-0ubuntu1 indicator-datetime 12.10.3daily13.02.06-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1125060 Title: Opening 'Settings › Appareance' involves losing workspace size settings Status in “gnome-control-center” package in Ubuntu: New Bug description: Steps to reproduce: 1. Set your hsize and vsize to a non default value: gsettings set org.compiz.core:/org/compiz/profiles/unity/plugins/core/ hsize 3 gsettings set org.compiz.core:/org/compiz/profiles/unity/plugins/core/ vsize 3 2. Check that the number of workspaces has increased. 3. Open 'System Settings' and go to 'Appareance': gnome-control-center background 4. Check the number of workspaces. What should happen? Nothing. The workspaces should be still 3×3=9. What happens instead? hsize and vsize are reset to their default value (2×2=4). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 CheckboxSubmission: 23d4ad9b5457fd302024f47052e863ca CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Thu Feb 14 11:26:09 2013 InstallationDate: Installed on 2011-10-17 (485 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to raring on 2013-02-13 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.2-0ubuntu1 indicator-datetime 12.10.3daily13.02.06-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1125060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1125060] Re: Opening 'Settings › Appareance' involves losing workspace size settings
** Package changed: gnome-control-center (Ubuntu) = gnome-control- center-unity (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1125060 Title: Opening 'Settings › Appareance' involves losing workspace size settings Status in “gnome-control-center-unity” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Set your hsize and vsize to a non default value: gsettings set org.compiz.core:/org/compiz/profiles/unity/plugins/core/ hsize 3 gsettings set org.compiz.core:/org/compiz/profiles/unity/plugins/core/ vsize 3 2. Check that the number of workspaces has increased. 3. Open 'System Settings' and go to 'Appareance': gnome-control-center background 4. Check the number of workspaces. What should happen? Nothing. The workspaces should be still 3×3=9. What happens instead? hsize and vsize are reset to their default value (2×2=4). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7 Uname: Linux 3.8.0-6-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 CheckboxSubmission: 23d4ad9b5457fd302024f47052e863ca CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Thu Feb 14 11:26:09 2013 InstallationDate: Installed on 2011-10-17 (485 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to raring on 2013-02-13 (0 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.2-0ubuntu1 indicator-datetime 12.10.3daily13.02.06-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-unity/+bug/1125060/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1103747] Re: Totem could not startup.
** Bug watch added: Red Hat Bugzilla #858538 https://bugzilla.redhat.com/show_bug.cgi?id=858538 ** Also affects: gstreamer1.0 (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=858538 Importance: Unknown Status: Unknown ** No longer affects: gstreamer0.10 (Ubuntu) ** No longer affects: totem (Ubuntu) ** Description changed: + WORKAROUND: + + Remove the Gstreamer cache files: + rm -f ~/.cache/gstreamer-1.0/registry.* + [https://bugzilla.redhat.com/show_bug.cgi?id=858538#c1] + When Launching Totem, it displays a window saying: Totem could not startup. Some necessary plug-ins are missing. Make sure that the program is correctly installed. So I launched it from the terminal in hopes of recieving a more detailed message for reporting and I recieved the following message: lucas@lucas-Inspiron-5520:~$ totem ** (totem:13625): WARNING **: Element 'cluttersink' is missing, verify your installation (totem:13625): Gtk-WARNING **: A floating object was finalized. This means that someone called g_object_unref() on an object that had only a floating reference; the initial floating reference is not owned by anyone and must be removed with g_object_ref_sink(). Additional Information: Ubuntu Release: Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 uname -a: Linux lucas-Inspiron-5520 3.8.0-1-generic #5-Ubuntu SMP Fri Jan 18 15:23:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Package details totem: Installed: 3.6.3-0ubuntu2 Candidate: 3.6.3-0ubuntu2 Version table: *** 3.6.3-0ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status - ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Wed Jan 23 18:03:32 2013 InstallationDate: Installed on 2013-01-16 (7 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to raring on 2013-01-23 (0 days ago) ** Description changed: WORKAROUND: - Remove the Gstreamer cache files: rm -f ~/.cache/gstreamer-1.0/registry.* [https://bugzilla.redhat.com/show_bug.cgi?id=858538#c1] + DESCRIPTION: When Launching Totem, it displays a window saying: - Totem could not startup. - Some necessary plug-ins are missing. Make sure that the program is correctly installed. + Totem could not startup. + Some necessary plug-ins are missing. Make sure that the program is correctly installed. So I launched it from the terminal in hopes of recieving a more detailed message for reporting and I recieved the following message: - lucas@lucas-Inspiron-5520:~$ totem + $ totem - ** (totem:13625): WARNING **: Element 'cluttersink' is missing, verify + ** (totem:13625): WARNING **: Element 'cluttersink' is missing, verify your installation - (totem:13625): Gtk-WARNING **: A floating object was finalized. This means that someone + (totem:13625): Gtk-WARNING **: A floating object was finalized. This means that someone called g_object_unref() on an object that had only a floating reference; the initial floating reference is not owned by anyone and must be removed with g_object_ref_sink(). Additional Information: Ubuntu Release: Description: Ubuntu Raring Ringtail (development branch) Release: 13.04 uname -a: Linux lucas-Inspiron-5520 3.8.0-1-generic #5-Ubuntu SMP Fri Jan 18 15:23:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Package details totem: Installed: 3.6.3-0ubuntu2 Candidate: 3.6.3-0ubuntu2 Version table: *** 3.6.3-0ubuntu2 0 500 http://ca.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Wed Jan 23 18:03:32 2013 InstallationDate: Installed on 2013-01-16 (7 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to raring on 2013-01-23 (0 days ago) ** Changed in: gstreamer1.0 (Ubuntu) Importance: Undecided = High ** Changed in: gstreamer1.0 (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1103747 Title: Totem could not startup. Status in Totem Movie Player: New Status in “gstreamer1.0” package in Ubuntu: Triaged Status in
[Desktop-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
** No longer affects: metacity (Ubuntu Maverick) ** No longer affects: metacity (Ubuntu) ** Changed in: unity-2d Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity 2D: Invalid Status in “light-themes” package in Ubuntu: Fix Released Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
On Thu, Jan 31, 2013 at 10:34 AM, Aleve Sicofante asicofa...@gmail.com wrote: That's why we call it a bug: probably you see the code being correct, but since the behavior isn't, there's something going on and it must be fixed. The grab area in the titlebar has nothing to do with the resizing area (or shouldn't). Please, feel free to report an another bug about that. There is a detailed guide on how you can do that here: https://help.ubuntu.com/community/ReportingBugs It does not make any sense to continue a discussion on an old bug report that is about a totally different issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity 2D: Invalid Status in “light-themes” package in Ubuntu: Fix Released Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
Dear Aleve, Please, do not modify this old bug. You are wasting contributors' time. As John Lea has already pointed out, the issue you are describing has already been reported as bug #717444. The reason why this bug should remain closed is that a fix has already been written for it. If you are still affected by the bug, then the root cause may be totally different. 'Symptoms' and 'causes' are totally different concepts, and for the propuse of this bug tracker we only look at causes (because we fix the causes, not the symptoms). I'm sorry that you are having difficulties, but this is not the right place to discuss. ** Changed in: unity Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in Unity 2D: Invalid Status in “light-themes” package in Ubuntu: Fix Released Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default thickness should still be increased considerably). Ideally all windows would also have a resize handle but I realize that these have to be application controlled (at least that seems to be the position of the metacity team). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/160311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 160311] Re: Resizing windows by grabbing window borders is difficult
If I understand this bug's description correctly, this problem exists in Unity-2D on Ubuntu 12.04 Precise Pangolin. This is an LTS release - according to https://wiki.ubuntu.com/Releases it will be supported on both the desktop and the server until April 2017. This should mean fully and wholly supported, not partly supported. That's true, but 'supported' means security and severe bug fixes only. See https://wiki.ubuntu.com/StableReleaseUpdates#When for more information. I also disagree with marking this bug's unity-2d task as Invalid while the upstream GNOME bug is still open Also, you should note that the situation in the GNOME bug is a bit different. Firstly, there is no consensus on whether Metacity or the theme(s) should be fixed. Secondly, whilist Metacity has not been deprecated (AFAIK), it is no longer the development focus of GNOME. In fact, the last comment made by a developer was made on 2011-01-10. as this implies that even if GNOME were to develop and deploy a fix, Ubuntu would not adopt the fix. I removed the metacity task just to make it clear that this bug is closed and to reduce the bug noise. This does not imply that if a fix is released by GNOME, then it won't be adopted by Ubuntu. We do not 'filter' upstream code. If Metacity makes a new release with the fix included, then it will just be packaged. And of course the fact that GNOME are considering fixing this issue should not in any way preclude Ubuntu from attempting to fix it. Again, you are free to open a bug about it, although I doubt it will be fixed as there are no developers working on Metacity on Ubuntu. Anyhow, the point is: this particular one is too old and too long to be useful. Your opinions are welcome, but if you continue posting here, they will just be ignored. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/160311 Title: Resizing windows by grabbing window borders is difficult Status in Ayatana Design: Fix Released Status in One Hundred Paper Cuts: Fix Released Status in The Metacity Window Manager: In Progress Status in Release Notes for Ubuntu: Fix Released Status in Unity: Fix Released Status in Unity 2D: Invalid Status in “light-themes” package in Ubuntu: Fix Released Bug description: This bug is fixed in unity-3d since ubuntu 11.04. It still exists in unity-2d and will never be fixed as unity-2d is no longer supported since ubuntu 12.10 (see comment #343). * This should mostly be fixed for Natty and might get backported to earlier releases as well. For Precise (12.04) this is again broken for unity-2d (as of 17.7.2012 unity-2d 5.12.0-0ubuntu1.1). Note that if the window has a scrollbar, you can grab that to resize the window. If not, you are stuck with the 1px border. Workaround: NONE KNOWN (see comment 320)? * *Blueprint for Natty, Ubuntu 11.04: https://blueprints.edge.launchpad.net/ubuntu/+spec/packageselection- dx-n-resizing-windows Work items1 * Make sure the new resize grip fits in current applications; doesn't interfere with anything. We should make some noise about this during the Natty cycle so people keep their eyes open and file bugs. 2 * Invisible window resize area - around 3px invisible area to allow resize on all sides. * Working grip backported to gtk2 already available in ppa : https://launchpad.net/~bratsche/+archive/gtk * Workaround for Compiz/Unity: Alt+Middlemousebutton resizes a window most comfortably. Workaround: Edit /usr/share/themes/Ambiance/metacity-1/metacity- theme-1.xml. Set the following values in frame_geometry_normal as desired: distance name=left_width value=3/ distance name=right_width value=3/ distance name=bottom_height value=3/ Binary package hint: metacity - The issue has been an issue for users (especially of large) screens for several releases- Trackpad users seem to be particularly impacted by this- The issue appears to have been significantly aggravated in Lucid by changing the border width from 3 pixels to 1 pixel The window borders in metacity are far too thin to be used for comfortable window resizing, and resize handles are not available in all applications (or even most). In fact, of all the windows I have open right now, not a single one of them has a resize handle. The result is that I get a lot of misses when I try to drag a window border, which usually results in my clicking on the wrong window altogether. The best fix for this usability bug is to create an invisible region around each non-maximized window about 4px thick that can be used for resizing (in addition to the visible border). Or perhaps there should be a border thickness option on the System Preferences Windows dialog (although the default
[Desktop-packages] [Bug 693842] Re: Merge nautilus-open-terminal with nautilus.
Thank you for your bug report. Unfortunately, the Ubuntu project does not 'own' neither nautilus nor its plugins, so this is something that the Ubuntu project can't do. This request should instead be proposed on bugzilla.gnome.org, like Pedro said. ** Changed in: nautilus-open-terminal (Ubuntu) Status: Confirmed = Invalid ** Changed in: nautilus (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/693842 Title: Merge nautilus-open-terminal with nautilus. Status in Nautilus: New Status in “nautilus” package in Ubuntu: Invalid Status in “nautilus-open-terminal” package in Ubuntu: Invalid Bug description: Binary package hint: nautilus Hi, there is a very useful package called nautilus-open-terminal, which allows you to open the current directory in the terminal from either the File menu or Right-Click. This is functionality I, personally, missed from days using Thunar file manager in XFCE and functionality i feel should be default in Unix file managers. I propose that the nautilus-open-terminal project is merged with the main nautilus project. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/693842/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected
@Steve, Susan: I was sure that the libreoffice task was already fixed. My bad, sorry! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected Status in “culmus” package in Ubuntu: Fix Released Status in “fonts-arphic-ukai” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-nanum-coding” package in Ubuntu: Fix Released Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Triaged Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “culmus” source package in Quantal: Fix Released Status in “fonts-arphic-ukai” source package in Quantal: Fix Released Status in “fonts-arphic-uming” source package in Quantal: Fix Released Status in “fonts-baekmuk” source package in Quantal: Fix Released Status in “fonts-droid” source package in Quantal: Fix Released Status in “fonts-nanum” source package in Quantal: Fix Released Status in “fonts-nanum-coding” source package in Quantal: Fix Released Status in “fonts-sil-andika” source package in Quantal: Fix Released Status in “fonts-tlwg” source package in Quantal: Fix Released Status in “fonts-unfonts-core” source package in Quantal: Fix Released Status in “fonts-unfonts-extra” source package in Quantal: Fix Released Status in “language-selector” source package in Quantal: Fix Released Status in “libreoffice” source package in Quantal: Confirmed Status in “ttf-wqy-zenhei” source package in Quantal: Fix Released Status in “fonts-arphic-ukai” package in Debian: New Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: Fix Released Status in “fonts-droid” package in Debian: Fix Released Status in “fonts-nanum” package in Debian: Fix Released Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: Fix Released Status in “fonts-unfonts-extra” package in Debian: Fix Released Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf, line 11: Having multiple values in test isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf [Test Case] 1) Install the fonts in question 2) Open a terminal 3) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal [Regression Potential] In case of a regression, the font in question can be affected. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/culmus/+bug/1034928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected
@Susan Cragin: I'm sorry for your problem. Unfortunately, it can't be fixed in Ubuntu because, as you said, you are using the beta version of LibreOffice, which is not shipped by Ubuntu. There's nothing we can do about it. You should create an issue in the LibreOffice bug tracker. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected Status in “culmus” package in Ubuntu: Fix Released Status in “fonts-arphic-ukai” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-nanum-coding” package in Ubuntu: Fix Released Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Triaged Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “culmus” source package in Quantal: Fix Released Status in “fonts-arphic-ukai” source package in Quantal: Fix Released Status in “fonts-arphic-uming” source package in Quantal: Fix Released Status in “fonts-baekmuk” source package in Quantal: Fix Released Status in “fonts-droid” source package in Quantal: Fix Released Status in “fonts-nanum” source package in Quantal: Fix Released Status in “fonts-nanum-coding” source package in Quantal: Fix Released Status in “fonts-sil-andika” source package in Quantal: Fix Released Status in “fonts-tlwg” source package in Quantal: Fix Released Status in “fonts-unfonts-core” source package in Quantal: Fix Released Status in “fonts-unfonts-extra” source package in Quantal: Fix Released Status in “language-selector” source package in Quantal: Fix Released Status in “libreoffice” source package in Quantal: Confirmed Status in “ttf-wqy-zenhei” source package in Quantal: Fix Released Status in “fonts-arphic-ukai” package in Debian: New Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: Fix Released Status in “fonts-droid” package in Debian: Fix Released Status in “fonts-nanum” package in Debian: Fix Released Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: Fix Released Status in “fonts-unfonts-extra” package in Debian: Fix Released Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf, line 11: Having multiple values in test isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf [Test Case] 1) Install the fonts in question 2) Open a terminal 3) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal [Regression Potential] In case of a regression, the font in question can be affected. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/culmus/+bug/1034928/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1095254] Re: Signond ignores HTTP proxy setting
** Bug watch added: AccountsSSO issues #137 http://code.google.com/p/accounts-sso/issues/detail?id=137 ** Also affects: signon via http://code.google.com/p/accounts-sso/issues/detail?id=137 Importance: Unknown Status: Unknown ** Summary changed: - Signond ignores HTTP proxy setting + Signond ignores GNOME proxy setting ** Description changed: Description: Ubuntu 12.10 Release: 12.10 Package version: 8.43-0ubuntu1 - Signon ignores proxy settings in System Settings... - Network - - Network proxy. Everytime I set the proxy (at work, not using it at home) - I get red power gear icon indicator with message about online accounts - being not accessible and have to re-connect everything (which does not - work from behind the proxy). Any application that uses signon (e.g. - shotwell, empathy, various lenses in unity) does not work while behind - the proxy (getting errors). Proxy server is McAffee Web Gateway (at - work) or Squid. + Signon ignores proxy settings in System Settings → Network → Network + proxy. If the Internet can only be reached through a proxy, the online + accounts won't connect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1095254 Title: Signond ignores GNOME proxy setting Status in Online Accounts: Sign-on daemon: Unknown Status in “signon” package in Ubuntu: Triaged Bug description: Description: Ubuntu 12.10 Release: 12.10 Package version: 8.43-0ubuntu1 Signon ignores proxy settings in System Settings → Network → Network proxy. If the Internet can only be reached through a proxy, the online accounts won't connect. To manage notifications about this bug go to: https://bugs.launchpad.net/signon/+bug/1095254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1095254] Re: Signond ignores GNOME proxy setting
** Changed in: signon (Ubuntu) Status: Confirmed = Triaged ** Changed in: signon (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1095254 Title: Signond ignores GNOME proxy setting Status in Online Accounts: Sign-on daemon: Unknown Status in “signon” package in Ubuntu: Triaged Bug description: Description: Ubuntu 12.10 Release: 12.10 Package version: 8.43-0ubuntu1 Signon ignores proxy settings in System Settings → Network → Network proxy. If the Internet can only be reached through a proxy, the online accounts won't connect. To manage notifications about this bug go to: https://bugs.launchpad.net/signon/+bug/1095254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1095254] Re: Signond ignores GNOME proxy setting
** Tags added: proxy quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1095254 Title: Signond ignores GNOME proxy setting Status in Online Accounts: Sign-on daemon: Unknown Status in “signon” package in Ubuntu: Triaged Bug description: Description: Ubuntu 12.10 Release: 12.10 Package version: 8.43-0ubuntu1 Signon ignores proxy settings in System Settings → Network → Network proxy. If the Internet can only be reached through a proxy, the online accounts won't connect. To manage notifications about this bug go to: https://bugs.launchpad.net/signon/+bug/1095254/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 882040] Re: should let users enable or disable suspend and hibernate
@John: hybrid suspend is already implemented in PowerManager, see pm- suspend-hybrid(8). So the lot of work would consist just in changing the action triggered when pressing the Suspend button. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/882040 Title: should let users enable or disable suspend and hibernate Status in Ayatana Design: Fix Committed Status in “gnome-control-center” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: We should have an ui in the power capplet for that: https://wiki.ubuntu.com/Power#Power_settings [The corresponding task for other desktop environments that do not use the GNOME control center is bug #976654.] To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/882040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885606] Re: terminator is always producing a zombie-process ([terminator] defunct)
You need to request a Stable Release Update. The procedure is
documented here: https://wiki.ubuntu.com/StableReleaseUpdates. In my
opinion, you should not request an update to 0.28.2-4, but to 0.28.2-5
which ships some CVE fixes.
I can help you preparing the SRU request, if you need.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/885606
Title:
terminator is always producing a zombie-process ([terminator]
defunct)
Status in Terminator:
Invalid
Status in Gnome Virtual Terminal Emulator:
Invalid
Status in “vte” package in Ubuntu:
Fix Released
Status in “vte” package in Debian:
Fix Released
Bug description:
Using terminator always producing a zombie-process for each instant
i start
terminator
[1] 5239
ps aux | grep terminator
michael 5239 7.2 2.3 195160 23924 pts/0Sl 10:58 0:01
/usr/bin/python /usr/bin/terminator
michael 5242 0.0 0.0 0 0 pts/0Z10:58 0:00 [terminator]
defunct
top
Tasks: 136 total, 2 running, 131 sleeping, 0 stopped, 1 zombie
output of pstree
├─terminator─┬─bash─┬─pstree
││ └─terminator─┬─bash
││ ├─terminator
││ └─{terminator}
│├─bash───ssh
│├─terminator
│└─2*[{terminator}]
├─terminator─┬─bash
│├─terminator
│└─{terminator}
if i read the output from pstree correctly, terminator is always
starting two instances and one of them is a zombie
i cant find any disadvantages in the usage right know but i dont think this
should be normal to have a zombie-process
This bug never came up with 11.04 or earlier, just with 11.10
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: terminator 0.95-1
Uname: Linux 3.1.0-0301rc9-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Thu Nov 3 10:59:39 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
PackageArchitecture: all
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: terminator
UpgradeStatus: Upgraded to oneiric on 2011-09-16 (48 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/terminator/+bug/885606/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885606] Re: terminator is always producing a zombie-process ([terminator] defunct)
Michael, you should not confuse *source* packages and *binary* packages.
vte is a source package that produces multiple binary packages. apt-
cache show works for binary packages, the right command here is apt-
cache showsrc. Here is an example:
$ apt-cache show libvte9
Package: libvte9
...
Source: vte
...
$ apt-cache showsrc vte
Package: vte
Binary: libvte9, libvte9-udeb, libvte-dev, libvte-common, python-vte,
libvte-doc
...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/885606
Title:
terminator is always producing a zombie-process ([terminator]
defunct)
Status in Terminator:
Invalid
Status in Gnome Virtual Terminal Emulator:
Invalid
Status in “vte” package in Ubuntu:
Fix Released
Status in “vte” package in Debian:
Fix Released
Bug description:
Using terminator always producing a zombie-process for each instant
i start
terminator
[1] 5239
ps aux | grep terminator
michael 5239 7.2 2.3 195160 23924 pts/0Sl 10:58 0:01
/usr/bin/python /usr/bin/terminator
michael 5242 0.0 0.0 0 0 pts/0Z10:58 0:00 [terminator]
defunct
top
Tasks: 136 total, 2 running, 131 sleeping, 0 stopped, 1 zombie
output of pstree
├─terminator─┬─bash─┬─pstree
││ └─terminator─┬─bash
││ ├─terminator
││ └─{terminator}
│├─bash───ssh
│├─terminator
│└─2*[{terminator}]
├─terminator─┬─bash
│├─terminator
│└─{terminator}
if i read the output from pstree correctly, terminator is always
starting two instances and one of them is a zombie
i cant find any disadvantages in the usage right know but i dont think this
should be normal to have a zombie-process
This bug never came up with 11.04 or earlier, just with 11.10
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: terminator 0.95-1
Uname: Linux 3.1.0-0301rc9-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Thu Nov 3 10:59:39 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
PackageArchitecture: all
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: terminator
UpgradeStatus: Upgraded to oneiric on 2011-09-16 (48 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/terminator/+bug/885606/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885606] Re: terminator is always producing a zombie-process ([terminator] defunct)
This was fixed in Debian with vte 0.28.2-4. Quantal ships
0.28.2-5ubuntu1, so this bug is fixed in Ubuntu too.
** Changed in: vte (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/885606
Title:
terminator is always producing a zombie-process ([terminator]
defunct)
Status in Terminator:
Invalid
Status in Gnome Virtual Terminal Emulator:
Invalid
Status in “vte” package in Ubuntu:
Fix Released
Status in “vte” package in Debian:
Fix Released
Bug description:
Using terminator always producing a zombie-process for each instant
i start
terminator
[1] 5239
ps aux | grep terminator
michael 5239 7.2 2.3 195160 23924 pts/0Sl 10:58 0:01
/usr/bin/python /usr/bin/terminator
michael 5242 0.0 0.0 0 0 pts/0Z10:58 0:00 [terminator]
defunct
top
Tasks: 136 total, 2 running, 131 sleeping, 0 stopped, 1 zombie
output of pstree
├─terminator─┬─bash─┬─pstree
││ └─terminator─┬─bash
││ ├─terminator
││ └─{terminator}
│├─bash───ssh
│├─terminator
│└─2*[{terminator}]
├─terminator─┬─bash
│├─terminator
│└─{terminator}
if i read the output from pstree correctly, terminator is always
starting two instances and one of them is a zombie
i cant find any disadvantages in the usage right know but i dont think this
should be normal to have a zombie-process
This bug never came up with 11.04 or earlier, just with 11.10
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: terminator 0.95-1
Uname: Linux 3.1.0-0301rc9-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Thu Nov 3 10:59:39 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
PackageArchitecture: all
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: terminator
UpgradeStatus: Upgraded to oneiric on 2011-09-16 (48 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/terminator/+bug/885606/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 885606] Re: terminator is always producing a zombie-process ([terminator] defunct)
** Also affects: vte (Ubuntu)
Importance: Undecided
Status: New
** Also affects: vte (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645104
Importance: Unknown
Status: Unknown
** Changed in: vte (Ubuntu)
Status: New = Triaged
** Changed in: vte (Ubuntu)
Importance: Undecided = Medium
** Changed in: terminator
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to vte in Ubuntu.
https://bugs.launchpad.net/bugs/885606
Title:
terminator is always producing a zombie-process ([terminator]
defunct)
Status in Terminator:
Invalid
Status in Gnome Virtual Terminal Emulator:
New
Status in “vte” package in Ubuntu:
Triaged
Status in “vte” package in Debian:
Unknown
Bug description:
Using terminator always producing a zombie-process for each instant
i start
terminator
[1] 5239
ps aux | grep terminator
michael 5239 7.2 2.3 195160 23924 pts/0Sl 10:58 0:01
/usr/bin/python /usr/bin/terminator
michael 5242 0.0 0.0 0 0 pts/0Z10:58 0:00 [terminator]
defunct
top
Tasks: 136 total, 2 running, 131 sleeping, 0 stopped, 1 zombie
output of pstree
├─terminator─┬─bash─┬─pstree
││ └─terminator─┬─bash
││ ├─terminator
││ └─{terminator}
│├─bash───ssh
│├─terminator
│└─2*[{terminator}]
├─terminator─┬─bash
│├─terminator
│└─{terminator}
if i read the output from pstree correctly, terminator is always
starting two instances and one of them is a zombie
i cant find any disadvantages in the usage right know but i dont think this
should be normal to have a zombie-process
This bug never came up with 11.04 or earlier, just with 11.10
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: terminator 0.95-1
Uname: Linux 3.1.0-0301rc9-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
Date: Thu Nov 3 10:59:39 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
PackageArchitecture: all
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SourcePackage: terminator
UpgradeStatus: Upgraded to oneiric on 2011-09-16 (48 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/terminator/+bug/885606/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected
** Changed in: fonts-nanum-coding (Ubuntu) Status: Incomplete = In Progress ** Changed in: fonts-nanum-coding (Ubuntu) Assignee: (unassigned) = Benjamin Drung (bdrung) ** Changed in: culmus (Ubuntu) Status: Triaged = In Progress ** Changed in: culmus (Ubuntu) Assignee: (unassigned) = Benjamin Drung (bdrung) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected Status in “culmus” package in Ubuntu: In Progress Status in “fonts-arphic-ukai” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-nanum-coding” package in Ubuntu: In Progress Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Triaged Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “fonts-arphic-ukai” package in Debian: New Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: Fix Released Status in “fonts-droid” package in Debian: Fix Committed Status in “fonts-nanum” package in Debian: Fix Released Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: Fix Released Status in “fonts-unfonts-extra” package in Debian: Fix Released Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf, line 11: Having multiple values in test isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf To reproduce: 1) Open a terminal 2) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/culmus/+bug/1034928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 682788] Re: Improve Unity Global Menu
@papukaija: the Ubuntu bugcontrol team cannot revert such changes because they were made to projects, not to Ubuntu packages. However I have already contacted who can revert the changes; let's wait till Monday, if I do not get a response, I'll use the mailing list. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/682788 Title: Improve Unity Global Menu Status in Ayatana Design: Fix Released Status in Compiz: Triaged Status in Unity: In Progress Status in “compiz” package in Ubuntu: Triaged Status in “metacity” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: ===+++ _ ! ALL USERS ! _ +++=== ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++=== IMPORTANT 1: Please don't post any me too message; use the Does this bug affect you? feature you can find a bit above this bug description on Launchpad. IMPORTANT 2: Do not post anything if you haven't read all comments to verify that your point hasn't been made. If you feel tempted to stop reading because there are too many messages, that is a strong indicator that you shouldn't add even more comments. Developers have a tough time to find anything if you post redundant stuff. So please abstain from doing that. = Global menu in general (not only in Unity) is very unergonomic on large screens (see the attached screenshot) because if you have a small window somewhere near the low right corner you have to move the cursor all the way up to to panel to reach the menu. I understand why the global menu was used for the netbook edition (it saves space and most windows are maximized), but since Unity is intended to be for the desktop edition there should be an option to switch to the traditional position of the app menu. It would be welcomed by many desktop users. Please try to find a solution for it that works. A commonly suggested solution is: [ ] Global Menu on [ ] Global Menu off [ ] Global Menu only for maximized windows The default is usually suggested as either the first (on) or last (on only for maximized windows). - Desired change: Implement the 'Enhanced Menu' project for 12.10. This project will address the issue described in this bug and also issues described in the duplicates of this bus. Note this is the 'official' bug that tracks the implementation of this project. The following options will be added to 'System Settings/Appearance': --- Menus Location:Global/Local Visibility: Hidden/Always displayed --- To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/682788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected
@James: Looking at 90-fonts-nanum-coding.conf 2.0-4 (from Quantal) I cannot see any problem with test. Please, could you paste the warning you get and also tell the version you are using? ** Also affects: fonts-nanum-coding (Ubuntu) Importance: Undecided Status: New ** Changed in: fonts-nanum-coding (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected Status in “culmus” package in Ubuntu: Triaged Status in “fonts-arphic-ukai” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-nanum-coding” package in Ubuntu: Incomplete Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Triaged Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “fonts-arphic-ukai” package in Debian: New Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: Fix Released Status in “fonts-droid” package in Debian: Fix Committed Status in “fonts-nanum” package in Debian: Fix Released Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: Fix Released Status in “fonts-unfonts-extra” package in Debian: Fix Released Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf, line 11: Having multiple values in test isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf To reproduce: 1) Open a terminal 2) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/culmus/+bug/1034928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected
@Johan (sorry, I forgot to reply): unfortunately, that's not the right way to apply a patch. A patch contains just the differences between the old version of a file and the new version. To get the new version of the file, you need to combine the old version with the diff. Generally, to apply a patch you should use the following commands: cd /path/to/the/file patch -p0 /path/to/the/patch Though, this might not work in every case (see man patch for more information). ** Changed in: culmus (Ubuntu) Importance: Undecided = Low ** Changed in: culmus (Ubuntu) Status: Confirmed = Triaged ** No longer affects: libreoffice (Ubuntu) ** Also affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Changed in: libreoffice (Ubuntu) Importance: Undecided = Low ** Changed in: libreoffice (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected Status in “culmus” package in Ubuntu: Triaged Status in “fonts-arphic-ukai” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Triaged Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “fonts-arphic-ukai” package in Debian: New Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: Fix Released Status in “fonts-droid” package in Debian: Fix Committed Status in “fonts-nanum” package in Debian: Fix Released Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: Fix Released Status in “fonts-unfonts-extra” package in Debian: Fix Released Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf, line 11: Having multiple values in test isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf To reproduce: 1) Open a terminal 2) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/culmus/+bug/1034928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 10686] Re: No GUI method to disable screen lock on lid close event
Quantal has a way to disable the screen lock: Settings → Brightness and Lock → Lock: Off. Probably it is possible in Precise too, though I can't check. ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/10686 Title: No GUI method to disable screen lock on lid close event Status in “gnome-power-manager” package in Ubuntu: Fix Released Bug description: When I close my laptop lid, and open it again, the screensaver is locked. I'd like to change this behaviour, I've checked the screensaver preferences and the only option that mentions locking the screen (Lock screen after) is unset. I think it makes more sense to lock the screen on lid close dependant on the setting of Lock screen after option in screensaver preferences This is on a recently updated hoary, xscreensaver version 4.16-1ubuntu3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/10686/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 871047] Re: Can no longer set screen to lock when lid closed
** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/871047 Title: Can no longer set screen to lock when lid closed Status in “gnome-power-manager” package in Ubuntu: Incomplete Bug description: Before, with Gnome 2, I've configured it for when I close the laptop lid it lock the screen demanding the password. It's because sometimes I go to any places publics or with my friends and I don't want to have the PC trolled when I leave it for a while. Now, with Ubuntu 11.10, the gnome-screensaver is deleted, so when I select the blank option at org.gnome.settings-daemon.plugins.power lid-close-ac-action with dconf-editor, only it puts the screen black, but it doesn't block the screen because before the gnome- screensaver was the responsible of doing it and with Gnome 3 and Unity it dissapears. It's possible to add and lock-screen option that executes the lock screen command? Because I think that to close the screen is a better gesture to make sure that you've locked it more than remember always to do Ctrl+Alt+L. See also bug 888330, the equivalent for blanking the screen. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-power-manager 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Sun Oct 9 02:08:57 2011 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GnomeSessionSuspendInhibited: No InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20111006) MachineType: Dell Inc. XPS M1330 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=f2473a46-a5f1-46b1-8b14-e6677563f14b ro quiet splash nomodeset video=uvesafb:mode_option=1280x1024-24,mtrr=3,scroll=ywrap vt.handoff=7 SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to oneiric on 2011-10-07 (1 days ago) dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0U8042 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn0U8042:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. gnome-power-bugreport: Error: [Errno 2] No existe el archivo o el directorio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/871047/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 3644] Re: Cannot scroll horizontally using the mouse wheel
** No longer affects: mousepad (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/3644 Title: Cannot scroll horizontally using the mouse wheel Status in GTK+ GUI Toolkit: Confirmed Status in “gtk+2.0” package in Ubuntu: Triaged Bug description: When a control is only horizontal-scrollable, we should be able to sroll left/right using the mouse wheel. When a control is both horizontal- and vertical-scrollable, we should be able to scroll left/right using CTRL+mouse wheel (ala Inkscape). To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/3644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 3644] Re: Cannot scroll horizontally using the mouse wheel
Horizontal scrolling using the mouse whell is possible with Gtk 3. I don't know about Gtk 2, but given that it is superseeded it is very very unlikely that it will see new features. Therefore, I'm closing this bug. ** Package changed: gtk+2.0 (Ubuntu) = ubuntu ** Changed in: ubuntu Status: Triaged = Won't Fix ** Changed in: ubuntu Assignee: Ubuntu Desktop Bugs (desktop-bugs) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/3644 Title: Cannot scroll horizontally using the mouse wheel Status in GTK+ GUI Toolkit: Confirmed Status in Ubuntu: Won't Fix Bug description: When a control is only horizontal-scrollable, we should be able to sroll left/right using the mouse wheel. When a control is both horizontal- and vertical-scrollable, we should be able to scroll left/right using CTRL+mouse wheel (ala Inkscape). To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/3644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1060213] Re: firefox freezes each time loading flash plugin-container
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1060213 When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Also, please attach the relevant apparmor=DENIED lines from your log files. ** Changed in: firefox (Ubuntu) Status: Confirmed = Incomplete ** Also affects: adobe-flashplugin (Ubuntu) Importance: Undecided Status: New ** Changed in: adobe-flashplugin (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1060213 Title: firefox freezes each time loading flash plugin-container Status in AppArmor Profiles: New Status in “adobe-flashplugin” package in Ubuntu: Incomplete Status in “firefox” package in Ubuntu: Incomplete Bug description: I have ATI RV710 [Mobility Radeon HD 4500/5100 Series]. Each time I open up a new tab that has flash in it, firefox freezes for about 5 seconds, then moves on. I debugged it and it seems that this is caused by apparmor not allowing firefox to access some stuff that plugin-container wants because of the driver. I do not know if the change was caused by firefox , plugin-container or respective video driver, but I do know how to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor-profiles/+bug/1060213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1039097] Re: super tiny font and incorrect background
Hey there. Thanks for taking time reporting this bug. As you know, Quantal and Unity have changed much since when you reported this bug. Are you still experiencing the issue? If so, could you please open a new task using ubuntu-bug unity-greeter? I'm closing this bug because it lacks all the useful information from apport. ** Changed in: unity-greeter (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1039097 Title: super tiny font and incorrect background Status in “unity-greeter” package in Ubuntu: Invalid Bug description: After today's Quantal update, the login screen is unusable. After a reboot, I get what looks like it might be the normal login screen, and I get the bongos, but then almost immediately the screen turns into the old-style purple-and-orange background and all the fonts are super tiny. Although very small, I'm able to find the reboot button, but other than that I cannot log into the desktop. This is running in a VMware Fusion 4.1 virtual machine, but everything worked before today's reboot. I am going to try rebooting one of my native machines to see if the same problem occurs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1039097/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected
@mlentink: the messages from fontconfig are just warnings, not errors. If Libreoffice fails to start, then you are experiencing a different issue. Please, file a bug about that using ubuntu-bug libreoffice. For more information, see https://help.ubuntu.com/community/ReportingBugs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected Status in “fonts-arphic-ukai” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Confirmed Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “fonts-arphic-ukai” package in Debian: New Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: New Status in “fonts-droid” package in Debian: Fix Committed Status in “fonts-nanum” package in Debian: New Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: New Status in “fonts-unfonts-extra” package in Debian: New Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf, line 11: Having multiple values in test isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf To reproduce: 1) Open a terminal 2) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1034928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected
@Johan: how exactly have you applied the patch? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected Status in “fonts-arphic-ukai” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Confirmed Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “fonts-arphic-ukai” package in Debian: New Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: New Status in “fonts-droid” package in Debian: Fix Committed Status in “fonts-nanum” package in Debian: New Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: New Status in “fonts-unfonts-extra” package in Debian: New Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf, line 11: Having multiple values in test isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf To reproduce: 1) Open a terminal 2) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1034928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 984785] Re: .goutputstream files polluting $HOME
** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Importance: Undecided = Low ** Changed in: glib2.0 (Ubuntu Precise) Importance: Undecided = Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/984785 Title: .goutputstream files polluting $HOME Status in The G Library - GLib: New Status in Light Display Manager: New Status in X.Org X server: New Status in “glib2.0” package in Ubuntu: New Status in “lightdm” package in Ubuntu: Confirmed Status in “glib2.0” source package in Precise: New Status in “lightdm” source package in Precise: Confirmed Bug description: .goutputstream files polluting $HOME. Which software or operation is creating these and why? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xauth 1:1.0.6-1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ati ApportVersion: 2.0.1-0ubuntu4 Architecture: amd64 Date: Wed Apr 18 13:29:31 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xauth UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/984785/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected
** Also affects: fonts-arphic-ukai (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected Status in “fonts-arphic-ukai” package in Ubuntu: Triaged Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Confirmed Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: New Status in “fonts-droid” package in Debian: Fix Committed Status in “fonts-nanum” package in Debian: New Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: New Status in “fonts-unfonts-extra” package in Debian: New Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf, line 11: Having multiple values in test isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf To reproduce: 1) Open a terminal 2) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1034928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected
** Changed in: fonts-arphic-ukai (Ubuntu) Importance: Undecided = Low ** Description changed: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf, line 11: Having multiple values in test isn't supported and may not works as expected This affects fonts from a number of packages: + fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf To reproduce: 1) Open a terminal 2) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fonts-unfonts-core UpgradeStatus: Upgraded to quantal on 2012-08-07 (1 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected Status in “fonts-arphic-ukai” package in Ubuntu: Triaged Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Confirmed Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: New Status in “fonts-droid” package in Debian: Fix Committed Status in “fonts-nanum” package in Debian: New Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: New Status in “fonts-unfonts-extra” package in Debian: New Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf, line 11: Having multiple values in test isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf To reproduce: 1) Open a terminal 2) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies: InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage:
[Desktop-packages] [Bug 1029189] Re: ProcMaps.txt may contain private information such as username
All bugs that contain ProcMaps.txt (and also other similar files) are initially private. And private bugs must be checked from a bug control member before going public. Could you please explain the problem better? Specifically: do you think that Apport is not doing the right thing? Or have you found a public bug containing sensible information? Thank you in advance. ** Changed in: apport (Ubuntu) Status: New = Incomplete ** Changed in: launchpad Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1029189 Title: ProcMaps.txt may contain private information such as username Status in Launchpad itself: Invalid Status in “apport” package in Ubuntu: Incomplete Bug description: The ProcMaps.txt file that gets uploaded to Launchpad may contain private information such as username that can be obtained from the path of the home directory. 7fbd44c33000-7fbd44c34000 r--s 08:01 1306557 /home/alice/.local/share/mime/mime.cache To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1029189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1029189] Re: ProcMaps.txt may contain private information such as username
Bug reports created by Apport may containing a variety of sensible information -- from user names to credit card numbers. If you think that ProcMaps.txt is leaking private information, than don't look at the other files! :-) Well, jokes apart, all potentially sensible information uploaded is always secured and reviewed by experienced and competent people. When real sensible information are found, they are removed before a bug report is made public. There are well-established procedures used to deal with such cases. If you would like to have more information about the procedures used and the people involved, please read the following pages, they are a good start: https://wiki.ubuntu.com/Bugs/HowToTriage https://wiki.ubuntu.com/UbuntuBugControl If you still have suggestions or comments about the procedures and tools we use, then it's better to continue the discussion on the bugsquad mailing list: https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad. I'm invalidating the bug, as this is really not the right place to discuss. ** Changed in: apport (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1029189 Title: ProcMaps.txt may contain private information such as username Status in “apport” package in Ubuntu: Invalid Bug description: The ProcMaps.txt file that gets uploaded to Launchpad may contain private information such as username that can be obtained from the path of the home directory. 7fbd44c33000-7fbd44c34000 r--s 08:01 1306557 /home/alice/.local/share/mime/mime.cache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1029189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 3294] Re: Mouse cursor gets stuck in drag and drop mode. Keyboard input dies.
I'm closing this bug since the epiphany/webkit part has already been reported as bug #461424 and fixed, as Jouni already pointed out. ** Changed in: epiphany-browser (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/3294 Title: Mouse cursor gets stuck in drag and drop mode. Keyboard input dies. Status in “epiphany-browser” package in Ubuntu: Invalid Status in “galeon” package in Ubuntu: Invalid Status in “wxwidgets2.6” package in Ubuntu: Fix Released Bug description: I'm not sure which package this belongs to: python-wxgtk2.6 or libwxgtk2.6-0 (or something else), but it appears in the following programs: gvr, drpython, spe. When text is highlighted and an attempt is made to drag the text to another window, the mouse cursor gets stuck in the drag and drop mode. Sometimes keyboard input still works, and you can use Alt-f keys to get to a drop down menu and make the cursor change back to normal. Other times keyboard input is lost and restarting X is the only solution. My students are using GvR and drpython and accidentally make this happen several times each day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/3294/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 26303] Re: Floating toolbars prevent attaining focus when selected in Gnome taskbar
** Also affects: df-libreoffice via https://bugs.freedesktop.org/show_bug.cgi?id=48096 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/26303 Title: Floating toolbars prevent attaining focus when selected in Gnome taskbar Status in LibreOffice Productivity Suite: Unknown Status in The OpenOffice.org Suite: Invalid Status in “libreoffice” package in Ubuntu: New Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: If i use the taskbar to switch to openoffice, and openoffice has a floating bar, the openoffice window get visible but not active. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/26303/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 22891] Re: GNOME About Me info not used in User Data fields
I'm marking the libreoffice task as Triaged, like the old OpenOffice one. ** Changed in: libreoffice (Ubuntu) Importance: Undecided = Wishlist ** Changed in: libreoffice (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/22891 Title: GNOME About Me info not used in User Data fields Status in LibreOffice Productivity Suite: New Status in The OpenOffice.org Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: I'm using GNOME 2.12, and I've filled in the About Me page (from gnome-about). When I open OpenOffice.org2 Writer, none of the information added in GNOME's About Me is available to OpenOffice. It would be fantastic if these two worked together ! Cheers mercurus To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/22891/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 29894] Re: can't take screenshot when menu on panel is opened
Are we sure the cause of this bug are the various shells? As Sebastien said, this looks to me as an Xorg bug. Could somebody with more knowledge than me provide feedback, please? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-utils in Ubuntu. https://bugs.launchpad.net/bugs/29894 Title: can't take screenshot when menu on panel is opened Status in gnome-utils - GNOME Desktop Utilities: In Progress Status in Unity: Triaged Status in “gnome-screenshot” package in Ubuntu: Confirmed Status in “gnome-shell” package in Ubuntu: New Status in “gnome-utils” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: I can always press the Print screen key to take a screenshot of my desktop. When i click on say, the System menu in the gnome-panel, it just doesn't work anymore. Note: this is in fact only a symptom of bug 10905 that states that no hotkeys/shortcuts whatsoever can be triggered when a menu is open. there seems to be a dispute if that is a bug or an intended design decision. thus bug 10905 and its duplicates always get closed. people seem to agree that not being able to take screenshots is not intended bahavior and considered a bug. thus this report is allowed to stay open :) a known workaround for taking screenshots of menus is to directly launch the screengrabber with a delay like so: gnome-screenshot --delay=5 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-utils/+bug/29894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 994739] Re: wireless takes several seconds longer to connect from standby
Hi Pau, and thank you for your work. Please consider going thorough described in this wiki page in order to have your patch included in Ubuntu: https://wiki.ubuntu.com/Bugs/HowToFix You may also want to contact upstream directly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/994739 Title: wireless takes several seconds longer to connect from standby Status in “network-manager” package in Ubuntu: Invalid Status in “wpasupplicant” package in Ubuntu: Confirmed Bug description: My observation is that network-manager is taking longer to connect to my wireless access point than 11.10. I trust the rest of the attached info will reveal all necessary system data. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-24.38-generic-pae 3.2.16 Uname: Linux 3.2.0-24-generic-pae i686 NonfreeKernelModules: wl nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri May 4 12:47:28 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) IpRoute: default via 192.168.1.1 dev eth1 proto static 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.116 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1264165e3-74f6-4750-8198-6e8b6d3632cf 802-3-ethernet1336133356 Fri 04 May 2012 07:09:16 AM CDTyes no /org/freedesktop/NetworkManager/Settings/1 2.4GHzWPA29afe3092-8693-4b03-92cd-fd179af0fca8 802-11-wireless 1336153624 Fri 04 May 2012 12:47:04 PM CDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/994739/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 882040] Re: should let users enable or disable suspend and hibernate
** Description changed: We should have an ui in the power capplet for that: https://wiki.ubuntu.com/Power#Power_settings + + [The corresponding task for other desktop environments that do not use + the GNOME control center is bug #976654.] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/882040 Title: should let users enable or disable suspend and hibernate Status in Ayatana Design: Fix Committed Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: We should have an ui in the power capplet for that: https://wiki.ubuntu.com/Power#Power_settings [The corresponding task for other desktop environments that do not use the GNOME control center is bug #976654.] To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/882040/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976654] Re: let users disable/enable hibernation and suspension from the system settings
Hello and thanks for your bug report. I made a few changes to it, here is a full explaination of my actions: * I've changed the title and description to match what the bug is really trying to address. The bug tracker isn't a place to discuss decisions, but rather a place to track project goals. Discussions about what needs to be done should go to a mailing list, specifically -desktop (https://lists.ubuntu.com/mailman/listinfo/ubuntu-desktop) or -devel- discuss (https://lists.ubuntu.com/mailman/listinfo/Ubuntu-devel- discuss), depending on what you want to discuss exactly. * I marked this bug as affecting the GNOME control center. For KDE or Xfce new bugs should be filed (or new tasks should be added to this one). If you need it, the full old bug description can be retrieved viewing using the See full activity log link at the bottom of the page. ** Summary changed: - Please allow users to re-enable hibernation from GUI + let users disable/enable hibernation and suspension from the system settings ** Description changed: - Disabling hibernation is justifiable if it doesn't work on a particular - system. Making it the default for all systems isn't. First of all, it - breaks systems in which hibernation works. If a laptop runs out of - battery, the system would shut down and the user loses all unsaved - files. All unsaved files wouldn't be lost if hibernation was enabled. - - Secondly, hibernation was enabled in all Ubuntu releases before Precise. - This lack of consistency will just make peole confused and angry. - - Thirdly, disabling hibernation isn't environmentally friendly. Windows - is now greener than Ubuntu. - - My suggestion is - - 1) Keep hibernation disabled by default but allow people to enable it - again from the GUI - - or - - 2) Re-enable hibernation by default and let people to report bugs for - systems in which it doesn't work + It should be possible for average users to enable and disable suspension + and hibernation from the Power tab of the GNOME control center. ** Package changed: policykit-desktop-privileges (Ubuntu) = gnome- control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided = Wishlist ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/976654 Title: let users disable/enable hibernation and suspension from the system settings Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: It should be possible for average users to enable and disable suspension and hibernation from the Power tab of the GNOME control center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/976654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 976654] Re: let users disable/enable hibernation and suspension from the system settings
On Sun, 2012-04-08 at 17:13 +, RussianNeuroMancer wrote: The bug tracker isn't a place to discuss decisions Reading first ~fifteen comments in https://bugs.launchpad.net/bugs/812394 make me think there is another point of view on right place for discuss decisions topic. That bug has exactly one aim: disable hibernation by default. And the discussion was around that topic. However the original description of this specific bug was too vague: it listed too many things to do, i.e. it had too many tasks. We should always have one (and exactly one) active bug for each task. For KDE or Xfce new bugs should be filed (or new tasks should be added to this one) So basically it's mean KDE and Xfce developers need to do additional job just because feature is disabled in Ubuntu by default? Maybe it's better to keep it disabled by default only for Ubuntu users and don't make troubles for users and developers of Kubuntu, Xubuntu, etc.? I think it's logic desicion that save time and manpower. No, sorry, I didn't express myself correctly. What I meant is: a bug should be filed against the Ubuntu package that contains the power settings tool for KDE, and the same should be done against the Ubuntu package for Xfce. I didn't want bugs to be reported upstream. Whether the hibernation option should be disabled or not and where it should be disabled should be discussed on the mailing list. If you don't use the mailing list, your comments, opinions and ideas really risk to be ignored. Everyone in the Ubuntu community is always open to discussion, but if you don't hit the right people, your wishes will never be realized. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/976654 Title: let users disable/enable hibernation and suspension from the system settings Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: It should be possible for average users to enable and disable suspension and hibernation from the Power tab of the GNOME control center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/976654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 976654] Re: Let users disable/enable hibernation from the system settings
Hi papukaija. It is already possible to enable/disable hibernation by manually editing a configuration file. This bug is about giving the possibility of toggling the hibernation through a graphical tool, and the Power tab of the system settings is probably the best place where this option should be put. For this reason the package that should be patched is gnome-control-center. About the suspension: thanks for the correction! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/976654 Title: Let users disable/enable hibernation from the system settings Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: It should be possible for average users to enable and disable hibernation from the Power tab of the GNOME control center. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/976654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 940583] Re: Terminal Ctrl+u doesn't clear the line
** Also affects: ubuntu-website Importance: Undecided Status: New ** Changed in: ubuntu-website Status: New = Fix Released ** Changed in: ubuntu-website Assignee: (unassigned) = Andrea Corbellini (andrea.corbellini) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/940583 Title: Terminal Ctrl+u doesn't clear the line Status in Ubuntu Website Product: Fix Released Status in “gnome-terminal” package in Ubuntu: Invalid Bug description: In many documentations, ctrl+u in Terminal is supposed to clear the whole line. But I find it just clear the content BEFORE the CURSOR, which has no difference with ctrl+w. My current Ubuntu is v11.10. The referenced documentations https://help.ubuntu.com/community/UsingTheTerminal https://help.ubuntu.com/community/AdvancedCommandlineHowto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-website/+bug/940583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 940583] Re: Terminal Ctrl+u doesn't clear the line
The terminal actually behaves correctly, it's the documentation that is unclear. ** Changed in: gnome-terminal (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/940583 Title: Terminal Ctrl+u doesn't clear the line Status in “gnome-terminal” package in Ubuntu: Invalid Bug description: In many documentations, ctrl+u in Terminal is supposed to clear the whole line. But I find it just clear the content BEFORE the CURSOR, which has no difference with ctrl+w. My current Ubuntu is v11.10. The referenced documentations https://help.ubuntu.com/community/UsingTheTerminal https://help.ubuntu.com/community/AdvancedCommandlineHowto To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/940583/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 937971] Re: Save-As dialog box is not consistent with Nautilus' SidePane layout
** Tags added: usability -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/937971 Title: Save-As dialog box is not consistent with Nautilus' SidePane layout Status in GTK+ GUI Toolkit: Unknown Status in “gtk+3.0” package in Ubuntu: Triaged Bug description: I spend a lot of time teaching people how to use Ubuntu. A lot of the people I teach are not very computer savvy. It is confusing to people when they see in the Nautilus SidePane how things are categorized by DEVICES, COMPUTER, NETWORK only to be confronted with a lack of the same categorization/demarcation when they are presented with a Save-As dialog box. This results in users not fully understanding where something is going to be saved. The Save-As dialog box should use the same categorization/demarcation paradigm as the Nautilus SidePane. For example, look at the two screenshots I have attached. In the Nautilus SidePane screenshot, you can see that HOME, DESKTOP, and FILE SYSTEM are all located under the COMPUTER heading. This clearly communicates that these folders are located on the user's computer. Now look at the Save-As dialog SidePane. Notice how the USER, DESKTOP, and FILE SYSTEM folders are located where the DEVICES are listed? This is confusing. These folders are located on the COMPUTER and yet they are being listed along with DEVICES. The Save-As dialog box layout should match Nautilus' SidePane layout. That is, USER, DESKTOP, and FILE SYSTEM should be moved below the DEVICES section so they are listed together with the other folders located on the user's computer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.3.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6 Uname: Linux 3.2.0-17-generic i686 ApportVersion: 1.92-0ubuntu1 Architecture: i386 Date: Tue Feb 21 12:14:05 2012 ExecutablePath: /usr/bin/nautilus GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+65+24' org.gnome.nautilus.window-state maximized true org.gnome.nautilus.window-state sidebar-width 197 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110901) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to precise on 2012-02-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/937971/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 882633] Re: Cannot quit gwibber
Everything works as expected (i.e. I can quit Gwibber both using Ctrl+Q and Gwibber→Quit). Thanks! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/882633 Title: Cannot quit gwibber Status in Gwibber: Fix Committed Status in “gwibber” package in Ubuntu: Fix Released Status in “gwibber” source package in Oneiric: Fix Committed Bug description: I'm not able to quit Gwibber using Gwibber→Quit or Ctrl+Q. Whenever I try, I get the following on stderr: Gtk-CRITICAL **: gtk_main_quit: assertion `main_loops != NULL' failed Empathy has exactly the same problem: https://bugzilla.gnome.org/show_bug.cgi?id=662504 (the bug contains a patch). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Thu Oct 27 17:45:00 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/882633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 882633] Re: Cannot quit gwibber
Hi Martin. Thanks for the information. I'm using a mirror, so I'm currently unable to test the newest gwibber. I think tomorrow the package will get synced and I'll be able to upgrade+test. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/882633 Title: Cannot quit gwibber Status in Gwibber: Fix Committed Status in “gwibber” package in Ubuntu: Fix Released Status in “gwibber” source package in Oneiric: Fix Committed Bug description: I'm not able to quit Gwibber using Gwibber→Quit or Ctrl+Q. Whenever I try, I get the following on stderr: Gtk-CRITICAL **: gtk_main_quit: assertion `main_loops != NULL' failed Empathy has exactly the same problem: https://bugzilla.gnome.org/show_bug.cgi?id=662504 (the bug contains a patch). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Thu Oct 27 17:45:00 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/882633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 882633] [NEW] Cannot quit gwibber
Public bug reported: I'm not able to quit Gwibber using Gwibber→Quit or Ctrl+Q. Whenever I try, I get the following on stderr: Gtk-CRITICAL **: gtk_main_quit: assertion `main_loops != NULL' failed Empathy has exactly the same problem: https://bugzilla.gnome.org/show_bug.cgi?id=662504 (the bug contains a patch). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Thu Oct 27 17:45:00 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gwibber Importance: Undecided Status: New ** Affects: gwibber (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/882633 Title: Cannot quit gwibber Status in Gwibber: New Status in “gwibber” package in Ubuntu: New Bug description: I'm not able to quit Gwibber using Gwibber→Quit or Ctrl+Q. Whenever I try, I get the following on stderr: Gtk-CRITICAL **: gtk_main_quit: assertion `main_loops != NULL' failed Empathy has exactly the same problem: https://bugzilla.gnome.org/show_bug.cgi?id=662504 (the bug contains a patch). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Thu Oct 27 17:45:00 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/882633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 882633] Re: Cannot quit gwibber
** Also affects: gwibber Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/882633 Title: Cannot quit gwibber Status in Gwibber: New Status in “gwibber” package in Ubuntu: New Bug description: I'm not able to quit Gwibber using Gwibber→Quit or Ctrl+Q. Whenever I try, I get the following on stderr: Gtk-CRITICAL **: gtk_main_quit: assertion `main_loops != NULL' failed Empathy has exactly the same problem: https://bugzilla.gnome.org/show_bug.cgi?id=662504 (the bug contains a patch). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6 Uname: Linux 3.0.0-13-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Thu Oct 27 17:45:00 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: gwibber UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/882633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 871985] Re: The printing panel shouldn't display errors about firewalld not running
For your interest, system-config-printer can be used from Gnome Shell too, without the need of Unity. Just open a terminal (or press Alt+F2), write system-config-printer and press Enter. I'm going to add this easy workaround to the bug description. ** Description changed: + WORKAROUND: As an alternative to the printer configuration tool from the + new Gnome Shell control center, you can still use system-config-printer. + To open it, just press Alt+F2, type system-config-printer and press + Enter. + It appears a patch was added to Gnome back in July that requires FirewallD to be running in order to add a network printer. - see: http://mail.gnome.org/archives/commits-list/2011-July/msg09761.html + see: http://mail.gnome.org/archives/commits-list/2011-July/msg09761.html This only appears to affect those using the Gnome 3 desktop environment, and this problem is not present in Unity, so you can still add the pinter in Unity's control panel, but users wanting to use Gnome will encounter this. The specific error message is: - FirewallD is not running. Network printer detection needs services mdns, ipp, ipp-client and samba-client enabled on firewall. + FirewallD is not running. Network printer detection needs services mdns, ipp, ipp-client and samba-client enabled on firewall. The documentation in the mentioned patch suggests this behavior is actually intentional. However, FirewallD is, as far as I know, specific to Fedora. 1) release: Ubuntu Oneiric Beta 2 (64 bit, but others likely to be affected) - 2) issue is more specific to the Gnome 3 desktop environment as a whole, although there may be individual packages that can be patched to circumvent this behavior - - 3) I expected the previous behavior of being able to add a network printer without having a package that does not even exist for Ubuntu + 2) issue is more specific to the Gnome 3 desktop environment as a whole, + although there may be individual packages that can be patched to + circumvent this behavior + + 3) I expected the previous behavior of being able to add a network + printer without having a package that does not even exist for Ubuntu 4) I got this nice error message that tells me FirewallD is not running. Network printer detection needs services mdns, ipp, ipp-client and samba-client enabled on firewall. As far as a solution goes, a documented work-around may be a good idea (such as an FAQ entry that says simply to install the network printer in Unity), at least until a more permanent solution can be found. This is bug was originally asked as a question here: https://answers.launchpad.net/ubuntu/+source/gnome- nettool/+question/173836 but it was suggested that a bug report be submitted instead. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Mon Oct 10 14:49:32 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: - deja-dup 20.0-0ubuntu3 - gnome-bluetooth3.2.0-0ubuntu1 - indicator-datetime 0.3.0-0ubuntu3 + deja-dup 20.0-0ubuntu3 + gnome-bluetooth3.2.0-0ubuntu1 + indicator-datetime 0.3.0-0ubuntu3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/871985 Title: The printing panel shouldn't display errors about firewalld not running Status in GNOME Control Center: Confirmed Status in “gnome-control-center” package in Ubuntu: Triaged Bug description: WORKAROUND: As an alternative to the printer configuration tool from the new Gnome Shell control center, you can still use system-config- printer. To open it, just press Alt+F2, type system-config-printer and press Enter. It appears a patch was added to Gnome back in July that requires FirewallD to be running in order to add a network printer. see: http://mail.gnome.org/archives/commits-list/2011-July/msg09761.html This only appears to affect those using the Gnome 3 desktop environment, and this problem is not present in Unity, so you can still add the pinter in Unity's control panel, but users wanting to use Gnome will encounter this. The specific error message is: FirewallD is not running. Network printer detection needs services mdns, ipp, ipp-client and samba-client enabled on firewall. The documentation in the mentioned patch suggests this behavior is actually intentional. However, FirewallD is, as far as I know, specific to Fedora. 1) release: Ubuntu Oneiric Beta 2 (64 bit, but
[Desktop-packages] [Bug 764632] Re: The Use SSH tunnel option doesn't work
** Tags removed: ayatana-scrollbar i386 natty ** Tags added: patch patch-forwarded-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vinagre in Ubuntu. https://bugs.launchpad.net/bugs/764632 Title: The Use SSH tunnel option doesn't work Status in Vinagre: VNC client for GNOME: Confirmed Status in “vinagre” package in Ubuntu: Triaged Bug description: Binary package hint: vinagre I get this message: Error creating the SSH tunnel Error reading from Unix: Input/output error I've had this problem in the past but it usually worked if I simply retried the connection. Now it happens every time and it won't establish the ssh tunnel. If I connect to the tunnel host with ssh from the command line that works fine, also if I create the tunnel with: $ ssh -L5999:h1:5901 m...@my.home.server.net it also works fine when I then connect to localhost:5999 in vinagre. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: vinagre 2.30.3-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Mon Apr 18 14:33:11 2011 ExecutablePath: /usr/bin/vinagre InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100427.1) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: vinagre UpgradeStatus: Upgraded to natty on 2011-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/vinagre/+bug/764632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
