I realize that the conflict is probably intended and my issue is that
vanilla-gnome-desktop relies on pulseaudio still. I'll create a separate
bug, sorry.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
h
I seem to hit the same dep issues on a freshly installed 23.04 system
when trying to install vanilla-gnome-desktop.
The following packages have unmet dependencies:
pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be
installed
pipewire-audio : Conflicts: pulseaudio but 1:16.
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 p
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 f
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
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/18
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 th
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
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
Touch seeded packages, which is subscribed to tzdata in Ubunt
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 notif
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
@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
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 receiv
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
*** 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 receive
*** 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 notificati
*** 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 receive
*** 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 receive
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
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
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1629611
Title:
dns server priority broken
Status in Net
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
Touch
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 Netw
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
"workd
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
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
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
h
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
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
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 shoul
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
Touch seeded packages, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/499773
Title:
Race with ureadahead can
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:/
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.l
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1532553
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
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
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1532553
Title:
/et
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
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 wor
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 pl
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
Touch seeded packages, which is subscribed to systemd
37 matches
Mail list logo
