Same issue here with
$ echo $XDG_CURRENT_DESKTOP
MATE
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04 LTS
Release:22.04
Codename: jammy
$ apt-cache policy evince
evince:
Installed: 42.1-3
Candidate: 42.1-3
Version table:
point taken, apologies for addressing the wrong audience, who indeed
volunteer their time to help.
I do not quite agree with the metaphor, as my old parcel deliverer has taken an
old working delivery back and pushed me a new delivery that doesn't work in my
environment - without prior notice or
Thanks for your attention to this bug report. I don't quite see how it's
invalid - the upgrading behavior implemented here is breaking systems
without prior notice (and without offering any choice).
The least that could have been done is warn during one update cycle and
switch over sometimes
Please, please, pretty please use apt for deb and snap for snap, and
don't pollute apt with snap packages.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1965960
Public bug reported:
$ lsb_release -rd
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04
$ apt-cache policy apt
apt:
Installed: 2.4.1
Candidate: 2.4.1
Version table:
*** 2.4.1 500
500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
Dimitri, indeed, my bad.
In other news: it seems that this issue has been known for a while and somebody
has been (trying to) solv(e|ing) it - I guess the solution will come to Ubuntu
at some stage...
https://github.com/systemd/systemd/pull/12004
Thanks for the feedback, looking forward to a
ER SECTION:
name.cc.dd.edu. 51243 IN A SOME_IP
;; Query time: 2 msec
;; SERVER: IPv4_3#53(IPv4_3)
;; WHEN: Thu Oct 31 13:50:01 CET 2019
;; MSG SIZE rcvd: 88
$ dig @IPv4_1 name.cc.dd.edu
; <<>> DiG 9.11.5-P4-5.1ubuntu2-Ubuntu <<>> @IPv4_1 name.cc.dd.edu
; (1 s
Hi Dan, thanks for the feedback.
Being at the office (University) my interface is configured correctly,
but name resolution fails for specific (local) names.
This was a problem before, I fixed it unlinking /run/systemd/stub-
resolv.conf and linking /run/systemd/resolv.conf to /etc/
I then
Hi everybody,
upgrading to 19.10 the fix from #8 (thanks for helping with previous
setups) does not seem to work anymore, as there's only a
/run/resolvconf/resolv.conf (no stub-resolve anymore), which now keeps
everything broken.
This leaves me with switching to another distro for the moment, as
Public bug reported:
systemd name resolution is broken in professional setups.
https://askubuntu.com/a/974482 used to provide a solution, simply ignore
stub-resolution (which is broken) and fall back to the normal name
resolution as configured (e.g. through dhcp).
this solution does not seem to
So mate used to be great but doesn't seem to be a solution anymore
either, type-ahead-find seemingly has been replaced for search-as-you-
type in mate sometimes this summer as well, too.
+1 for replacement, it could at least be a configuration option
--
You received this bug notification
Public bug reported:
Adding a lease section to a dhclient config file does not work, the
closing bracket is not merged into the generated config file, leading to
a broken config file. Is this a bug?
More specific: Trying to add a static fallback IP in case DHCP does not work. I
added into
I have a very similar situation on Ubuntu mate 17.10, I suddenly can
boot 4.13.0-36 only..
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1761121
Title:
Latest intel ucode
I seem to have a similar (the same) problem. Ubuntu 17.10 - sleep and
resume leaves the resolv.conf with a "search" directive that breaks name
resolution for any name within the domains mentioned in the search
directive.
Trying to resolve any name fails, as e.g.:
% systemd-resolve
: resolve
The file itself may be not specific to evince, but the behaviour that evince
tries to read it (and AppArmor denies that) is specific to the AppArmor profile
file that gets delivered with evince-common (/etc/apparmor.d/usr.bin.evince).
That is why i think it affects the package evince or
Public bug reported:
Upgrade failed
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-13-generic 4.4.0-13.29
ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
16 matches
Mail list logo
