[Desktop-packages] [Bug 1802225] [NEW] LightDM login doesn't display after screen lock
Public bug reported: When locking the screen via the xfce menu or light-locker tool the screen sits at a blank/black screen. Moving the mouse or pressing a button on the keyboard does nothing. After searching I found I could just enter my password blindly and it would unlock the screen. Also going to a console tty and back to the graphical login would then show a login screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 Uname: Linux 4.19.0-041900-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 8 13:29:14 2018 InstallationDate: Installed on 2017-11-06 (366 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) LightdmConfig: [LightDM] logind-check-graphical=true display-setup-script=xrandr --output eDP-1 --primary SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1802225 Title: LightDM login doesn't display after screen lock Status in lightdm package in Ubuntu: New Bug description: When locking the screen via the xfce menu or light-locker tool the screen sits at a blank/black screen. Moving the mouse or pressing a button on the keyboard does nothing. After searching I found I could just enter my password blindly and it would unlock the screen. Also going to a console tty and back to the graphical login would then show a login screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 Uname: Linux 4.19.0-041900-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 8 13:29:14 2018 InstallationDate: Installed on 2017-11-06 (366 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) LightdmConfig: [LightDM] logind-check-graphical=true display-setup-script=xrandr --output eDP-1 --primary SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1802225/+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 1265898] Re: thunderbird doesn't remember maximized window state in Ubuntu Gnome
Cf.: https://bugzilla.mozilla.org/show_bug.cgi?id=732812 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1265898 Title: thunderbird doesn't remember maximized window state in Ubuntu Gnome Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Not sure if this is thunderbird or gnome-shell related issue. Steps to reproduce: 1. Run thunderbird. 2. Maximize thunderbird window. 3. Close thunderbird. 4. Run thunderbird again. 5. Notice that thunderbird window is not maximized - maximized window state was not saved during closing. Expected behaviour: In 5. thudnderbird window is open in maximized state. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: thunderbird 1:24.2.0+build1-0ubuntu1 Uname: Linux 3.13.0-031300rc6-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.12.7-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dotnokato 1431 F pulseaudio /dev/snd/pcmC0D0p: dotnokato 1431 F...m pulseaudio BuildID: 20131206222054 Channel: Unavailable CurrentDesktop: GNOME Date: Fri Jan 3 21:02:28 2014 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-15 (79 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) IpRoute: default via 10.100.10.1 dev eth0 proto static 10.100.10.0/24 dev eth0 proto kernel scope link src 10.100.10.8 metric 1 10.100.10.0/24 dev wlan0 proto kernel scope link src 10.100.10.12 metric 9 Plugins: iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Gnome Shell Integration - /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell) PrefSources: prefs.js [Profile]/extensions/gnomeintegrat...@davidmartinez.net/defaults/preferences/gnomeintegration.js Profiles: Profile0 (Default) - LastVersion=24.2.0/20131206222054 (In use) RelatedPackageVersions: rhythmbox-mozilla 3.0.1-1ubuntu8 gnome-shell 3.8.4-0ubuntu6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to trusty on 2013-11-05 (59 days ago) dmi.bios.date: 05/08/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68TT2 Ver. F.07 dmi.board.name: 30B0 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 40.15 dmi.chassis.asset.tag: CNU7110B09 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68TT2Ver.F.07:bd05/08/2007:svnHewlett-Packard:pnHPCompaqnx6325(EY349EA#AKD):pvrF.07:rvnHewlett-Packard:rn30B0:rvrKBCVersion40.15:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx6325 (EY349EA#AKD) dmi.product.version: F.07 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1265898/+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 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Actually (cf. my comment above) the Manager does reconnect after sleep. However: a script of my disconnects weak networks, the idea being to allow connection to a stronger network. Yet, after the weak network is disconnected, there is no automatic connection to my stronger network (even though that network is known to the system and set to connect automatically). I know it's bad form to ask this, but one does wonder: is any attention being paid to bugs in this area, save by those who suffer from them? -- 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/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' Status in network-manager package in Ubuntu: Confirmed Bug description: The Wifi network can't connect after the wake up from suspend. Xubuntu 15.04 I'll post more useful details (journalctl log) as a comment to this bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 Uname: Linux 4.0.0-04rc5-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 2 18:18:56 2015 InstallationDate: Installed on 2015-03-27 (5 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+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 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
Linux Mint 19. ThinkPad X1C6, on wifi. `dbus: Failed to construct signal`, upon resumption from sleep. -- 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/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' Status in network-manager package in Ubuntu: Confirmed Bug description: The Wifi network can't connect after the wake up from suspend. Xubuntu 15.04 I'll post more useful details (journalctl log) as a comment to this bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 Uname: Linux 4.0.0-04rc5-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 2 18:18:56 2015 InstallationDate: Installed on 2015-03-27 (5 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+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 1450247] Re: gnome-system-monitor freezes during free space query on inactive network mounts (cifs)
@seb128 I would report this upstream, but the link provided in the post above seems to lead to an *Ubuntu* bugtracker, and one that confronts me with seemingly only a wall of text. Please could someone provide a fairly- direct, correct URL. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1450247 Title: gnome-system-monitor freezes during free space query on inactive network mounts (cifs) Status in gnome-system-monitor package in Ubuntu: Confirmed Bug description: either display a waiting dialog (and optionally a button to abort the df call on network mounts) or fetch the free space asynchronously (display a "fetching..." label instead of the percentage bar while the retrieval is in progress) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: gnome-system-monitor 3.15.91-0ubuntu1 Uname: Linux 4.0.0-04-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 30 01:40:51 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-04-02 (27 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor SystemImageInfo: current build number: 0 device name: channel: daily last update: Unknown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1450247/+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 1655348] Re: gpu-manager Error: can't open /lib/modules/
Cf. #1731651. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1655348 Title: gpu-manager Error: can't open /lib/modules/ Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: At least once a day there is an unexpected desktop freeze incl. mouse and keyboard. Even magic-sys-rq isn't possible, only hard switch-off. From smartmontools I can exclude a hardware failure. I've found that gpu-manager and systemd fail to load kernel modules. This is among the output of journalctl | grep modules Jan 10 13:12:34 systemd[1]: systemd-modules-load.service: Unit entered failed state. Jan 10 13:12:34 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. Jan 10 13:12:49 gpu-manager[791]: Error: can't open /lib/modules/4.4.0-57-generic/updates/dkms Jan 10 13:12:49 gpu-manager[791]: Error: can't open /lib/modules/4.4.0-57-generic/updates/dkms (terminal-output attached) dito with latest kernel Jan 11 07:53:04 gpu-manager[786]: Error: can't open /lib/modules/4.4.0-59-generic/updates/dkms Jan 11 07:53:04 gpu-manager[786]: Error: can't open /lib/modules/4.4.0-59-generic/updates/dkms ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-drivers-common 1:0.4.17.2 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 10 14:37:00 2017 InstallationDate: Installed on 2012-02-05 (1801 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120204) SourcePackage: ubuntu-drivers-common UpgradeStatus: Upgraded to xenial on 2016-08-01 (162 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1655348/+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 1491666] Re: System Monitor hangs when network offline
@Sebastian Bacher: yes (and a serious usability problem, if I may say so). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1491666 Title: System Monitor hangs when network offline Status in Linux Mint: New Status in gnome-system-monitor package in Ubuntu: New Bug description: The System Monitor hangs, or appears to hang, when a FSTAB-mounted network filesystem is offline. For, in that scenario, nothing - no message, nothing - happens for over 60 seconds - and then, after the filesystem tab *is* displayed, the Monitor generates a hang prompt when I try to close the window. C'mon, guys. Also: surely the System Monitor uses too much CPU for something that measures the CPU. Linux Mint 17.2 x64, Cinnamon, on a dualcore 2.2Gh processor, on a good SSD. Laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1491666/+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 608162] Re: GNOME Keyring Daemon stops panel's shutdown
I'll bump this, if I may. I too am affected - on Mint 18.3 Cinnamon. -- 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/608162 Title: GNOME Keyring Daemon stops panel's shutdown Status in gnome-keyring package in Ubuntu: Invalid Bug description: Binary package hint: gnome-keyring Almost every time I click "Shut Down" from the panel's menu for it, I get an error that says: "GNOME-Keyring-Daemon is not responding." Then I can choose "Shut Down anyway" and the computer usually turns off after that, but sometimes I need to use a sudo shutdown command. Also, sometimes when I select "Shut Down" from the panel, nothing happens at all. Again, I need to use a sudo shutdown command to turn off the computer. This happens for all of the users on this computer (a Thinkpad laptop). This issue is particularly annoying for non-administrator users, because if selecting "Shut Down" from the panel doesn't work they cannot issue a sudo shutdown command - which means I need to assist them in changing to a tty terminal, logging in as me, and then giving the sudo shutdown command. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-keyring 2.92.92.is.2.30.3-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic x86_64 Architecture: amd64 Date: Wed Jul 21 20:17:15 2010 ExecutablePath: /usr/bin/gnome-keyring-daemon InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcEnviron: LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: gnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/608162/+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 1716788] [NEW] Hang on running Windows 8 VM in virtualBox
Public bug reported: To (try to) reproduce: Start Windows 8 in VirtualBox Run the Gnome System Monitor whilst the vm is starting Try to switch tabs within the Gnome System Monitor My result: Gnome System Monitor hangs. Mint 18.2 x64 Cinnamon. Gnome System Monitor 3.18.2-1ubuntu1 ** Affects: gnome-system-monitor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1716788 Title: Hang on running Windows 8 VM in virtualBox Status in gnome-system-monitor package in Ubuntu: New Bug description: To (try to) reproduce: Start Windows 8 in VirtualBox Run the Gnome System Monitor whilst the vm is starting Try to switch tabs within the Gnome System Monitor My result: Gnome System Monitor hangs. Mint 18.2 x64 Cinnamon. Gnome System Monitor 3.18.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1716788/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
On my Mint (18.2 and I think I did it on 18.3 too - both Cinnamon) the network-manager downgrade sufficed; I did not need to adjust resolvconf. However, I don't think I was using a 'PPTP tunnel'. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
@lukas-d: I understand, but perhaps you are thinking that I work for Canonical or that I have the skill to contribute to the network-manager project. Neither of those things are true. I am a frustrated user (with fairly low programming ability). It seems to me that switching to a distribution that is not Ubuntu and is not based on Ubuntu might be an idea, in your circumstances. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
@terry69lawson and other frustrated users: perhaps you are in a position to try *WireGuard* as a replacement for OpenVPN (or for other methods of connecting to a VPN). Your VPN provider will need to have WireGuard servers for this to work. If your provider does have such servers, then you are in luck, for not only does Wireguard work with the latest (unfixed) Network Manager, it's also fast and easy. Still, it's also still in development and, though it has had some testing and had good reviews, it is not guaranteed secure. Still, I am amazed and boggled that Canonical has not fixed the problem. Perhaps it's been fixed in a newer version of Ubuntu and not backported? A bit of information, clearly presented, would not go amiss (@cyphermox) -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
I experience the same state of affairs on Linux Mint x64 18.2 Cinnamon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Corrections to the above post. (i) '[I]t its original' should be 'in its original'. (ii) 'Inference from the conjunction of 1, 2 and 3' should be, 'Inference from the conjunction of 1, 2, 3 and 4' - because I found another reason. A facility to edit posts would be welcome (but perhaps that exists and I overlook it somehow). -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
1. It has been four months since this bug - it its original incarnation (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606) - was reported. 2. The bug is critical: it breaks security software. 3. The bug has been reported to Ubuntu, which has paid employees. 4. The bug is a regression and hence presumably not especially hard to fix. Inference from the conjunction of 1, 2 and 3: *this bug should have been fixed by now*. Yet, it has not. Nor has any explanation been provided as to why not, at least not here. Not has there been a shortage of people asking, politely, for a fix. Perhaps then a slightly more strident question is in order. To wit: **what gives?** This is the sort of unfixed major problem that drives people back to Windows and Mac OS. (I know that https://bugs.launchpad.net/ubuntu/+bug/1 is closed, but still.) -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Cruz, thanks for this. However, (1) after all the trouble I had getting OpenVPN working, I don't fancy switching to something else (and my system does work at present, using the older version of Network Manager). Also, (2) I don't really understand what you say about /etc/hosts, though probably I could work it out. Further, (3) if I understand the last paragraph of your comment #13: I don't know; after all, at the top of this page we can read not only, 'Xenial - In Progress' (though it seems pretty slow progress! It's been at least a month since this show-stopping bug was first reported) but also, 'Yakkety - Triaged'. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Might I ask when this rather severe bug is due to be fixed (in Xenial or rather, for me, in Mint)? Thank you. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
I am glad to see that this bug is being worked on and is rightly labelled as being of high importance. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
I am on Mint 18.1. This problem affects me too. Is anyone working on it, please? -- 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/1264368 Title: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c Status in AndroidSDK: New Status in Banshee: New Status in gnome-control-center: Incomplete Status in GParted: Unknown Status in notification-daemon: New Status in anjuta package in Ubuntu: Confirmed Status in consolekit package in Ubuntu: Confirmed Status in f-spot package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in putty package in Ubuntu: Confirmed Bug description: Steps to recreate: 1. Open gnome-control-center in terminal. 2. Go to Network. 3. Go back to All preferences. 4. Notice that in terminal there is a warning: $ gnome-control-center (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu49 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 26 21:03:52 2013 InstallationDate: Installed on 2013-10-15 (71 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/androidsdk/+bug/1264368/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Seumas: since Canonical seem to be dragging their feet on this, you might as well downgrade to network-manager 1.2.2, which is a version that works. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Confirmed Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 556670] Re: Can't click on UI elements in gimp (intermittent)
Somewhat similarly, I found that, on a laptop with no external input device (only the touchpad), the file menu would not drop down from the toolbar, though all the other menus did. Odd. It lasted about a minute. Gimp 2.8 on Mint 18 x64. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/556670 Title: Can't click on UI elements in gimp (intermittent) Status in Inkscape: Incomplete Status in gimp package in Ubuntu: Fix Released Status in inkscape package in Ubuntu: Incomplete Bug description: Binary package hint: gimp Using kubuntu/9.10 on a lenovo x60 tablet PC (wacom). When using gimp, I find that drawing with extended input devices causes all UI interaction outside of the drawing area to stop. For example, I can not click on menus, toolbox, etc. No other programs are affected, and I can usually restore UI interaction by switching the active window (specifically, clicking the title bar on the image window and then the toolbox window restores interaction. I do not have this problem when using the mouse, only the tablet pen. Here is an exact sequence that produces this result: - start gimp, create new image - select paintbrush tool - draw in image - now I can no longer click on menus or toolboxes (although they do respond to the mouse pointer rollover w/hilighting, tooltips, etc) - click the image window title bar (focus switches from toolbox to image window) - now I can interact with menus and toolbox again - repeat! ProblemType: Bug Architecture: i386 Date: Tue Apr 6 12:50:18 2010 DistroRelease: Ubuntu 9.10 Package: gimp 2.6.7-1ubuntu1.1 ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-21.59-generic SourcePackage: gimp Uname: Linux 2.6.31-21-generic i686 XsessionErrors: (polkit-gnome-authentication-agent-1:17580): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/556670/+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 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 . . and now I can't remove your patched version of dnsmasq-base: === # apt remove dnsmasq-base Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: cinnamon-common cinnamon-control-center cinnamon-control-center-data cinnamon-l10n libandroid-properties1 libcinnamon-control-center1 libcinnamon-menu-3-0 libhardware2 libhybris libhybris-common1 libmedia1 libndp0 libqofono-qt5-0 libqt5xmlpatterns5 streamer ubuntu-mobile-icons urfkill xawtv-plugins Use 'apt autoremove' to remove them. The following packages will be REMOVED cinnamon dnsmasq dnsmasq-base indicator-network mint-meta-cinnamon network-manager network-manager-gnome tlp-rdw === Nor does apt or synaptic seem to allow me to reinstall (as against remove) dnsmasq-base I found a webpage that might be able to help (https://askubuntu.com/questions/17745/how-to-remove-a-deb-without- removing-its-dependencies) but I am worried about borking my system (and certainly I don't want to let apt remove all those packages). -- 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/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
*** This bug is a duplicate of bug 1639776 *** https://bugs.launchpad.net/bugs/1639776 Nicholas Stommel (nstommel): your fix didn't work for me. I think I had the newer version of dnsmasq already, from my distro's repositories, and Network-Manager 1.2.6 still - even after installing the patched version of dnsmasq you supplied - would not work with my VPN. I had to restore Network-Manager 1.2.2. Again. -- 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/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1639776] Re: name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface
I've installed dnsmasq-base_2.75-1ubuntu0.16.04.2 (on Linux Mint),
installed the 1.2.6 version of Network Manager and . . my VPN still
didn't work; the problem (that I had with network-manager 1.2.6 and the
older version of dnsmasq) wasn't solved. Still, my problem didn't begin
after suspend/resume but rather with boot. Reverting back, once again,
to the 1.2.2 version of Network Manager makes everything work again.
--
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/1639776
Title:
name resolution (dnsmasq) fails to send queries out after
suspend/resume reconnects the interface
Status in dnsmasq package in Ubuntu:
Fix Released
Status in network-manager package in Ubuntu:
Invalid
Status in dnsmasq source package in Xenial:
Fix Released
Status in network-manager source package in Xenial:
Invalid
Status in dnsmasq source package in Yakkety:
Fix Released
Status in network-manager source package in Yakkety:
Invalid
Status in dnsmasq package in Debian:
Fix Released
Bug description:
[Impact]
* suspend/resume (which involves disconnection of network devices)
leads to dnsmasq failures.
[Test Case]
* suspend/resume on 16.04 or 16.10 when using dnsmasq, and see
failures upon resume.
[Regression Potential]
* The fix was NMU'd in Debian in the version immediately after
16.10's. I believe the regression potential is very low as this is a
clear bug-fix from upstream.
---
Failure is caused by ENODEV return for all dns queries like:
sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33,
0, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device)
Problem is reported and fixed:
https://bugzilla.redhat.com/show_bug.cgi?id=1367772
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b
I didn't yet test if applying that patch to ubuntu package works. I
will try the patch in a few hours.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: dnsmasq-base 2.76-4
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Nov 7 14:11:51 2016
InstallationDate: Installed on 2037-12-25 (-7718 days ago)
InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
SourcePackage: dnsmasq
UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+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 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
This bug appears to be a duplicate of #167196; can the two reports - and their 'heat' - be merged? -- 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/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1265898] Re: thunderbird doesn't remember maximized window state in Ubuntu Gnome
This problem seems to occur on Mint 18 Cinnamon too (unless an extension is causing it). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1265898 Title: thunderbird doesn't remember maximized window state in Ubuntu Gnome Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Not sure if this is thunderbird or gnome-shell related issue. Steps to reproduce: 1. Run thunderbird. 2. Maximize thunderbird window. 3. Close thunderbird. 4. Run thunderbird again. 5. Notice that thunderbird window is not maximized - maximized window state was not saved during closing. Expected behaviour: In 5. thudnderbird window is open in maximized state. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: thunderbird 1:24.2.0+build1-0ubuntu1 Uname: Linux 3.13.0-031300rc6-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.12.7-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dotnokato 1431 F pulseaudio /dev/snd/pcmC0D0p: dotnokato 1431 F...m pulseaudio BuildID: 20131206222054 Channel: Unavailable CurrentDesktop: GNOME Date: Fri Jan 3 21:02:28 2014 ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-15 (79 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) IpRoute: default via 10.100.10.1 dev eth0 proto static 10.100.10.0/24 dev eth0 proto kernel scope link src 10.100.10.8 metric 1 10.100.10.0/24 dev wlan0 proto kernel scope link src 10.100.10.12 metric 9 Plugins: iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so Gnome Shell Integration - /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell) PrefSources: prefs.js [Profile]/extensions/gnomeintegrat...@davidmartinez.net/defaults/preferences/gnomeintegration.js Profiles: Profile0 (Default) - LastVersion=24.2.0/20131206222054 (In use) RelatedPackageVersions: rhythmbox-mozilla 3.0.1-1ubuntu8 gnome-shell 3.8.4-0ubuntu6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: Upgraded to trusty on 2013-11-05 (59 days ago) dmi.bios.date: 05/08/2007 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68TT2 Ver. F.07 dmi.board.name: 30B0 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 40.15 dmi.chassis.asset.tag: CNU7110B09 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68TT2Ver.F.07:bd05/08/2007:svnHewlett-Packard:pnHPCompaqnx6325(EY349EA#AKD):pvrF.07:rvnHewlett-Packard:rn30B0:rvrKBCVersion40.15:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq nx6325 (EY349EA#AKD) dmi.product.version: F.07 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1265898/+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
