[Bug 1973618] Re: can no longer open new windows after some time
I haven't been able to find other actual bugs/issues describing this issue, but there are threads on reddit and such that seem to indicate that this is a wayland/gnome42 issue, and that it affects all distributions. https://www.reddit.com/r/gnome/comments/ugpe12/firefox_on_gnome_42_cant_open_new_windows_after/ https://www.reddit.com/r/archlinux/comments/ugp9af/firefox_on_gnome_42_wayland_cant_create_new/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973618 Title: can no longer open new windows after some time To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1973618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947210] Re: Firefox Snap can't copy or drag in Wayland
Still a problem here. I'm on 22.04 with all updates (including proposed) installed, latest firefox snap (99.0-2, rev 1188). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947210 Title: Firefox Snap can't copy or drag in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1947210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962718] Re: Firefox snap crashes on every upgrade
While the problem might be in snapd, Firefox is still very much impacted, when it comes to the decision to ship 22.04 LTS without a deb version of Firefox to fall back to. In my experience, this is just one of many ways the experience with the snap version of Firefox is not on par with the traditional package time - yet. Lots of serious problems exist, that have still not been sorted out since the beginning of the 21.10 lifecycle. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962718 Title: Firefox snap crashes on every upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1962718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886728] Re: OpenVPN OTP replaces the ordinary password
This is still an issue in Ubuntu 21.04 (development, as of March 30, 2021) It looks like people have been complaining about this for years, and while some people have tried to fix it, those fixes never made it in. Surely it must be of some type of urgency to support 2FA one-time passwords in the primary network management solution in Ubuntu? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886728 Title: OpenVPN OTP replaces the ordinary password To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1886728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918033] Re: gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor))
I am no longer able to reproduce the crash after installing the proposed fix! Looks good to me! :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918033 Title: gnome-shell crashed with Clutter:ERROR:../clutter/clutter/clutter- stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1918033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918127] Re: gnome-shell crash when using panel
Problem occurs on Wayland as well as Xorg. Please let me know what kind of info you need. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918127 Title: gnome-shell crash when using panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918127] [NEW] gnome-shell crash when using panel
Public bug reported: Whenever I perform an action in the Gnome Panel (Activate a VPN has 100% failure-rate, but I have seen it when clearing notifications and other things too), the entire session crashes and I'm back at login. I'm running gnome-session on Hirsute. journalctl /usr/bin/gnome-shell shows the following just before the crash: Mar 08 07:02:40 localhost gnome-shell[67382]: ** Mar 08 07:02:40 localhost gnome-shell[67382]: Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor)) Mar 08 07:02:40 localhost gnome-shell[67382]: Bail out! Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed: assertion failed: (!clutter_actor_get_reactive (actor)) The problem is 100% reproducible. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute ** Tags added: hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918127 Title: gnome-shell crash when using panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1918127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879087] Re: dbus errors, frequent roaming and unstable connectivity
Never mind - Somehow my local package simply looked newer from a versioning perspective. I found the right version and as far as I can tell the problems are gone in this version. I have not seen any of the dbus messages and roaming works better (less erratic) here. Thanks a lot for getting this fix in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879087 Title: dbus errors, frequent roaming and unstable connectivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1879087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879087] Re: dbus errors, frequent roaming and unstable connectivity
I've been looking for the package but cannot seem to find it for testing. Please help me find it and I will test it immediately. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879087 Title: dbus errors, frequent roaming and unstable connectivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1879087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872964] Re: Reliable crash in lowlatency kernel with LXD
So in my case, my VM was configured with only 256MB of memory. This caused no problem on the normal -virtual kernel but caused all sorts of problems when I installed -lowlatency in the guest. Upgrading to 384MB solved the problem reliably here, so perhaps this is not the same thing afterall. - Sorry for the interruption -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872964 Title: Reliable crash in lowlatency kernel with LXD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1872964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872964] Re: Reliable crash in lowlatency kernel with LXD
Kernel version 5.4.0-37-lowlatency, btw -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872964 Title: Reliable crash in lowlatency kernel with LXD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1872964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872964] Re: Reliable crash in lowlatency kernel with LXD
I have an LXD Virtual Machine refusing to boot after installing the -lowlatency kernel on it. Sounds like these _might_ be related, so here's my info. I'm on a NUC too, btw. Host: Ubuntu 20.04 LTS, LXD 4.2 snap (running -lowlatency) Guest: Ubuntu 20.04 LTS The guest was running without problems on the -virtual kernel, but refuses to boot after installing -lowlatency # lxc info --show-log gw2 Name: gw2 Location: none Remote: unix:// Architecture: x86_64 Created: 2020/06/20 22:18 UTC Status: Stopped Type: virtual-machine Profiles: default Pid: 326329 Resources: Processes: 0 Log: KVM internal error. Suberror: 1 emulation failure RAX=0a00 RBX=0b2639e0 RCX=0f3c1f40 RDX=0b20 RSI=0103 RDI=0b24e1c0 RBP=0b24e120 RSP=0f3c20f0 R8 =0c914168 R9 = R10= R11=0af9d800 R12=0b24f120 R13=0b24e0e0 R14=00020004 R15=0c90d483 RIP=000a RFL=00210246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0030 00c09300 DPL=0 DS [-WA] CS =0038 00a09b00 DPL=0 CS64 [-RA] SS =0030 00c09300 DPL=0 DS [-WA] DS =0030 00c09300 DPL=0 DS [-WA] FS =0030 00c09300 DPL=0 DS [-WA] GS =0030 00c09300 DPL=0 DS [-WA] LDT= 8200 DPL=0 LDT TR = 8b00 DPL=0 TSS64-busy GDT= 0edee698 0047 IDT= 0e80e018 0fff CR0=80010033 CR2= CR3=0f001000 CR4=0668 DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER=0d00 Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872964 Title: Reliable crash in lowlatency kernel with LXD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1872964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879087] Re: dbus errors, frequent roaming and unstable connectivity
Thank you for taking care of this so swiftly. I don't believe I have much to add to the test-case. From testing locally I can see that the warnings disappear from the log and the connection _seems_ more stable. I underscore _seems_ because I have not been able to figure out which other parts of the system are actually using these particular dbus messages, if any. If nobody is actually using these, the perceived improvement could be placebo. I will keep testing though, because I've generally been struggling with a stable wifi connection on 20.04. Thanks again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879087 Title: dbus errors, frequent roaming and unstable connectivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1879087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879087] [NEW] dbus errors, frequent roaming and unstable connectivity
Public bug reported: When using this version of wpa_supplicant with my company WPA2-Enterprise wireless setup, I'm experiencing far too frequent roaming events (even when not moving around) accompanied by hiccups in connectivity. I also see these messages in the wpa_supplicant log: dbus: wpa_dbus_property_changed: no property RoamComplete in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property RoamTime in object /fi/w1/wpa_supplicant1/Interfaces/3 dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/3 Having done a little research, at least the dbus errors seem to be fixed by this commit upstream: https://w1.fi/cgit/hostap/commit/wpa_supplicant/dbus/dbus_new.c?id=23d87687c2428f3b94865580b0d33e05c03e6756 So I built a version of wpa_supplicant including this particular patch and installed on my machine. Apart from solving the dbus errors completely, it seems to have had a positive impact on the frequent roaming and unstable connectivity as well (I've run for a day with no burst of roaming events at all, where they used to happen every few minutes most of the time.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat May 16 16:47:27 2020 InstallationDate: Installed on 2020-05-12 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879087 Title: dbus errors, frequent roaming and unstable connectivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1879087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
On a fully updated Ubuntu 19.10, I feel most of my problems occur, when copying from a Wayland application, and pasting to an XWindow application. Most of the time, that doesn't work at all. As an example. Running my Firefox as a native Wayland application, I am experiencing problems copying a URL and pasting it into Chrome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1734967] Re: tzdata info for WGT/WGST broken
I have started a dialogue on the TZ mailinglist to perhaps have the change (WGT/WGST at least) reverted. That's my goal anyway, so we'll see how it goes. /Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734967 Title: tzdata info for WGT/WGST broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734967] Re: tzdata info for WGT/WGST broken
Hi guys, The removal of WGT/WGST from tzdata is crazy to me. Living in Greenland, I can imagine a bunch of different issues this will cause, so I'll try to figure out what is going on and what possibilities we have of rectifying it. Starting with upstream. /Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734967 Title: tzdata info for WGT/WGST broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734967] [NEW] tzdata info for WGT/WGST broken
Public bug reported: Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed from date command but instead just "-03". Problem is evident in PHP applications too, which now think we're in Sao Paolo. This appears to have changed with latest tzdata update or perhaps in combination with change from DST. Same problem on 16.04, 17.10 and Debian 9. ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734967 Title: tzdata info for WGT/WGST broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1734967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614557] Re: Add support for Challenge/Response input
Looking through the code, these outputs may differ because of the different ways to authenticate... I'm not sure but both messages are certainly present in the latest openvpn code. FWIW, I'm connecting to an OpenVPN-AS solution with Certificates and Password -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614557 Title: Add support for Challenge/Response input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1614557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614557] Re: Add support for Challenge/Response input
Looks like the message that's being looked for might have changed: This is from my log now: AUTH: Received control message: AUTH_FAILED,CRV1:R,E:93NBZNaOH799HLoxv7tWefldc8JtIpbf:eHRod3Q=:Enter PASSCODE But based on the commit, it might be looking for: This is from the commit below: >PASSWORD:Verification Failed: 'Auth' ['CRV1:flags:state_id:username:text'] https://git.gnome.org/browse/network-manager- openvpn/commit/?h=1.2.10=5b96fecb97c752e08fdcebb331b983196f4b8935 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614557 Title: Add support for Challenge/Response input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1614557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614557] Re: Add support for Challenge/Response input
This doesn't seem to work for me on Ubuntu 17.10: openvpn 2.4.3-4ubuntu1 network-manager 1.8.4-1ubuntu3 network-manager-gnome 1.8.4-1ubuntu3 network-manager-openvpn 1.2.10-0ubuntu2 network-manager-openvpn-gnome 1.2.10-0ubuntu2 When activating an OpenVPN connection that's challenge/response enabled, I'm prompted to reenter a password but it never works. The entered password is stored in the VPN definition as the primary password, so perhaps NM is reconnecting altogether rather than allowing me to pass the challenge response? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614557 Title: Add support for Challenge/Response input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1614557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
@Vincent, re the "If lookups are routed to multiple interfaces, the first successful response is returned", this is indeed the problem with systemd-resolved as I see it, as that method will never be stable for a split DNS setup... You can never reliably predict if you'll get a good or a bad IP for the connections you're currently using. dnsmasq allows a solution to this, because NetworkManager can tell dnsmasq to use the LAN DNS for default stuff, but use the VPN DNS for lookups in the example.lan domain and 10.in-addr.arpa, for example. The dhcp-options you mention is for a direct call to openvpn if I'm not mistaken(?). That would work if you're content with launching every VPN connection by hand. In my case, I use a bunch of different VPN clients and as such, solving this in NetworkManager is a much more universally applicable fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
To clarify... I believe NetworkManager is the culprit here - or systemd- resolved is fundamentally broken (i don't have the working knowledge to guess which it is). So my comment #44 is more about getting a working system than addressing any issue with systemd and/or NetworkManager. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
So I have come up with a working solution that actually solves all MY needs in this regard. Hopefully it will be of use or inspiration to some of you guys too... Part 1 -- Switch NetworkManager to use dnsmasq (this will NOT work with resolved!) # apt-get install dnsmasq-base Add dns=dnsmasq to /etc/NetworkManager/NetworkManager.conf [main] section # systemctl disable systemd-resolved # systemctl stop systemd-resolved # systemctl restart network-manager Part 2 -- Modify VPN configuration (in /etc/NetworkManager/system-connections) DNS, Routes and reverse IP for the VPN networks can be tricked to work by modifying the [ipv4] section of the VPN configuration file: dns-search=example.lan;example2.lan;example.net # <-- make sure dns requests for these domains and all subdomains are sent to the VPN DNS servers, allowing the split DNS to work never-default=true # <-- make sure the VPN will not be made the default route ignore-auto-routes=true # <-- if you want to manually select the routes route1=192.168.1.0/24 # <-- sets up a route - with reverse dns forwarding to the vpn dns server for network 1 route2=192.168.2.0/24 # <-- sets up a route - with reverse dns forwarding to the vpn dns server for network 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629611] Re: dns server priority broken
*** This bug is a duplicate of bug 1624317 *** https://bugs.launchpad.net/bugs/1624317 This is not fixed, but is marked as a duplicate of #1624317 ** This bug has been marked a duplicate of bug 1624317 systemd-resolved breaks VPN with split-horizon DNS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629276] Re: network-manager ignoring DNS settings in wifi connections
*** This bug is a duplicate of bug 1624317 *** https://bugs.launchpad.net/bugs/1624317 ** This bug is no longer a duplicate of bug 1629611 dns server priority broken ** This bug has been marked a duplicate of bug 1624317 systemd-resolved breaks VPN with split-horizon DNS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629276 Title: network-manager ignoring DNS settings in wifi connections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633003] Re: (Cisco) VPN name resolution breaks after upgrade to 1.2.2-0ubuntu0.16.04.3
*** This bug is a duplicate of bug 1624317 *** https://bugs.launchpad.net/bugs/1624317 ** This bug is no longer a duplicate of bug 1629611 dns server priority broken ** This bug has been marked a duplicate of bug 1624317 systemd-resolved breaks VPN with split-horizon DNS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633003 Title: (Cisco) VPN name resolution breaks after upgrade to 1.2.2-0ubuntu0.16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
For the record, this continued to bother me until I got a replacement laptop. I received an exact identical new laptop and have never since seen this issue... Hardware fault and nothing else! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1634208] Re: VPN cannot resolve DNS entries on second connect
*** This bug is a duplicate of bug 1624317 *** https://bugs.launchpad.net/bugs/1624317 ** This bug is no longer a duplicate of bug 1629611 dns server priority broken ** This bug has been marked a duplicate of bug 1624317 systemd-resolved breaks VPN with split-horizon DNS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634208 Title: VPN cannot resolve DNS entries on second connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1634208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I'm on 17.04 too and suffering from this issue for a while. As I understand this issue, the problem may actually very well be in Network-Manager rather than in systemd-resolved, but the problem is indeed very visible with resolved. Here's how I experience the problem (the root of my problems are a split DNS setup, just like most other people following this ticket). This is the state of my resolved... With no VPN connected (wireless and wifi only): Link 7 (vpn0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 3 (wlp4s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.8.1 DNS Domain: int.example.com Link 2 (enp0s31f6) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.8.1 DNS Domain: int.example.com With VPN connected: Link 7 (vpn0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.180.48 192.168.180.49 DNS Domain: example.lan Link 3 (wlp4s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.8.1 DNS Domain: int.example.com Link 2 (enp0s31f6) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.8.1 DNS Domain: int.example.com Now, I have one split DNS entry, testserver.example.net. On a public DNS, it will resolve to a public IP - On the example.lan DNS servers, it will resolve to a private IP. Doing the following a couple of times is bound to sometimes return the private IP and sometimes the public IP: systemd-resolve --flush-caches && ping -c1 testserver.example.net So for things to work in this particular example, I'd need the 192.168.8.1 DNS to either be disabled completely or only used for int.example.com. 192.168.180.48 and 49 as provided by the VPN would somehow need to be the default/active nameserver. Note that for my VPN connection in Network Manager, I've *not* enabled the "use this connection only for resources on its own network". In an attempt to work around this problem, I decided to configure network-manager for dnsmasq, which worked fine back in the 16.04 days. Basically the setup worked, but Network-Manager only added the VPN DNS servers for the VPN provided search domain example.lan. Needless to say this works even worse than the resolved solution, because now I get the wrong answer for testserver.example.net every time. It does seem to indicates that perhaps there's something fishy about how network-manager passes DNS servers to resolved. I have not found a way to force network- manager to completely replace the configured DNS servers for a VPN connection, but that might provide a usable workaround. Hopefully this can shed some light on things? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
@Tim - What Patrick said... Or prevent the kernel package from being updated until the fix is included: https://askubuntu.com/questions/18654/how-to-prevent-updating-of-a-specific-package -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Okay, so MIGRATION is indeed enabled on the mainline kernel too and that possibility has been ruled out - So we're not chasing ghosts. :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
There must be a better way to do this... All of these issues seem to arise from a BUG event in swapops.h:129. That particular spot is a section that's only active, when the kernel was built with CONFIG_MIGRATION=y. So first step is probably to verify that CONFIG_MIGRATION is even enabled for the mainline kernel (the configs are not the same, I'm told). So for all we know, the bug could still be upstream. If somebody running the mainline kernel could post the output of the following command, that would be useful: cat /boot/config-$(uname -r) |grep CONFIG_MIGRATION If CONFIG_MIGRATION is enabled on mainline (CONFIG_MIGRATION=y in the output above), next step should be to check if some of the Ubuntu modifications touch in the source in any relevant places. The BUG event in swapops.h:129 seems to be hit if migration_entry_to_page() is called with an unlocked page. Grepping through the source, this function is only called from a handful of places, so it should be possible cross- reference with the Ubuntu modifications. Perhaps this will bring us closer to the problem a bit faster? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629611] Re: dns server priority broken
Seems to work in 1.4.4-1ubuntu3 in 17.04 at least... Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
Okay, Since updating the BIOS of my Lenovo T460s laptop from version 1.15 to 1.20, I've not seen this issue once. Since I've not been able to successfully reproduce the error at any point, I can't say for sure that the problem is gone. It has been a weeks time, however, which is certainly a first. I'm happy to close this bug at this time, marking it a hardware/firmware issue. /Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
The most promising so far is a brand new BIOS upgrade for my system. Haven't seen the problem since upgrading 4 days ago. Not quite ready to declare it solved, but certainly looks promising. Happy holidays. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629611] Re: dns server priority broken
That is certainly a possibility, but unfortunately returns us to a state where applications have to be restarted when nameservers change (glibc resolved.conf issue). That's probably even worse in my situation at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629611] Re: dns server priority broken
Unfortunately not much traction here, and this appears to annoy people across distros. In the meantime, an ugly hack is to manually add all internal domains to the NetworkManager VPN config file's dns-search= parameter: dns-search=domain1.lan;domain2.lan;domain3.lan;example.com; This causes NetworkManager to split DNS all lookups for these domains to the VPN DNS server, but with the added overhead of searching through all domains for non-existing hostname queries (make sure the primary internal domains are mentioned first). Also, for a multi-city setup like ours, I need to add A LOT of domains to get a functional DNS while on VPN - Including in-addr.arpa specifications for all IP subnets. So there's a way to sweeten the deal - but this is by no means anything other than a hack. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
Please let me know what kind of info you need, in order to find a resolution to this issue - I can't imagine it's a hard one to solve, given the right information. At the very least, determining if this is indeed a hardware/firmware bug or a kernel bug, would be a HUGE step in the right direction. Unfortunately, this bug along with one single other one, pretty much makes Ubuntu 16.10 unusable to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
Hmmm, so several crashes again today while on battery. Even with power/control set to "on" rather than auto. I'm on 4.9-rc8 btw. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629611] Re: dns server priority broken
Wow - Long message, but what I got from it was "I need to see a debug log", correct? I'll attach that... I'll also point you to the problematic part: Dec 5 15:14:48 bar14860 NetworkManager[921]: [1480961688.1915] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.48@vpn0' for domain "workdom.lan" Dec 5 15:14:48 bar14860 NetworkManager[921]: [1480961688.1915] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.48@vpn0' for domain "22.60.10.in-addr.arpa" Dec 5 15:14:48 bar14860 NetworkManager[921]: [1480961688.1916] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.48@vpn0' for domain "23.60.10.in-addr.arpa" Dec 5 15:14:48 bar14860 NetworkManager[921]: [1480961688.1916] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.49@vpn0' for domain "workdom.lan" Dec 5 15:14:48 bar14860 NetworkManager[921]: [1480961688.1916] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.49@vpn0' for domain "22.60.10.in-addr.arpa" Dec 5 15:14:48 bar14860 NetworkManager[921]: [1480961688.1916] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.49@vpn0' for domain "23.60.10.in-addr.arpa" Dec 5 15:14:48 bar14860 NetworkManager[921]: [1480961688.1916] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.48@enp0s31f6' Dec 5 15:14:48 bar14860 NetworkManager[921]: [1480961688.1917] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.49@enp0s31f6' Now for this test, I'm using the same DNS before and after, but the VPN connection adds DNS resolution using the VPN provided DNS ONLY for the domains it feels is behind the VPN, and there's nothing I can seemingly do to change that behaviour. This is the exact assumption that breaks VPN for many users. When I connect to VPN, especially one that becomes my default gateway, I need all DNS requests to go the the DNS servers behind the VPN. Need more info, let me know. ** Attachment added: "network-manager.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+attachment/4787680/+files/network-manager.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/1629611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
FWIW, this appears to work around the issue:
Create file /etc/udev/rules.d/90-nvme-power.rules :
---
KERNEL=="nvme*[0-9]n*[0-9]", ATTRS{model}=="SAMSUNG MZSLW1T0HMLH-000L1*",
ATTR{device/power/control}="on"
---
On my system at least.
I'm sure the kernel should somehow blacklist settings that bakes certain
devices behave erratically, but until then, this appears to do the
trick. No issue in 4 days!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641322
Title:
frequently lost connection to nvme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
Okay - Crashed 3 times this morning on rc7 AND rc6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
I'd really like to have this issue resolved, so anything you guys need to get closer to the culprit, just let me know. So far, 4.9-rc6 mainline build appears stable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
Darn it... Just had the crash on rc7. Going back to rc6, thinking it may be workload related... Will report back... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
Problem not seen on 4.9-rc6 mainline. Moving on to 4.9-rc7 mainline now... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
I haven't found a positive fix for this issue in 4.9-rc6, but FWIW, I've been running 4.9-rc6 for a couple of days without encountering this issue. I'll let you know how this goes after further testing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
I've not found a positive match, but this MIGHT be related to the following upstream bug. https://bugzilla.kernel.org/show_bug.cgi?id=112121 ** Bug watch added: Linux Kernel Bug Tracker #112121 http://bugzilla.kernel.org/show_bug.cgi?id=112121 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
Okay, I've been running on 4.9-rc5 mainline all day, at work, with no issue at all. After I take my laptop home, boom! Same problem. This is likely triggered more often at home, where I'm on battery more than I am at work, causing more aggressive power savings to take place. In any case, my issue is confirmed on 4.9-rc5 mainline. /Thomas ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
I've installed latest mainline build and awaits the issue... I have definitely seen the issue with the 4.9-rc4 mainline build, but the rc5 just yet... I'll be back with an update in a few days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] Re: frequently lost connection to nvme
** Attachment added: "Captured dmesg output from the error happening" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+attachment/4776493/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641322] [NEW] frequently lost connection to nvme
Public bug reported: Since before the release of Yakkety Yak, I've been having problems with a new laptop with a Samsung nvme device: 05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a804 (prog-if 02 [NVM Express]) For whatever reason, I sometimes (often) loose connection to the device, causing the entire system to stop working until a powercycle has been completed. I can go a full day without having the problem - Just as I can have an entire night of the system just refusing to be stable for long enough to be usable. I've tried with official kernels and mainline kernels of 4.8 and 4.9 versions of the kernel, but all show the exact same problem at one point or another. I'm aware that this COULD be a hardware-related issue, but have no real way to be certain at this point. The system is a brand new Lenovo ThinkPad T460s. Dmesg always shows the following few lines, in association with the error: kern :warn : [Nov12 03:34] nvme :05:00.0: Failed status: 0x, reset controller. kern :warn : [ +0,017726] pci_raw_set_power_state: 40 callbacks suppressed kern :info : [ +0,04] nvme :05:00.0: Refused to change power state, currently in D3 kern :warn : [ +0,91] nvme nvme0: Removing after probe failure status: -19 kern :info : [ +0,13] nvme0n1: detected capacity change from 1024209543168 to 0 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-27-generic 4.8.0-27.29 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thms 1592 F pulseaudio CurrentDesktop: GNOME Date: Sat Nov 12 11:59:50 2016 HibernationDevice: RESUME=UUID=aeb50d49-fb7a-4e4c-928c-582e6a77ad7e InstallationDate: Installed on 2016-10-15 (28 days ago) InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 (20161012.1) MachineType: LENOVO 20FAS43T00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed root=UUID=881c937d-6215-43a5-b57a-257adaee046b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-27-generic N/A linux-backports-modules-4.8.0-27-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET47W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS43T00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1CET47W(1.15):bd08/08/2016:svnLENOVO:pn20FAS43T00:pvrThinkPadT460s:rvnLENOVO:rn20FAS43T00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20FAS43T00 dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1641322 Title: frequently lost connection to nvme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1641322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629611] Re: dns server priority broken
Here's the thing, I'm on 16.10 which has the debian equiv listed as stretch/sid and my network-manager version is 1.2.4-0ubuntu1. Looking at Debian stretch and sid, they have network-manager packages in various versions but not 1.2.4. Furthermore, since Ubuntu employ their own patches, backports, versions, scripts, configuration etc, It'd be wrong of me to file this bug upstream, since I'd certainly risk wasting the Debian folks' time with something that might very well be Ubuntu specific. I simply cannot be certain. The only proper way to do this, would be for the Ubuntu maintainer to have a look at this bug and decide whether we're dealing with an Ubuntu specific config issue or something upstream and take the proper action upstream if needed. I have found similar but not identical reports in Debian, so I cannot reference anything that resembles duplicates. /T -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629611] Re: dns server priority broken
I'll do it :) Any helpful pointers to which package/version i should reference, since I don't have the real debian version of this package anywhere? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629611] Re: dns server priority broken
No, that does not seem like the problem to me - Or it's not described correctly. I can't seem to find a proper match in that list. resolv.conf is not the issue here - the problem is in the DNS servers that dnsmasq uses. I.e. one is added to dnsmasq when my wireless connection comes up, and when I launch my VPN, to more are APPENDED. And it seems like dnsmasq will try by wifi DNS first, VPN DNS later. So for split DNS, the VPN DNS servers are not queried at all, causing problems. The proper way is probably to PREPEND the VPN DNS servers to the list of DNS servers that dnsmasq uses or otherwise prioritize these over previously configured servers. That way everything should work as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS
This bug seems to bite me in a slightly different way. Please let me know if you feel that this is really a separate bug... Also, this is happening on Yakkety - network-manager-1.2.4-0ubuntu1 When I connect to my work VPN, I'm not using split-tunnelling. Still the DNS resolution is split, causing DNS resolution to only be correct for my primary VPN search domain. This log snippet seems to explain it all: - 192.168.0.1 is my home ADSL DNS. - example.local is the search suffix provided by my VPN. - 10.10.10.12 and 10.10.10.13 are my VPN provided DNS servers. Oct 12 06:43:04 bar14860 NetworkManager[870]: [1476261784.8455] dns-mgr: Writing DNS information to /sbin/resolvconf Oct 12 06:43:04 bar14860 dnsmasq[1226]: setting upstream servers from DBus Oct 12 06:43:04 bar14860 dnsmasq[1226]: using nameserver 192.168.0.1#53(via enp0s31f6) Oct 12 06:43:04 bar14860 dnsmasq[1226]: using nameserver 10.10.10.12#53 for domain example.local Oct 12 06:43:04 bar14860 dnsmasq[1226]: using nameserver 10.10.10.12#53 for domain 20.10.10.in-addr.arpa Oct 12 06:43:04 bar14860 dnsmasq[1226]: using nameserver 10.10.10.12#53 for domain 21.10.10.in-addr.arpa Oct 12 06:43:04 bar14860 dnsmasq[1226]: using nameserver 10.10.10.13#53 for domain example.local Oct 12 06:43:04 bar14860 dnsmasq[1226]: using nameserver 10.10.10.13#53 for domain 20.10.10.in-addr.arpa Oct 12 06:43:04 bar14860 dnsmasq[1226]: using nameserver 10.10.10.13#53 for domain 21.10.10.in-addr.arpa Oct 12 06:43:04 bar14860 NetworkManager[870]: [1476261784.9543] policy: set 'vpn0' (vpn0) as default for IPv4 routing and DNS The result of this is that all my other internal work-domains does not work at all, and may, as the bug describes, leak onto the internet as well. If you need more info, let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1592721 Title: Don't write search domains to resolv.conf in the case of split DNS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1629611] [NEW] dns server priority broken
Public bug reported: network-manager: 1.2.4-0ubuntu1 Yakkety appears to have switched back from resolved to dnsmasq, but it seems server priority/order is broken. Example: In split DNS setups, connecting to VPN will not cause us to query the DNS provided by the VPN first (or only), which should be the proper way to resolve names in that case. Say server.example.com in the public DNS resolves to a.a.a.a and in the private DNS resolves to b.b.b.b. Stuff would work from my normal internet-connection, but connection to VPN would cause stuff to misbehave. I expect to hit the b.b.b.b address but since my normal LAN DNS is being used first, I'm really hitting a.a.a.a. Please let me know how to proceed - Hopefully this can be fixed in time for release. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629611 Title: dns server priority broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1614557] [NEW] Add support for Challenge/Response input
Public bug reported: 2-factor authentication is all the rage these days, so we should to be able to prompt for the Challenge Response when needed... Right now the behaviour looks more like a password failure and it doesn't work (I'm on Gnome3). OpenVPN transaction that is probably what we need to look for is something along the lines of: "AUTH_FAILED,CRV1:R,E:lYxXoM3BLBcdnCytgqUoRn64c4y5b3BB:eHRoc3Q=:Enter PASSCODE" Prompt for "Enter PASSCODE" and submit that to openvpn and it should probably be it? The terminal openvpn client added similar support in 2.3.11 and it works. /Thomas ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1614557 Title: Add support for Challenge/Response input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1614557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 499773] Re: Race with ureadahead can mean that /var/lib/ureadahead/debugfs appears in /etc/mtab
open-vm-tools also chokes on this, when freezing filesystems for a quiesced snapshot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/499773 Title: Race with ureadahead can mean that /var/lib/ureadahead/debugfs appears in /etc/mtab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/499773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
Hmmm I can't seem to find it documented anywhere, but last time I needed this to work was in the good old sysvinit days and it may have even been on a different distro. Sorry for not brushing thoroughly up on this, prior to filing this bug. I have checked with CentOS 7 and it has the halt.local placed in /usr/sbin/halt.local as well In any case, this is part of the rc-local type magic that systemd performs and with rc.local in /etc/rc.local, one could argue, that it makes sense for these scripts to be located together. But more importantly, user-maintained stuff in /usr/sbin/ is just bad practice and we should not encourage people to do that. /T -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532553 Title: /etc/halt.local has become /usr/sbin/halt.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
You're absolutely right - Changed to systemd ** Package changed: transmission (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532553 Title: /etc/halt.local has become /usr/sbin/halt.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
Also all other distros, regardless of init system, appears to have this file somewhere. Bad solution IMHO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532553 Title: /etc/halt.local has become /usr/sbin/halt.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
Fair enough... As mentioned earlier, this may be from a systemv time and perhaps from Red Hat, I'm not sure. I do know that /usr/sbin/halt.local works in both Wily and in debian 8 out of the box, the file is just located in dpkg- managed space, which makes no sense. Look, I'm not actually arguing that we keep this particular file, but I think we need to keep the functionality. /lib/systemd/system-shutdown/ seems to provide that functionality, but again, this is in dpkg-managed territory. Is there a user managed folder that is handled the same? If I need to create my own unit-file, I'd be happy to, but I've had a hard time figuring out the proper requiremends/dependencies/befores and afters that will make this the very last thing to run, just before the system prints "system halted". This is where the need for further documentation comes in (or perhaps I'm just too dense to find it) If you can help point me to somewhere that will allow me to figure our the correct dependencies etc for a new unit-file, I'll be happy to let this go :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532553 Title: /etc/halt.local has become /usr/sbin/halt.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
Alright - Got your comments late, let me try that out Are these targets documented somewhere, so it becomes clear exactly what is started when? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532553 Title: /etc/halt.local has become /usr/sbin/halt.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
systemd.special(7) explains what they are, but if I could somehow get the correlation between targets, that'd be cool -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532553 Title: /etc/halt.local has become /usr/sbin/halt.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
In that case we are missing documentation for the shutdown/halt procedure more than ever. Very often halt.local is where we'd do stuff like powering off UPS outlets, to handle power-outage scenarios properly. It may not have been documented or placed ideally, but AFAIKT, it's actually always worked. Without the halt-local.service, we're missing that easy hook, as I see it. The nut package for one, does not include a systemd unit that can do the exact same thing, and to my experience, figuring out exactly which depencencies to create for a new unit tile to accomplish the same without breaking something else, is really not that well documented, or just not very easy to find. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532553 Title: /etc/halt.local has become /usr/sbin/halt.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
Thowing user-managed executables in /lib/systemd/system-shutdown/ is not much better than editing /usr/sbin/halt.local. Is there an /etc or a /usr/local based version of this directory available somewhere, that will work out of the box, then that will work for me, i guess.. I'll try it out at least. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532553 Title: /etc/halt.local has become /usr/sbin/halt.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local
Thank you for your input. It's not working how I want it to right now, but I'm confident it can be done. I need to read up on systemd for this to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532553 Title: /etc/halt.local has become /usr/sbin/halt.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532552] Re: transmission-daemon settings gone after system halt
I was wrong. It appears as if the XFS filesystem on / is the actual culprit here. The way XFS works, makes it lose last-second changes such as the new settings file written by transmission-daemon, whet the power is cut after halt. I've added a "sync" to my UPS power-off script and everything appears to be much more stable now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532552 Title: transmission-daemon settings gone after system halt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1532552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532552] Re: transmission-daemon settings gone after system halt
After this, I have no indication that anything should be wrong with transmission-daemon regarding this, so I'm closing the case. ** Changed in: transmission (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532552 Title: transmission-daemon settings gone after system halt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1532552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532552] [NEW] transmission-daemon settings gone after system halt
Public bug reported: Ubuntu-15.10, amd64 systemd-225-1ubuntu9 transmission-daemon-2.84-1ubuntu1 I've noticed more than once, that "halt" can cause transmission-daemon to loose it's settings. AFAIK, "halt" is not that different from "poweroff" or "reboot" in regards to the shutdown sequence, so it is probably a problem for those as well. What I've noticed is that after my system comes back up after being halted, transmission-daemon won't start, citing config issues. Looking at /etc/transmission-daemon/settings.json, it's there but it's empty. This does not happen every time, but I've seen it on at least 3 different occasions. My guess (and I'm relatively new to systemd) is that while the transmission-daemon systemd unit-file wants to start after network.target, there is nothing that would prompt a "stop" of the service during shutdown. This seems to leave a race where the transmission-daemon is killed too close to remounting the / filesystem read-only, giving the daemon enough time to truncate it's config, yet making it impossible for the daemon to write it's settings, as it likes to do on "stop". My / filesystem is XFS, but that does not seem to have anything to do with this. I'm still looking for a way to map out the dependencies of systemd on shutdown, but it seems to me that perhaps adding Require=network.target to the unit-file might cause the daemon to stop early and solve this issue. Please let me know if you need anything else ** Affects: transmission (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532552 Title: transmission-daemon settings gone after system halt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1532552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1532553] [NEW] /etc/halt.local has become /usr/sbin/halt.local
Public bug reported: Ubuntu 15.10, amd64 systemd-225-1ubuntu9 /etc/halt.local seems to have moved to /usr/sbin/halt.local which IMO is bad for a couple of reasons. 1) This is not where it's supposed to be 2) Locally modified (non-dpkg managed) scripts under /usr is bad I have not been able to find anywhere documenting this as a decided change, so it seems like a bug to me. Please let me know if you need more info from me /Thomas ** Affects: transmission (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1532553 Title: /etc/halt.local has become /usr/sbin/halt.local To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1532553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1503655] Re: Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107
I'm having this issue on Wily today - Occurs on Wily kernel 4.2.0-15 but not on 4.2.0-14 for me. Bug #1503738 mentions this bug # as a duplicate, but while it probably is the exact same issue, it's on a very different kernel/distro version for me. Please let me know if the fix is automatically handled across all supported Ubuntu kernels, or if I need to submit info to the other bug.. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1503655 Title: Kernel bug in eventpoll_release_file+0x46/0xa0 with 3.13.0-66.107 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1396889] Re: [Lenovo ThinkPad T400] kexec reboot fails
I'm on a virtual machine and experiencing the same thing. The problem seems to be covered pretty well in pages mentioned in #8. My problem in more detail is trying to kexec the 3.16 kernel provided by linux-generic-lts-utopic in trusty (from original 3.13 kernel, to allow normal kernel updates on DigitalOcean). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1396889 Title: [Lenovo ThinkPad T400] kexec reboot fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1396889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310350] Re: Oops __rpc_clnt_handle_event+0x48/0xd0
I have the same problem on several different machines, both on 3.11.0-20 and 3.11.0-24. For me it only happens on boot, and not entirely consistantly - Sometimes it works, sometimes it crashes. It does crash pretty often though, and I'm trying to find a way to reproduce consistently. [2.962760] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [2.973227] BUG: unable to handle kernel NULL pointer dereference at 0010 [2.973436] IP: [a00a9618] __rpc_clnt_handle_event+0x48/0xd0 [sunrpc] [2.973607] PGD 136103067 PUD 136102067 PMD 0 [2.973777] Oops: [#1] SMP [2.973907] Modules linked in: nfsd nfsv4 nfs_acl mac_hid auth_rpcgss shpchp vmw_vmci nfs fscache i2c_piix4 lockd lp sunrpc parport floppy mptspi mptscsih e1000 mptbase vmw_pvscsi vmxnet3 [2.974766] CPU: 1 PID: 511 Comm: mount Not tainted 3.11.0-24-generic #41~precise1-Ubuntu [2.974911] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 07/30/2013 [2.975092] task: 880135df8000 ti: 880136ffc000 task.ti: 880136ffc000 [2.975231] RIP: 0010:[a00a9618] [a00a9618] __rpc_clnt_handle_event+0x48/0xd0 [sunrpc] [2.975441] RSP: 0018:880136ffdc18 EFLAGS: 00010283 [2.975554] RAX: 88013908ea80 RBX: 8801383dbe00 RCX: 0002 [2.975679] RDX: RSI: 0100 RDI: [2.975797] RBP: 880136ffdc38 R08: 88013908e7b8 R09: [2.975916] R10: 0001 R11: 00017960 R12: [2.976032] R13: 880135c86400 R14: R15: [2.976152] FS: 7f82b8da7800() GS:88013fd0() knlGS: [2.976299] CS: 0010 DS: ES: CR0: 80050033 [2.976403] CR2: 0010 CR3: 000136106000 CR4: 000407e0 [2.976621] Stack: [2.976688] 880136ffdc28 8801383dbe00 [2.976933] 880136ffdc68 a00aa14a 880135c86400 [2.977182] a01c3de0 880136ffdca8 8174eeed [2.977427] Call Trace: [2.977505] [a00aa14a] rpc_pipefs_event+0x6a/0xb0 [sunrpc] [2.977617] [8174eeed] notifier_call_chain+0x4d/0x70 [2.977724] [8108ed28] __blocking_notifier_call_chain+0x58/0x80 [2.977837] [8108ed66] blocking_notifier_call_chain+0x16/0x20 [2.977964] [a00c4fdc] rpc_fill_super+0xfc/0x1b0 [sunrpc] [2.978081] [811b75a0] ? set_anon_super+0x30/0x30 [2.978190] [a00c4ee0] ? rpc_kill_sb+0x110/0x110 [sunrpc] [2.978298] [811b8565] mount_ns+0xa5/0xe0 [2.978400] [a00c3599] rpc_mount+0x29/0x30 [sunrpc] [2.978503] [811b91c3] mount_fs+0x43/0x1b0 [2.978603] [811d2e33] ? find_filesystem+0x63/0x80 [2.978706] [811d4116] vfs_kern_mount+0x76/0x120 [2.978807] [811d57a4] do_new_mount+0xa4/0x1f0 [2.978907] [811d6e06] do_mount+0x1e6/0x230 [2.979004] [811d6ee0] SyS_mount+0x90/0xe0 [2.979101] [81753a1d] system_call_fastpath+0x1a/0x1f [2.979204] Code: 01 00 00 48 89 de 48 8b 50 20 e8 54 f5 ff ff 48 85 c0 0f 84 8c 00 00 00 48 3d 00 f0 ff ff 77 5e 48 8b 7b 58 48 89 83 b0 00 00 00 48 8b 47 10 48 8b 50 38 31 c0 48 85 d2 74 44 ff d2 85 c0 74 3e [2.981267] RIP [a00a9618] __rpc_clnt_handle_event+0x48/0xd0 [sunrpc] [2.981436] RSP 880136ffdc18 [2.981516] CR2: 0010 [2.981626] ---[ end trace 3663d7a4a73c156e ]--- Please let me know if you guys need more info to resolve this. I'm afraid it makes NFS pretty useless here, right now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310350 Title: Oops __rpc_clnt_handle_event+0x48/0xd0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1310350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310350] Re: Oops __rpc_clnt_handle_event+0x48/0xd0
Without too many details, the problem seems to be triggered by some sort of race condition between the loading of the sunrpc module and using it (mounting the rpc_pipefs filesystem). This can happen in two places, as far as I can tell... in /etc/init/gssd.conf and /etc/init/idmapd.conf. On my system, I seem to have worked around the problem by: 1) Disabling GSSD in /etc/default/nfs-common (not used on my system anyways) 2) Adding a delay (sleep 1) just after the do_modprobe sunrpc on line 27 in /etc/init/idmapd.conf Before the workaround I was able to reproduce the problem in a few minutes by continously rebooting the system (basically adding a reboot command to /etc/rc.local). After the workaround, my test system rebooted continously for 90 minutes with no issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310350 Title: Oops __rpc_clnt_handle_event+0x48/0xd0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1310350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1289961] Re: 8086:08b2 [Lenovo ThinkPad T440s] Power management causes Intel wifi 7260 slowness
Lots of talk about bandwidth, but (IMHO) at least as interesting is ping times (because the results are instantly visible): I'm on a ThinkPad T431s with an Intel Corporation Centrino Advanced-N 6235 (rev 24) 3.13.0-24-generic without PM (pinging my AP): $ ping -c 5 192.168.8.2 PING 192.168.8.2 (192.168.8.2) 56(84) bytes of data. 64 bytes from 192.168.8.2: icmp_seq=1 ttl=64 time=0.882 ms 64 bytes from 192.168.8.2: icmp_seq=2 ttl=64 time=0.948 ms 64 bytes from 192.168.8.2: icmp_seq=3 ttl=64 time=0.960 ms 64 bytes from 192.168.8.2: icmp_seq=4 ttl=64 time=0.768 ms 64 bytes from 192.168.8.2: icmp_seq=5 ttl=64 time=0.848 ms --- 192.168.8.2 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4002ms rtt min/avg/max/mdev = 0.768/0.881/0.960/0.072 ms 3.13.0-24-generic with PM (pinging my AP): $ ping -c 5 192.168.8.2 PING 192.168.8.2 (192.168.8.2) 56(84) bytes of data. 64 bytes from 192.168.8.2: icmp_seq=1 ttl=64 time=96.9 ms 64 bytes from 192.168.8.2: icmp_seq=2 ttl=64 time=17.2 ms 64 bytes from 192.168.8.2: icmp_seq=3 ttl=64 time=39.4 ms 64 bytes from 192.168.8.2: icmp_seq=4 ttl=64 time=61.9 ms 64 bytes from 192.168.8.2: icmp_seq=5 ttl=64 time=84.7 ms --- 192.168.8.2 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4005ms rtt min/avg/max/mdev = 17.298/60.076/96.938/29.065 ms -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1289961 Title: 8086:08b2 [Lenovo ThinkPad T440s] Power management causes Intel wifi 7260 slowness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1289961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1098561] Re: Unsupported hardware watermark appears when FGLRX is installed on 13.04
Comfirmed on HD 7400M Series $ fglrxinfo display: :0.0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: AMD Radeon HD 7400M Series OpenGL version string: 4.2.11986 Compatibility Profile Context -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1098561 Title: Unsupported hardware watermark appears when FGLRX is installed on 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1098561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1058015] Re: compiz crashed with SIGSEGV in g_signal_emit_valist()
*** This bug is a duplicate of bug 1054499 *** https://bugs.launchpad.net/bugs/1054499 ** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1058015 Title: compiz crashed with SIGSEGV in g_signal_emit_valist() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1058015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1057833] Re: soffice.bin crashed with SIGSEGV in Menu::~Menu()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1057833 Title: soffice.bin crashed with SIGSEGV in Menu::~Menu() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1057833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1056067] Re: java crashed with SIGABRT in Java_com_sun_java_swing_plaf_gtk_GTKStyle_nativeGetXThickness()
** Visibility changed to: Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1056067 Title: java crashed with SIGABRT in Java_com_sun_java_swing_plaf_gtk_GTKStyle_nativeGetXThickness() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1056067/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046822] [NEW] Zooming does not work corrently
Public bug reported: In gnome-terminal CTRL-'+' and CTRL-'-' is supposed to zoom in and out respectively: Zoom in should: increase the font size and resize the window to match the new font size (keep rows and cols consistent) Zoom out should do the exact opposite: reduce the font size and resize the window to match the new font size (keep rows and cols consistent) This does not work within unity. Instead, it would appear that the font size is handled correctly, whereas the windows resizing is messed up. Consequently, repeating a few zoom ins and outs will result in an unusably small window - but with the font size corect. Note: It works, runing under gnome-shell ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1046822 Title: Zooming does not work corrently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1046822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046822] Re: Zooming does not work corrently
This is on quantal (up to date as per now) - Problem existed on precise last I checked too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1046822 Title: Zooming does not work corrently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1046822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 951246] Re: 13b1:002f Linksys AE1000 v1 802.11n [Ralink RT3572] not usable in network manager or elsewhere
Not a firefox bug but a missing driver AFAICT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/951246 Title: 13b1:002f Linksys AE1000 v1 802.11n [Ralink RT3572] not usable in network manager or elsewhere To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/951246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1019561] Re: 148f:5370 Please enable Ralink rt35xx and rt53xx support on the rt2800usb driver
When will a kernel with this fix be released? Pending that, is there somewhere to download a daily kernel package for Precise? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1019561 Title: 148f:5370 Please enable Ralink rt35xx and rt53xx support on the rt2800usb driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1019561/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 930916] Re: amavis start-stop script fails to stop amavisd
Any reason why this fix has not gone into final precise? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in Ubuntu. https://bugs.launchpad.net/bugs/930916 Title: amavis start-stop script fails to stop amavisd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/930916/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 930916] Re: amavis start-stop script fails to stop amavisd
Any reason why this fix has not gone into final precise? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/930916 Title: amavis start-stop script fails to stop amavisd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/930916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 905449] Re: Please fix dante package for precise
dante-client is not even installable in precise atm. Please let me know what I need to provide you with, to have this fixed. Please take a look at https://launchpad.net/~tmus/+archive/ppa/+sourcepub/2249432/+listing- archive-extra - This package installs and works on precise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/905449 Title: Please fix dante package for precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dante/+bug/905449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 510059] Re: Gvfs keeps asking for password when trying to mount Samba share
I have this exact problem on a freshly installed Precise. This is what I had to do, to fix the problem: in /etc/samba/smb.conf add the following to the bottom of the [global] section: client lanman auth = yes client ntlmv2 auth = no I could gvfs-mount a Windows 2008 share, but not an Alfresco CIFS share. With the above changes to smb.conf, I can access all shares withoput problems. I didn't have this problem on a freshly installed Oneiric machine, so I'm not sure what's changed og wether thes should be fixed in gvfs or in the default samba installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510059 Title: Gvfs keeps asking for password when trying to mount Samba share To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/510059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 905453] Re: Please upgrade for precise
Answering myself (Comment #4), the 0.12.5 package does not include an initscript for sfacctd og nfacctd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/905453 Title: Please upgrade for precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pmacct/+bug/905453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 905453] Re: Please upgrade for precise
Jamie, does the 0.12.5 package include initscripts for nfacctd and sfacctd? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/905453 Title: Please upgrade for precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pmacct/+bug/905453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 905449] [NEW] Please fix dante package for precise
Public bug reported: Dante (at least the client portion - socksify) has been broken on the past few releases of Ubuntu. Socksify would throw an error, trying to preload libraries (more details on this if you need it - see Bug #857598) Please make sure this works for precise - And why not update the package to a contemporary release at the same time. If you need somewhere to start, I have made an updated package (for oneiric and later) available in my ppa here: https://launchpad.net/~tmus/+archive/ppa - I've attempted to rework all relevant patches, and all look great to me, although that's not to say that it's flawless. I have successfully tested the client portion - socksify works great - and I have verified that the server portion starts and stops nicely (but not tested in beyond this). Thanks /Thomas ** Affects: dante (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/905449 Title: Please fix dante package for precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dante/+bug/905449/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 905453] [NEW] Please upgrade for precise
Public bug reported: There's a new upstream version of pmacct available, that would be great to get in precise. More urgent though, is the need for an initscript for sfacctd, nfacctd (only one for pmacctd is included, even though sfacctd and nfacctd are also provided by the package). As far as I can see - the pmacct initscript can very easily be adapted for sfacct and nfacct respectively. Please let me know I you need more info, assistance... /Thomas ** Affects: pmacct (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/905453 Title: Please upgrade for precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pmacct/+bug/905453/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 861265] Re: [Oneiric] [Regression] firefox title bar does not appear (same problem with thunderbird) no window decoration for either application.
In my case, I seem to loose the windows controls some times. Some times they are there... My feeling is, it usually has something to do with leaving fullscreen mode... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861265 Title: [Oneiric] [Regression] firefox title bar does not appear (same problem with thunderbird) no window decoration for either application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/861265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843350] [NEW] Unity task switched stuck in background (behind other windows)
Public bug reported: Running: Ubuntu oneiric (development branch), Unity 4.12.0-0ubuntu2. Task switcher gets stuck behind all the other active windows. Minimizing all other apps, makes it visible and shows it's actualy working fine - But it really should be in the foreground to be really useful. :-) Not sure what triggers the problem, but I've seen it happening. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/843350 Title: Unity task switched stuck in background (behind other windows) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/843350/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 780007] Re: [Natty] Stuttering video playback
Any news here? Could this problem be related to the missing libvideo.so Compiz Video Playback plugin? I'm having all these problems as well on Natty, using fglrx. Mplayer works sort of okay in fullscreen with gl output, but nowhere near optimal. Windowed gl output as well as xv output (fullscreen og windowed) performs really bad. Please let me know is you need any info from my system -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/780007 Title: [Natty] Stuttering video playback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/780007/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 652821] [NEW] evolution crashed with SIGSEGV in memcpy()
Public bug reported: Binary package hint: evolution Just connected by MAPI to Exchange 2010 server, Evolution was downloading messages and crashed during the initial sync-stuff... ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: evolution 2.30.3-1ubuntu5 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Fri Oct 1 07:01:48 2010 ExecutablePath: /usr/bin/evolution InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release Candidate amd64 (20100928) ProcCmdline: evolution ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f6fabd73b62 memcpy+210: mov(%rsi),%rax PC (0x7f6fabd73b62) ok source (%rsi) (0x) not located in a known VMA region (needed readable region)! destination %rax ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: evolution StacktraceTop: memcpy () from /lib/libc.so.6 ndr_push_bytes () from /usr/lib/libndr.so.0 ndr_push_array_uint8 () from /usr/lib/libndr.so.0 ndr_push_SBinary_short () from /usr/lib/libmapi.so.0 ndr_push_mapi_SPropValue_CTR () from /usr/lib/libmapi.so.0 Title: evolution crashed with SIGSEGV in memcpy() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash maverick -- evolution crashed with SIGSEGV in memcpy() https://bugs.launchpad.net/bugs/652821 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 652821] Re: evolution crashed with SIGSEGV in memcpy()
** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/652821/+attachment/1662065/+files/Dependencies.txt ** Attachment added: Disassembly.txt https://bugs.launchpad.net/bugs/652821/+attachment/1662066/+files/Disassembly.txt ** Attachment added: ProcMaps.txt https://bugs.launchpad.net/bugs/652821/+attachment/1662067/+files/ProcMaps.txt ** Attachment added: ProcStatus.txt https://bugs.launchpad.net/bugs/652821/+attachment/1662068/+files/ProcStatus.txt ** Attachment added: Registers.txt https://bugs.launchpad.net/bugs/652821/+attachment/1662069/+files/Registers.txt ** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/652821/+attachment/1662070/+files/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/652821/+attachment/1662071/+files/ThreadStacktrace.txt ** Attachment added: XsessionErrors.txt https://bugs.launchpad.net/bugs/652821/+attachment/1662072/+files/XsessionErrors.txt -- evolution crashed with SIGSEGV in memcpy() https://bugs.launchpad.net/bugs/652821 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447134] Re: Evolution (MAPI) crashes when trying to view/open mail
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/33350465/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/33350466/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/33350467/ProcStatus.txt -- Evolution (MAPI) crashes when trying to view/open mail https://bugs.launchpad.net/bugs/447134 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447134] [NEW] Evolution (MAPI) crashes when trying to view/open mail
Public bug reported: Binary package hint: evolution-mapi I have set up an account, connecting to my company Exchange 2007 server, using evolution-mapi. When opening Evolution, it retrieves message- and folder lists okay, but when I click on a mail to read it, evolution crashes almost every single time (I've only ever succeeded in successfully viewing 2 mails - Trying those same mails again later, also produced the crash). Also - I'm not any problems with evolution-exchange against Exchange 2003 og IMAP against the Exchange 2007 server. Please let me know what kind of debug info I can provide you guys with, to have this problem resolved. :-) ProblemType: Bug Architecture: amd64 Date: Fri Oct 9 08:30:30 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/evolution Package: evolution 2.28.0-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-12.41-generic SourcePackage: evolution Uname: Linux 2.6.31-12-generic x86_64 XsessionErrors: (gnome-settings-daemon:2429): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:2429): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:2533): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:2519): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (evolution:2698): libexchangemapi-WARNING **: ** Affects: evolution-mapi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- Evolution (MAPI) crashes when trying to view/open mail https://bugs.launchpad.net/bugs/447134 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
