[Desktop-packages] [Bug 860003] Re: running LightDM in test mode doesn't work
Got exactly the same. L ~ : lightdm --test-mode Running inside an X server requires Xephyr to be installed but it cannot be found. Please install it or update your PATH environment variable. L ~ : cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=15.10 DISTRIB_CODENAME=wily DISTRIB_DESCRIPTION="Ubuntu 15.10" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/860003 Title: running LightDM in test mode doesn't work Status in Light Display Manager: Fix Released Status in lightdm package in Ubuntu: Fix Released Bug description: As described on https://wiki.ubuntu.com/LightDM, I should be able to run lightdm --test-mode in a console. However, when I try that, I first get this error: matthijs@Simba:~$ lightdm --test-mode Running inside an X server requires Xephyr to be installed but it cannot be found. Please install it or update your PATH environment variable. When I then install the xserver-xephyr package and try again, a small window opens for less than a second and then closes again. No errors, no testing environment. Nothing. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Mon Sep 26 22:01:52 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1) SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-09-22 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/860003/+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 1029702] Re: Chromium CPU usage high with Pepper Flash
The same happens on Ubuntu 15.04. Adobe Flash Player - Version: 11.2.999.999 Shockwave Flash 11.2 r999 Name: Shockwave Flash Description:Shockwave Flash 11.2 r999 Version:11.2.999.999 Place: /usr/lib/adobe-flashplugin/libpepflashplayer.so Type: PPAPI -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1029702 Title: Chromium CPU usage high with Pepper Flash Status in chromium-browser package in Ubuntu: Confirmed Bug description: Hi, Chromium used too much CPU usage with Pepper Flash. I don't know if the Pepper API has really had time to be tested in the real world? New technology may sometimes cause problems, consume more resources until extensive rigorous testing until fine-tuning for the performance. I found Chromium had higher CPU usage than normal when playing an online game using Pepper Flash. chrome://plugins/ Flash (2 files) - Version: 11.3.31.103 Shockwave Flash 11.3 r31 Namn: Shockwave Flash Beskrivning: Shockwave Flash 11.3 r31 Version: 11.3.31.103 Plats:/usr/lib/chromium-browser/libpepflashplayer.so Typ: PPAPI (utanför process) MIME-typer: MIME-typBeskrivning Filtillägg application/x-shockwave-flash Shockwave Flash .swf application/futuresplash FutureSplash Player .spl See also: Re: Chromium Flash Pepper on precise, how? http://ubuntuforums.org/showpost.php?p=12072504postcount=13 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 18.0.1025.168~r134367-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-27.43-generic 3.2.21 Uname: Linux 3.2.0-27-generic i686 NonfreeKernelModules: wl ApportVersion: 2.0.1-0ubuntu11 Architecture: i386 ChromiumPrefs: can't open profile /root/.config/chromium/Default/Preferences Date: Fri Jul 27 01:30:32 2012 Desktop-Session: DESKTOP_SESSION = None XDG_CONFIG_DIRS = None XDG_DATA_DIRS = None Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None ExecutablePath: /usr/lib/chromium-browser/chromium-browser InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423) ProcEnviron: SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS=--ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-version=11.3.31.103 modified.conffile..etc.chromium.browser.default: # Default settings for chromium-browser. This file is sourced by /bin/sh from # /usr/bin/chromium-browser # Options to pass to chromium-browser CHROMIUM_FLAGS=--ppapi-flash-path=/usr/lib/chromium-browser/libpepflashplayer.so --ppapi-flash-version=11.3.31.103 mtime.conffile..etc.chromium.browser.default: 2012-07-03T19:49:00.118816 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1029702/+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 1241258] Re: wallpaper doesn't span across multiple monitors, white background shows instead
*** This bug is a duplicate of bug 1241252 *** https://bugs.launchpad.net/bugs/1241252 I have the same issue. When I switch between the screen of my laptop and the external monitor, the background of the external one suddenly changes to blank white sometimes (the background colour of the launcher on the external screen doesn't change but the notable objects from the wallpaper shown below the launcher aren't there so the launcher keeps the colour but misses the background image). Right click on the blank white screen shows the menu and icons are visible as well. I think it's not a duplicate of bug #1241252: the top menu bar doesn't change. I'm not sure it matters but according to lshw, I has an nVidia GT218M [NVS 3100M] and I use the binary 319.60 driver (nvidia-319-updates). -- 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/1241258 Title: wallpaper doesn't span across multiple monitors, white background shows instead Status in “nautilus” package in Ubuntu: Incomplete Bug description: Wallpaper should span across my two monitors (it worked in ubuntu 13.04). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 17 19:38:59 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1263x880+655+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'236' InstallationDate: Installed on 2013-10-17 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1241258/+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 1241258] Re: wallpaper doesn't span across multiple monitors, white background shows instead
*** This bug is a duplicate of bug 1241252 *** https://bugs.launchpad.net/bugs/1241252 s/has/have/, sorry :) -- 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/1241258 Title: wallpaper doesn't span across multiple monitors, white background shows instead Status in “nautilus” package in Ubuntu: Incomplete Bug description: Wallpaper should span across my two monitors (it worked in ubuntu 13.04). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 17 19:38:59 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'1263x880+655+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'236' InstallationDate: Installed on 2013-10-17 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1241258/+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 728804] Re: NetworkManager connection timeout on Wlan0
Hi! I bought a new Acer Aspire E1-571-3114G50Mnks laptop for my father a few weeks ago and installed Ubuntu 13.04 on it. It seems I have a similar problem. The wireless network is hidden. Here are the last lines of the output of lspci -v...: 03:00.0 Network controller: Intel Corporation Centrino Wireless-N 105 (rev c4) Subsystem: Intel Corporation Centrino Wireless-N 105 BGN Flags: bus master, fast devsel, latency 0, IRQ 42 Memory at c050 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [e0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number confidential Kernel driver in use: iwlwifi ...the output of cat /etc/NetworkManager/system-connections/alpha- canis-majoris...: [connection] id=alpha-canis-majoris uuid=does-not-matter type=802-11-wireless [802-11-wireless] ssid=alpha-canis-majoris mode=infrastructure mac-address=confidential security=802-11-wireless-security [802-11-wireless-security] key-mgmt=wpa-psk psk=confidential [ipv4] method=auto [ipv6] method=ignore ...and the relevant lines of the output of grep -i networkmanager /var/log/syslog: Apr 28 13:30:30 gepem NetworkManager[1000]: info Activation (wlan0) starting connection 'alpha-canis-majoris' Apr 28 13:30:30 gepem NetworkManager[1000]: info (wlan0): device state change: disconnected - prepare (reason 'none') [30 40 0] Apr 28 13:30:30 gepem NetworkManager[1000]: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Apr 28 13:30:30 gepem NetworkManager[1000]: info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Apr 28 13:30:30 gepem NetworkManager[1000]: info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Apr 28 13:30:30 gepem NetworkManager[1000]: info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Apr 28 13:30:30 gepem NetworkManager[1000]: info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Apr 28 13:30:30 gepem NetworkManager[1000]: info (wlan0): device state change: prepare - config (reason 'none') [40 50 0] Apr 28 13:30:30 gepem NetworkManager[1000]: info Activation (wlan0/wireless): connection 'alpha-canis-majoris' has security, and secrets exist. No new secrets needed. Apr 28 13:30:30 gepem NetworkManager[1000]: info Config: added 'ssid' value 'alpha-canis-majoris' Apr 28 13:30:30 gepem NetworkManager[1000]: info Config: added 'scan_ssid' value '1' Apr 28 13:30:30 gepem NetworkManager[1000]: info Config: added 'key_mgmt' value 'WPA-PSK' Apr 28 13:30:30 gepem NetworkManager[1000]: info Config: added 'psk' value 'omitted' Apr 28 13:30:30 gepem NetworkManager[1000]: info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Apr 28 13:30:30 gepem NetworkManager[1000]: info Config: set interface ap_scan to 1 Apr 28 13:30:30 gepem NetworkManager[1000]: info (wlan0): supplicant interface state: inactive - scanning Apr 28 13:30:30 gepem NetworkManager[1000]: info (wlan0): supplicant interface state: scanning - authenticating Apr 28 13:30:55 gepem NetworkManager[1000]: warn Activation (wlan0/wireless): association took too long, failing activation. Apr 28 13:30:55 gepem NetworkManager[1000]: info (wlan0): device state change: config - failed (reason 'SSID not found') [50 120 53] Apr 28 13:30:55 gepem NetworkManager[1000]: warn Activation (wlan0) failed for connection 'alpha-canis-majoris' Apr 28 13:30:55 gepem NetworkManager[1000]: info (wlan0): supplicant interface state: authenticating - disconnected Apr 28 13:30:55 gepem NetworkManager[1000]: info (wlan0): device state change: failed - disconnected (reason 'none') [120 30 0] Apr 28 13:30:55 gepem NetworkManager[1000]: info (wlan0): deactivating device (reason 'none') [0] Is there a way to force Network Manager to wait more? I'd like to avoid this message somehow: association took too long, failing activation. :) By the way, I had a timeout/delay problem on my Dell machine as well when I tried to connect to an OpenVPN network (connecting to other OpenVPN networks worked like a charm) with Network Manager on Ubuntu 12.10 but I was able to connect from my CentOS virtual machine with an older version of NM. But I think it's a different story. :) -- 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/728804 Title: NetworkManager connection timeout on Wlan0 Status in “network-manager” package in Ubuntu: Expired Bug description: Binary package hint: network-manager I am trying to connect wlan0 to an access point that is hidden broadcast, put all data in network-manager but takes longer to connect. Occasionally the connection drops and must try to reconnect several times. Description: Ubuntu 10.04.2 LTS Release:
[Desktop-packages] [Bug 728804] Re: NetworkManager connection timeout on Wlan0
Oops... I figured out that I pressed a wrong button on the web interface of my OpenWrt router yesterday when I set the MAC filter. Sorry... It works now. -- 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/728804 Title: NetworkManager connection timeout on Wlan0 Status in “network-manager” package in Ubuntu: Expired Bug description: Binary package hint: network-manager I am trying to connect wlan0 to an access point that is hidden broadcast, put all data in network-manager but takes longer to connect. Occasionally the connection drops and must try to reconnect several times. Description: Ubuntu 10.04.2 LTS Release: 10.04 network-manager: Instalado: 0.8-0ubuntu3 Candidato: 0.8-0ubuntu3 Tabela de versão: *** 0.8-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status network-manager-gnome: Instalado: 0.8-0ubuntu3 Candidato: 0.8-0ubuntu3 Tabela de versão: *** 0.8-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status Logs in SYSLOG: Mar 3 20:35:22 bruno-desktop wpa_supplicant[873]: last message repeated 9 times Mar 3 20:35:22 bruno-desktop NetworkManager: info Activation (wlan0/wireless): association took too long. Mar 3 20:35:22 bruno-desktop NetworkManager: info (wlan0): device state change: 5 - 6 (reason 0) Mar 3 20:35:22 bruno-desktop NetworkManager: info Activation (wlan0/wireless): asking for new secrets Mar 3 20:35:22 bruno-desktop NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... Mar 3 20:35:22 bruno-desktop NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... Mar 3 20:35:22 bruno-desktop NetworkManager: info (wlan0): device state change: 6 - 4 (reason 0) Mar 3 20:35:22 bruno-desktop NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... Mar 3 20:35:22 bruno-desktop NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. Mar 3 20:35:22 bruno-desktop NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... Mar 3 20:35:22 bruno-desktop NetworkManager: info (wlan0): device state change: 4 - 5 (reason 0) Mar 3 20:35:22 bruno-desktop NetworkManager: info Activation (wlan0/wireless): connection 'star00' has security, and secrets exist. No new secrets needed. Mar 3 20:35:22 bruno-desktop NetworkManager: info Config: added 'ssid' value 'star00' Mar 3 20:35:22 bruno-desktop NetworkManager: info Config: added 'scan_ssid' value '1' Mar 3 20:35:22 bruno-desktop NetworkManager: info Config: added 'key_mgmt' value 'NONE' Mar 3 20:35:22 bruno-desktop NetworkManager: info Config: added 'auth_alg' value 'OPEN' Mar 3 20:35:22 bruno-desktop NetworkManager: info Config: added 'wep_key0' value 'omitted' Mar 3 20:35:22 bruno-desktop NetworkManager: info Config: added 'wep_tx_keyidx' value '0' Mar 3 20:35:22 bruno-desktop NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed Mar 3 20:35:22 bruno-desktop NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed Mar 3 20:35:22 bruno-desktop NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Mar 3 20:35:22 bruno-desktop NetworkManager: info (wlan0): supplicant connection state: scanning - disconnected Mar 3 20:35:22 bruno-desktop NetworkManager: info Config: set interface ap_scan to 1 Mar 3 20:35:26 bruno-desktop NetworkManager: info (wlan0): supplicant connection state: disconnected - scanning Mar 3 20:35:27 bruno-desktop wpa_supplicant[873]: WPS-AP-AVAILABLE Mar 3 20:38:49 bruno-desktop NetworkManager: info (wlan0): device state change: 5 - 3 (reason 39) Mar 3 20:38:49 bruno-desktop NetworkManager: info (wlan0): deactivating device (reason: 39). Mar 3 20:38:51 bruno-desktop NetworkManager: info (wlan0): device state change: 3 - 2 (reason 0) Mar 3 20:38:51 bruno-desktop NetworkManager: info (wlan0): deactivating device (reason: 0). Mar 3 20:38:51 bruno-desktop NetworkManager: info (wlan0): taking down device. Mar 3 20:38:59 bruno-desktop NetworkManager: info (wlan0): bringing up device. Mar 3 20:38:59 bruno-desktop NetworkManager: info (wlan0): supplicant interface state: starting - ready Mar 3 20:38:59 bruno-desktop NetworkManager: info (wlan0): device state change: 2 - 3 (reason 42) Mar 3 20:38:59 bruno-desktop wpa_supplicant[873]: Failed to initiate AP scan. Mar 3 20:39:21 bruno-desktop wpa_supplicant[873]: WPS-AP-AVAILABLE I tried to disconnect and connect the interface on the icon of network-manager and this appears in the logs,
[Desktop-packages] [Bug 455792] Re: deluge doesn't open .torrent files from firefox while apparmor is on
The problem still exists on Ubuntu 12.10. -- 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/455792 Title: deluge doesn't open .torrent files from firefox while apparmor is on Status in “firefox” package in Ubuntu: Fix Released Status in “firefox” source package in Lucid: Fix Released Status in “firefox” source package in Karmic: In Progress Bug description: Binary package hint: firefox-3.5 If I open firefox downloaded torrent file with deluge I get couldn't be open because of unknown error (I have Russian locale; so I'm not sure about exact English message). If I turn apparmor off everything works fine. To reproduce: 1) Start downloading torrent with firefox. 2) Select open with deluge. What happens: Couldn't open because of unknown error What should happen: Deluge should start. ProblemType: Bug Architecture: amd64 Date: Tue Oct 20 00:25:27 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: firefox-3.5 3.5.3+build1+nobinonly-0ubuntu4 ProcEnviron: PATH=(custom, user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.46-generic SourcePackage: firefox-3.5 Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/455792/+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 455792] Re: deluge doesn't open .torrent files from firefox while apparmor is on
** Package changed: firefox-3.5 (Ubuntu) = firefox (Ubuntu) -- 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/455792 Title: deluge doesn't open .torrent files from firefox while apparmor is on Status in “firefox” package in Ubuntu: Fix Released Status in “firefox” source package in Lucid: Fix Released Status in “firefox” source package in Karmic: In Progress Bug description: Binary package hint: firefox-3.5 If I open firefox downloaded torrent file with deluge I get couldn't be open because of unknown error (I have Russian locale; so I'm not sure about exact English message). If I turn apparmor off everything works fine. To reproduce: 1) Start downloading torrent with firefox. 2) Select open with deluge. What happens: Couldn't open because of unknown error What should happen: Deluge should start. ProblemType: Bug Architecture: amd64 Date: Tue Oct 20 00:25:27 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: firefox-3.5 3.5.3+build1+nobinonly-0ubuntu4 ProcEnviron: PATH=(custom, user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.46-generic SourcePackage: firefox-3.5 Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/455792/+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 455792] Re: deluge doesn't open .torrent files from firefox while apparmor is on
Same here on Ubuntu 12.04 (Precise Pangolin) with Firefox (aa-enforced) and Deluge. -- 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/455792 Title: deluge doesn't open .torrent files from firefox while apparmor is on Status in “firefox” package in Ubuntu: Fix Released Status in “firefox” source package in Lucid: Fix Released Status in “firefox” source package in Karmic: In Progress Bug description: Binary package hint: firefox-3.5 If I open firefox downloaded torrent file with deluge I get couldn't be open because of unknown error (I have Russian locale; so I'm not sure about exact English message). If I turn apparmor off everything works fine. To reproduce: 1) Start downloading torrent with firefox. 2) Select open with deluge. What happens: Couldn't open because of unknown error What should happen: Deluge should start. ProblemType: Bug Architecture: amd64 Date: Tue Oct 20 00:25:27 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: firefox-3.5 3.5.3+build1+nobinonly-0ubuntu4 ProcEnviron: PATH=(custom, user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.46-generic SourcePackage: firefox-3.5 Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/455792/+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
