[Bug 1766076] Re: USB over thunderbolt turns off every once in a while

Interesting, I am on a Precision 7530 on the 1.6.0 BIOS and I am definitely still having the problems. Tuomas, what method did you use to update the BIOS and the TB18DC firmware? And can you document the BIOS settings you have in place relating to thunderbolt? -- You received this bug

[Bug 1815275] Re: logind fails to detect amdgpu external displays as external.

Marking as invalid because this isn't actually what's going on. The xrandr name isn't used, the sysfs/udev node name is, and that is correct. Something else is triggering the behavior, but that will need to be tracked in it's own bug. Sorry for the noise. ** Changed in: systemd (Ubuntu)

[Bug 1815275] [NEW] logind fails to detect amdgpu external displays as external.

Public bug reported: So, with a Dell Precision 7530 outfitted with an AMD GPU, I can run into issues relating to systemd not detecting that my laptop is docked. This results in my booting the system, getting the login prompt on my external displays, logging in, and having the system immediately

[Bug 1766076] Re: USB over thunderbolt turns off every once in a while

Alright, I have a little more detail, but it's still largely a puzzle. My current machine state (expected to remain this way until the next reboot), is that any time I plug a USB device into a port under the xHCI controller in the TB18DC dock, the xHCI controller dies a horrible death. This is

[Bug 1766076] Re: USB over thunderbolt turns off every once in a while

So, I am seeing this as well on Ubuntu 18.04, with a Dell Precision 7530 with the TB18DC, powered via the dock. I am running a mainline kernel, 4.20.6 at the moment. Of note, this is (by a huge margin) mostly triggered at the time of USB plugin for me, specifically off of any port on the dock,

[Bug 1584407] Re: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)

$ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ uname -r 4.15.0-43-generic [0.00] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20170831/dswload-210) [0.00] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog

[Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

Ryan, The problem is not that a recent change in resolvconf caused a regression. The problem with resolvconf is that the upgrade to network-manager exposed an existing bug in resolvconf. This happens because the new version of network-manager now tells resolvconf that it must only use a

[Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

After two and a half weeks, can we please get a build of resolvconf with http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b applied pushed out? We don't even need the full new release of resolvconf, we just need the documented bug

[Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

So, this managed to break at least my VPN setup quite well. See #1672491 with the details, but the short version is that 'specify egress interface for each dnsmasq upstream server' breaks things in two cases. The first could be argued to be a bug on the VPN client side, though a behavior change

[Bug 1672491] Re: New NetworkManager breaks VPN DNS.

Alright, this is due to a change to 1.2.4: commit 2f12f485607590d6415cf5fb81ad4db5b04615cd Author: Beniamino Galvani Date: Wed May 11 18:43:41 2016 +0200 dns: specify egress interface for each dnsmasq upstream server Currently we don't specify to dnsmasq

[Bug 1672491] [NEW] New NetworkManager breaks VPN DNS.

Public bug reported: Alright, this is going to be a frustrating bug for everyone involved I expect, but here goes. On Ubuntu 16.04, using a non-released VPN client (making this _much_ harder for anyone to reproduce), upgrading the network-manager packages from 1.2.2-0ubuntu0.16.04.3 to

[Bug 1435664] Re: Installer crashes trying to install grub on EFI system with custom partition latout.

Well, this really was my fault. I forgot to make a separate /boot partition outside of the encrypted area. Once I reinstalled with that fixed it broke differently, specifically no /etc/crypttab was created, and so the initramfs didn't know how to access the root partition. Still not fun, but

[Bug 1435664] [NEW] Installer crashes trying to install grub on EFI system with custom partition latout.

Public bug reported: Installing Ubuntu 14.10 on an HP x360 13 unit. This is a UEFI system running Windows 8.1. The goal was to do dual boot, with an encrypted partition containing LVM, with root and swap under the LVM. I ended up creating the crypt partition with the installer, and then had to

[Bug 1302331] Re: org.freedesktop.login1.service references non-existant systemd-logind-launcher, gdm will not start

*** This bug is a duplicate of bug 1302264 *** https://bugs.launchpad.net/bugs/1302264 With 204-5ubuntu17 the package is still not shipping systemd-logind- launch, which is still referred to by /usr/share/dbus-1/system- services/org.freedesktop.login1.service. I'll have to retest to see if

[Bug 1302331] [NEW] org.freedesktop.login1.service references non-existant systemd-logind-launcher, gdm will not start

Public bug reported: debian/patches/debian-changes alters systemd-204/src/login/org.freedesktop.login1.service to exec /lib/systemd/systemd-logind-launch, instead of /bin/false. systemd-logind-launch is in debian/, and the override_dh_install rule in debian/rules does an install. Sadly,

[Bug 598375] Re: socksify fails running wine

Alright, so I have bisected down my crash to bcd5023c961a44c7149936553b6929b2b233dd27, which alters the lid detection logic. Reverting this change in 2.6.39 results in a kernel that is vaguely usable, however there is no output to the laptop's display. Closing the lid works, it redetects

[Bug 598375] Re: socksify fails running wine

... If someone could please tell me how to delete or modify comments here, my last comment was on the wrong bug entirely, my apologies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/598375 Title:

[Bug 398155] Re: evolution forgotten password google calendar

I tried to create it as a google calendar but did not work and then I created webcal experiencing this problem. I believe that the cause is the keychain ubuntu. when they asked me if I wanted to grant access evolution I said no. now makes me not store even if evolution is set to remember. now I

[Bug 398155] Re: evolution forgotten password google calendar

ps: i removed and reinstalled evolution (deleting the configuration) -- evolution forgotten password google calendar https://bugs.launchpad.net/bugs/398155 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list

[Bug 398155] Re: evolution forgotten password google calendar

Note: I added the calendar as follows: New- Calendar-On the web, and then I entered the address ical's google calendar. -- evolution forgotten password google calendar https://bugs.launchpad.net/bugs/398155 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 398155] [NEW] evolution forgotten password google calendar

Public bug reported: Binary package hint: evolution After following the guide: http://wiki.ubuntu- it.org/InternetRete/Messaggistica/Evolution/GoogleCalendar?highlight=(google), evolution asks me my password to log on to google account. by selecting remember password evolution calls for the

[Bug 398155] Re: evolution forgotten password google calendar

** Attachment added: Dependencies.txt http://launchpadlibrarian.net/28909090/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/28909091/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/28909092/ProcStatus.txt -- evolution