[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
This is personally impacting my ability to use Chromium to run the F5 SSL VPN, which uses the f5-epi and f5-vpn schemes. There needs to be a way for individual users to add to the whitelist. Adding more schemes like "apt" is just making the issue less painful. -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+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 1861738] [NEW] Proprietary Snap applications are displayed even in "Free Software Only" mode on install.
Public bug reported: When installing Ubuntu with the free software only session, the following installation will not have any proprietary Deb sources enabled, but the Snap sources will be. Gnome Software will then advertise Spotify, Discord, (etc). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 22:44:34 2020 InstallationDate: Installed on 2020-02-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.2-0ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1861738 Title: Proprietary Snap applications are displayed even in "Free Software Only" mode on install. Status in gnome-software package in Ubuntu: New Bug description: When installing Ubuntu with the free software only session, the following installation will not have any proprietary Deb sources enabled, but the Snap sources will be. Gnome Software will then advertise Spotify, Discord, (etc). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 22:44:34 2020 InstallationDate: Installed on 2020-02-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.2-0ubuntu1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1861738/+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 1858336] Re: [qxl] Xorg crashed with assertion failure in DRIMoveBuffersHelper
Set to issue #10 [here](https://gitlab.freedesktop.org/xorg/driver/xf86 -video-qxl/issues/10). ** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/issues #10 https://gitlab.freedesktop.org/xorg/driver/xf86-video-qxl/issues/10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1858336 Title: [qxl] Xorg crashed with assertion failure in DRIMoveBuffersHelper Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-qxl package in Ubuntu: New Bug description: After doing a normal installation with erasing the disk in GNOME Boxes, I cannot log into the Ubuntu Xorg session. Wayland works fine, but this still isn't a workaround if the user wants to use Xorg for any given reason. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 10:21:36 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=3faaad6a-d32e-4d07-877f-3ef17831e142 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: ?-20191223_100556-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr?-20191223_100556-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1858336/+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 1858336] [NEW] Login loops with GNOME Boxes on Xorg
Public bug reported: After doing a normal installation with erasing the disk in GNOME Boxes, I cannot log into the Ubuntu Xorg session. Wayland works fine, but this still isn't a workaround if the user wants to use Xorg for any given reason. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 10:21:36 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Chip/SmartCard, Driver=, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=3faaad6a-d32e-4d07-877f-3ef17831e142 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: ?-20191223_100556-anatol dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr?-20191223_100556-anatol:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal regression reproducible ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1858336 Title: Login loops with GNOME Boxes on Xorg Status in xorg package in Ubuntu: New Bug description: After doing a normal installation with erasing the disk in GNOME Boxes, I cannot log into the Ubuntu Xorg session. Wayland works fine, but this still isn't a workaround if the user wants to use Xorg for any given reason. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 5 10:21:36 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] InstallationDate: Installed on 2020-01-05 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 08e6:4433 Gemalto (was Gemplus) GemPC433-Swap Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1,
[Desktop-packages] [Bug 1853709] Re: lightdm does not greet or present login prompt when resuming from laptop suspend
Happens with the Dell XPS 9570 (Intel-Nvidia) as well on a fresh install. -- 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/1853709 Title: lightdm does not greet or present login prompt when resuming from laptop suspend Status in lightdm package in Ubuntu: Confirmed Bug description: Expected result: when opening laptop lid the lock screen presents itself so I can unlock my session Actual result: the contents of my desktop are visible (windows, etc) and I can move my mouse cursor around but I cannot interact with the desktop session at all. Hovering over UI elements or clicking them has no effect. In order to get the login prompt I have to ctrl+alt+f1, login at the console, and run sudo systemctl restart lightdm, then I can login normally and resume whatever I was doing from before I closed the laptop lid. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: lightdm 1.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Nov 23 09:08:32 2019 InstallationDate: Installed on 2019-11-09 (14 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1853709/+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 1163565] Re: Middle-clicking a link triggers onpaste event
The bug is not present in chromium-browser 65.0.3325.181-0ubuntu1 on 18.04. Thanks. -- 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/1163565 Title: Middle-clicking a link triggers onpaste event Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Incomplete Bug description: Ubuntu release: 12.10 chromium-browser version: 25.0.1364.160-0ubuntu0.12.1 Expected: Consider this bit of HTML: http://google.com/;>Google Middle-clicking the link to Google should open the link in a new tab, but not trigger the onpaste event. Observed: Middle-clicking the link opens the link in a new tab, but does trigger the onpaste event. The same is true on any page with a body onpaste handler. See also https://code.google.com/p/chromium/issues/detail?id=22810, which was fixed in 2009 and is not present in the 22.0.1229.94~r161065-0ubuntu1 package. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1163565/+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 1580692] Re: Dell latitude e6520 display freezes must reboot
[solved?] Hello, I have experienced this issue on two E6520 laptops with i5 processors running the Linux Mint live image for installing Mint version 18 (booted off the USB port.) Both laptops running BIOS version A19, which is the latest version at this time. In my troubleshooting I found this issue continues to happen despite removing the hard drive, cdrom drive, and despite switching from a low quality USB 2.0 thumb drive as the boot device to a high quality USB 3.0 thumb drive. This issue seems to be the same as what is discussed here: http://en.community.dell.com/support-forums/laptop/f/3518/t/19579391 My preliminary testing indicates that the solution may be as simple as ... choosing the option of "Load Defaults" in the BIOS. When you choose this option, you will also be asked if you want to allow the SATA Operation to be changed. I suggest selecting "NO" for the SATA Operation change. Then press "Apply" to confirm the "Load Defaults" command. As far as I can tell, there is no specific setting or combination of settings in the BIOS which causes this issue. That is to say, I am so far not able to replicate this issue after choosing to "Load Defaults" despite the fact that I have set all the BIOS settings back to what they were before choosing to "Load Defaults." Therefore, I think that "Load Defaults" may be clearing up some corruption in the BIOS settings. If this is the case, then it is in theory possible that the BIOS corruption happened due to an upgrade of the BIOS, or a low NVRAM battery. A low NVRAM battery can be tricky in some laptops because it may not cause problems until the main battery is removed from the laptop which leaves the NVRAM totally dependent on the NVRAM battery. I have tested for several hours after loading defaults, with no further crashes. Before loading defaults, I would get at least a couple crashes per hour while doing nothing more than navigating the GUI. I will update this comment if I find any new info or any info which contradicts my preliminary experience so far. x84 -- 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/1580692 Title: Dell latitude e6520 display freezes must reboot Status in firefox package in Ubuntu: New Bug description: This is a fresh install of Ubuntu 16.04LTS 64 on a Dell Latitude E6520 laptop with an Intel core i7-2720QM (4 core) CPU, 8GB RAM and an NVIDIA N12P-NS2 video controller. The display freezes at random (I had this 10 times today with completely different apps running). The mouse still moves but the system does not react to clicks or keypresses (not even Ctrl-Alt-Del etc. and I can't access terminals at Ctrl+Alt+F1 etc.) It does not shut down gracefully when the power button is pressed. The system is however still active and can be accessed externally through SSH. The mouse and screen seems slightly less responsive than usual a few seconds before the freeze so that I can "feel it coming". However, it is hardly noticeable. I noticed that the underside of the laptop is sometimes very hot when the display freezes, but it is not systematic, sometimes the freeze happens after the laptop had time to cool before booting and hasn't got hot yet. Until recently this laptop was running windows 7 64 pro without any problem. I have performed a full hardware test of the laptop (via setup) only a couple of days ago, there was no issue. I attached the output of dmesg and the Xorg.0.log file. This is not a critical system to me but I thought I'd report the bug for all intents and purposes, and I'd rather not reinstall windows on it if it can be helped ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580692/+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 1433032] Re: Starting Chrome makes gnome-keyring-daemon loading 100% of a CPU thread for 5 at least mins
I'm using Chrome Version 41.0.2272.89 (64-bit). I'm running Linux Mint 17.1 Cinnamon I went in and removed some of the many, many stored passwords in Menu Preferences Passwords and Keys The ~/.local/share/keyrings/login.keyring file was 1018K before, and 765K after working through about one-third of the list of passwords. Starting up Chrome, I was asked to login again. After I did that, things appear to be working smoothly. I'll update after some more extended use. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1433032 Title: Starting Chrome makes gnome-keyring-daemon loading 100% of a CPU thread for 5 at least mins Status in gnome-keyring package in Ubuntu: Confirmed Bug description: This is Ubuntu 14.04 LTS x64. I removed good amount of remembered passwords but there are no noticable changes. Chrome is v 40.0.2214.10 beta (64-bit) --- Regards respect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1433032/+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 1405232] [NEW] ping reports wrong IP responding under certain conditions
Public bug reported: Description:Ubuntu 14.04.1 LTS Release:14.04 iputils-ping: Installed: 3:20121221-4ubuntu1.1 Candidate: 3:20121221-4ubuntu1.1 ping will report the incorrect reply IP address under certain, specific conditions, and is repeatable. This is how to re-create the issue: 1. Start pinging an IP where you get an ICMP error message from some other device (RFC792 lists errors). For instance: Destination IP is offline and the last-hop router reports message type Destination Unreachable. I assume this would work for any ICMP error, though. 2. When the device comes back online, ping reports replies from the other device, when it should report replies from the device that is sending the Echo Reply messages. 3. If the ping is stopped and restarted after the device is up, it reports the correct IP address again. Other ping utilities do not exhibit this behavior. Example output (Destination that was pinged was 172.21.56.50, last hop router was 172.21.25.103): circle@circle:~$ /bin/ping 172.21.56.50 PING 172.21.56.50 (172.21.56.50) 56(84) bytes of data. From 172.21.25.103 icmp_seq=1 Destination Host Unreachable From 172.21.25.103 icmp_seq=2 Destination Host Unreachable From 172.21.25.103 icmp_seq=3 Destination Host Unreachable From 172.21.25.103 icmp_seq=4 Destination Host Unreachable From 172.21.25.103 icmp_seq=5 Destination Host Unreachable From 172.21.25.103 icmp_seq=6 Destination Host Unreachable 64 bytes from 172.21.25.103: icmp_seq=7 ttl=63 time=0.689 ms 64 bytes from 172.21.25.103: icmp_seq=8 ttl=63 time=0.635 ms 64 bytes from 172.21.25.103: icmp_seq=9 ttl=63 time=0.656 ms 64 bytes from 172.21.25.103: icmp_seq=10 ttl=63 time=0.822 ms 64 bytes from 172.21.25.103: icmp_seq=11 ttl=63 time=0.785 ms ^C --- 172.21.56.50 ping statistics --- 11 packets transmitted, 5 received, +6 errors, 54% packet loss, time 10023ms rtt min/avg/max/mdev = 0.635/0.717/0.822/0.077 ms, pipe 3 circle@circle:~$ /bin/ping 172.21.56.50 PING 172.21.56.50 (172.21.56.50) 56(84) bytes of data. 64 bytes from 172.21.56.50: icmp_seq=1 ttl=63 time=0.737 ms 64 bytes from 172.21.56.50: icmp_seq=2 ttl=63 time=0.646 ms 64 bytes from 172.21.56.50: icmp_seq=3 ttl=63 time=0.626 ms ^C --- 172.21.56.50 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 1998ms rtt min/avg/max/mdev = 0.626/0.669/0.737/0.056 ms ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: iputils-ping 3:20121221-4ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Dec 23 10:50:35 2014 InstallationDate: Installed on 2014-10-08 (76 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) SourcePackage: iputils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iputils (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 iputils in Ubuntu. https://bugs.launchpad.net/bugs/1405232 Title: ping reports wrong IP responding under certain conditions Status in iputils package in Ubuntu: New Bug description: Description: Ubuntu 14.04.1 LTS Release: 14.04 iputils-ping: Installed: 3:20121221-4ubuntu1.1 Candidate: 3:20121221-4ubuntu1.1 ping will report the incorrect reply IP address under certain, specific conditions, and is repeatable. This is how to re-create the issue: 1. Start pinging an IP where you get an ICMP error message from some other device (RFC792 lists errors). For instance: Destination IP is offline and the last-hop router reports message type Destination Unreachable. I assume this would work for any ICMP error, though. 2. When the device comes back online, ping reports replies from the other device, when it should report replies from the device that is sending the Echo Reply messages. 3. If the ping is stopped and restarted after the device is up, it reports the correct IP address again. Other ping utilities do not exhibit this behavior. Example output (Destination that was pinged was 172.21.56.50, last hop router was 172.21.25.103): circle@circle:~$ /bin/ping 172.21.56.50 PING 172.21.56.50 (172.21.56.50) 56(84) bytes of data. From 172.21.25.103 icmp_seq=1 Destination Host Unreachable From 172.21.25.103 icmp_seq=2 Destination Host Unreachable From 172.21.25.103 icmp_seq=3 Destination Host Unreachable From 172.21.25.103 icmp_seq=4 Destination Host Unreachable From 172.21.25.103 icmp_seq=5 Destination Host Unreachable From 172.21.25.103 icmp_seq=6 Destination Host Unreachable 64 bytes from 172.21.25.103: icmp_seq=7 ttl=63 time=0.689 ms 64 bytes from 172.21.25.103: icmp_seq=8 ttl=63 time=0.635 ms 64 bytes from 172.21.25.103: icmp_seq=9 ttl=63 time=0.656 ms 64 bytes from 172.21.25.103: icmp_seq=10 ttl=63
[Desktop-packages] [Bug 303862] Re: Pidgin freezes when generating new OTR private key
haveged fixed my problem on debian as well. 3s ! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/303862 Title: Pidgin freezes when generating new OTR private key Status in Off-the-Record Messaging plugin for pidgin: New Status in “pidgin” package in Ubuntu: Invalid Status in “pidgin-otr” package in Ubuntu: Confirmed Bug description: Binary package hint: pidgin Package: pidgin-otr (Intrepid) 3.2.0-1 Version of Ubuntu: Ubuntu 8.10 (Intrepid) Systems used: AMD XP 3200+, 1 GB DDR, 160 GB HDD running Ubuntu 8.10 HP dv9500t laptop, 2.0 Ghz Core 2 Duo, 2 GB DDR, 160 GB HDD running of Ubuntu 8.10 LiveCD When I enable the pidgin-otr plugin and attempt to generate a new private key, Pidgin pops up a dialog box telling me that a new private key is being generated. However, key generation never completes and eventually I receive a notification that Pidgin or Generating Private Key is not responding. I have attempted to generate keys for both a XMPP (GMail Account) and an AIM account with the same result, and have repeated the process on both systems multiple times. I have successfully generated keys using the same version of OTR on Windows XP SP3 on the HP dv9500t laptop. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/pidgin Package: pidgin 1:2.5.2-0ubuntu1 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pidgin Uname: Linux 2.6.27-9-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pidgin-otr/+bug/303862/+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 1098233] Re: flashplugin-installer do not honore proxy settings
Aso affects 12.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1098233 Title: flashplugin-installer do not honore proxy settings Status in Adobe Flash Plugin Tools: New Status in “flashplugin-nonfree” package in Ubuntu: Confirmed Bug description: Description: Ubuntu 12.10 Release: 12.10 Codename: quantal flashplugin-installer: Installato: 11.2.202.258ubuntu0.12.10.1 Candidato: 11.2.202.261ubuntu0.12.10.1 Tabella versione: 11.2.202.261ubuntu0.12.10.1 0 500 http://archive.ubuntu.com/ubuntu/ quantal-updates/multiverse i386 Packages 500 http://archive.ubuntu.com/ubuntu/ quantal-security/multiverse i386 Packages *** 11.2.202.258ubuntu0.12.10.1 0 100 /var/lib/dpkg/status 11.2.202.243ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ quantal/multiverse i386 Packages flashplugin-installer do not honore proxy settings so cannot download the proxy so my update are frozen on Elaborazione dei trigger per update-notifier-common... flashplugin-installer: downloading http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.261.orig.tar.gz already reported: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1037662 Very old issue still not solved... :-( # Workaround for user with same issue As a workaround... while the apt-get update process is frozen on the row below Elaborazione dei trigger per update-notifier-common... flashplugin-installer: downloading http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.261.orig.tar.gz Opening another terminal... wget http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.261.orig.tar.gz sudo /usr/lib/flashplugin-installer/install_plugin $(pwd)/adobe-flashplugin_11.2.202.261.orig.tar.gz rm adobe-flashplugin_11.2.202.261.orig.tar.gz then to release the frozen update process, type: sudo killall dpkg or reboot the pc, then type: sudo dpkg --configure -a to check and put in a good state the apt env... # -- Thanks ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: flashplugin-installer 11.2.202.258ubuntu0.12.10.1 Uname: Linux 3.7.1-030701-generic i686 ApportVersion: 2.6.1-0ubuntu9 Architecture: i386 Date: Thu Jan 10 15:39:05 2013 MarkForUpload: True SourcePackage: flashplugin-nonfree UpgradeStatus: Upgraded to quantal on 2012-07-02 (192 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/1098233/+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 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate
Please.. somebody could post the entire configuration where appears certs...=true where system-ca-cert is located. Thanks -- 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/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate Status in “network-manager” package in Ubuntu: Confirmed Bug description: I can connect to Eduroam in 12.10 and any other previous release, but not in 13.04. I checked, my name and password are correct, all settings are the same as in 12.10. Network properties: security: WPA - WPA2 enterprise authentication: protected EAP (PEAP) CA certificate: none PEAP version: automatic inner autentication: MSCHAPv2 username: (required) password: (required) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 ApportVersion: 2.8-0ubuntu2 Architecture: i386 CasperVersion: 1.330 Date: Thu Jan 24 21:32:25 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.43.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.149 metric 9 LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130123) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set 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 AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 16703fabc-9519-49bd-a4af-45fbfb7d660e 802-3-ethernet1359062570 Thu 24 Jan 2013 09:22:50 PM UTCyes no /org/freedesktop/NetworkManager/Settings/1 eduroam 00f69a95-4a1b-436c-b462-a284f45fbaa1 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 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.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1104476/+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 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate
Dear friends... I have same problem, I did test with live cd Ubuntu 12.08 and it worked smooth, but when I return to 13.04 I got the same problem. Only we have to wait the fix for this bug.. thanks for share your experiences. -- 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/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate Status in “network-manager” package in Ubuntu: Confirmed Bug description: I can connect to Eduroam in 12.10 and any other previous release, but not in 13.04. I checked, my name and password are correct, all settings are the same as in 12.10. Network properties: security: WPA - WPA2 enterprise authentication: protected EAP (PEAP) CA certificate: none PEAP version: automatic inner autentication: MSCHAPv2 username: (required) password: (required) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 ApportVersion: 2.8-0ubuntu2 Architecture: i386 CasperVersion: 1.330 Date: Thu Jan 24 21:32:25 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.43.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.149 metric 9 LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130123) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set 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 AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 16703fabc-9519-49bd-a4af-45fbfb7d660e 802-3-ethernet1359062570 Thu 24 Jan 2013 09:22:50 PM UTCyes no /org/freedesktop/NetworkManager/Settings/1 eduroam 00f69a95-4a1b-436c-b462-a284f45fbaa1 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 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.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1104476/+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 1163565] Re: Middle-clicking a link triggers onpaste event
This bug is still present in Ubuntu 13.04 / chromium-browser
25.0.1364.160-0ubuntu3
--
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/1163565
Title:
Middle-clicking a link triggers onpaste event
Status in “chromium-browser” package in Ubuntu:
New
Bug description:
Ubuntu release: 12.10
chromium-browser version: 25.0.1364.160-0ubuntu0.12.1
Expected: Consider this bit of HTML:
html
body onpaste=alert('Hi');
a href=http://google.com/;Google/a
/body
/html
Middle-clicking the link to Google should open the link in a new tab,
but not trigger the onpaste event.
Observed: Middle-clicking the link opens the link in a new tab, but
does trigger the onpaste event. The same is true on any page with a
body onpaste handler.
See also https://code.google.com/p/chromium/issues/detail?id=22810,
which was fixed in 2009 and is not present in the
22.0.1229.94~r161065-0ubuntu1 package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1163565/+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 1173673] Re: 13.04 - marvell driver bugs- surface pro w/ avastar 350N
I am also seeing this issue on 13.04 final. I can't connect to open networks either. Any solutions? -- 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/1173673 Title: 13.04 - marvell driver bugs- surface pro w/ avastar 350N Status in “network-manager” package in Ubuntu: New Bug description: I would like to comment that I did not spend a lot of time debugging this due to time constraints. Then again, something like this should probably work out of the box. Upon installing the 13.04 beta2 (about 1-2 weeks ago, whatever release that was), I attempted to use the wifi on my MS surface pro. This was a fresh install, I re-formatted the partition of the hard drive that ubuntu sits on. I downloaded updates, etc, via a usb-ethernet interface. The wifi widget in the top right hand corner shows 3 active instances of the wireless network interface for the marvell chip. http://i.imgur.com/Y2vTdFd.png When switching the wireless functionality to ON, they seem to be competing with each other. All 3 of them show that they see the surrounding wifi networks but I can never actually get a connection. I get a prompt for the network password, I enter it, and then 1-2 seconds later I get another prompt, ad nauseum. I am not simply mis- typing the password. I remember seeing this behaviour before when I was trying to kluge together a working wifi driver with a 12.04 installation on my surface pro by grabbing the marvell driver packages from the 13.04 beta and manually implementing them. This suggests to me that there is something wrong with the driver for that particular chipset, rather than an installation error on my end. Though, I could be wrong. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1173673/+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 1163565] [NEW] Middle-clicking a link triggers onpaste event
Public bug reported:
Ubuntu release: 12.10
chromium-browser version: 25.0.1364.160-0ubuntu0.12.1
Expected: Consider this bit of HTML:
html
body onpaste=alert('Hi');
a href=http://google.com/;Google/a
/body
/html
Middle-clicking the link to Google should open the link in a new tab,
but not trigger the onpaste event.
Observed: Middle-clicking the link opens the link in a new tab, but does
trigger the onpaste event. The same is true on any page with a body
onpaste handler.
See also https://code.google.com/p/chromium/issues/detail?id=22810,
which was fixed in 2009 and is not present in the
22.0.1229.94~r161065-0ubuntu1 package.
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
--
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/1163565
Title:
Middle-clicking a link triggers onpaste event
Status in “chromium-browser” package in Ubuntu:
New
Bug description:
Ubuntu release: 12.10
chromium-browser version: 25.0.1364.160-0ubuntu0.12.1
Expected: Consider this bit of HTML:
html
body onpaste=alert('Hi');
a href=http://google.com/;Google/a
/body
/html
Middle-clicking the link to Google should open the link in a new tab,
but not trigger the onpaste event.
Observed: Middle-clicking the link opens the link in a new tab, but
does trigger the onpaste event. The same is true on any page with a
body onpaste handler.
See also https://code.google.com/p/chromium/issues/detail?id=22810,
which was fixed in 2009 and is not present in the
22.0.1229.94~r161065-0ubuntu1 package.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1163565/+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 1071578] Re: Transmission starts saving to a folder within Downloads and will not allow me to select another folder to save to
As a messy short-term workaround, I've been able to change the save-to location by picking 'other' from the drop-down box in preferences, selecting the desired folder (e.g. Downloads), and editing the 'Location' string to make sure there's no suffix at the end (e.g. 'Downloads', not 'Downloads/xxx'). Then pressing ok. For me, if the string isn't edited manually it auto-completes to the nested folder, so even if the Downloads folder is clicked on, the location string becomes 'Downloads/xxx' where x is the destination folder of the previously added torrent. Hope that makes sense. The same steps also work for moving an individual torrent through the right-click-'set location' dialog. -- 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/1071578 Title: Transmission starts saving to a folder within Downloads and will not allow me to select another folder to save to Status in “transmission” package in Ubuntu: Confirmed Bug description: When using Transmission, I do not modify the default setting 'Save to Location', it should still be set to Downloads. But, if I download a torrent that creates a folder within Downloads, or make an empty folder myself, Transmission changes the Save-to location to this folder. The drop down in Preferences is not responsive, I click Downloads but it goes back to saying the name of whichever folder it has selected. Selecting 'Other' and choosing the folder from within the dialogue changes nothing. I have deleted ~/.config/transmission. This did not solve the problem, it occurred again as soon as there was a folder within my Donwloads dir. What is expected to happen: Transmission saves all files and folders into Downloads and this setting does not change. What is happening: Transmission saves files into any folder it can find within Downloads. It changes the setting in Preferences and does not allow it to be changed back. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: transmission-gtk 2.61-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu4 Architecture: amd64 Date: Thu Oct 25 21:01:49 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MarkForUpload: True ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: Upgraded to quantal on 2012-09-18 (37 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1071578/+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
