I was able to solve my problem by setting the dns-priority of my VPN
connection to a negative value: `nmcli connection modify
ipv4.dns-priority -100`. You might be able to resolve
your issue by setting the dns-priority of your VPN connection to a
*higher* value (e.g. equal to that of the other con
What type of VPN connection are you using?
I am using network-manager-openvpn, and it has the opposite behavior (I
can only get it to append a new DNS server to the list reported by
`systemd-resolve --status`, while in my case, I would like network-
manager to *only* use the VPN DNS).
The change
Public bug reported:
After upgrading to kubuntu 13.04, I found that I was unable to install
pyxml via setuptools. It would throw the following error during the
build process:
extensions/expat/lib/xmlparse.c:75:2: error: #error memmove does not
exist on this platform, nor is a substitute available
Warning: antenna connector problem too !
That's a shame, I just discovered that the Ralink RT3290 has a quite bad
antenna connector.
So my antenna was not correctly connected, now that's not perfect but much
better...
Good luck everyone !
--
You received this bug notification because you are a
Hi everyone !
I tried everything but I have the same slow signal problem...
Anyone has a new idea on how to fix that ?
Thanks a lot ;)
Cedric.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1049466
Tit
I hate to be "that guy" but somebody has to say what I'm sure others are
thinking.
It's a horrible decision to ship a broken Mesa in a desktop-oriented
distro, when both major desktop environments (Unity and KDE) use or rely
on it, and it affects nearly-ubiquitous commodity video hardware.
It was
I will like to may have that on the AVG internet
** Also affects: postfix
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/10436
Title:
Postfix shou
** Patch added: "stunnel.init.in.patch"
https://bugs.launchpad.net/bugs/882110/+attachment/2573882/+files/stunnel.init.in.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/882110
Title:
init s
Public bug reported:
The Linux Standards Base requires SysV init scripts to support the
'status' action. That is, I should be able to run '/etc/init.d/stunnel4
status' to find out whether stunnel is running.
See: http://wiki.debian.org/LSBInitScripts.
For certain applications, LSB compatibility
