[Touch-packages] [Bug 2017840] Re: ifupdown resolved script has typo
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/bugs/2017840 Title: ifupdown resolved script has typo Status in ifupdown package in Ubuntu: New Bug description: 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/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` used to appear before `mystatedir` on line 12, but that was when it was a function. When it was converted back from being a function, the 'local' keyword was removed, but the variables remained. Either make it into a function again, or delete line 12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2017840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017840] Re: ifupdown resolved script has typo
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 seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2017840 Title: ifupdown resolved script has typo Status in ifupdown package in Ubuntu: New Bug description: 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/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` used to appear before `mystatedir` on line 12, but that was when it was a function. When it was converted back from being a function, the 'local' keyword was removed, but the variables remained. Either make it into a function again, or delete line 12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2017840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017840] Re: ifupdown resolved script has typo
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 configuration: Invalid argument
# cat /run/network/ifupdown-inet-enp2s0
"DNS"="1.1.1.1"
"DOMAINS"="example.org"
```
And that comes from lines 47-51 of /etc/network/if-up.d/resolved:
```
if [ -n "$NEW_DNS" ]; then
cat <"$mystatedir/ifupdown-${ADDRFAM}-$interface"
"$DNS"="$NEW_DNS"
EOF
if [ -n "$NEW_DOMAINS" ]; then
cat <>"$mystatedir/ifupdown-${ADDRFAM}-$interface"
"$DOMAINS"="$NEW_DOMAINS"
EOF
```
Basically, the double-quotes around "$DNS" and "$DOMAINS" shouldn't be there,
because it's a here-doc.
But this reveals another bug: the variable $DOMAINS is used to hold
either "DOMAINS" or "DOMAINS6" in lines 41 or 44, but the actual search
domains in line 95.
Has this code ever worked?
--
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/2017840
Title:
ifupdown resolved script has typo
Status in systemd package in Ubuntu:
New
Bug description:
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/network/if-up.d/resolved
#!/bin/sh
#
# Script fragment to make ifupdown supply DNS infromation to resolved
#
case "$ADDRFAM" in
inet|inet6) : ;;
*) exit 0 ;;
esac
if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then
mystatedir statedir ifindex interface
```
I'm thinking that the word `local` used to appear before `mystatedir`
on line 12, but that was when it was a function. When it was
converted back from being a function, the 'local' keyword was removed,
but the variables remained.
Either make it into a function again, or delete line 12.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017840/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017840] Re: ifupdown resolved script has typo
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 255.255.255.0 ``` and it creates this file: ``` # cat /run/systemd/resolve/netif/3 # This is private data. Do not parse. LLMNR=yes MDNS=no SERVERS=DNS DOMAINS=DOMAINS ``` Oh, and when you run `ifup enp3s0` by hand, you get this error: ``` # ifup enp3s0 ifup: interface enp3s0 already configured # ifdown enp3s0 # ifup enp3s0 mkdir: missing operand Try 'mkdir --help' for more information. ``` It looks like this error is from line 26 of /etc/network/if-up.d/resolved: ``` if [ ! "$ifindex" ]; then return fi # mystatedir=/run/network mkdir -p $mystatedir statedir=/run/systemd/resolve/netif mkdir -p $statedir chown systemd-resolve:systemd-resolve $statedir ``` Not sure why mystatedir is commented out, but it looks like that's what's wrong this time. -- 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/2017840 Title: ifupdown resolved script has typo Status in systemd package in Ubuntu: New Bug description: 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/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` used to appear before `mystatedir` on line 12, but that was when it was a function. When it was converted back from being a function, the 'local' keyword was removed, but the variables remained. Either make it into a function again, or delete line 12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017840] Re: ifupdown resolved script has typo
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 notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/2017840 Title: ifupdown resolved script has typo Status in systemd package in Ubuntu: New Bug description: 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/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` used to appear before `mystatedir` on line 12, but that was when it was a function. When it was converted back from being a function, the 'local' keyword was removed, but the variables remained. Either make it into a function again, or delete line 12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017840] Re: ifupdown resolved script has typo
** 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 scripts: ``` # head -n 12 /etc/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` - I'm thinking that the word `local` should appear before `mystatedir` on line 12. - The `shellcheck` command is ok with that line, but only because it's not checking to see if `mystatedir` is an executable in the $PATH. + I'm thinking that the word `local` used to appear before `mystatedir` on + line 12, but that was when it was a function. When it was converted + back from being a function, the 'local' keyword was removed, but the + variables remained. + + Either make it into a function again, or delete line 12. -- 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/2017840 Title: ifupdown resolved script has typo Status in systemd package in Ubuntu: New Bug description: 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/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` used to appear before `mystatedir` on line 12, but that was when it was a function. When it was converted back from being a function, the 'local' keyword was removed, but the variables remained. Either make it into a function again, or delete line 12. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017840] [NEW] ifupdown resolved script has typo
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/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` should appear before `mystatedir` on line 12. The `shellcheck` command is ok with that line, but only because it's not checking to see if `mystatedir` is an executable in the $PATH. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** 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 lines of that script: + Here's the first 12 lines of those scripts: ``` # head -n 12 /etc/network/if-up.d/resolved - + #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in - inet|inet6) : ;; - *) exit 0 ;; - esac + inet|inet6) : ;; + *) exit 0 ;; + esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then - mystatedir statedir ifindex interface + mystatedir statedir ifindex interface ``` I'm thinking that the word `local` should appear before `mystatedir` on line 12. The `shellcheck` command is ok with that line, but only because it's not checking to see if `mystatedir` is an executable in the $PATH. -- 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/2017840 Title: ifupdown resolved script has typo Status in systemd package in Ubuntu: New Bug description: 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/network/if-up.d/resolved #!/bin/sh # # Script fragment to make ifupdown supply DNS infromation to resolved # case "$ADDRFAM" in inet|inet6) : ;; *) exit 0 ;; esac if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then mystatedir statedir ifindex interface ``` I'm thinking that the word `local` should appear before `mystatedir` on line 12. The `shellcheck` command is ok with that line, but only because it's not checking to see if `mystatedir` is an executable in the $PATH. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2017840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2011484] [NEW] ifup@%i.service systemd unit file can't be restarted for br0 device
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` or `ifdown br0`, everything works perfectly. If we run `systemctl restart ifup@br0`, br0 goes down but doesn't come back up. It prints this error: A dependency job for ifup@br0.service failed. See 'journalctl -xe' for details. The command `systemctl status ifup@br0` says (in part): Mar 13 15:09:10 example.com systemd[1]: ifup@br0.service: Bound to unit sys-subsystem-net-devices-br0.device, but unit isn't active. Mar 13 15:09:10 example.com systemd[1]: Dependency failed for ifup for br0. Mar 13 15:09:10 example.com systemd[1]: ifup@br0.service: Job ifup@br0.service/start failed with result 'dependency'. The lines in /lib/systemd/system/ifup@.service that seem to be causing the problem are: BindsTo=sys-subsystem-net-devices-%i.device After=sys-subsystem-net-devices-%i.device Versions tested+affected: ifupdown/jammy,now 0.8.36+nmu1ubuntu3 amd64 [installed] ifupdown/focal,now 0.8.35ubuntu1 amd64 [installed] Our workaround is to use `ifdown br0` and `ifup br0`, but it'd be nice if systemd could handle it. Thanks ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New -- 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/bugs/2011484 Title: ifup@%i.service systemd unit file can't be restarted for br0 device Status in ifupdown package in Ubuntu: New Bug description: 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` or `ifdown br0`, everything works perfectly. If we run `systemctl restart ifup@br0`, br0 goes down but doesn't come back up. It prints this error: A dependency job for ifup@br0.service failed. See 'journalctl -xe' for details. The command `systemctl status ifup@br0` says (in part): Mar 13 15:09:10 example.com systemd[1]: ifup@br0.service: Bound to unit sys-subsystem-net-devices-br0.device, but unit isn't active. Mar 13 15:09:10 example.com systemd[1]: Dependency failed for ifup for br0. Mar 13 15:09:10 example.com systemd[1]: ifup@br0.service: Job ifup@br0.service/start failed with result 'dependency'. The lines in /lib/systemd/system/ifup@.service that seem to be causing the problem are: BindsTo=sys-subsystem-net-devices-%i.device After=sys-subsystem-net-devices-%i.device Versions tested+affected: ifupdown/jammy,now 0.8.36+nmu1ubuntu3 amd64 [installed] ifupdown/focal,now 0.8.35ubuntu1 amd64 [installed] Our workaround is to use `ifdown br0` and `ifup br0`, but it'd be nice if systemd could handle it. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2011484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2011480] [NEW] /etc/network/if-up.d/resolved: 12: mystatedir: not found
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/network/if-up.d/resolved: 1 #!/bin/sh 2 # 3 # Script fragment to make ifupdown supply DNS infromation to resolved 4 # 5 6 case "$ADDRFAM" in 7 inet|inet6) : ;; 8 *) exit 0 ;; 9 esac 10 11 if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then 12 mystatedir statedir ifindex interface 13 14 interface=$IFACE 15 if [ ! "$interface" ]; then 16 return 17 fi Surprisingly, the same line is present in /etc/network/if- down.d/resolved and causes the same error message. Given that line 16 says 'return', I'm guessing that this used to be a function, and so line 12 might have started with 'local'...? Fortunately, this is just a cosmetic problem, generating a few errors in the system logs. ** Affects: ifupdown (Ubuntu) Importance: Undecided Status: New ** Package changed: bind9 (Ubuntu) => ifupdown (Ubuntu) -- 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/bugs/2011480 Title: /etc/network/if-up.d/resolved: 12: mystatedir: not found Status in ifupdown package in Ubuntu: New Bug description: 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/network/if-up.d/resolved: 1 #!/bin/sh 2 # 3 # Script fragment to make ifupdown supply DNS infromation to resolved 4 # 5 6 case "$ADDRFAM" in 7 inet|inet6) : ;; 8 *) exit 0 ;; 9 esac 10 11 if systemctl is-enabled systemd-resolved > /dev/null 2>&1; then 12 mystatedir statedir ifindex interface 13 14 interface=$IFACE 15 if [ ! "$interface" ]; then 16 return 17 fi Surprisingly, the same line is present in /etc/network/if- down.d/resolved and causes the same error message. Given that line 16 says 'return', I'm guessing that this used to be a function, and so line 12 might have started with 'local'...? Fortunately, this is just a cosmetic problem, generating a few errors in the system logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/2011480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1937899] Re: [Inspiron 5577, Realtek ALC3246, Black Headphone Out, Front] fails after a while
** 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: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1937899 Title: [Inspiron 5577, Realtek ALC3246, Black Headphone Out, Front] fails after a while Status in alsa-driver package in Ubuntu: New Status in alsa-driver package in Fedora: Unknown Status in alsa-driver package in openSUSE: New Bug description: 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 screen this issue is happening in both Firefox browser and chrome browser also. the volume in the speakers is already set to maximum level. Version-Release number of selected component (if applicable): Description: Ubuntu 21.04 Release: 21.04 How reproducible: all the times this issue is occurring Steps to Reproduce: 1.open any web browser and open any video website like youtube 2. set the volume in the system to less 30 percent or so then the audio is not able to listen even with slightest volume 3.in order the hear the audio again the volume need to be adjusted in the sound bar. Actual results:after playing the video pause it and again try to play the video the audio is not audible some times, again i have to adjust the slider to listen the audio. Expected results: the audio should be audible slightly even after setting the audio level set to 30 percent. Additional Information: Facing this issue in latest version of Fedora 34 also with the latest updated kernel 5.13.4-200.fc34.x86_64 and in red hat enterprise linux 8.4 too. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: swamych1002 F pulseaudio /dev/snd/pcmC0D0p: swamych1002 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 17:57:41 2021 InstallationDate: Installed on 2021-07-24 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5577, Realtek ALC3246, Black Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2018 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 00 dmi.board.vendor: Dell Inc. dmi.board.version: 000 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:br1.1:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn00:rvr000:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1937899/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1937899] [NEW] [Inspiron 5577, Realtek ALC3246, Black Headphone Out, Front] fails after a while
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 screen this issue is happening in both Firefox browser and chrome browser also. the volume in the speakers is already set to maximum level. Version-Release number of selected component (if applicable): Description:Ubuntu 21.04 Release:21.04 How reproducible: all the times this issue is occurring Steps to Reproduce: 1.open any web browser and open any video website like youtube 2. set the volume in the system to less 30 percent or so then the audio is not able to listen even with slightest volume 3.in order the hear the audio again the volume need to be adjusted in the sound bar. Actual results:after playing the video pause it and again try to play the video the audio is not audible some times, again i have to adjust the slider to listen the audio. Expected results: the audio should be audible slightly even after setting the audio level set to 30 percent. Additional Information: Facing this issue in latest version of Fedora 34 also with the latest updated kernel 5.13.4-200.fc34.x86_64 and in red hat enterprise linux 8.4 too. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: swamych1002 F pulseaudio /dev/snd/pcmC0D0p: swamych1002 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jul 24 17:57:41 2021 InstallationDate: Installed on 2021-07-24 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [Inspiron 5577, Realtek ALC3246, Black Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2018 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 00 dmi.board.vendor: Dell Inc. dmi.board.version: 000 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd12/02/2018:br1.1:svnDellInc.:pnInspiron5577:pvr1.1.3:rvnDellInc.:rn00:rvr000:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 5577 dmi.product.sku: 07E1 dmi.product.version: 1.1.3 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1937899 Title: [Inspiron 5577, Realtek ALC3246, Black Headphone Out, Front] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: 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 screen this issue is happening in both Firefox browser and chrome browser also. the volume in the speakers is already set to maximum level. Version-Release number of selected component (if applicable): Description: Ubuntu 21.04 Release: 21.04 How reproducible: all the times this issue is occurring Steps to Reproduce: 1.open any web browser and open any video website like youtube 2. set the volume in the system to less 30 percent or so then the audio is not able to listen even with slightest volume 3.in order the hear the audio again the volume need to be adjusted in the sound bar. Actual results:after playing the video pause it and again try to play the video the audio is not audible some times, again i have to adjust the slider to listen the audio. Expected results: the audio should be audible slightly even after setting the audio level set to 30 percent. Additional Information: Facing this issue in latest version of Fedora 34 also with the latest updated kernel 5.13.4-200.fc34.x86_64 and in red hat enterprise linux 8.4 too. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7
[Touch-packages] [Bug 1913933] [NEW] System freeze while dbus-daemon execution
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=1400 audit(1612017269.344:43): apparmor="DENIED" operation="open" profile="snap.standard-notes.standard-notes" name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 label="snap.standard-notes.standard-notes" Jan 30 15:34:29 ubuntu kernel: [24749.903525] exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ So I think this is related to the dbus-daemon. If you need any more information, please let me know so I can provide them. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dbus 1.12.20-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sun Jan 31 09:22:49 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/bash SourcePackage: dbus UpgradeStatus: Upgraded to groovy on 2021-01-24 (6 days ago) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Description changed: 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=1400 audit(1612017269.344:43): apparmor="DENIED" operation="open" profile="snap.standard-notes.standard-notes" name="/home/chshr/.dotfiles/config/.config/gtk-3.0/settings.ini" pid=21631 comm="standard-notes" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Jan 30 15:34:29 ubuntu kernel: [24749.903525] audit: type=1107 audit(1612017269.392:44): pid=1236 uid=103 auid=4294967295 ses=4294967295 subj=unconfined msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=21631 label="snap.standard-notes.standard-notes" Jan 30 15:34:29 ubuntu kernel: [24749.903525] exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?'
[Touch-packages] [Bug 1737282] [NEW] package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fede 1850 F...m pulseaudio /dev/snd/controlC0: fede 1850 F pulseaudio Date: Sat Dec 9 09:31:59 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2017-11-22 (16 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 (20171017.1) MachineType: Acer Aspire one ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=5366d7fb-dea5-49b7-8ac9-ca6f4ef3cc0d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 SourcePackage: initramfs-tools Title: package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2009 dmi.bios.vendor: Acer dmi.bios.version: V1.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire one dmi.board.vendor: Acer dmi.board.version: V1.21 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.21 dmi.modalias: dmi:bvnAcer:bvrV1.21:bd09/28/2009:svnAcer:pnAspireone:pvrV1.21:rvnAcer:rnAspireone:rvrV1.21:cvnAcer:ct10:cvrV1.21: dmi.product.family: Intel_Mobile dmi.product.name: Aspire one dmi.product.version: V1.21 dmi.sys.vendor: Acer ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package artful i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1737282 Title: package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: fede 1850 F...m pulseaudio /dev/snd/controlC0: fede 1850 F pulseaudio Date: Sat Dec 9 09:31:59 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2017-11-22 (16 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release i386 (20171017.1) MachineType: Acer Aspire one ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=5366d7fb-dea5-49b7-8ac9-ca6f4ef3cc0d ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7 SourcePackage: initramfs-tools Title: package linux-image-extra-4.13.0-19-generic 4.13.0-19.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2009 dmi.bios.vendor: Acer dmi.bios.version: V1.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire one dmi.board.vendor: Acer dmi.board.version: V1.21 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.21 dmi.modalias: dmi:bvnAcer:bvrV1.21:bd09/28/2009:svnAcer:pnAspireone:pvrV1.21:rvnAcer:rnAspireone:rvrV1.21:cvnAcer:ct10:cvrV1.21: dmi.product.family: Intel_Mobile dmi.product.name: Aspire one dmi.product.version: V1.21 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1737282/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574777] Re: tablet connected to monitor shows black screen - Idek Iiyama PL2409HD
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 packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1574777 Title: tablet connected to monitor shows black screen - Idek Iiyama PL2409HD Status in Canonical System Image: New Status in Mir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: When connecting my M10 device to my monitor (Idek Iiyama PL2409HD), the monitor shows that there is a signal on hdmi, but the screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574777] Re: tablet connected to monitor shows black screen - Idek Iiyama PL2409HD
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-system-image/+bug/1574777/+attachment/4660584/+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.launchpad.net/bugs/1574777 Title: tablet connected to monitor shows black screen - Idek Iiyama PL2409HD Status in Canonical System Image: New Status in Mir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: When connecting my M10 device to my monitor (Idek Iiyama PL2409HD), the monitor shows that there is a signal on hdmi, but the screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574777] Re: tablet connected to monitor shows black screen - Idek Iiyama PL2409HD
** 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.launchpad.net/bugs/1574777 Title: tablet connected to monitor shows black screen - Idek Iiyama PL2409HD Status in Canonical System Image: New Status in Mir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: When connecting my M10 device to my monitor (Idek Iiyama PL2409HD), the monitor shows that there is a signal on hdmi, but the screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574777] Re: tablet connected to monitor shows black screen - Idek Iiyama PL2409HD
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.491656] mirserver: New display configuration: [2016-05-10 22:53:54.500558] mirserver: 0.1: LVDS 10,0" 135x216mm [2016-05-10 22:53:54.500700] mirserver:Current mode 1200x1920 57,07Hz [2016-05-10 22:53:54.500730] mirserver:Preferred mode 1200x1920 57,07Hz [2016-05-10 22:53:54.500753] mirserver:Logical position +0+0 [2016-05-10 22:53:54.510085] mirserver: 0.2: DisplayPort 9,2" 203x114mm [2016-05-10 22:53:54.510203] mirserver:Current mode 1920x1080 0,60Hz [2016-05-10 22:53:54.510259] mirserver:Preferred mode 1920x1080 0,60Hz [2016-05-10 22:53:54.510330] mirserver:Logical position +1200+0 [2016-05-10 22:53:54.510371] mirserver: 0.3: unused LVDS [2016-05-10 22:54:49.797556] mirserver: New display configuration: [2016-05-10 22:54:49.832026] mirserver: 0.1: LVDS 10,0" 135x216mm [2016-05-10 22:54:49.841870] mirserver:Current mode 1200x1920 57,07Hz [2016-05-10 22:54:49.844096] mirserver:Preferred mode 1200x1920 57,07Hz [2016-05-10 22:54:49.846243] mirserver:Logical position +0+0 [2016-05-10 22:54:49.849306] mirserver: 0.2: unused DisplayPort [2016-05-10 22:54:49.850798] mirserver: 0.3: unused LVDS 3. M10's screen changes to the grey virtual touchpad immediately, after a few seconds the OSD of the monitor shows that there is something on hdmi, the backlights go on, but only black pixels. In the attach unity8.log: I made a "service lightdm restart", plugged in the tv , saw the desktop on the tv-screen, unplugged the tv, plugged in the monitor, waited a few 30 seconds, unplugged the monitor. ** Attachment added: "unity8.log" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574777/+attachment/4660210/+files/unity8.log ** Changed in: canonical-devices-system-image Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1574777 Title: tablet connected to monitor shows black screen - Idek Iiyama PL2409HD Status in Canonical System Image: New Status in Mir: Incomplete Status in mir package in Ubuntu: Incomplete Status in qtmir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: When connecting my M10 device to my monitor (Idek Iiyama PL2409HD), the monitor shows that there is a signal on hdmi, but the screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1574777/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
