[Touch-packages] [Bug 2074210] Re: systemd-coredump not installable on 24.04
> Yeah, you need an entry enabling noble-updates for universe. ok, it works!! thank you! -- 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/2074210 Title: systemd-coredump not installable on 24.04 Status in systemd package in Ubuntu: Invalid Bug description: $ sudo apt install systemd-coredump [sudo] password for paolo: Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: systemd-coredump : Depends: libsystemd-shared (= 255.4-1ubuntu8) but 255.4-1ubuntu8.2 is to be installed E: Unable to correct problems, you have held broken packages. There is no way to resolve that. libsystemd-shared cannot be downgraded ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-coredump (not installed) ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Fri Jul 26 10:10:31 2024 InstallationDate: Installed on 2023-10-25 (276 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2074210/+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 2074210] Re: systemd-coredump not installable on 24.04
universe deb http://cu.archive.ubuntu.com/ubuntu/ noble multiverse deb http://security.ubuntu.com/ubuntu noble-security main restricted deb http://security.ubuntu.com/ubuntu noble-security universe deb http://security.ubuntu.com/ubuntu noble-security multiverse deb http://cu.archive.ubuntu.com/ubuntu/ noble-backports restricted universe multiverse main -- 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/2074210 Title: systemd-coredump not installable on 24.04 Status in systemd package in Ubuntu: Incomplete Bug description: $ sudo apt install systemd-coredump [sudo] password for paolo: Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: systemd-coredump : Depends: libsystemd-shared (= 255.4-1ubuntu8) but 255.4-1ubuntu8.2 is to be installed E: Unable to correct problems, you have held broken packages. There is no way to resolve that. libsystemd-shared cannot be downgraded ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-coredump (not installed) ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Fri Jul 26 10:10:31 2024 InstallationDate: Installed on 2023-10-25 (276 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2074210/+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 2074210] [NEW] systemd-coredump not installable on 24.04
Public bug reported: $ sudo apt install systemd-coredump [sudo] password for paolo: Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: systemd-coredump : Depends: libsystemd-shared (= 255.4-1ubuntu8) but 255.4-1ubuntu8.2 is to be installed E: Unable to correct problems, you have held broken packages. There is no way to resolve that. libsystemd-shared cannot be downgraded ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-coredump (not installed) ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Fri Jul 26 10:10:31 2024 InstallationDate: Installed on 2023-10-25 (276 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (92 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- 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/2074210 Title: systemd-coredump not installable on 24.04 Status in systemd package in Ubuntu: New Bug description: $ sudo apt install systemd-coredump [sudo] password for paolo: Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: systemd-coredump : Depends: libsystemd-shared (= 255.4-1ubuntu8) but 255.4-1ubuntu8.2 is to be installed E: Unable to correct problems, you have held broken packages. There is no way to resolve that. libsystemd-shared cannot be downgraded ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: systemd-coredump (not installed) ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8 Uname: Linux 6.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Fri Jul 26 10:10:31 2024 InstallationDate: Installed on 2023-10-25 (276 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: Upgraded to noble on 2024-04-25 (92 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2074210/+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 2039280] Re: Support IP address protocol
** Also affects: iproute2 (Ubuntu Mantic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
New
Status in iproute2 source package in Mantic:
New
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
Two clean upstream cherry-picks, regression potential should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+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 2039280] Re: Support IP address protocol
** Patch added: "iproute2_6.1.0-1ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+attachment/5709212/+files/iproute2_6.1.0-1ubuntu3.debdiff
** Description changed:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
- Two clean upstream cherry-picks so regression potential is low.
+ Two clean upstream cherry-picks, low regression potential is low.
** Description changed:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
- Two clean upstream cherry-picks, low regression potential is low.
+ Two clean upstream cherry-picks, regression potential should be low.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
New
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
Two clean upstream cherry-picks, regression potential should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More
[Touch-packages] [Bug 2039280] Re: Support IP address protocol
** Description changed:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
-
+
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
-
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
- Alternativerly, you could download Linux v6.5 and run:
+ Alternativerly, you could download Linux v6.5 source code and run:
- $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t
- kci_test_address_proto
-
+ $ cd linux
+ $ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
The cherry-picked patches are 2 upstream commits so regression potential
is low.
** Description changed:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
- The cherry-picked patches are 2 upstream commits so regression potential
- is low.
+ Two clean upstream cherry-picks so regression potential is low.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
New
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 source code and run:
$ cd linux
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t kci_test_address_proto
[Regression potential]
Two clean upstream cherry-picks so regression potential is low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+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 2039280] [NEW] Support IP address protocol
Public bug reported:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 and run:
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t
kci_test_address_proto
[Regression potential]
The cherry-picked patches are 2 upstream commits so regression potential
is low.
** Affects: iproute2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
New
Bug description:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to the actor in question.
Support for this feature was merged with commit 47f0bd503210 ("net: Add new
protocol attribute to IP addresses"), for kernel 5.18.
In this patch, add support for setting the protocol attribute at IP address
addition, replacement, and listing requests.
[Fix]
Apply the attached patch
[How to test]
$ cat << EOF > test.sh
#!/bin/sh
addr=192.0.2.1/28
addr2=${addr%/*}2/${addr#*/}
ifr=test-dummy123
sudo ip link add name "$ifr" type dummy
sudo ip link set "$ifr" up
sudo ip address add dev "$ifr" "$addr2" proto 0x99
sudo ip link del "$ifr"
EOF
$chmod +x test.sh
$test.sh
$ echo $?
0
if you get an error instead, like:
Error: either "local" is duplicate, or "proto" is a garbage.
your iproute2 is not patched.
Alternativerly, you could download Linux v6.5 and run:
$ sudo ./tools/testing/selftests/net/rtnetlink.sh -t
kci_test_address_proto
[Regression potential]
The cherry-picked patches are 2 upstream commits so regression
potential is low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+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 2016908] Re: Unable to deploy hosts with lunar images after 20230319 - fails to connect and download squashfs
Kernel side:
kernel/sys.c::SYSCALL_DEFINE5(prctl, int, option,...):
{
struct task_struct *me = current;
unsigned char comm[sizeof(me->comm)];
long error;
error = security_task_prctl(option, arg2, arg3, arg4, arg5);
if (error != -ENOSYS)
return error;
error = 0;
switch (option) {
case PR_SET_PDEATHSIG:
if (!valid_signal(arg2)) {
error = -EINVAL;
break;
}
me->pdeath_signal = arg2;
break;
...
return error;
}
and include/linux/signal.h::valid_signal():
/* Test if 'sig' is valid signal. Use this instead of testing _NSIG directly */
static inline int valid_signal(unsigned long sig)
{
return sig <= _NSIG ? 1 : 0;
}
and arch/x86/include/asm/signal.h:#define _NSIG 64
I wonder about security_task_prctl() though.
--
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/2016908
Title:
Unable to deploy hosts with lunar images after 20230319 - fails to
connect and download squashfs
Status in maas-images:
Incomplete
Status in systemd package in Ubuntu:
New
Bug description:
I'm assuming the image being used for these deploys is 20230417 or
20230417.1 based on the fact that I saw a 6.2 kernel being used which
I don't believe was part of the 20230319 serial. I don't have access
to the maas server, so I can't directly check any log files.
MAAS Version: 3.3.2
Here's where the serial log indicates it can't download the squashfs. The
full log is attached as scobee-lunar-no-squashfs.log (there are some other
console message intermixed):
no search or nameservers found in /run/net-BOOTIF.conf /run/net-*.conf
/run/net6
-*.conf
::
root=squash:http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.04/lunar/candi
date/squa[ 206.804704] Btrfs loaded, crc32c=crc32c-generic, zoned=yes,
fsverity
=yes
shfs
:: mount_squash downloading
http://10.229.32.21:5248/images/ubuntu/arm64/ga-23.0
4/lunar/candidate/squashfs to /root.tmp.img
Connecting to 10.229.32.21:5248 (10.229.32.21:5248)
wget: can't connect to remote host (10.229.32.21): Network is unreachable
:: mount -t squashfs -o loop '/root.tmp.img' '/root.tmp'
mount: mounting /root.tmp.img on /root.tmp failed: No such file or directory
done.
Still gathering logs and info and will update as I go.
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas-images/+bug/2016908/+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 1958127] [NEW] jammy:armhf assertion fail ../../bfd/elf32-arm.c:14759
Public bug reported: While running glibc autopkgtsts, ld assertion fail like this: arm-linux-gnueabihf-gcc-10 -shared -static-libgcc -Wl,-dynamic-linker=/lib/ld-linux-armhf.so.3 -Wl,-z,defs -B/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/csu/ -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/math -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/dlfcn -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nss -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nis -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/rt -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/resolv -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/mathvec -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/support -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nptl -Wl,-rpath-link=/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/math:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/dlfcn:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nss:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nis:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/rt:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/resolv:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/mathvec:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/support:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nptl -o /tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf/sotruss-lib.so /tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/csu/abi-note.o -Wl,--as-needed /tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf/sotruss-lib.os -Wl,--no-as-needed -Wl,--start-group /tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/libc.so /tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/libc_nonshared.a -Wl,--as-needed /tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf/ld.so -Wl,--no-as-needed -Wl,--end-group mv -f /tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf/ld-linux-armhf.so.3.new /tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf/ld-linux-armhf.so.3 /usr/bin/ld: BFD (GNU Binutils for Ubuntu) 2.37 assertion fail ../../bfd/elf32-arm.c:14759 collect2: error: ld returned 1 exit status Full log here: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy- canonical-kernel-team- bootstrap/jammy/armhf/g/glibc/20220114_114517_661dd@/log.gz ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Affects: binutils (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: binutils (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1958127 Title: jammy:armhf assertion fail ../../bfd/elf32-arm.c:14759 Status in binutils package in Ubuntu: New Status in binutils source package in Jammy: New Bug description: While running glibc autopkgtsts, ld assertion fail like this: arm-linux-gnueabihf-gcc-10 -shared -static-libgcc -Wl,-dynamic-linker=/lib/ld-linux-armhf.so.3 -Wl,-z,defs -B/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/csu/ -Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/math -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/dlfcn -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nss -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nis -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/rt -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/resolv -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/mathvec -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/support -L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nptl
[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
I have the same issue with the headphone's microphone. My Bose 700 connects and has sound output for A2DP, but terrible audio quality (HSP/HFP) when switching on headphone's microphone. Laptop: Acer Predator G9 591 2016 OS: Ubuntu 20.04.01 LTS Kernel: 5.4.0-66-generic Headset: Bose 700 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1912609] Re: mac80211_hwsim: hostapd fails to start with S1G band
** Patch added: "Upstream cherry pick for S1G band fix" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+attachment/5455144/+files/wpa_2.9-1ubuntu10.debdiff -- 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/1912609 Title: mac80211_hwsim: hostapd fails to start with S1G band Status in wpa package in Ubuntu: New Status in wpa source package in Hirsute: New Bug description: Hostapd fails to start on a recent 5.10+ kernel: $ cat repro.sh #!/bin/sh sudo modprobe mac80211_hwsim sudo ip a flush dev wlan0 sudo ip a add 192.168.5.1/24 dev wlan0 cat << EOF > hostapd.conf interface=wlan0 driver=nl80211 hw_mode=b channel=1 ssid=fake net EOF sudo hostapd hostapd.conf ubuntu@hirsute-amd64:~$ ./repro.sh Configuration file: hostapd.conf nl80211: kernel reports: expected nested data Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED ^C wlan0: interface state ENABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING nl80211: deinit ifname=wlan0 disabled_11b_rates=0 this due to the mismanagement of the newly added S1G band, the attached patch fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+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 1912609] [NEW] mac80211_hwsim: hostapd fails to start with S1G band
Public bug reported: Hostapd fails to start on a recent 5.10+ kernel: $ cat repro.sh #!/bin/sh sudo modprobe mac80211_hwsim sudo ip a flush dev wlan0 sudo ip a add 192.168.5.1/24 dev wlan0 cat << EOF > hostapd.conf interface=wlan0 driver=nl80211 hw_mode=b channel=1 ssid=fake net EOF sudo hostapd hostapd.conf ubuntu@hirsute-amd64:~$ ./repro.sh Configuration file: hostapd.conf nl80211: kernel reports: expected nested data Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED ^C wlan0: interface state ENABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING nl80211: deinit ifname=wlan0 disabled_11b_rates=0 this due to the mismanagement of the newly added S1G band, the attached patch fixes it. ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Affects: wpa (Ubuntu Hirsute) Importance: Undecided Status: New ** Patch added: "Upstream cherry pick for S1G band fix" https://bugs.launchpad.net/bugs/1912609/+attachment/5455142/+files/wpa_2.9-1ubuntu10.debdiff ** Also affects: wpa (Ubuntu Hirsute) Importance: Undecided Status: New ** Patch removed: "Upstream cherry pick for S1G band fix" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+attachment/5455142/+files/wpa_2.9-1ubuntu10.debdiff -- 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/1912609 Title: mac80211_hwsim: hostapd fails to start with S1G band Status in wpa package in Ubuntu: New Status in wpa source package in Hirsute: New Bug description: Hostapd fails to start on a recent 5.10+ kernel: $ cat repro.sh #!/bin/sh sudo modprobe mac80211_hwsim sudo ip a flush dev wlan0 sudo ip a add 192.168.5.1/24 dev wlan0 cat << EOF > hostapd.conf interface=wlan0 driver=nl80211 hw_mode=b channel=1 ssid=fake net EOF sudo hostapd hostapd.conf ubuntu@hirsute-amd64:~$ ./repro.sh Configuration file: hostapd.conf nl80211: kernel reports: expected nested data Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED ^C wlan0: interface state ENABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING nl80211: deinit ifname=wlan0 disabled_11b_rates=0 this due to the mismanagement of the newly added S1G band, the attached patch fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+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 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD
I'm at the end of a Ubuntu installation on a pre-installed windows laptop. I have the same issue Ubuntu 20 hangs at "kvm: exiting hardware virtualization" on AMD laptop. It has been stuck there for half an hour or more. I didn't set the wi-fi connection during installation -- 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/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD Status in dellserver: New Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+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 1881292] [NEW] Linux 5.7: autopkgtest failures - lxc-test-cloneconfig && lxc-destroy
Public bug reported: ... make[1]: Leaving directory '/tmp/autopkgtest.OzTsXV/build.myP/src' PASS: lxc-tests: lxc-test-api-reboot (75s) PASS: lxc-tests: lxc-test-apparmor (1s) PASS: lxc-tests: lxc-test-apparmor-generated (0s) PASS: lxc-tests: lxc-test-apparmor-mount (25s) PASS: lxc-tests: lxc-test-attach (0s) PASS: lxc-tests: lxc-test-autostart (38s) PASS: lxc-tests: lxc-test-basic (0s) PASS: lxc-tests: lxc-test-cgpath (0s) PASS: lxc-tests: lxc-test-checkpoint-restore (0s) FAIL: lxc-tests: lxc-test-cloneconfig (1s) --- lxc-destroy: lxctestb: tools/lxc_destroy.c: main: 242 Container is not defined Test 1 starting (/tmp/lxctest-2SbLtT/1.conf) lxc-destroy: lxctestb2: tools/lxc_destroy.c: main: 242 Container is not defined FAIL --- ... Groovy 5.7 kernel here: https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/bootstrap - linux-5.7 Full log here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy-canonical-kernel-team- bootstrap/groovy/amd64/l/lxc/20200528_142652_ac8b1@/log.gz ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1881292 Title: Linux 5.7: autopkgtest failures - lxc-test-cloneconfig && lxc-destroy Status in lxc package in Ubuntu: New Bug description: ... make[1]: Leaving directory '/tmp/autopkgtest.OzTsXV/build.myP/src' PASS: lxc-tests: lxc-test-api-reboot (75s) PASS: lxc-tests: lxc-test-apparmor (1s) PASS: lxc-tests: lxc-test-apparmor-generated (0s) PASS: lxc-tests: lxc-test-apparmor-mount (25s) PASS: lxc-tests: lxc-test-attach (0s) PASS: lxc-tests: lxc-test-autostart (38s) PASS: lxc-tests: lxc-test-basic (0s) PASS: lxc-tests: lxc-test-cgpath (0s) PASS: lxc-tests: lxc-test-checkpoint-restore (0s) FAIL: lxc-tests: lxc-test-cloneconfig (1s) --- lxc-destroy: lxctestb: tools/lxc_destroy.c: main: 242 Container is not defined Test 1 starting (/tmp/lxctest-2SbLtT/1.conf) lxc-destroy: lxctestb2: tools/lxc_destroy.c: main: 242 Container is not defined FAIL --- ... Groovy 5.7 kernel here: https://launchpad.net/~canonical-kernel- team/+archive/ubuntu/bootstrap - linux-5.7 Full log here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy-canonical-kernel-team- bootstrap/groovy/amd64/l/lxc/20200528_142652_ac8b1@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1881292/+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 1871182] Re: [RTL810xE] No ethernet connection
Here is a test kernel, could you test it and tell us if it fixes your problem? https://people.canonical.com/~ppisati/lp1871182/ linux-image-unsigned-5.4.0-25-generic_5.4.0-25.29~lp1871182_amd64.deb linux-modules-5.4.0-25-generic_5.4.0-25.29~lp1871182_amd64.deb linux-modules-extra-5.4.0-25-generic_5.4.0-25.29~lp1871182_amd64.deb -- 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/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+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 1868085] Re: Bug related to the new kernel version 5.3.0-42-generic
I confirm the ACPI problems using the sof drivers starting from 5.3.0-40, is there something i can use to debug back from sleep issue ? -- 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/1868085 Title: Bug related to the new kernel version 5.3.0-42-generic Status in alsa-driver package in Ubuntu: Incomplete Bug description: Hi all, After an update of Ubuntu kernel (version 5.3.0-42-generic) I can't have sound any more. No soundcards are detected any I have a "dummy output" in the sound pannel in settings. Furthermore I can't resume from sleep anymore. Output of ALSA Information script: !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Wed Mar 18 14:46:19 UTC 2020 !!Linux Distribution !!-- Ubuntu 18.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=bionic !!DMI Information !!--- Manufacturer: HP Product Name: HP ZBook 15u G6 Product Version: Firmware Version: R70 Ver. 01.03.04 Board Vendor: HP Board Name:8549 !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/HPIC000C:00/status 15 /sys/bus/acpi/devices/HPQ6001:00/status15 /sys/bus/acpi/devices/IFX0785:00/status15 /sys/bus/acpi/devices/INT3400:00/status15 /sys/bus/acpi/devices/INT3403:00/status15 /sys/bus/acpi/devices/INT3403:01/status15 /sys/bus/acpi/devices/INT340E:00/status15 /sys/bus/acpi/devices/INT34BB:00/status15 /sys/bus/acpi/devices/INT3F0D:00/status15 /sys/bus/acpi/devices/LNXPOWER:00/status 15 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0B00:00/status15 /sys/bus/acpi/devices/PNP0C02:00/status3 /sys/bus/acpi/devices/PNP0C02:01/status3 /sys/bus/acpi/devices/PNP0C02:05/status3 /sys/bus/acpi/devices/PNP0C09:00/status15 /sys/bus/acpi/devices/PNP0C0A:00/status31 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PRP1:00/status 11 /sys/bus/acpi/devices/SYNA3092:00/status 15 /sys/bus/acpi/devices/USBC000:00/status15 /sys/bus/acpi/devices/device:04/status 15 /sys/bus/acpi/devices/device:27/status 15 /sys/bus/acpi/devices/device:28/status 15 /sys/bus/acpi/devices/device:4c/status 15 !!Kernel Information !!-- Kernel release:5.3.0-42-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-42-generic Library version:1.1.3 Utilities version: 1.1.3 !!Loaded ALSA modules !!--- !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- --- no soundcards --- !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:9dc8] (rev 11) Subsystem: Hewlett-Packard Company Device [103c:8549] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 !!Loaded sound module options !!--- !!ALSA Device nodes !!- crw-rw 1 root audio 116, 1 Mar 18 14:45 /dev/snd/seq crw-rw 1 root audio 116, 33 Mar 18 14:44 /dev/snd/timer !!Aplay/Arecord output !! APLAY
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Ok thanks @jui.wang, it's in the pre-released updates, because i saw that -42 had been promoted upstream between yesterday and today causing several issues, i had to manually downgrade to -40. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
thanks @hui.wang, where can i find the 5.3.0-43 ? is it in the upstream repos ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Hi @hui.wang, ok thanks, is there an ETA for -43 to be released ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Hi everyone again, i am experiencing some APCI issues using 5.3.0-40 with sof drivers activated. It happens, almost randomly at this stage that the system is not waking up after a sleep, initiated by Gnome, what i see is just the fn led active on the X1-carbon-7h. It seems that disabling sof and loading the standard kernel modules (the blacklisted ones) the problem disappear. I saw that in 41 and 42 there are some ACPI-related fixes, but suddenly they broke the mic. Is this something tracked somewhere ? Is there something should i check to debug this error ? Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Please discard the last message, the webcam has just a mic, my bad :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Still having other troubles, it seems that usb audio cards don't get recognized correctly. I see this: ▶ cat /proc/asound/cards 0 [sofsklhdacard ]: sof-skl_hda_car - sof-skl_hda_card LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX 1 [C920 ]: USB-Audio - HD Pro Webcam C920 HD Pro Webcam C920 at usb-:00:14.0-2.2.1.4, high speed But cannot use it through pulseaudio/gnome. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in HWE Next: New Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@hui.wang, I confirm that now everything works as expected, thanks for your outstanding work. Just to be understand a bit more the release cycle, what is the plan to integrate all the things we did in this thread into the 18.04 standard repository ? Is already planned or for now it's better to just stick with the proposed repository ? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
I found some more interesting logs, while switching the hdmi1-3 output: Feb 26 20:35:00 spark-carbon-cto kernel: [17745.742041] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=206059 end=206060) time 138 us, min 1431, max 1439, scanline start 1428, end 1440 Feb 26 20:35:01 spark-carbon-cto slack.desktop[26636]: [02/26/20, 20:35:01:025] info: [DND] (T025L5BAC) Checking for changes in DND status for the following members: U02Q8NN0E,U025P7R5R,U03KJ3DUQ,U02Q7NP19,U03HD1F72,U025P3QLV,U03BQJS0V,U025P6YRF,UNF2WRT7H,U632EB0SF,U03BQM6CV,U288F67HS,UKFNC48SX,U3N5QH4P3,U0D78EXC4,U03V5EH0K Feb 26 20:35:01 spark-carbon-cto slack.desktop[26636]: [02/26/20, 20:35:01:026] info: [DND] (T025L5BAC) Will check for changes in DND status again in 5 minutes Feb 26 20:35:01 spark-carbon-cto CRON[2554]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Feb 26 20:35:01 spark-carbon-cto kernel: [17746.899506] wlp0s20f3: Limiting TX power to 20 (23 - 3) dBm as advertised by 90:35:6e:e2:d6:3c Feb 26 20:35:05 spark-carbon-cto kernel: [17750.175668] wlp0s20f3: Limiting TX power to 17 (23 - 6) dBm as advertised by 90:35:6e:e2:d6:3c Feb 26 20:35:15 spark-carbon-cto pulseaudio[2923]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Feb 26 20:35:15 spark-carbon-cto pulseaudio[2923]: [pulseaudio] alsa-ucm.c: Failed to enable ucm device HDMI1 Feb 26 20:35:15 spark-carbon-cto pulseaudio[2923]: [pulseaudio] source.c: Default and alternate sample rates are the same. Feb 26 20:35:15 spark-carbon-cto rtkit-daemon[1436]: Supervising 1 threads of 1 processes of 1 users. Feb 26 20:35:15 spark-carbon-cto rtkit-daemon[1436]: Successfully made thread 2562 of process 2923 (n/a) owned by '1002' RT at priority 5. Feb 26 20:35:15 spark-carbon-cto rtkit-daemon[1436]: Supervising 2 threads of 1 processes of 1 users. Feb 26 20:35:15 spark-carbon-cto pulseaudio[2923]: [pulseaudio] source.c: Default and alternate sample rates are the same. Feb 26 20:35:15 spark-carbon-cto rtkit-daemon[1436]: Supervising 2 threads of 1 processes of 1 users. Feb 26 20:35:15 spark-carbon-cto rtkit-daemon[1436]: Successfully made thread 2564 of process 2923 (n/a) owned by '1002' RT at priority 5. Feb 26 20:35:15 spark-carbon-cto rtkit-daemon[1436]: Supervising 3 threads of 1 processes of 1 users. Feb 26 20:35:15 spark-carbon-cto gsd-media-keys[3115]: Unable to get default source Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] alsa-ucm.c: Failed to enable ucm device HDMI2 Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] source.c: Default and alternate sample rates are the same. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 1 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Successfully made thread 2565 of process 2923 (n/a) owned by '1002' RT at priority 5. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 2 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] source.c: Default and alternate sample rates are the same. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 2 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Successfully made thread 2566 of process 2923 (n/a) owned by '1002' RT at priority 5. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 3 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto gsd-media-keys[3115]: Unable to get default source Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] sink.c: Default and alternate sample rates are the same. Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] alsa-ucm.c: Failed to enable ucm device HDMI1 Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] source.c: Default and alternate sample rates are the same. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 1 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Successfully made thread 2567 of process 2923 (n/a) owned by '1002' RT at priority 5. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 2 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto pulseaudio[2923]: [pulseaudio] source.c: Default and alternate sample rates are the same. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 2 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Successfully made thread 2568 of process 2923 (n/a) owned by '1002' RT at priority 5. Feb 26 20:35:17 spark-carbon-cto rtkit-daemon[1436]: Supervising 3 threads of 1 processes of 1 users. Feb 26 20:35:17 spark-carbon-cto gsd-media-keys[3115]: Unable to get default source Feb 26 20:35:18 spark-carbon-cto
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
The previous comment missed the attachment. ** Attachment added: "pactl-list" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5331364/+files/pactl-list -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
** Attachment added: "alsa-info after attaching an hdmi tv" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5331363/+files/alsa-info.txt.VGDIH3ZkNA -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
pactl list after attaching an hdmi tv -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
And this one is the only hdmi-related thing i can found on dmesg: "[17231.810042] HDMI HDA Codec ehdaudio0D2: hdac_hdmi_present_sense: disconnect for pin:port 5:0" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Just for the sake of clarity, this is what i see from gnome audio settings. ** Attachment added: "Screenshot from 2020-02-26 20-31-47.png" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5331365/+files/Screenshot%20from%202020-02-26%2020-31-47.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Hello @hui.wang, it seems that HDMI audio output is not working as expected, i can see the HDMI[1-3] devices (why 3 ?) but trying to using, when attached to a TV for example, what i get is just a new "dummy output" device. How should i debug this ? Thanks a lot! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@hui.wang thanks, it's finally works, i've got both speakers and mic recognized as specified in the UCM files. There is just another major drawback that affect thinkpad x1 carbon 7th which has 5 speakers 4+1, but only 2 of them gets recognized, as shown in the attachment. Should the UCM file be in charge of this ? ** Attachment added: "Screenshot from 2020-02-14 21-02-43.png" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5328236/+files/Screenshot%20from%202020-02-14%2021-02-43.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
@hui.wang thans for your reply. tree -L 1 . . ├── apq8064-tabla-snd-card ├── broadwell-rt286 ├── chtrt5645 ├── DAISY-I2S ├── DB410c ├── Dell-WD15-Dock ├── GoogleNyan ├── HDAudio-Lenovo-DualCodecs ├── LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX ├── LENOVO-20QE000VMC-ThinkPadX1Carbon7th-20QE000VMC ├── LENOVO-20QESITR05-ThinkPadX1Carbon7th-20QESITR05 ├── LENOVO-20UB0SIT17-ThinkPadX1YogaGen5-20UB0SIT17 ├── LENOVO-MFG_IN_GO-ThinkPad-MFG_IN_GO ├── Manta-I2S ├── Manta-SPDIF ├── msm8974-taiko-mtp-snd-card ├── PandaBoard ├── PandaBoardES ├── PAZ00 ├── SDP4430 ├── skylake-rt286 ├── sof-skl_hda_card ├── tegraalc5632 ├── tegra-rt5640 ├── Tuna └── VEYRON-I2S > grep -r "Headset Mic Boost Volume" LENOVO-* LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX/LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX.conf: cset "name='Headset Mic Boost Volume' 2" LENOVO-20QE000VMC-ThinkPadX1Carbon7th-20QE000VMC/LENOVO-20QE000VMC-ThinkPadX1Carbon7th-20QE000VMC.conf: cset "name='Headset Mic Boost Volume' 2" LENOVO-20QESITR05-ThinkPadX1Carbon7th-20QESITR05/LENOVO-20QESITR05-ThinkPadX1Carbon7th-20QESITR05.conf: cset "name='Headset Mic Boost Volume' 2" LENOVO-20UB0SIT17-ThinkPadX1YogaGen5-20UB0SIT17/LENOVO-20UB0SIT17-ThinkPadX1YogaGen5-20UB0SIT17.conf: cset "name='Headset Mic Boost Volume' 1" LENOVO-MFG_IN_GO-ThinkPad-MFG_IN_GO/LENOVO-MFG_IN_GO-ThinkPad-MFG_IN_GO.conf: cset "name='Headset Mic Boost Volume' 2" But nothing changed, i still need "load-module module-alsa-source device=hw:0,7" under "/etc/pulse/default.pa" to see a working mic. How can i see which ucm files getting loaded by Alsa ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Thanks for your reply @hui.wang So, i've tried to change "name='Mic Boost Volume' 2"" all the LENOVO files but nothing changed. Your assumption about the cardlongname was right, because it seems that is different from the versioned ones, mine is "LENOVO-20QD00LKIX- ThinkPadX1Carbon7th-20QD00LKIX". pactl list cards Card #0 Name: alsa_card.pci-_00_1f.3-platform-skl_hda_dsp_generic Driver: module-alsa-card.c Owner Module: 7 Properties: alsa.card = "0" alsa.card_name = "sof-skl_hda_card" alsa.long_card_name = "LENOVO-20QD00LKIX-ThinkPadX1Carbon7th-20QD00LKIX" alsa.driver_name = "snd_soc_skl_hda_dsp" device.bus_path = "pci-:00:1f.3-platform-skl_hda_dsp_generic" sysfs.path = "/devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0" device.bus = "pci" device.vendor.id = "8086" device.vendor.name = "Intel Corporation" device.product.id = "9dc8" device.string = "0" device.description = "sof-skl_hda_card" module-udev-detect.discovered = "1" device.icon_name = "audio-card-pci" Profiles: input:stereo-fallback: Stereo Input (sinks: 0, sources: 1, priority: 51, available: no) input:multichannel-input: Multichannel Input (sinks: 0, sources: 1, priority: 1, available: yes) output:stereo-fallback: Stereo Output (sinks: 1, sources: 0, priority: 5100, available: yes) output:stereo-fallback+input:stereo-fallback: Stereo Output + Stereo Input (sinks: 1, sources: 1, priority: 5151, available: yes) output:stereo-fallback+input:multichannel-input: Stereo Output + Multichannel Input (sinks: 1, sources: 1, priority: 5101, available: yes) output:multichannel-output: Multichannel Output (sinks: 1, sources: 0, priority: 100, available: yes) output:multichannel-output+input:stereo-fallback: Multichannel Output + Stereo Input (sinks: 1, sources: 1, priority: 151, available: yes) output:multichannel-output+input:multichannel-input: Multichannel Duplex (sinks: 1, sources: 1, priority: 101, available: yes) off: Off (sinks: 0, sources: 0, priority: 0, available: yes) Active Profile: output:stereo-fallback+input:multichannel-input Ports: analog-input-mic: Microphone (priority: 8700, latency offset: 0 usec, not available) Properties: device.icon_name = "audio-input-microphone" Part of profile(s): input:stereo-fallback, output:stereo-fallback+input:stereo-fallback, output:multichannel-output+input:stereo-fallback multichannel-input: Multichannel Input (priority: 0, latency offset: 0 usec) Part of profile(s): input:multichannel-input, output:stereo-fallback+input:multichannel-input, output:multichannel-output+input:multichannel-input analog-output-speaker: Speakers (priority: 1, latency offset: 0 usec) Properties: device.icon_name = "audio-speakers" Part of profile(s): output:stereo-fallback, output:stereo-fallback+input:stereo-fallback, output:stereo-fallback+input:multichannel-input analog-output-headphones: Headphones (priority: 9000, latency offset: 0 usec, not available) Properties: device.icon_name = "audio-headphones" Part of profile(s): output:stereo-fallback, output:stereo-fallback+input:stereo-fallback, output:stereo-fallback+input:multichannel-input multichannel-output: Multichannel Output (priority: 0, latency offset: 0 usec) Part of profile(s): output:multichannel-output, output:multichannel-output+input:stereo-fallback, output:multichannel-output+input:multichannel-input -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
** Attachment added: "Screenshot from 2020-02-13 00-50-52.png" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5327774/+files/Screenshot%20from%202020-02-13%2000-50-52.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
It seems that adding "load-module module-alsa-source device=hw:0,7" to "/etc/pulse/default.pa" i have the mic recognized and working, see the attachment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
On a machine Lenovo Thinkpad X1 Carbon 7th, running Bionic, verification failed. What i did: 1) Enabled Proposed repository 2) Installed libasound2: ``` > dpkg -l | grep libasound2 ii libasound2:amd64 1.1.3-5ubuntu0.3 amd64shared library for ALSA applications ii libasound2-data1.1.3-5ubuntu0.3 all Configuration files and profiles for ALSA drivers ii libasound2-plugins:amd64 1.1.1-1ubuntu1 amd64ALSA library additional plugins ``` 3) Upgraded linux-firmware to "1.173.15" 4) Installed "linux-oem-osp1" - "5.0.0-1038-oem-osp1" 5) Verified that all the UCM files are there: ``` ucm ├── apq8064-tabla-snd-card ├── broadwell-rt286 ├── chtrt5645 ├── DAISY-I2S ├── DB410c ├── Dell-WD15-Dock ├── GoogleNyan ├── HDAudio-Lenovo-DualCodecs ├── LENOVO-20QE000VMC-ThinkPadX1Carbon7th-20QE000VMC ├── LENOVO-20QESITR05-ThinkPadX1Carbon7th-20QESITR05 ├── LENOVO-20UB0SIT17-ThinkPadX1YogaGen5-20UB0SIT17 ├── LENOVO-MFG_IN_GO-ThinkPad-MFG_IN_GO ├── Manta-I2S ├── Manta-SPDIF ├── msm8974-taiko-mtp-snd-card ├── PandaBoard ├── PandaBoardES ├── PAZ00 ├── SDP4430 ├── skylake-rt286 ├── sof-skl_hda_card ├── tegraalc5632 ├── tegra-rt5640 ├── Tuna └── VEYRON-I2S ``` 6) Blacklisted "snd_soc_skl" and "snd_hda_intel" on "/etc/modprobe.d/blacklist.conf" 7) Verified that SOF firmware has been loaded correctly: ``` dmesg | grep sof | grep -iv microsoft [3.558639] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.558647] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.558800] sof-audio-pci :00:1f.3: use msi interrupt mode [3.567161] sof-audio-pci :00:1f.3: Linked as a consumer to :00:02.0 [3.567247] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.607451] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.607454] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.641575] sof-audio-pci :00:1f.3: unexpected ipc interrupt raised! [3.641577] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [3.723585] sof-audio-pci :00:1f.3: Firmware info: version 1:1:0-0f736 [3.723587] sof-audio-pci :00:1f.3: Firmware: ABI 3:7:0 Kernel ABI 3:6:0 [3.723588] sof-audio-pci :00:1f.3: warn: FW ABI is more recent than kernel [3.723793] sof-audio-pci :00:1f.3: firmware boot complete [3.969365] sof-audio-pci :00:1f.3: Topology: ABI 3:7:0 Kernel ABI 3:6:0 [3.969366] sof-audio-pci :00:1f.3: warn: topology ABI is more recent than kernel [3.969369] sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp3 Tx not handled [3.970268] sof-audio-pci :00:1f.3: warning: widget type 0 name codec0_in not handled [3.970269] sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp2 Tx not handled [3.970986] sof-audio-pci :00:1f.3: warning: widget type 0 name codec1_in not handled [3.970989] sof-audio-pci :00:1f.3: warning: widget type 7 name iDisp1 Tx not handled [3.971741] sof-audio-pci :00:1f.3: warning: widget type 1 name codec0_out not handled [3.971743] sof-audio-pci :00:1f.3: warning: widget type 7 name Analog CPU Playback not handled [3.972525] sof-audio-pci :00:1f.3: warning: widget type 1 name codec1_out not handled [3.972527] sof-audio-pci :00:1f.3: warning: widget type 7 name Digital CPU Playback not handled [3.972529] sof-audio-pci :00:1f.3: warning: widget type 0 name codec2_in not handled [3.972531] sof-audio-pci :00:1f.3: warning: widget type 7 name Alt Analog CPU Playback not handled [3.972532] sof-audio-pci :00:1f.3: warning: widget type 1 name codec2_out not handled [3.972534] sof-audio-pci :00:1f.3: warning: widget type 0 name Analog CPU Capture not handled [3.973342] sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp1_out not handled [3.973343] sof-audio-pci :00:1f.3: warning: widget type 0 name Digital CPU Capture not handled [3.974153] sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp2_out not handled [3.974155] sof-audio-pci :00:1f.3: warning: widget type 0 name Alt Analog CPU Capture not handled [3.974930] sof-audio-pci :00:1f.3: warning: widget type 1 name iDisp3_out not handled [3.981916] sof-audio-pci :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [4.058562] input: sof-skl_hda_card Mic as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input16 [4.058597] input: sof-skl_hda_card Headphone as /devices/pci:00/:00:1f.3/skl_hda_dsp_generic/sound/card0/input17 [4.058638] input: sof-skl_hda_card HDMI/DP,pcm=3 as
[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Following my last comment, this is what i see from gnome audio settings. ** Attachment added: "Screenshot from 2020-02-12 23-28-30.png" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5327771/+files/Screenshot%20from%202020-02-12%2023-28-30.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
Any changes to have this backported to 18.04 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+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 1583801] Re: [XPS 15 9550] [ALC3266] No sound via headphones (headset) when Ubuntu boots with them plugged in
Don't know if it's related, but sometimes I don't get headphones audio when my XPS boots. Disabling "Auto-Mute Mode" from alsamixer seems to fix the problem. -- 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/1583801 Title: [XPS 15 9550] [ALC3266] No sound via headphones (headset) when Ubuntu boots with them plugged in Status in PulseAudio: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1583801/+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 1800309] [NEW] not installed during update to ubuntu 18
Public bug reported: some errors on installing video xorg intel, some corrupted files/dependencies ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 27 22:14:06 2018 DistUpgraded: 2018-10-27 15:51:41,727 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio "./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon HD 7470M [1043:2002] InstallationDate: Installed on 2018-03-29 (212 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK Computer Inc. K54HR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=d5e3b7bd-e24f-42fc-9840-8e671d6e8c81 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-27 (0 days ago) dmi.bios.date: 06/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K54HR.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K54HR dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK54HR.205:bd06/20/2012:svnASUSTeKComputerInc.:pnK54HR:pvr1.0:rvnASUSTeKComputerInc.:rnK54HR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K54HR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Oct 27 12:38:54 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output HDMI-0LVDS VGA-0 xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- 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/1800309 Title: not installed during update to ubuntu 18 Status in xorg package in Ubuntu: New Bug description: some errors on installing video xorg intel, some corrupted files/dependencies ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 27 22:14:06 2018 DistUpgraded: 2018-10-27 15:51:41,727 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Esecuzione del processo figlio "./xorg_fix_proprietary.py" non riuscita (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] [1002:6760] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon HD 7470M [1043:2002] InstallationDate: Installed on 2018-03-29 (212 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: ASUSTeK Computer Inc. K54HR ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=d5e3b7bd-e24f-42fc-9840-8e671d6e8c81 ro quiet splash
[Touch-packages] [Bug 1452115] Re: Python interpreter binary is not compiled as PIE
** Also affects: python3.6 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1452115 Title: Python interpreter binary is not compiled as PIE Status in python2.7 package in Ubuntu: Fix Released Status in python3.4 package in Ubuntu: Fix Released Status in python3.6 package in Ubuntu: New Bug description: The python2.7 binary (installed at /usr/bin/python2.7; package version 2.7.6-8) is not compiled as a position independent executable (PIE). It appears that the python compilation process is somewhat arcane and the hardening wrapper probably doesn't do the trick for it. This is incredibly dangerous as it means that any vulnerability within a native module (e.g. ctypes-based), or within python itself will expose an incredibly large amount of known memory contents at known addresses (including a large number of dangerous instruction groupings). This enables ROP-based (https://en.wikipedia.org/wiki /Return-oriented_programming) to abuse the interpreter itself to bypass non-executable page protections. I have put together an example vulnerable C shared object (with a buffer overflow) accessed via python through the ctypes interface as an example. This uses a single ROP "gadget" on top of using the known PLT location for system(3) (https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example code is accessible at: - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367 I'm not exactly familiar enough with the python build process to say where exactly an -fPIE needs to be injected into a script/makefile, but I feel that given the perceived general preference for ctypes- based modules over python written ones, as the native code implementations tend to be more performant, this feels like a large security hole within the system. Given the nature of this "issue," I'm not 100% sure of where it is best reported, but from what I can tell, this conflicts with the Ubuntu hardening features and is definitely exploitable should a native module contain a sufficiently exploitable vulnerability that allows for control of the instruction register. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1452115/+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 1452115] Re: Python interpreter binary is not compiled as PIE
I do believe pie is explicitly disabled when building Python 3.6. Using hardening-check on Ubuntu Bionic (from the devscripts package): $ hardening-check /usr/bin/python3 /usr/bin/python3: Position Independent Executable: no, normal executable! Stack protected: yes Fortify Source functions: yes (some protected functions found) Read-only relocations: yes Immediate binding: no, not found! Also from debian/rules in http://archive.ubuntu.com/ubuntu/pool/main/p/python3.6/python3.6_3.6.5-3.debian.tar.xz: export DEB_BUILD_MAINT_OPTIONS=hardening=-pie According to http://manpages.ubuntu.com/manpages/bionic/man1/dpkg- buildflags.1.html this syntax disables pie - it should be "+pie", and is enabled by default on Bionic: $ dpkg-buildflags --status dpkg-buildflags: status: vendor is Ubuntu dpkg-buildflags: status: future features: lfs=no dpkg-buildflags: status: hardening features: bindnow=no format=yes fortify=yes pie=yes relro=yes stackprotector=yes stackprotectorstrong=yes dpkg-buildflags: status: qa features: bug=no canary=no dpkg-buildflags: status: reproducible features: fixdebugpath=yes timeless=yes dpkg-buildflags: status: sanitize features: address=no leak=no thread=no undefined=no ... with the environment variable set: $ DEB_BUILD_MAINT_OPTIONS=hardening=-pie dpkg-buildflags --status dpkg-buildflags: status: environment variable DEB_BUILD_MAINT_OPTIONS=hardening=-pie dpkg-buildflags: status: vendor is Ubuntu dpkg-buildflags: status: future features: lfs=no dpkg-buildflags: status: hardening features: bindnow=no format=yes fortify=yes pie=no relro=yes stackprotector=yes stackprotectorstrong=yes dpkg-buildflags: status: qa features: bug=no canary=no dpkg-buildflags: status: reproducible features: fixdebugpath=yes timeless=yes dpkg-buildflags: status: sanitize features: address=no leak=no thread=no undefined=no ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1452115 Title: Python interpreter binary is not compiled as PIE Status in python2.7 package in Ubuntu: Fix Released Status in python3.4 package in Ubuntu: Fix Released Bug description: The python2.7 binary (installed at /usr/bin/python2.7; package version 2.7.6-8) is not compiled as a position independent executable (PIE). It appears that the python compilation process is somewhat arcane and the hardening wrapper probably doesn't do the trick for it. This is incredibly dangerous as it means that any vulnerability within a native module (e.g. ctypes-based), or within python itself will expose an incredibly large amount of known memory contents at known addresses (including a large number of dangerous instruction groupings). This enables ROP-based (https://en.wikipedia.org/wiki /Return-oriented_programming) to abuse the interpreter itself to bypass non-executable page protections. I have put together an example vulnerable C shared object (with a buffer overflow) accessed via python through the ctypes interface as an example. This uses a single ROP "gadget" on top of using the known PLT location for system(3) (https://en.wikipedia.org/wiki/Return-to-libc_attack) to call "id". The example code is accessible at: - https://gist.github.com/ChaosData/ae6076cb1c3cc7b0a367 I'm not exactly familiar enough with the python build process to say where exactly an -fPIE needs to be injected into a script/makefile, but I feel that given the perceived general preference for ctypes- based modules over python written ones, as the native code implementations tend to be more performant, this feels like a large security hole within the system. Given the nature of this "issue," I'm not 100% sure of where it is best reported, but from what I can tell, this conflicts with the Ubuntu hardening features and is definitely exploitable should a native module contain a sufficiently exploitable vulnerability that allows for control of the instruction register. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1452115/+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 1701850] Re: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
I wait the answer because i need also Wine don't manage the accent caracters solved with the updates? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701850 Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: unable to install some product after ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-24.28-lowlatency 4.10.15 Uname: Linux 4.10.0-24-lowlatency x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: bsdutils:amd64: Configure python-xmltodict:amd64: Install python-pyquery:amd64: Install wxbanker:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Jun 30 22:47:13 2017 DpkgTerminalLog: dpkg: error processing package bsdutils (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-06-11 (20 days ago) InstallationMedia: Ubuntu-Studio 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1701850/+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 1689825] Re: gnome-keyring not unlocked on boot
An easy workaround, while waiting a fix, is to add a startup application with this command /usr/bin/gnome-keyring-daemon * You will be required to re-enter the password once logged, but it should work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in D-Bus: New Status in chromium-browser package in Ubuntu: Invalid Status in flatpak package in Ubuntu: Confirmed Status in gdm package in Ubuntu: Confirmed Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+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 1701834] [NEW] package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente pr
Public bug reported: I was reading my mail with thunderbird ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sat Jul 1 19:11:37 2017 DpkgTerminalLog: dpkg: errore nell'elaborare il pacchetto bsdutils (--configure): il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. InstallationDate: Installed on 2017-04-25 (67 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701834 Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. Status in util-linux package in Ubuntu: New Bug description: I was reading my mail with thunderbird ProblemType: Package DistroRelease: Ubuntu 17.04 Package: bsdutils 1:2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Sat Jul 1 19:11:37 2017 DpkgTerminalLog: dpkg: errore nell'elaborare il pacchetto bsdutils (--configure): il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. InstallationDate: Installed on 2017-04-25 (67 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package bsdutils 1:2.29-1ubuntu2.1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima di tentare la configurazione. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1701834/+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 1261191] Re: indicator-datetime list evolution calendar all day event a day before actual date of event
I have similar behaviour on ubuntu touch since OTA-13 (vivid), but i don't know if this bug involves also phones or it's another story. However in my tests (with google calendar) i found this: a) if i set an event with defined time (eg. from 09:00 am to 10:00 am) indicator works always as expected; b) if i add an event for the whole day (one shot) indicator reports correct date and time 00:00; c) if i add an event for the whole day yearly repeated (eg. birthday), indicator reports wrong values, always a day ahead, with this particularity: - If notification is turned off the time is 00:00; - If notification is set (any value), the time is always 02:00 am If i tap on the wrong date, calendar opens on (indeed) the wrong date, which doesn't have events registered, but in calendar and in agenda events are correctly registered. Analyzing the ical file for both b) and c) cases, i can see that the only difference between the two files is the RRULE:FREQ=YEARLY statement. ical snippet for case b) is: DTSTART;VALUE=DATE:20170413 DTEND;VALUE=DATE:20170414 ical snippet for case c) is: DTSTART;VALUE=DATE:20170413 RRULE:FREQ=YEARLY DTEND;VALUE=DATE:20170414 Maybe it's a different case, but i have both DTSTART and DTEND correctly(?) set. It seems that there is something wrong in parsing the RRULE statement. I tried also to play with google parameters, but the only that highlights the problem is the repetition of an event. Doesn't indicator expects the DTEND closely after DTSTART in the ical file? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1261191 Title: indicator-datetime list evolution calendar all day event a day before actual date of event Status in indicator-datetime package in Ubuntu: Confirmed Bug description: 1. What is expected I add new all day events to evolution calendar (caldav sync with owncloud and also local calendar). Evolution shows events just OK and indicator-datetime calendar shows correct day as bold as well and should also list events below as defined. 2. What actually happens Indicator-datetime lists events to take place one day ahead e.g. all day event on Monday is listed to be happen on Sunday. --- ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MarkForUpload: True NonfreeKernelModules: wl Package: indicator-datetime 0.3.94-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-15.23~precise1-generic 3.11.10 Tags: precise running-unity third-party-packages Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin debian-tor dialout dip libvirtd lpadmin plugdev sudo syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1261191/+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 1645021] Re: indicator-datetime shows all-day events from google calendar a day before the actual date of the event
The same for krillin (BQ Aquaris E4.5) for timezone UTC+2. At least for me, it happened after OTA-12 update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1645021 Title: indicator-datetime shows all-day events from google calendar a day before the actual date of the event Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: bq M10 rc-proposed/r240 The date-time indicator shows all-day events from google calendar one day before the actual date of the event. For example, the event happening on Monday is shown on Sunday. It applies for both the calendar and the list of events in the indicator. At the same time, the Calendar App shows the all-day events correctly. This behavior is related to the time zone. My time zone is UTC+3. When I set the zone to UTC+0, the indicator shows the all-day events correctly. This bug looks just like Bug #1261191, but for Unity 8. It also seems to be somehow related to Bug #1641720 and Bug #1641726. But after marking them as fixed, this one is still present. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1645021/+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 1635906] Re: Low graphics mode in multi monitor setup after upgrade to 16.10
Hi! At last I... SOLVED!!! Before I saw: http://askubuntu.com/questions/436374/how-to-get-rid-of-the-gallium-0-4 -on-llvmpipe-llvm-0x300-driver-intel-needed ...then I saw: https://wiki.ubuntu.com/Kernel/LTSEnablementStack ...later, on a terminal, I've run: sudo apt-get install --install-recommends linux-generic-lts-xenial xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial xserver-xorg-video- all-lts-xenial xserver-xorg-input-all-lts-xenial libwayland-egl1-mesa- lts-xenial ...and, after a restart, my PC returned to work with the correct "Intel® Sandybridge Desktop" instead of "Gallium 0.4 on llvmpipe..."! I hope that it can help you. BR Paolo -- 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/1635906 Title: Low graphics mode in multi monitor setup after upgrade to 16.10 Status in xorg package in Ubuntu: Confirmed Bug description: Hi, After upgrading from 16.04 to 16.10 my multi monitor setup is unable to reach login screen. Computer is Panasonic CF-52 on dock station with two external monitors. The error says low graphics mode enabled.Used to work just fine in previous distributions. the last error in the log file says: ScreenInit failed for driver 0. I have Intel graphics. Workaround found so far: boot laptop out of dock station, then dock it and monitors are recognized no problem. Troubleshooting done: Reintsall Ubuntu from thumb drive - reinstall option: same results Reinstall Ubuntu from thumb drive - clean install except for /home drive kept: same results Run X -configure: same results Regards, isotope ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 22 18:47:00 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series Chipset Integrated Graphics Controller [10f7:8338] Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series Chipset Integrated Graphics Controller [10f7:8338] InstallationDate: Installed on 2016-10-22 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Matsushita Electric Industrial Co.,Ltd. CF-52GCMBSAE PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=54989005-afb3-4eb2-9813-17ee5bf134c2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.50L20 dmi.board.name: CF52-2L dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.50L20:bd03/27/2009:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-52GCMBSAE:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF52-2L:rvr1:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001: dmi.product.name: CF-52GCMBSAE dmi.product.version: 002 dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Oct 22 17:49:03 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-1DP-2 DP-3
[Touch-packages] [Bug 1634152] Re: Driver video doesn't work properly after Upgrade (16.04 LTS)
** Attachment added: "enable_intel__video_drivers" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634152/+attachment/4771203/+files/enable_intel__video_drivers -- 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/1634152 Title: Driver video doesn't work properly after Upgrade (16.04 LTS) Status in xorg package in Ubuntu: New Bug description: After the last automatic upgrade (kernel?), the system suggested a restart to finalize the installation. Immediately after the reboot, the graph login page worked at 640x480. Using "xdiagnose", checking (disabling) all, I was able to set the resolution 1280x1024, but no more capable to manage the dual-screen as before: in the "Monitor" configuration page, I see only one "Built-in Display" instead the two Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been changed. My PC is an Acer Veriton X4610G CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4 RAM: 4GiB (128MiB VGA shared) I use an UBUNTU 16.04 LTS 64-bit Thanks for any feedback! Paolo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 17 15:39:54 2016 DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0492] InstallationDate: Installed on 2015-05-15 (521 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Veriton X4610G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago) dmi.bios.date: 05/30/2011 dmi.bios.vendor: Acer dmi.bios.version: P01-B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Veriton X4610G dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr: dmi.product.name: Veriton X4610G dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 17 15:32:10 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634152/+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 1634152] Re: Driver video doesn't work properly after Upgrade (16.04 LTS)
** Attachment added: "Intel_video_drivers.png" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634152/+attachment/4771201/+files/Intel_video_drivers.png -- 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/1634152 Title: Driver video doesn't work properly after Upgrade (16.04 LTS) Status in xorg package in Ubuntu: New Bug description: After the last automatic upgrade (kernel?), the system suggested a restart to finalize the installation. Immediately after the reboot, the graph login page worked at 640x480. Using "xdiagnose", checking (disabling) all, I was able to set the resolution 1280x1024, but no more capable to manage the dual-screen as before: in the "Monitor" configuration page, I see only one "Built-in Display" instead the two Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been changed. My PC is an Acer Veriton X4610G CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4 RAM: 4GiB (128MiB VGA shared) I use an UBUNTU 16.04 LTS 64-bit Thanks for any feedback! Paolo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 17 15:39:54 2016 DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0492] InstallationDate: Installed on 2015-05-15 (521 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Veriton X4610G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago) dmi.bios.date: 05/30/2011 dmi.bios.vendor: Acer dmi.bios.version: P01-B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Veriton X4610G dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr: dmi.product.name: Veriton X4610G dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 17 15:32:10 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634152/+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 1634152] Re: Driver video doesn't work properly after Upgrade (16.04 LTS)
SOLVED!!! http://askubuntu.com/questions/436374/how-to-get-rid-of-the-gallium-0-4 -on-llvmpipe-llvm-0x300-driver-intel-needed -- 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/1634152 Title: Driver video doesn't work properly after Upgrade (16.04 LTS) Status in xorg package in Ubuntu: New Bug description: After the last automatic upgrade (kernel?), the system suggested a restart to finalize the installation. Immediately after the reboot, the graph login page worked at 640x480. Using "xdiagnose", checking (disabling) all, I was able to set the resolution 1280x1024, but no more capable to manage the dual-screen as before: in the "Monitor" configuration page, I see only one "Built-in Display" instead the two Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been changed. My PC is an Acer Veriton X4610G CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4 RAM: 4GiB (128MiB VGA shared) I use an UBUNTU 16.04 LTS 64-bit Thanks for any feedback! Paolo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 17 15:39:54 2016 DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0492] InstallationDate: Installed on 2015-05-15 (521 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Veriton X4610G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago) dmi.bios.date: 05/30/2011 dmi.bios.vendor: Acer dmi.bios.version: P01-B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Veriton X4610G dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr: dmi.product.name: Veriton X4610G dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 17 15:32:10 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634152/+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 1631660] Re: Arrow keys not working in sqlite3 prompt
Confirmed and very annoying. It feels like working in the 80s (I remember). There is workaround until they fix this bug: sudo apt install rlwrap rlwrap sqlite3 db-file but I'm afraid that very few people know about rlwrap. I do only because I googled this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1631660 Title: Arrow keys not working in sqlite3 prompt Status in sqlite3 package in Ubuntu: Confirmed Bug description: sqlite3 uses history via the readline library. It used to work just fine on 14.04. After I upgraded to 16.04, the arrow keys stopped working. The sqlite3 executable is NOT linked against the readline library, and from googling on the internet that seems to be the reason why the keys are not working. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: sqlite3 3.11.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 8 14:15:09 2016 InstallationDate: Installed on 2016-02-22 (229 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: sqlite3 UpgradeStatus: Upgraded to xenial on 2016-09-22 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1631660/+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 1633479] Re: dhclient does not wait for ipv6 dad (duplicate address detection)
** Tags added: 4010 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1633479 Title: dhclient does not wait for ipv6 dad (duplicate address detection) Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Precise: New Status in isc-dhcp source package in Trusty: New Status in isc-dhcp source package in Xenial: New Status in isc-dhcp source package in Yakkety: New Bug description: dhclient -6 does not wait for an interface go through duplicate address detection. As a result the following will almost always fail: $ dev=eth0 $ ip link set down dev $dev $ dhclient -6 -1 -v eth0 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Can't bind to dhcp address: Cannot assign requested address Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. $ echo $? 1 Related bugs: * bug 1447715: dhclient -6: Can't bind to dhcp address: Cannot assign requested address * bug 1633562: 'dhclient -6 -S' does not bring interface up ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: isc-dhcp-client 4.3.3-5ubuntu15 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 14 09:18:52 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (449 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1633479/+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 1635906] Re: Low graphics mode in multi monitor setup after upgrade to 16.10
Maybe as my reported bug? (Bug #1634152) Can you confirm my bug if it's a similar problem, pls? Thanks! BR Paolo -- 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/1635906 Title: Low graphics mode in multi monitor setup after upgrade to 16.10 Status in xorg package in Ubuntu: Confirmed Bug description: Hi, After upgrading from 16.04 to 16.10 my multi monitor setup is unable to reach login screen. Computer is Panasonic CF-52 on dock station with two external monitors. The error says low graphics mode enabled.Used to work just fine in previous distributions. the last error in the log file says: ScreenInit failed for driver 0. I have Intel graphics. Workaround found so far: boot laptop out of dock station, then dock it and monitors are recognized no problem. Troubleshooting done: Reintsall Ubuntu from thumb drive - reinstall option: same results Reinstall Ubuntu from thumb drive - clean install except for /home drive kept: same results Run X -configure: same results Regards, isotope ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 22 18:47:00 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series Chipset Integrated Graphics Controller [10f7:8338] Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series Chipset Integrated Graphics Controller [10f7:8338] InstallationDate: Installed on 2016-10-22 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Matsushita Electric Industrial Co.,Ltd. CF-52GCMBSAE PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic root=UUID=54989005-afb3-4eb2-9813-17ee5bf134c2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.50L20 dmi.board.name: CF52-2L dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.board.version: 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd. dmi.chassis.version: 001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.50L20:bd03/27/2009:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-52GCMBSAE:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF52-2L:rvr1:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001: dmi.product.name: CF-52GCMBSAE dmi.product.version: 002 dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Oct 22 17:49:03 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: OutputDP-1DP-2 DP-3 HDMI-1 HDMI-2 LVDS-1 VGA-1 product id 17709 vendor VSC xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1635906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touc
[Touch-packages] [Bug 1634152] Re: Driver video doesn't work properly after Upgrade (16.04 LTS)
** Summary changed: - Driver video doesn't work properly after Upgrade + Driver video doesn't work properly after Upgrade (16.04 LTS) -- 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/1634152 Title: Driver video doesn't work properly after Upgrade (16.04 LTS) Status in xorg package in Ubuntu: New Bug description: After the last automatic upgrade (kernel?), the system suggested a restart to finalize the installation. Immediately after the reboot, the graph login page worked at 640x480. Using "xdiagnose", checking (disabling) all, I was able to set the resolution 1280x1024, but no more capable to manage the dual-screen as before: in the "Monitor" configuration page, I see only one "Built-in Display" instead the two Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been changed. My PC is an Acer Veriton X4610G CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4 RAM: 4GiB (128MiB VGA shared) I use an UBUNTU 16.04 LTS 64-bit Thanks for any feedback! Paolo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 17 15:39:54 2016 DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0492] InstallationDate: Installed on 2015-05-15 (521 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Veriton X4610G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago) dmi.bios.date: 05/30/2011 dmi.bios.vendor: Acer dmi.bios.version: P01-B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Veriton X4610G dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr: dmi.product.name: Veriton X4610G dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 17 15:32:10 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634152/+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 1634152] Re: Driver video doesn't work properly after Upgrade
** Description changed: - After the last automatic upgrade, the system suggested a restart to finalize the installation. + After the last automatic upgrade (kernel?), the system suggested a restart to finalize the installation. Immediately after the reboot, the graph login page worked at 640x480. Using "xdiagnose", checking (disabling) all, I was able to set a resolution 1280x1024, but no more capable to manage the dual-screen as before: in the "Monitor" configuration page, I see only one "Built-in Display" instead the two Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been changed. My PC is an Acer Veriton X4610G CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4 RAM: 4GiB (128MiB VGA shared) I use an UBUNTU 16.04 LTS 64-bit - Thanks for any feedback! Paolo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 .tmp.unity_support_test.1: - + ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 17 15:39:54 2016 DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0492] + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0492] InstallationDate: Installed on 2015-05-15 (521 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: - Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub - Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp. - Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp. + Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Veriton X4610G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago) dmi.bios.date: 05/30/2011 dmi.bios.vendor: Acer dmi.bios.version: P01-B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Veriton X4610G dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr: dmi.product.name: Veriton X4610G dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 17 15:32:10 2016 xserver.configfile: default xserver.devices: - inputPower Button KEYBOARD, id 6 - inputPower Button KEYBOARD, id 7 - inputAT Translated Set 2 keyboard KEYBOARD, id 8 - inputImPS/2 Generic Wheel Mouse MOUSE, id 9 + inputPower Button KEYBOARD, id 6 + inputPower Button KEYBOARD, id 7 + inputAT Translated Set 2 keyboard KEYBOARD, id 8 + inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 ** Desc
[Touch-packages] [Bug 1634152] Re: Driver video doesn't work properly after Upgrade
** Summary changed: - Driver video doesn't work properly + Driver video doesn't work properly after Upgrade -- 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/1634152 Title: Driver video doesn't work properly after Upgrade Status in xorg package in Ubuntu: New Bug description: After the last automatic upgrade, the system suggested a restart to finalize the installation. Immediately after the reboot, the graph login page worked at 640x480. Using "xdiagnose", checking (disabling) all, I was able to set a resolution 1280x1024, but no more capable to manage the dual-screen as before: in the "Monitor" configuration page, I see only one "Built-in Display" instead the two Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been changed. My PC is an Acer Veriton X4610G CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4 RAM: 4GiB (128MiB VGA shared) I use an UBUNTU 16.04 LTS 64-bit Thanks for any feedback! Paolo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 17 15:39:54 2016 DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0492] InstallationDate: Installed on 2015-05-15 (521 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Veriton X4610G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago) dmi.bios.date: 05/30/2011 dmi.bios.vendor: Acer dmi.bios.version: P01-B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Veriton X4610G dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr: dmi.product.name: Veriton X4610G dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 17 15:32:10 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1634152/+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 1634152] [NEW] Driver video doesn't work properly
Public bug reported: After the last automatic upgrade, the system suggested a restart to finalize the installation. Immediately after the reboot, the graph login page worked at 640x480. Using "xdiagnose", checking (disabling) all, I was able to set a resolution 1280x1024, but no more capable to manage the dual-screen as before: in the "Monitor" configuration page, I see only one "Built-in Display" instead the two Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been changed. My PC is an Acer Veriton X4610G CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4 RAM: 4GiB (128MiB VGA shared) I use an UBUNTU 16.04 LTS 64-bit Thanks for any feedback! Paolo ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 17 15:39:54 2016 DistUpgraded: 2016-09-01 11:14:36,382 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0492] InstallationDate: Installed on 2015-05-15 (521 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 058f:6363 Alcor Micro Corp. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Veriton X4610G ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-43-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-09-01 (46 days ago) dmi.bios.date: 05/30/2011 dmi.bios.vendor: Acer dmi.bios.version: P01-B0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Veriton X4610G dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAcer:bvrP01-B0:bd05/30/2011:svnAcer:pnVeritonX4610G:pvr:rvnAcer:rnVeritonX4610G:rvr:cvnAcer:ct3:cvr: dmi.product.name: Veriton X4610G dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 17 15:32:10 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1634152 Title: Driver video doesn't work properly Status in xorg package in Ubuntu: New Bug description: After the last automatic upgrade, the system suggested a restart to finalize the installation. Immediately after the reboot, the graph login page worked at 640x480. Using "xdiagnose", checking (disabling) all, I was able to set a resolution 1280x1024, but no more capable to manage the dual-screen as before: in the "Monitor" configuration page, I see only one "Built-in Display" instead the two Acer AL1917 & AL1716 as before. Obviously, the HW connections are not been changed. My PC is an Acer Veriton X4610G CPU: Intel® Core™ i3-2120 @ 3.30GHz × 4 RAM: 4GiB (128MiB VGA shared) I use an UBUNTU 16.04 LTS 64-bit Thanks for any feedbac
[Touch-packages] [Bug 1633224] [NEW] package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 5
Public bug reported: Error launched while upgrading to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Oct 13 22:33:22 2016 ErrorMessage: il sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 5 InstallationDate: Installed on 2014-04-19 (908 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: android-tools Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 5 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) ** Affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1633224 Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 5 Status in android-tools package in Ubuntu: New Bug description: Error launched while upgrading to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Thu Oct 13 22:33:22 2016 ErrorMessage: il sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 5 InstallationDate: Installed on 2014-04-19 (908 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: android-tools Title: package android-tools-adbd 5.1.1r36+git20160322-0ubuntu3 failed to install/upgrade: il sottoprocesso nuovo script pre-removal ha restituito lo stato di errore 5 UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1633224/+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 1631659] [NEW] package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: reported while upgrading from 15.10 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20160104ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21 Uname: Linux 4.4.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Oct 8 17:25:09 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2013-12-01 (1042 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: ca-certificates Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-10-08 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1631659 Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in ca-certificates package in Ubuntu: New Bug description: reported while upgrading from 15.10 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ca-certificates 20160104ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21 Uname: Linux 4.4.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Oct 8 17:25:09 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2013-12-01 (1042 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.14 SourcePackage: ca-certificates Title: package ca-certificates 20160104ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-10-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1631659/+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 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo
Same issue here on a Dell Vostro 1700 with Ubuntu 16.04. Linux briga-laptop 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:01:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux [ 3125.120019] iwl3945 :0c:00.0: Queue 4 stuck for 2500 ms. [ 3125.120026] iwl3945 :0c:00.0: On demand firmware reload [ 3125.125835] ieee80211 phy0: Hardware restart was requested [ 3125.173756] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 [ 3125.173761] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 [ 3125.220478] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 [ 3125.220481] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 [ 3125.267181] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 [ 3125.267185] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 [ 3125.313896] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 [ 3125.313900] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 [ 3125.360606] iwl3945 :0c:00.0: BSM uCode verification failed at addr 0x3800+0 (of 900), is 0xa5a5a5a2, s/b 0xf802020 [ 3125.360614] iwl3945 :0c:00.0: Unable to set up bootstrap uCode: -5 [ 3125.397069] iwl3945 :0c:00.0: Unable to initialize device after 5 attempts. [ 3125.397077] [ cut here ] [ 3125.397139] WARNING: CPU: 0 PID: 4936 at /build/linux-a2WvEb/linux-4.4.0/net/mac80211/util.c:1818 ieee80211_reconfig+0x1e0/0xf80 [mac80211]() [ 3125.397141] Hardware became unavailable during restart. [ 3125.397143] Modules linked in: drbg ansi_cprng ctr ccm binfmt_misc nvidia_uvm(POE) gpio_ich dell_wmi sparse_keymap dell_laptop dcdbas coretemp dell_smm_hwmon kvm_intel kvm irqbypass input_leds serio_raw nvidia(POE) lpc_ich uvcvideo arc4 iwl3945 videobuf2_vmalloc videobuf2_memops iwlegacy videobuf2_v4l2 videobuf2_core joydev snd_hda_codec_hdmi v4l2_common mac80211 videodev r852 sm_common media nand snd_hda_codec_idt snd_hda_codec_generic nand_ecc nand_bch bch snd_hda_intel nand_ids r592 snd_hda_codec mtd cfg80211 memstick snd_hda_core snd_hwdep snd_pcm drm snd_seq_midi snd_seq_midi_event snd_rawmidi wmi mac_hid snd_seq snd_seq_device snd_timer snd soundcore shpchp parport_pc ppdev lp parport autofs4 ses enclosure hid_generic psmouse usbhid hid firewire_ohci firewire_core uas crc_itu_t b44 ssb sdhci_pci [ 3125.397226] mii sdhci pata_acpi usb_storage video [ 3125.397235] CPU: 0 PID: 4936 Comm: kworker/0:2 Tainted: P OE 4.4.0-36-generic #55-Ubuntu [ 3125.397238] Hardware name: Dell Inc. Vostro 1700 /0HX767, BIOS A07 04/21/2008 [ 3125.397261] Workqueue: events_freezable ieee80211_restart_work [mac80211] [ 3125.397264] 0286 122297b0 88006c84fcf0 813f13b3 [ 3125.397269] 88006c84fd38 c0410930 88006c84fd28 810810f2 [ 3125.397273] 8800b8c70700 fffb 8800b8c70700 [ 3125.397277] Call Trace: [ 3125.397288] [] dump_stack+0x63/0x90 [ 3125.397294] [] warn_slowpath_common+0x82/0xc0 [ 3125.397298] [] warn_slowpath_fmt+0x5c/0x80 [ 3125.397325] [] ? drv_start+0x44/0x110 [mac80211] [ 3125.397358] [] ieee80211_reconfig+0x1e0/0xf80 [mac80211] [ 3125.397364] [] ? mutex_lock+0x12/0x30 [ 3125.397389] [] ieee80211_restart_work+0x6b/0xa0 [mac80211] [ 3125.397395] [] process_one_work+0x165/0x480 [ 3125.397399] [] worker_thread+0x4b/0x4c0 [ 3125.397403] [] ? process_one_work+0x480/0x480 [ 3125.397406] [] ? process_one_work+0x480/0x480 [ 3125.397410] [] kthread+0xd8/0xf0 [ 3125.397414] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 3125.397419] [] ret_from_fork+0x3f/0x70 [ 3125.397422] [] ? kthread_create_on_node+0x1e0/0x1e0 [ 3125.397425] ---[ end trace fba2cc789462e954 ]--- [ 3125.397489] wlp12s0: deauthenticating from f4:f2:6d:98:6d:a4 by local choice (Reason: 3=DEAUTH_LEAVING) [ 3125.397503] [ cut here ] [ 3125.397526] WARNING: CPU: 0 PID: 4936 at /build/linux-a2WvEb/linux-4.4.0/net/mac80211/driver-ops.h:12 ieee80211_bss_info_change_notify+0x1be/0x1d0 [mac80211]() [ 3125.397529] wlp12s0: Failed check-sdata-in-driver check, flags: 0x4 [ 3125.397530] Modules linked in: drbg ansi_cprng ctr ccm binfmt_misc nvidia_uvm(POE) gpio_ich dell_wmi sparse_keymap dell_laptop dcdbas coretemp dell_smm_hwmon kvm_intel kvm irqbypass input_leds serio_raw nvidia(POE) lpc_ich uvcvideo arc4 iwl3945 videobuf2_vmalloc videobuf2_memops iwlegacy videobuf2_v4l2 videobuf2_core joydev snd_hda_codec_hdmi v4l2_common mac80211 videodev r852 sm_common media nand snd_hda_codec_idt snd_hda_codec_generic nand_ecc nand_bch bch snd_hda_intel nand_ids r592 snd_hda_codec mtd cfg80211 memstick snd_hda_core snd_hwdep snd_pcm drm snd_seq_midi snd_seq_midi_event snd_rawmidi wmi mac_hid snd_seq snd_seq_device
[Touch-packages] [Bug 1320784] Re: music in bind mounted directories are not shown in music scope
I don't know if i'm affected exactly by this bug and if it covers ubuntu touch (i'm on a BQ Aquaris E 4.5), i've found that mediascanner-service-2.0 won't scan my bind mounts at boot, but if i start it manually, all works fine... A bit annoying to open a terminal every boot :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1320784 Title: music in bind mounted directories are not shown in music scope Status in mediascanner: Invalid Status in Ubuntu Music App: Fix Released Status in mediascanner2 package in Ubuntu: Confirmed Bug description: If there is music in a directory other than ~/Music, and that directory is then mounted with "mount --bind" to ~/Music/mountedmusic, those songs are not shown in music scope. It would be important that music app had the priviliges to read these directories too, mainly because the music from the android userdata could also be mounted under ~/Music for the music app. This would be a nice step towards the using Ubuntu Touch dual-boot-installed nexto to android. Same goes for Video scopes and Gallery app. EDIT: Symbolic links do not work either. To manage notifications about this bug go to: https://bugs.launchpad.net/mediascanner/+bug/1320784/+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 1579098] Re: [touch] Mobile data connection drops, and doesn't automatically reconnect
The same Tomas reported occurs also in krillin after OTA11 -- 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/1579098 Title: [touch] Mobile data connection drops, and doesn't automatically reconnect Status in Canonical System Image: In Progress Status in network-manager package in Ubuntu: In Progress Bug description: Krillin, rc-proposed, r325 In the last couple of weeks it often happened that the mobile data connection dropped without reconnecting afterwards. I often find my device without mobile data connection without apparent reason. Switching mobile data connection Off and back On from settings restores the connection. I don't have any useful additional info to provide, unfortunately. Please let me know if you need log/cmd output in particular. phablet@ubuntu-phablet:~$ nmcli d status DEVICE TYPE STATE CONNECTION ril_1gsm disconnected -- wlan0wifi disconnected -- ril_0gsm unavailable -- ifb0 ifb unmanaged -- ifb1 ifb unmanaged -- ip6tnl0 ip6tnlunmanaged -- sit0 iptunnel unmanaged -- lo loopback unmanaged -- tunl0unknown unmanaged -- Syslog since last time mobile data was connected: http://pastebin.ubuntu.com/16259803/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579098/+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 1512100] Re: Blinking screen during the call if you remove the phone from your ear
As far as i can see, there is no bug for krillin... blinking screen is there after OTA-11 :( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1512100 Title: Blinking screen during the call if you remove the phone from your ear Status in Canonical System Image: Fix Released Status in android package in Ubuntu: Fix Released Status in powerd package in Ubuntu: Invalid Status in unity-system-compositor package in Ubuntu: Invalid Bug description: I have a problem with my Meizu MX4 (Arale r6). During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call. When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512100/+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 1588162] Re: Time in header is UTC instead oft UTC+2
The problem remains after reboot. It affects only the date/time menu in the notification area: all my events are forwarded by two hours, but in calendar are recorded with correct time All other times (clock, greeter, clock in top bar) are correct -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1588162 Title: Time in header is UTC instead oft UTC+2 Status in Canonical System Image: Incomplete Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I think it happened After OTA 11. All other time displays are correct also the alarm matches the real time, checked the kalendar too the red time indicator is also correct. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588162/+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 1574582] Re: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager
I have an HP EliteBook 745 G3 with the HP lt4120 Qualcomm® Snapdragon™ X5 LTE Mobile Broadband Module and it is not recognized by Xubuntu 16.04 as well. -- 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/1574582 Title: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network- manager Status in network-manager package in Ubuntu: Confirmed Bug description: USB modem not recognized by network-manager. Modem information in attached ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Mon Apr 25 11:14:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.106.36.1 dev wlp2s0 proto static metric 600 1.1.1.1 via 10.106.36.1 dev wlp2s0 proto dhcp metric 600 10.106.36.0/22 dev wlp2s0 proto kernel scope link src 10.106.39.123 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 IQORAMS_REPAIR 3b1e13ff-f9c9-4a49-a576-465bc2713e21 /org/freedesktop/NetworkManager/ActiveConnection/1 enxb2e41f35ffe1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- enp0s31f6ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+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 1521618] Re: wrong subnet in DHCP answer when multiple networks are present
We hit this bug also with DT and we noticed that moving conditional options
(those below) in the global section solve the problem, so we worked around
changing dhcp.conf template.
if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
} elsif option arch = 00:07 {
filename "bootx64.efi";
} elsif option arch = 00:0B {
filename "grubaa64.efi";
} elsif option arch = 00:0C {
filename "bootppc64.bin";
} else {
filename "pxelinux.0";
}
class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
}
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1521618
Title:
wrong subnet in DHCP answer when multiple networks are present
Status in MAAS:
Triaged
Status in isc-dhcp package in Ubuntu:
Confirmed
Bug description:
So I have 3 interfaces with 3, non-overlapping subnets defined in my
maas cluster controller.
The idea would be that there is a provisioning network (10.6.0.0/16)
to do the actual provisioning and once the node gets deployed it is
using a different network (because the provisioning network is only
1x1Gbit while the production network is bonded (LACP) 10Gbit).
However, when I boot up a fresh, new node to add to MAAS, it gets the
following DHCP reply:
ip=10.6.239.3:10.6.250.250:9.4.113.254:255.255.255.0
So instead of picking up the /16 subnet correctly for the 10.6.239.3
IP, it picks up the /24 from the network where it gets it's default
gateway from.
Is this a bug or my understanding of how MAAS should behave when there
are multiple networks flawed?
Here is my /var/lib/maas/dhcpd.conf:
subnet 9.4.113.0 netmask 255.255.255.0 {
if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
} elsif option arch = 00:07 {
filename "bootx64.efi";
} elsif option arch = 00:0B {
filename "grubaa64.efi";
} elsif option arch = 00:0C {
filename "bootppc64.bin";
} else {
filename "pxelinux.0";
}
interface "eth0";
ignore-client-uids true;
option subnet-mask 255.255.255.0;
option broadcast-address 9.4.113.255;
option domain-name-servers 9.4.113.251;
option domain-name "i.zc2.ibm.com";
option routers 9.4.113.254;
option ntp-servers ntp.ubuntu.com;
range dynamic-bootp 9.4.113.150 9.4.113.190;
class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
}
}
subnet 10.6.0.0 netmask 255.255.0.0 {
if option arch = 00:0E {
filename "pxelinux.0";
option path-prefix "ppc64el/";
} elsif option arch = 00:07 {
filename "bootx64.efi";
} elsif option arch = 00:0B {
filename "grubaa64.efi";
} elsif option arch = 00:0C {
filename "bootppc64.bin";
} else {
filename "pxelinux.0";
}
interface "eth1";
ignore-client-uids true;
option subnet-mask 255.255.0.0;
option broadcast-address 10.6.255.255;
option domain-name-servers 9.4.113.251;
option domain-name "i.zc2.ibm.com";
option ntp-servers ntp.ubuntu.com;
range dynamic-bootp 10.6.239.0 10.6.239.239;
class "PXE" {
match if substring (option vendor-class-identifier, 0, 3) = "PXE";
default-lease-time 30;
max-lease-time 30;
}
}
Here is "subnets read":
[
{
"dns_servers": [],
"name": "9.4.113.0/24",
"space": "space-0",
"vlan": {
"name": "untagged",
"resource_uri": "/MAAS/api/1.0/vlans/0/",
"fabric": "fabric-0",
"vid": 0,
"id": 0
},
"gateway_ip": "9.4.113.254",
"cidr": "9.4.113.0/24",
"id": 1,
"resource_uri": "/MAAS/api/1.0/subnets/1/"
},
{
"dns_servers": [],
"name": "10.7.0.0/16",
"space": "space-0",
"vlan": {
"name": "untagged",
"resource_uri": "/MAAS/api/1.0/vlans/5001/",
"fabric": "fabric-1",
"vid": 0,
"id": 5001
},
"gateway_ip": null,
"cidr": "10.7.0.0/16",
"id": 2,
"resource_uri": "/MAAS/api/1.0/subnets/2/"
},
{
"dns_servers": [],
"name": "10.6.0.0/16",
"space": "space-0",
"vlan": {
"name": "untagged",
"resource_uri":
[Touch-packages] [Bug 1568485] Re: kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13
I'm hitting the same bug, during the commissioning using trusty image in maas with wily kernel, due to intel NICs (supported only with kernel 4.2) We hit the bug running dhclient: root@messy-body:~# dhclient -nw eth2 dhclient: error while loading shared libraries: libc.so.6: cannot stat shared object: Permission denied isc-dhcp-client 4.2.4-7ubuntu12.4 ** Attachment added: "dmesg of node to be commissioned" https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1568485/+attachment/4634403/+files/dmseg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1568485 Title: kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 Status in apparmor package in Ubuntu: Confirmed Bug description: Get this logged on a fully upgraded 64 desktop (proposed archive enabled) kernel: audit: type=1400 audit(1460259033.648:34): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/sbin/dhclient" name="run/systemd/journal/dev-log" pid=1102 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Apr 10 12:23:56 2016 ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1568485/+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 1512100] Re: Blinking screen during the call if you remove the phone from your ear
Is this in OTA-10? After the update my phone (BQ Aquaris E4.5) still shows the same issue... Very annoying... I cannot hang up calls. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1512100 Title: Blinking screen during the call if you remove the phone from your ear Status in Canonical System Image: Fix Committed Status in android package in Ubuntu: Fix Committed Status in powerd package in Ubuntu: Invalid Status in unity-system-compositor package in Ubuntu: Invalid Bug description: I have a problem with my Meizu MX4 (Arale r6). During a call if you remove the phone from your ear, sometimes (not always) the screen remains turned off. When you try to push the power button to wake up the screen, that starts blinking and it's not possible to hang up. The screen remains in that condition even after the end of the call. When it keeps blinking I try to hold the button down and in few seconds the screen turns black and the phone starts working again. Sometimes, instead, it starts working again by itself. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512100/+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 1413818] Re: Notification sounds aren't being played back on E4.5 (ubuntu-push restricts directories and block custom sounds)
Again... no luck with OTA-9, please reopen... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/1413818 Title: Notification sounds aren't being played back on E4.5 (ubuntu-push restricts directories and block custom sounds) Status in Canonical System Image: Fix Released Status in The Savilerow project: Confirmed Status in ubuntu-push package in Ubuntu: Fix Committed Status in ubuntu-touch-session package in Ubuntu: Confirmed Bug description: This affects mostly the push notifications based alerts, SMS et.al. work fine. With export PULSE_PROP='media.role=alert' This has no audible output: paplay /usr/share/sounds/ubuntu/notifications/Slick.ogg This does: paplay /usr/share/sounds/ubuntu/ringtones/Soul.ogg $ system-image-cli -i current build number: 14 device name: mako channel: ubuntu-touch/stable alias: ubuntu-touch/ubuntu-rtm/14.09 last update: 2015-01-16 13:12:29 version version: 14 version ubuntu: 20150116 version device: 20141119 version custom: mako-1.1 The hunch is some buffering going on on the android side for short sound bytes. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1413818/+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
Re: [Touch-packages] [Bug 1512132] Re: sometimes no ring for incoming calls.
*** This bug is a duplicate of bug 1506953 *** https://bugs.launchpad.net/bugs/1506953 @pat as crash reporting is always enabled on my phone, i'll willingly check in /var/crash when the problem will recur. However i noticed that after last updates (ota 8.5) the problem occours very rarely. The last time it happened i did a full dump of the phablet directory, maybe useful for log analisys? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1512132 Title: sometimes no ring for incoming calls. Status in Canonical System Image: Incomplete Status in telephony-service package in Ubuntu: In Progress Bug description: This is similar, but not equal to this: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338 After ota-7, my aquaris E4.5 sometimes doesn't ring on incoming calls. It vibrates, the led blinks, but no sound at all. The phone isn't muted and toggle the related function doesn't affect the problem - the phone remains muted and only a reboot let the ringer work again for a while. after that the problem returns. when the problem presents, telephone-service-indicator.log reports: void CallManager::onCallEnded() void CallManager::onCallEnded() TelephonyService/MessagingMenu: Calling back "+" Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' void CallManager::onCallEnded() void CallManager::onCallEnded() void CallManager::onCallEnded() ** (process:2264): WARNING **: a source with id 'telephony-service-indicator' doesn't exist void CallManager::onCallEnded() void CallManager::onCallEnded() system-image-cli -i current build number: 28 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en last update: 2015-12-17 18:07:06 version version: 28 version ubuntu: 20151210 version tag: OTA-8.5 version device: 20150821-736d127 version custom: 2015--36-46-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512132/+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 1512132] Re: sometimes no ring for incoming calls.
** Description changed: This is similar, but not equal to this: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338 After ota-7, my aquaris E4.5 sometimes doesn't ring on incoming calls. It vibrates, the led blinks, but no sound at all. The phone isn't muted and toggle the related function doesn't affect the problem - the phone remains muted and only a reboot let the ringer work again for a while. after that the problem returns. when the problem presents, telephone-service-indicator.log reports: void CallManager::onCallEnded() void CallManager::onCallEnded() TelephonyService/MessagingMenu: Calling back "+" Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' void CallManager::onCallEnded() void CallManager::onCallEnded() void CallManager::onCallEnded() ** (process:2264): WARNING **: a source with id 'telephony-service-indicator' doesn't exist void CallManager::onCallEnded() void CallManager::onCallEnded() + + system-image-cli -i + + current build number: 28 + device name: krillin + channel: ubuntu-touch/stable/bq-aquaris.en + last update: 2015-12-17 18:07:06 + version version: 28 + version ubuntu: 20151210 + version tag: OTA-8.5 + version device: 20150821-736d127 + version custom: 2015--36-46-vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1512132 Title: sometimes no ring for incoming calls. Status in Canonical System Image: Incomplete Status in telephony-service package in Ubuntu: In Progress Bug description: This is similar, but not equal to this: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338 After ota-7, my aquaris E4.5 sometimes doesn't ring on incoming calls. It vibrates, the led blinks, but no sound at all. The phone isn't muted and toggle the related function doesn't affect the problem - the phone remains muted and only a reboot let the ringer work again for a while. after that the problem returns. when the problem presents, telephone-service-indicator.log reports: void CallManager::onCallEnded() void CallManager::onCallEnded() TelephonyService/MessagingMenu: Calling back "+" Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' void CallManager::onCallEnded() void CallManager::onCallEnded() void CallManager::onCallEnded() ** (process:2264): WARNING **: a source with id 'telephony-service-indicator' doesn't exist void CallManager::onCallEnded() void CallManager::onCallEnded() system-image-cli -i current build number: 28 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en last update: 2015-12-17 18:07:06 version version: 28 version ubuntu: 20151210 version tag: OTA-8.5 version device: 20150821-736d127 version custom: 2015--36-46-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512132/+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 1512132] Re: sometimes no ring for incoming calls.
Ok, finally the bug returned back. Via ssh i made a full dump of the .cache/upstart directory, so - this time - i have a full log availability :) and some other info: @Bill >When the phone is in this state, do any other sounds play correctly? For >example, can you play music from the music-app or try to change >ringtones and preview them from system-settings? I tried both, listen music and change ringtones in system.settings: no sounds. @Tiago >Could you run the following command and paste the output for us? >zgrep "Failed to get current playback position" $HOME/.cache/upstart/* That command still reports no results, so, i believe this is not a duplicate of that in comment #3 (at least is slightly different). The error, this time, blown out when i'm trying to figure out reasons i can't play some kind of videos as reported in bug 1512090, so, surely something has crashed somewhere and this prevents sessions to be restored. There is a thing i don't full understand: in comment #4 Bill mentions a workaround, then, is this workaround included in OTA-8.5? If so, then it doesn't solve this bug. Now i'm going to attach some logs. feel free to ask the full upstart dump if useful to solve this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1512132 Title: sometimes no ring for incoming calls. Status in Canonical System Image: Incomplete Status in telephony-service package in Ubuntu: In Progress Bug description: This is similar, but not equal to this: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338 After ota-7, my aquaris E4.5 sometimes doesn't ring on incoming calls. It vibrates, the led blinks, but no sound at all. The phone isn't muted and toggle the related function doesn't affect the problem - the phone remains muted and only a reboot let the ringer work again for a while. after that the problem returns. when the problem presents, telephone-service-indicator.log reports: void CallManager::onCallEnded() void CallManager::onCallEnded() TelephonyService/MessagingMenu: Calling back "+" Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' void CallManager::onCallEnded() void CallManager::onCallEnded() void CallManager::onCallEnded() ** (process:2264): WARNING **: a source with id 'telephony-service-indicator' doesn't exist void CallManager::onCallEnded() void CallManager::onCallEnded() system-image-cli -i current build number: 28 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en last update: 2015-12-17 18:07:06 version version: 28 version ubuntu: 20151210 version tag: OTA-8.5 version device: 20150821-736d127 version custom: 2015--36-46-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512132/+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 1512132] Re: sometimes no ring for incoming calls.
dbus.log ** Attachment added: "dbus.log" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512132/+attachment/4538607/+files/dbus.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1512132 Title: sometimes no ring for incoming calls. Status in Canonical System Image: Incomplete Status in telephony-service package in Ubuntu: In Progress Bug description: This is similar, but not equal to this: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338 After ota-7, my aquaris E4.5 sometimes doesn't ring on incoming calls. It vibrates, the led blinks, but no sound at all. The phone isn't muted and toggle the related function doesn't affect the problem - the phone remains muted and only a reboot let the ringer work again for a while. after that the problem returns. when the problem presents, telephone-service-indicator.log reports: void CallManager::onCallEnded() void CallManager::onCallEnded() TelephonyService/MessagingMenu: Calling back "+" Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' void CallManager::onCallEnded() void CallManager::onCallEnded() void CallManager::onCallEnded() ** (process:2264): WARNING **: a source with id 'telephony-service-indicator' doesn't exist void CallManager::onCallEnded() void CallManager::onCallEnded() system-image-cli -i current build number: 28 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en last update: 2015-12-17 18:07:06 version version: 28 version ubuntu: 20151210 version tag: OTA-8.5 version device: 20150821-736d127 version custom: 2015--36-46-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512132/+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 1512132] Re: sometimes no ring for incoming calls.
media-hub.log ** Attachment added: "media-hub.log" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512132/+attachment/4538608/+files/media-hub.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1512132 Title: sometimes no ring for incoming calls. Status in Canonical System Image: Incomplete Status in telephony-service package in Ubuntu: In Progress Bug description: This is similar, but not equal to this: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338 After ota-7, my aquaris E4.5 sometimes doesn't ring on incoming calls. It vibrates, the led blinks, but no sound at all. The phone isn't muted and toggle the related function doesn't affect the problem - the phone remains muted and only a reboot let the ringer work again for a while. after that the problem returns. when the problem presents, telephone-service-indicator.log reports: void CallManager::onCallEnded() void CallManager::onCallEnded() TelephonyService/MessagingMenu: Calling back "+" Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' void CallManager::onCallEnded() void CallManager::onCallEnded() void CallManager::onCallEnded() ** (process:2264): WARNING **: a source with id 'telephony-service-indicator' doesn't exist void CallManager::onCallEnded() void CallManager::onCallEnded() system-image-cli -i current build number: 28 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en last update: 2015-12-17 18:07:06 version version: 28 version ubuntu: 20151210 version tag: OTA-8.5 version device: 20150821-736d127 version custom: 2015--36-46-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512132/+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 1512132] Re: sometimes no ring for incoming calls.
@Tiago Yes, when the phone receive a call, the snap decision is always shown, if i realize that there is an incoming call (vibration) i can always answer the phone. Then the call goes as usual, the only strangeness is the total absence of ringtone (when this happen, all incoming calls are without tones until a phone reboot) The command you suggested reports no results, but after the last reboot i deleted all .gz files in that directory, so i fear that interesting results may be just in that files :( I'm sorry, when the problem will be repeated (quite random), i'll quickly post the result of that command -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1512132 Title: sometimes no ring for incoming calls. Status in Canonical System Image: In Progress Status in telephony-service package in Ubuntu: In Progress Bug description: This is similar, but not equal to this: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338 After ota-7, my aquaris E4.5 sometimes doesn't ring on incoming calls. It vibrates, the led blinks, but no sound at all. The phone isn't muted and toggle the related function doesn't affect the problem - the phone remains muted and only a reboot let the ringer work again for a while. after that the problem returns. when the problem presents, telephone-service-indicator.log reports: void CallManager::onCallEnded() void CallManager::onCallEnded() TelephonyService/MessagingMenu: Calling back "+" Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' void CallManager::onCallEnded() void CallManager::onCallEnded() void CallManager::onCallEnded() ** (process:2264): WARNING **: a source with id 'telephony-service-indicator' doesn't exist void CallManager::onCallEnded() void CallManager::onCallEnded() To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512132/+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 1512132] Re: sometimes no ring for incoming calls.
@Bill | It's possible media-hub could be crashing. Also, please go to System-Settings and enable sending crash reports as this will | help us see if something is crashing. OK, done! Sorry i didn't test other sounds while the problem was in act. Please mark this bug as "needinfo" so i can test other sounds/ringtones when the problem occours (i rebooted the phone and - for now - ring works) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1512132 Title: sometimes no ring for incoming calls. Status in Canonical System Image: Confirmed Status in telephony-service package in Ubuntu: New Bug description: This is similar, but not equal to this: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471338 After ota-7, my aquaris E4.5 sometimes doesn't ring on incoming calls. It vibrates, the led blinks, but no sound at all. The phone isn't muted and toggle the related function doesn't affect the problem - the phone remains muted and only a reboot let the ringer work again for a while. after that the problem returns. when the problem presents, telephone-service-indicator.log reports: void CallManager::onCallEnded() void CallManager::onCallEnded() TelephonyService/MessagingMenu: Calling back "+" Loading module: 'libubuntu_application_api_touch_mirclient.so.3.0.0' void CallManager::onCallEnded() void CallManager::onCallEnded() void CallManager::onCallEnded() ** (process:2264): WARNING **: a source with id 'telephony-service-indicator' doesn't exist void CallManager::onCallEnded() void CallManager::onCallEnded() To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512132/+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 1494172] [NEW] package modemmanager 1.4.10-1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 100
Public bug reported: Thanks ProblemType: Package DistroRelease: Ubuntu 15.10 Package: modemmanager 1.4.10-1 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Wed Sep 9 10:52:06 2015 DuplicateSignature: package:modemmanager:1.4.10-1:il sottoprocesso installato script di post-installation ha restituito lo stato di errore 100 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 100 InstallationDate: Installed on 2015-05-29 (104 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.2ubuntu3 apt 1.0.9.10ubuntu6 SourcePackage: modemmanager Title: package modemmanager 1.4.10-1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 100 UpgradeStatus: Upgraded to wily on 2015-09-09 (0 days ago) ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1494172 Title: package modemmanager 1.4.10-1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 100 Status in modemmanager package in Ubuntu: New Bug description: Thanks ProblemType: Package DistroRelease: Ubuntu 15.10 Package: modemmanager 1.4.10-1 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Wed Sep 9 10:52:06 2015 DuplicateSignature: package:modemmanager:1.4.10-1:il sottoprocesso installato script di post-installation ha restituito lo stato di errore 100 ErrorMessage: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 100 InstallationDate: Installed on 2015-05-29 (104 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.2ubuntu3 apt 1.0.9.10ubuntu6 SourcePackage: modemmanager Title: package modemmanager 1.4.10-1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 100 UpgradeStatus: Upgraded to wily on 2015-09-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1494172/+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 1333140] Re: Fix udev rules to consider mmc rpmb partitions
On my HP stream 11 with xubuntu 14.04, the 204.5ubuntu20.11 did not solve the
issue.
(I do not know how to tag it as not working).
--
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/1333140
Title:
Fix udev rules to consider mmc rpmb partitions
Status in systemd package in Ubuntu:
Fix Released
Status in udev package in Ubuntu:
Invalid
Status in udisks package in Ubuntu:
Triaged
Status in udev source package in Precise:
Triaged
Status in udisks source package in Precise:
Confirmed
Status in systemd source package in Trusty:
Fix Committed
Status in udisks source package in Trusty:
Confirmed
Bug description:
As per JEDEC 4.5 spec for eMMC devices,
There is a new partitions as part of eMMC storage devices it self. (Further
details please refer eMMC spec)
*In Linux Kernel@ 3.10.33, mmc driver has created a new partitions
with mmcblkXrpmb if device expresses it support of RPMB.
Issues observed:
issue 1:
RPMB (Replay Protected Memory Block), A signed access to a Replay Protected
Memory Block is provided. This function provides means for the system to store
data to the specific memory area in an authenticated and replay protected
manner.
In that case, any read/write access to this partition device will report
errors.
issue 2:
The by-path, line is wrongly mapping to platform-sdhci-tegra.1 -
mmcblk2rpmb were as
it should be platform-sdhci-tegra.1 - mmcblk2
ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 -
../../mmcblk2rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 -
../../mmcblk2p1
lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 - ../../mmcblk1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 -
../../mmcblk1p1
lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 -
../../mmcblk0rpmb
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 -
../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 -
../../mmcblk0p2
We have locally resolved in our platform in this file 60-persistent-
storage.rules
For issue 1: (with this rule)
# skip block read for partitions of type rpmb
KERNEL==mmcblk[0-9]rpmb, SUBSYSTEM==block, GOTO=persistent_storage_end
For issue 2:
ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL==mmcblk[0-9]rpmb,
SYMLINK+=disk/by-path/$env{ID_PATH}-rpmb
ENV{DEVTYPE}==disk, ENV{ID_PATH}==?*, KERNEL!=mmcblk[0-9]rpmb,
SYMLINK+=disk/by-path/$env{ID_PATH}
Please consider this issues fix in next udev release .
SRU INFO: This is mostly an issue with running backported kernels on 12.04
and 14.04. There is no test case which would reproduce this on arbitrary
hardware, but there are several reporters which are in a position to verify a
proposed update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+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 1395090] [NEW] libc6-dev required dependency missing for gcc-4.8 package
Public bug reported: The gcc-4.8 package in Ubuntu Trusty (14.04.1) does not include libc6-dev package as a required package but only as a recommended packages If libc6-dev is not installed cc command cannot compile anything... root@zoe:~# cc a.c /usr/bin/ld: cannot find crt1.o: No such file or directory /usr/bin/ld: cannot find crti.o: No such file or directory /usr/bin/ld: cannot find -lc /usr/bin/ld: cannot find crtn.o: No such file or directory collect2: error: ld returned 1 exit status root@zoe:~# env libc6-dev is a required dependency for g++ compiler... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gcc-4.8 4.8.2-19ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Nov 21 15:45:19 2014 SourcePackage: gcc-4.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gcc-4.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1395090 Title: libc6-dev required dependency missing for gcc-4.8 package Status in “gcc-4.8” package in Ubuntu: New Bug description: The gcc-4.8 package in Ubuntu Trusty (14.04.1) does not include libc6-dev package as a required package but only as a recommended packages If libc6-dev is not installed cc command cannot compile anything... root@zoe:~# cc a.c /usr/bin/ld: cannot find crt1.o: No such file or directory /usr/bin/ld: cannot find crti.o: No such file or directory /usr/bin/ld: cannot find -lc /usr/bin/ld: cannot find crtn.o: No such file or directory collect2: error: ld returned 1 exit status root@zoe:~# env libc6-dev is a required dependency for g++ compiler... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gcc-4.8 4.8.2-19ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Nov 21 15:45:19 2014 SourcePackage: gcc-4.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1395090/+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 1395090] Re: libc6-dev required dependency missing for gcc-4.8 package
cc needs libc6-dev to compile even the most basic source file, and it is part of gcc-4.8 I think a package should not depend on manually install build-essential package to work, in fact g++-4.8 package has a required dependencies on libc6-dev ** Changed in: gcc-4.8 (Ubuntu) Status: Invalid = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1395090 Title: libc6-dev required dependency missing for gcc-4.8 package Status in “gcc-4.8” package in Ubuntu: Incomplete Bug description: The gcc-4.8 package in Ubuntu Trusty (14.04.1) does not include libc6-dev package as a required package but only as a recommended packages If libc6-dev is not installed cc command cannot compile anything... root@zoe:~# cc a.c /usr/bin/ld: cannot find crt1.o: No such file or directory /usr/bin/ld: cannot find crti.o: No such file or directory /usr/bin/ld: cannot find -lc /usr/bin/ld: cannot find crtn.o: No such file or directory collect2: error: ld returned 1 exit status root@zoe:~# env libc6-dev is a required dependency for g++ compiler... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gcc-4.8 4.8.2-19ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Fri Nov 21 15:45:19 2014 SourcePackage: gcc-4.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1395090/+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 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()
I am trying to run the patch with the command: sudo patch -p1 0001-upowerd-Fix-cleanup-in-up_device_idevice_coldplug- fi.patch but the terminal get stuck for a long time without giving any output. Am I doing it wrong? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1305699 Title: upowerd crashed with SIGSEGV in service_client_free() Status in “upower” package in Ubuntu: Confirmed Bug description: it looks like nothing happend. When I switch on the PC and after loging in this window with 'report an error/bug' appeard. so I guess it is minor. thanks for doing :) ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 Date: Wed Apr 9 15:37:43 2014 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2014-04-04 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Beta i386 (20140326) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: SegvAnalysis: Segfault happened at: 0xb74e9919 service_client_free+25: mov (%esi),%eax PC (0xb74e9919) ok source (%esi) (0x302e) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: upower StacktraceTop: service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 property_list_service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 ?? () g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: upowerd crashed with SIGSEGV in service_client_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+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 1371625] Re: wifi don't work after suspend
Thank you very much Yu Ning. I hope someone can solve but is not mandatory. :) -- 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/1371625 Title: wifi don't work after suspend Status in OEM Priority Project: New Status in “network-manager” package in Ubuntu: Confirmed Bug description: When i take my laptop, fujitsu-siemens AMILO-Li3710, from a suspend state wifi don't work. I need to restart it to function properly. This is my laptop and i have ubuntu 14.04.. http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710 thx To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1371625/+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 1371625] Re: wifi don't work after suspend
Yes i did. Nothing happened and wifi dont' work. -- 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/1371625 Title: wifi don't work after suspend Status in OEM Priority Project: New Status in “network-manager” package in Ubuntu: Confirmed Bug description: When i take my laptop, fujitsu-siemens AMILO-Li3710, from a suspend state wifi don't work. I need to restart it to function properly. This is my laptop and i have ubuntu 14.04.. http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710 thx To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1371625/+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 1371625] Re: wifi don't work after suspend
I installed 14.10 os. Sorry. Same problem. i followed #11 comment. Nothing change. After suspend mode wifi don't work. If i launch twice: sudo nmcli nm sleep false it respond: Error in sleep: Already awake but wifi don't work. -- 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/1371625 Title: wifi don't work after suspend Status in OEM Priority Project: New Status in “network-manager” package in Ubuntu: Confirmed Bug description: When i take my laptop, fujitsu-siemens AMILO-Li3710, from a suspend state wifi don't work. I need to restart it to function properly. This is my laptop and i have ubuntu 14.04.. http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710 thx To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1371625/+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 1371625] Re: wifi don't work after suspend
1-Ok i reported a new bug for boot problem here: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1388097 2-I followed instruction in comment #9 but the situation now is worst. I also deleted 90_awake-network-manager file but command: sudo nmcli nm sleep false dont' work and output: Error in sleep: Already awake command: nmcli nm output: RUNNING:running STATE:asleep WIFI-HARDWARE:enabled WIFI:enabled WWAN-HARDWARE:enabled WWAN:disabled I cant' go online. -- 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/1371625 Title: wifi don't work after suspend Status in OEM Priority Project: New Status in “network-manager” package in Ubuntu: Confirmed Bug description: When i take my laptop, fujitsu-siemens AMILO-Li3710, from a suspend state wifi don't work. I need to restart it to function properly. This is my laptop and i have ubuntu 14.04.. http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710 thx To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1371625/+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 1371625] Re: wifi don't work after suspend
Your command is very useful. Thank you! :) I have also a problem in boot sequence. Do you have same situation? When i boot pc i receive those messages: waiting for network configuration waiting up to 60 more seconds for network configuration. After login wifi network is ready after more 60 seconds and before nmcli nm command display: RUNNING:not running STATE:unknown WIFI-HARDWARE:unknown WIFI:unknown WWAN-HARDWARE:unknown WWAN:unknown -- 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/1371625 Title: wifi don't work after suspend Status in OEM Priority Project: New Status in “network-manager” package in Ubuntu: Confirmed Bug description: When i take my laptop, fujitsu-siemens AMILO-Li3710, from a suspend state wifi don't work. I need to restart it to function properly. This is my laptop and i have ubuntu 14.04.. http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710 thx To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1371625/+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 1388097] [NEW] waiting for network configuration in boot sequence - ubuntu 13.04
Public bug reported: When i boot my pc i receive those messages: waiting for network configuration waiting up to 60 more seconds for network configuration. After login wifi network don't work and nmcli nm command display: RUNNING:not running STATE:unknown WIFI-HARDWARE:unknown WIFI:unknown WWAN-HARDWARE:unknown WWAN:unknown After a minute this is output of nmcli nm command: RUNNING:running STATE:connected WIFI-HARDWARE:enabled WIFI:enabled WWAN-HARDWARE:enabled WWAN:enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1388097 Title: waiting for network configuration in boot sequence - ubuntu 13.04 Status in “network-manager” package in Ubuntu: New Bug description: When i boot my pc i receive those messages: waiting for network configuration waiting up to 60 more seconds for network configuration. After login wifi network don't work and nmcli nm command display: RUNNING:not running STATE:unknown WIFI-HARDWARE:unknown WIFI:unknown WWAN-HARDWARE:unknown WWAN:unknown After a minute this is output of nmcli nm command: RUNNING:running STATE:connected WIFI-HARDWARE:enabled WIFI:enabled WWAN-HARDWARE:enabled WWAN:enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1388097/+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 1371625] Re: wifi don't work after suspend
Sorry i can't change language in chinese. This is output in english language: RUNNING:running STATE:asleep WIFI-HARDWARE:enabled WIFI:enabled WWAN-HARDWARE:enabled WWAN:disabled I hope help you. Thank you. -- 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/1371625 Title: wifi don't work after suspend Status in “network-manager” package in Ubuntu: New Bug description: When i take my laptop, fujitsu-siemens AMILO-Li3710, from a suspend state wifi don't work. I need to restart it to function properly. This is my laptop and i have ubuntu 14.04.. http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710 thx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1371625/+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 1383410] Re: gcc PR 58854 - 4.8.1 and 4.8.2 are known to miscompile the ARM kernel
** Package changed: gcc-4.8-armhf-cross (Ubuntu) = gcc-4.8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1383410 Title: gcc PR 58854 - 4.8.1 and 4.8.2 are known to miscompile the ARM kernel Status in “gcc-4.8” package in Ubuntu: New Bug description: From https://lkml.org/lkml/2014/10/10/272: gcc versions 4.8.[012] and 4.9.0 generates code that prematurely adjusts the stack pointer such that still-to-be-referenced locals are below the stack pointer, which allows them to be overwritten by interrupts. rmk already has a patch in his for-next branch that blacklist this compiler: http://ftp.arm.linux.org.uk/cgit/linux-arm.git/commit/?h=for- nextid=7fc150543c73de71859631c8a6b17e3067fe7617 and Trusty's toolchain is affected: [flag@stinkpad linux-2.6]$ make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/zconf.lex.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h make[1]: `include/generated/mach-types.h' is up to date. CC kernel/bounds.s GEN include/generated/bounds.h CC arch/arm/kernel/asm-offsets.s arch/arm/kernel/asm-offsets.c:53:2: error: #error Your compiler is too buggy; it is known to miscompile kernels #error Your compiler is too buggy; it is known to miscompile kernels ^ arch/arm/kernel/asm-offsets.c:54:2: error: #error and result in filesystem corruption and oopses. #error and result in filesystem corruption and oopses. ^ make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 [flag@stinkpad linux-2.6]$ [flag@stinkpad linux-2.6]$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.8.2-19ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) [flag@stinkpad linux-2.6]$ [flag@stinkpad linux-2.6]$ dpkg -l | grep linux-gnueabihf- ii gcc-4.6-arm-linux-gnueabihf-base 4.6.3-8ubuntu1cross1.67 all GCC, the GNU Compiler Collection (base package) ii gcc-4.8-arm-linux-gnueabihf-base 4.8.2-16ubuntu4cross0.11amd64GCC, the GNU Compiler Collection (base package) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1383410/+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 1383410] Re: gcc PR 58854 - 4.8.1 and 4.8.2 are known to miscompile the ARM kernel
while we carry the 4.8.2 version, the proper fix was already cherry- picked and applied, we'll revert Russel patch when it flows downstream. Marking as invalid. ** Changed in: gcc-4.8 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1383410 Title: gcc PR 58854 - 4.8.1 and 4.8.2 are known to miscompile the ARM kernel Status in “gcc-4.8” package in Ubuntu: Invalid Bug description: From https://lkml.org/lkml/2014/10/10/272: gcc versions 4.8.[012] and 4.9.0 generates code that prematurely adjusts the stack pointer such that still-to-be-referenced locals are below the stack pointer, which allows them to be overwritten by interrupts. rmk already has a patch in his for-next branch that blacklist this compiler: http://ftp.arm.linux.org.uk/cgit/linux-arm.git/commit/?h=for- nextid=7fc150543c73de71859631c8a6b17e3067fe7617 and Trusty's toolchain is affected: [flag@stinkpad linux-2.6]$ make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabihf- HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o SHIPPED scripts/kconfig/zconf.tab.c SHIPPED scripts/kconfig/zconf.lex.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h make[1]: `include/generated/mach-types.h' is up to date. CC kernel/bounds.s GEN include/generated/bounds.h CC arch/arm/kernel/asm-offsets.s arch/arm/kernel/asm-offsets.c:53:2: error: #error Your compiler is too buggy; it is known to miscompile kernels #error Your compiler is too buggy; it is known to miscompile kernels ^ arch/arm/kernel/asm-offsets.c:54:2: error: #error and result in filesystem corruption and oopses. #error and result in filesystem corruption and oopses. ^ make[1]: *** [arch/arm/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2 [flag@stinkpad linux-2.6]$ [flag@stinkpad linux-2.6]$ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.8.2-19ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.8 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) [flag@stinkpad linux-2.6]$ [flag@stinkpad linux-2.6]$ dpkg -l | grep linux-gnueabihf- ii gcc-4.6-arm-linux-gnueabihf-base 4.6.3-8ubuntu1cross1.67 all GCC, the GNU Compiler Collection (base package) ii gcc-4.8-arm-linux-gnueabihf-base 4.8.2-16ubuntu4cross0.11amd64GCC, the GNU Compiler Collection (base package) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1383410/+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 1380050] [NEW] Ubuntu boots to a black screen
Public bug reported: Ubuntu boots to a black screen. I can hear the opening chimes, but I cannot see anything until I switch my screen off and on again. Then I can see the login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Oct 11 12:49:21 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1041] InstallationDate: Installed on 2014-09-26 (14 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: HP-Pavilion KA869AA-ABZ a6335.it ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-36-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.13 dmi.board.name: NARRA2 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 2.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.13:bd10/29/2007:svnHP-Pavilion:pnKA869AA-ABZa6335.it:pvr:rvnASUSTekComputerINC.:rnNARRA2:rvr2.00:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: KA869AA-ABZ a6335.it dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Oct 11 12:48:11 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMLK Trust Keyboard 14909 KEYBOARD, id 8 inputMLK Trust Keyboard 14909 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- 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/1380050 Title: Ubuntu boots to a black screen Status in “xorg” package in Ubuntu: New Bug description: Ubuntu boots to a black screen. I can hear the opening chimes, but I cannot see anything until I switch my screen off and on again. Then I can see the login screen. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Oct 11 12:49:21 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1041] InstallationDate: Installed on 2014-09-26 (14 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: HP-Pavilion KA869AA-ABZ a6335.it ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-36-generic root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.13 dmi.board.name: NARRA2
[Touch-packages] [Bug 1326954] Re: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904)
systemd workaround: systemctl stop/start ModemManager.service in pm-utils /etc/pm/sleep.d/ works only if mobile broadband is connected before suspend. Seems a kernel/firmware/something issue to me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904) Status in ModemManager (with NetworkManager support): New Status in “libmbim” package in Ubuntu: Confirmed Status in “modemmanager” package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): debug [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... debug [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' debug [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested debug [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested debug [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... debug [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... RAW: length = 16 data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... Header: length = 16 type= open (0x0001) transaction = 1 Contents: max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... RAW: length = 16 data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 debug [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... RAW: length = 12 data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... Header: length = 12 type= close (0x0002) transaction = 2 [/dev/cdc-wdm0] Received message... RAW: length = 16 data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 debug [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port debug [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin debug [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) debug [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested debug [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin debug [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device debug [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds info [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports debug [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' |
[Touch-packages] [Bug 1326954] Re: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904)
Mobile broadband not working after resume on Toshiba Tecra Z40, too. $ lsusb Bus 002 Device 002: ID 1199:9063 Sierra Wireless, Inc. How can i help troubleshooting the problem? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1326954 Title: ModemManager does not seem to recognize Sierra Wireless EM7305 (Fujitsu Lifebook S904) Status in ModemManager (with NetworkManager support): New Status in “libmbim” package in Ubuntu: Confirmed Status in “modemmanager” package in Ubuntu: Invalid Bug description: Ubuntu 14.04, x86_64, ModemManager-1.0.0-2ubuntu1 Card: Sierra Wireless EM7305 (PCI Express M.2 form factor) Expected: Sierra plugin is used Happens: Generic plugin is used instead After cold start the card seems to work almost fine, but does not come back after suspend or hibernate. At least after hibernate MM may go into a tight loop consuming 100% CPU. MM debug log output (full log attached): debug [1401992536.121631] [mm-plugin-manager.c:576] build_plugins_list(): (Plugin Manager) [wwan0] Found '1' plugins to try... debug [1401992536.125236] [mm-plugin-manager.c:580] build_plugins_list(): (Plugin Manager) [wwan0] Will try with plugin 'Generic' debug [1401992536.128923] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested debug [1401992536.132687] [mm-plugin-manager.c:505] plugin_supports_port_ready(): (Plugin Manager) [wwan0] deferring support check until result suggested debug [1401992536.142664] [mm-port-probe.c:536] wdm_probe_mbim(): (usbmisc/cdc-wdm0) probing MBIM... debug [1401992538.202591] [mm-plugin-manager.c:646] min_probing_timeout_cb(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] Minimum probing time consumed [/dev/cdc-wdm0] Queried max control message size: 4096[/dev/cdc-wdm0] Sent message... RAW: length = 16 data = 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 [/dev/cdc-wdm0] Sent message (translated)... Header: length = 16 type= open (0x0001) transaction = 1 Contents: max_control_transfer = 4096 [/dev/cdc-wdm0] Received message... RAW: length = 16 data = 01:00:00:80:10:00:00:00:01:00:00:00:00:00:00:00 debug [1401992539.481429] [mm-port-probe.c:300] mm_port_probe_set_result_mbim(): (usbmisc/cdc-wdm0) port is MBIM-capable [/dev/cdc-wdm0] Sent message... RAW: length = 12 data = 02:00:00:00:0C:00:00:00:02:00:00:00 [/dev/cdc-wdm0] Sent message (translated)... Header: length = 12 type= close (0x0002) transaction = 2 [/dev/cdc-wdm0] Received message... RAW: length = 16 data = 02:00:00:80:10:00:00:00:02:00:00:00:00:00:00:00 debug [1401992539.545529] [mm-plugin-manager.c:417] plugin_supports_port_ready(): (Plugin Manager) (Generic) [cdc-wdm0] found best plugin for port debug [1401992539.549361] [mm-plugin-manager.c:334] suggest_port_probe_result(): (Plugin Manager) (Generic) [wwan0] deferred task completed, got suggested plugin debug [1401992539.553247] [mm-plugin-manager.c:274] port_probe_context_finished(): (Plugin Manager) 'cdc-wdm0' port probe finished, still 1 running probes in this device (wwan0) debug [1401992539.556995] [mm-plugin.c:700] mm_plugin_supports_port(): (Generic) [wwan0] probing deferred until result suggested debug [1401992539.560690] [mm-plugin-manager.c:485] plugin_supports_port_ready(): (Plugin Manager) (Generic) [wwan0] task completed, got suggested plugin debug [1401992539.564175] [mm-plugin-manager.c:285] port_probe_context_finished(): (Plugin Manager) 'wwan0' port probe finished, last one in device debug [1401992539.567868] [mm-plugin-manager.c:107] find_device_support_context_complete_and_free(): (Plugin Manager) [/sys/devices/pci:00/:00:14.0/usb1/1-6] device support check finished in '3.677528' seconds info [1401992539.571611] [mm-device.c:486] mm_device_create_modem(): Creating modem with plugin 'Generic' and '2' ports debug [1401992539.575477] [generic/mm-plugin-generic.c:73] create_modem(): MBIM-powered generic modem found... mmcli output: /org/freedesktop/ModemManager1/Modem/0 (device id 'b3a77501ed8da196baa804a4142ff280766f6f98') - Hardware | manufacturer: 'Generic' | model: 'MBIM [1199:9063]' | revision: 'SWI9X15C_01.12' | supported: 'gsm-umts, lte' |current: 'gsm-umts, lte' | equipment id: '356906050069168' - System | device: '/sys/devices/pci:00/:00:14.0/usb1/1-6' |drivers: 'cdc_mbim' | plugin: 'Generic' | primary port: 'cdc-wdm0' | ports: 'cdc-wdm0 (mbim),
[Touch-packages] [Bug 1338254]
Author: paolo
Date: Tue Sep 23 08:09:14 2014
New Revision: 215497
URL: https://gcc.gnu.org/viewcvs?rev=215497root=gccview=rev
Log:
2014-09-23 Paolo Carlini paolo.carl...@oracle.com
PR c++/62155
* g++.dg/cpp0x/lambda/lambda-62155.C: New.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/lambda/lambda-62155.C
Modified:
trunk/gcc/testsuite/ChangeLog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1338254
Title:
internal error on lambda as argument
Status in The GNU Compiler Collection:
Fix Released
Status in “gcc-4.8” package in Ubuntu:
Confirmed
Status in “gcc-4.9” package in Ubuntu:
Confirmed
Status in “gcc-snapshot” package in Ubuntu:
Fix Released
Bug description:
1) The release of Ubuntu I am using:
$ lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04
2) The package version:
$ apt-cache policy g++
g++:
Installed: 4:4.8.2-1ubuntu6
Candidate: 4:4.8.2-1ubuntu6
Version table:
*** 4:4.8.2-1ubuntu6 0
500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
3) What I expected to happen:
I expected the source file test.cc to compile correctly, using the
compiler command:
g++ -std=c++1y test.cc
4) What happened instead:
Compiler output:
test.cc: In instantiation of ‘struct Sint::__lambda0’:
test.cc:15:8: required from here
test.cc:18:8: internal compiler error: in tsubst_copy, at cp/pt.c:12125
B b{[this]() { foo(); }};
^
Please submit a full bug report,
with preprocessed source if appropriate.
See file:///usr/share/doc/gcc-4.8/README.Bugs for instructions.
Preprocessed source stored into /tmp/ccgECJVP.out file, please attach this to
your bugreport.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1338254/+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 1338254]
Done.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1338254
Title:
internal error on lambda as argument
Status in The GNU Compiler Collection:
Fix Released
Status in “gcc-4.8” package in Ubuntu:
Confirmed
Status in “gcc-4.9” package in Ubuntu:
Confirmed
Status in “gcc-snapshot” package in Ubuntu:
Fix Released
Bug description:
1) The release of Ubuntu I am using:
$ lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04
2) The package version:
$ apt-cache policy g++
g++:
Installed: 4:4.8.2-1ubuntu6
Candidate: 4:4.8.2-1ubuntu6
Version table:
*** 4:4.8.2-1ubuntu6 0
500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
3) What I expected to happen:
I expected the source file test.cc to compile correctly, using the
compiler command:
g++ -std=c++1y test.cc
4) What happened instead:
Compiler output:
test.cc: In instantiation of ‘struct Sint::__lambda0’:
test.cc:15:8: required from here
test.cc:18:8: internal compiler error: in tsubst_copy, at cp/pt.c:12125
B b{[this]() { foo(); }};
^
Please submit a full bug report,
with preprocessed source if appropriate.
See file:///usr/share/doc/gcc-4.8/README.Bugs for instructions.
Preprocessed source stored into /tmp/ccgECJVP.out file, please attach this to
your bugreport.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1338254/+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 1338254]
Since it's just an ICE on invalid, I'm adding the testcase and closing
the bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1338254
Title:
internal error on lambda as argument
Status in The GNU Compiler Collection:
Fix Released
Status in “gcc-4.8” package in Ubuntu:
Confirmed
Status in “gcc-4.9” package in Ubuntu:
Confirmed
Status in “gcc-snapshot” package in Ubuntu:
Fix Released
Bug description:
1) The release of Ubuntu I am using:
$ lsb_release -rd
Description: Ubuntu 14.04 LTS
Release: 14.04
2) The package version:
$ apt-cache policy g++
g++:
Installed: 4:4.8.2-1ubuntu6
Candidate: 4:4.8.2-1ubuntu6
Version table:
*** 4:4.8.2-1ubuntu6 0
500 http://ch.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
3) What I expected to happen:
I expected the source file test.cc to compile correctly, using the
compiler command:
g++ -std=c++1y test.cc
4) What happened instead:
Compiler output:
test.cc: In instantiation of ‘struct Sint::__lambda0’:
test.cc:15:8: required from here
test.cc:18:8: internal compiler error: in tsubst_copy, at cp/pt.c:12125
B b{[this]() { foo(); }};
^
Please submit a full bug report,
with preprocessed source if appropriate.
See file:///usr/share/doc/gcc-4.8/README.Bugs for instructions.
Preprocessed source stored into /tmp/ccgECJVP.out file, please attach this to
your bugreport.
To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc/+bug/1338254/+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 1371625] [NEW] wifi don't work after suspend
Public bug reported: When i take my laptop, fujitsu-siemens AMILO-Li3710, from a suspend state wifi don't work. I need to restart it to function properly. This is my laptop and i have ubuntu 14.04.. http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710 thx ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1371625 Title: wifi don't work after suspend Status in “network-manager” package in Ubuntu: New Bug description: When i take my laptop, fujitsu-siemens AMILO-Li3710, from a suspend state wifi don't work. I need to restart it to function properly. This is my laptop and i have ubuntu 14.04.. http://wiki.ubuntu-it.org/Hardware/Notebook/FujitsuSiemensAMILOLi3710 thx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1371625/+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 1370208] [NEW] Black screen after booting
Public bug reported: When I switch on my desktop, I see the booting information on the screen, then the screen turns black. I can hear the opening sound of Ubuntu, but the screen remains black. Only if I switch off my screen and then switch it on again, I can see the login screen of Ubuntu, then everything works fine. This is not a major problem, but somehow annoying. My screen is a Samsung LCD TV set Series A 3-4-5-6-7. It used to work fine with Ubuntu 12.04. I have experienced this problem after upgrading to 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Sep 16 20:52:19 2014 DistUpgraded: 2014-08-20 11:57:07,417 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1041] InstallationDate: Installed on 2014-04-03 (165 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release i386 (20140204) MachineType: HP-Pavilion KA869AA-ABZ a6335.it ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=1f697905-8f52-4f35-9b5c-5b8a0a3c1dba ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-08-20 (27 days ago) dmi.bios.date: 10/29/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.13 dmi.board.name: NARRA2 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 2.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.13:bd10/29/2007:svnHP-Pavilion:pnKA869AA-ABZa6335.it:pvr:rvnASUSTekComputerINC.:rnNARRA2:rvr2.00:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: KA869AA-ABZ a6335.it dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Sep 16 20:37:02 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputMLK Trust Keyboard 14909 KEYBOARD, id 8 inputMLK Trust Keyboard 14909 KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.1 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- 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/1370208 Title: Black screen after booting Status in “xorg” package in Ubuntu: New Bug description: When I switch on my desktop, I see the booting information on the screen, then the screen turns black. I can hear the opening sound of Ubuntu, but the screen remains black. Only if I switch off my screen and then switch it on again, I can see the login screen of Ubuntu, then everything works fine. This is not a major problem, but somehow annoying. My screen is a Samsung LCD TV set Series A 3-4-5-6-7. It used to work fine with Ubuntu 12.04. I have experienced this problem after upgrading to 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.4 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz
[Touch-packages] [Bug 1359262] Re: Chrome + Radeon + hardware acceleration: black Google maps tab
** Attachment added: Screenshot2014-08-20.png https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1359262/+attachment/4182583/+files/Screenshot2014-08-20.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1359262 Title: Chrome + Radeon + hardware acceleration: black Google maps tab Status in “mesa” package in Ubuntu: New Bug description: When opening Google Maps, i got a completely black tab instead - see the attached image. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgl1-mesa-dri 10.1.3-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Aug 20 17:29:32 2014 DistUpgraded: 2014-04-04 15:34:47,605 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] [1002:68e1] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Caicos [Radeon HD 5450] [174b:3000] InstallationDate: Installed on 2012-11-15 (643 days ago) InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release amd64 (20121017.2) MachineType: Intel Corporation Shark Bay Client platform ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-34-generic root=UUID=5f908618-7000-4276-855c-8ec7a19ce316 ro crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M SourcePackage: mesa UpgradeStatus: Upgraded to trusty on 2014-04-04 (138 days ago) dmi.bios.date: 01/28/2013 dmi.bios.vendor: Intel Corporation dmi.bios.version: HSWLPTU1.86C.0109.R03.1301282055 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Flathead Creek Crb dmi.board.vendor: Intel Corp. dmi.board.version: 2 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnIntelCorporation:bvrHSWLPTU1.86C.0109.R03.1301282055:bd01/28/2013:svnIntelCorporation:pnSharkBayClientplatform:pvr0.1:rvnIntelCorp.:rnFlatheadCreekCrb:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.name: Shark Bay Client platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Aug 20 11:04:41 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1359262/+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
