FWIW, this would be complicated, because the profile.d scripts construct
DEBUGINFOD_URLS (and related variables) by concatenating other .d style
files under /etc/debuginfod/. pam_env's /etc/environment.* facilities
cannot do that, AFAIK.
--
You received this bug notification because you are a me
The upstream source doesn't have the error:
https://salsa.debian.org/debian/ifupdown/-/blob/master/debian/if-up.d/resolved#L69
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bug
My apologies, I neglected to specify these details:
OS: Ubuntu 22.04.2 LTS
Package: ifupdown
Version: 0.8.36+nmu1ubuntu3
It's the latest version of ifupdown.
** Package changed: systemd (Ubuntu) => ifupdown (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch
Whoops, found another bug:
```
# ifup enp2s0
/etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-enp2s0:
DNS=1.1.1.1: not found
/etc/network/if-up.d/resolved: 2: /run/network/ifupdown-inet-enp2s0:
DOMAINS=example.org: not found
Failed to parse DNS server address: DNS
Failed to set DNS
After fixing those lines, there's yet another bug:
```
search example.org DOMAINS
```
Somehow it's deciding that the DNS search domains for static interfaces is
"DOMAINS". Sample /etc/network/interface file:
```
auto enp3s0
iface enp3s0 inet static
address 172.16.198.5
netmask 25
There's another similar typo in the /etc/network/if-up.d/resolved script, on
line 71:
```
if ! cmp --silent "$oldstate" "$newstate" 2>/dev/null; then
DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE
# v4 first
```
Comment it out, as it's not valid code.
--
You received this bug notifi
** Description changed:
This error happens when you try to run ifup or ifdown:
```
# ifdown enp3s0
/etc/network/if-down.d/resolved: 12: mystatedir: not found
# ifup enp3s0
/etc/network/if-up.d/resolved: 12: mystatedir: not found
```
Here's the first 12 lines of those scrip
Public bug reported:
This error happens when you try to run ifup or ifdown:
```
# ifdown enp3s0
/etc/network/if-down.d/resolved: 12: mystatedir: not found
# ifup enp3s0
/etc/network/if-up.d/resolved: 12: mystatedir: not found
```
Here's the first 12 lines of those scripts:
```
# head -n 12 /etc
Public bug reported:
On Ubuntu 20.04 and 22.04, we've configured a bridged device (br0) in
/etc/network/interfaces like this:
auto br0
iface br0 inet static
address 172.16.201.5
netmask 255.255.255.0
broadcast 172.16.201.255
bridge_ports none
If we run `ifup br0`
Public bug reported:
We're using ifupdown-0.8.36+nmu1ubuntu3.deb on Ubuntu 22.04, and when
the system starts, it prints this line in /var/log/syslog and the
journal:
Mar 13 14:18:15 hostname-goes-here ifup[506]: /etc/network/if-
up.d/resolved: 12: mystatedir: not found
The relevant lines in /etc
** Bug watch added: Red Hat Bugzilla #1981602
https://bugzilla.redhat.com/show_bug.cgi?id=1981602
** Also affects: alsa-driver (Fedora) via
https://bugzilla.redhat.com/show_bug.cgi?id=1981602
Importance: Unknown
Status: Unknown
** Also affects: alsa-driver (openSUSE)
Importance
Public bug reported:
Description of problem:when using the youtube videos in web browser
after pausing the video the audio is not audible if audio level in the
system is set than less than 30 percent in order to listen to audio the
slider need to be changed to more than 35 percent in the desktop s
Public bug reported:
I regularly get my system frozen while using. It does not occur on any
user interaction I do periodically, so I checked the log files last time
it happened:
These are the last 3 kernel log entries before the freeze:
Jan 30 15:34:29 ubuntu kernel: [24749.856278] audit: type=1
Public bug reported:
bug bug bug
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: linux-image-extra-4.13.0-19-generic 4.13.0-19.22
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic i686
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: i386
AudioDevice
Ok. As said, I see "0.6Hz" when connecting to my tv, which works.
Can this bug report "merged" with
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574635
Seems to me the very same problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
Sorry, I'd attached the wrong unity8.log. Now this one is the one I
described above.
Hmm, and why can you ignore that the mirserver logs the same wrong
information about the display for two different monitors?
** Attachment added: "unity8.log"
https://bugs.launchpad.net/canonical-devices-sys
** Attachment removed: "unity8.log"
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574777/+attachment/4660210/+files/unity8.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.l
Because Stephen mentioned on the mailing list that it could depend on the
cable, I bought a second one, but no luck with that either.
1. sorry, the M10 is my only tablet/phone with hdmi
2. tablet+cables work on my LCD-TV. It seems my tv also wants a refresh
rate of 0,60Hz
[2016-05-10 22:53:54.4
18 matches
Mail list logo
