[Touch-packages] [Bug 2023442] [NEW] totem playback hangs after seeking
Public bug reported: Playback hangs after seeking forward and backwards a number of times, with some video files. This can been reproduced in Totem and gst-play-1.0. It seems to be caused by some audio stack related change in Ubuntu 22.04. This does not happen when using the Totem flatpak. upstream bug: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1477 ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023442 Title: totem playback hangs after seeking Status in gstreamer1.0 package in Ubuntu: New Bug description: Playback hangs after seeking forward and backwards a number of times, with some video files. This can been reproduced in Totem and gst-play-1.0. It seems to be caused by some audio stack related change in Ubuntu 22.04. This does not happen when using the Totem flatpak. upstream bug: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1477 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2023442/+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 2021889] Re: error OSSL_CMP_MSG_update_recipNonce on base64 decoding
Oh, I found out it was another image in CI/CD setup. Sorry, my bad. ** Changed in: openssl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2021889 Title: error OSSL_CMP_MSG_update_recipNonce on base64 decoding Status in openssl package in Ubuntu: Invalid Bug description: $ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not found Error loading key "(stdin)": error in libcrypto --- works with openssl Version: 3.0.2-0ubuntu1.9. version 3.0.2-0ubuntu1.10 is broken. private key was: DEK-Info: AES-128-CBC $lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Policy is from server where I did NOT upgrade (not wanted things to be broken). $apt-cache policy openssl openssl: Installed: 3.0.2-0ubuntu1.9 Candidate: 3.0.2-0ubuntu1.10 Version table: 3.0.2-0ubuntu1.10 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 3.0.2-0ubuntu1.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2021889/+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 2021889] Re: error OSSL_CMP_MSG_update_recipNonce on base64 decoding
Yes, I did upgrade of all packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2021889 Title: error OSSL_CMP_MSG_update_recipNonce on base64 decoding Status in openssl package in Ubuntu: New Bug description: $ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not found Error loading key "(stdin)": error in libcrypto --- works with openssl Version: 3.0.2-0ubuntu1.9. version 3.0.2-0ubuntu1.10 is broken. private key was: DEK-Info: AES-128-CBC $lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Policy is from server where I did NOT upgrade (not wanted things to be broken). $apt-cache policy openssl openssl: Installed: 3.0.2-0ubuntu1.9 Candidate: 3.0.2-0ubuntu1.10 Version table: 3.0.2-0ubuntu1.10 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 3.0.2-0ubuntu1.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2021889/+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 2021889] Re: error OSSL_CMP_MSG_update_recipNonce on base64 decoding
Nope, only distribution packages. I noted it first in my CI/CD setup where I install fresh docker image ubuntu:22.04 and then apt-get update && apt-get upgrade -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2021889 Title: error OSSL_CMP_MSG_update_recipNonce on base64 decoding Status in openssl package in Ubuntu: New Bug description: $ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not found Error loading key "(stdin)": error in libcrypto --- works with openssl Version: 3.0.2-0ubuntu1.9. version 3.0.2-0ubuntu1.10 is broken. private key was: DEK-Info: AES-128-CBC $lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Policy is from server where I did NOT upgrade (not wanted things to be broken). $apt-cache policy openssl openssl: Installed: 3.0.2-0ubuntu1.9 Candidate: 3.0.2-0ubuntu1.10 Version table: 3.0.2-0ubuntu1.10 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 3.0.2-0ubuntu1.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2021889/+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 2021889] [NEW] error OSSL_CMP_MSG_update_recipNonce on base64 decoding
Public bug reported: $ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not found Error loading key "(stdin)": error in libcrypto --- works with openssl Version: 3.0.2-0ubuntu1.9. version 3.0.2-0ubuntu1.10 is broken. private key was: DEK-Info: AES-128-CBC $lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Policy is from server where I did NOT upgrade (not wanted things to be broken). $apt-cache policy openssl openssl: Installed: 3.0.2-0ubuntu1.9 Candidate: 3.0.2-0ubuntu1.10 Version table: 3.0.2-0ubuntu1.10 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 3.0.2-0ubuntu1.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages ** Affects: openssl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/2021889 Title: error OSSL_CMP_MSG_update_recipNonce on base64 decoding Status in openssl package in Ubuntu: New Bug description: $ echo "$SSH_PRIVATE_KEY" | openssl base64 -A -d Error relocating /usr/bin/openssl: OSSL_CMP_MSG_update_recipNonce: symbol not found Error loading key "(stdin)": error in libcrypto --- works with openssl Version: 3.0.2-0ubuntu1.9. version 3.0.2-0ubuntu1.10 is broken. private key was: DEK-Info: AES-128-CBC $lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Policy is from server where I did NOT upgrade (not wanted things to be broken). $apt-cache policy openssl openssl: Installed: 3.0.2-0ubuntu1.9 Candidate: 3.0.2-0ubuntu1.10 Version table: 3.0.2-0ubuntu1.10 500 500 http://archive.ubuntu.com/ubuntu jammy-security/main amd64 Packages *** 3.0.2-0ubuntu1.9 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.0.2-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2021889/+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 1813394] Re: DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
Confirming the clevis issue.
Patch for reference:
--- /usr/share/initramfs-tools/scripts/local-bottom/clevis.orig 2022-07-11
10:52:16.938228467 -0500
+++ /usr/share/initramfs-tools/scripts/local-bottom/clevis 2022-07-11
10:30:08.040636353 -0500
@@ -46,5 +46,9 @@ for iface in /sys/class/net/*; do
ip link set dev "$iface" down
ip addr flush dev "$iface"
ip route flush dev "$iface"
+
+if [ -f "/run/netplan/${iface}.yaml" ]; then
+rm "/run/netplan/${iface}.yaml"
+fi
fi
done
Followed by: update-initramfs -u -k 'all'
--
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/1813394
Title:
DROPBEAR_IFDOWN=* takes interface down but leaves netplan config
Status in clevis package in Ubuntu:
Confirmed
Status in dropbear package in Ubuntu:
Confirmed
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
On bionic, setting the network interface up (e.g. eno1) with DHCP now
causes a /run/netplan/eno1.yaml and a /run/net-eno1.conf file to be
written. The former gets imported by netplan after boot and causes the
DHCP lease from the initrd to be around forever, which I think goes
against the intent of DROPBEAR_IFDOWN=*.
I have brewed up a workaround script that lives in /etc/initramfs-
tools/scripts/init-bottom/hack-delete-netif-netplan.sh for now:
8< cut >8
#!/bin/sh
PREREQ=""
prereqs() {
echo "$PREREQ"
}
case "$1" in
prereqs)
prereqs
exit 0
;;
esac
. /scripts/functions
log_begin_msg "Deleting all network configuration that systemd could try to
import"
rm /run/net-*.conf
rm /run/netplan/*.yaml
log_end_msg
8< cut >8
I think that dropbear-intiramfs's init-bottom script should do this in
addition to downing the interfaces that it finds via the
DROPBEAR_IFDOWN pattern. Do you agree?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1813394/+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 1008213] Re: Missing depends on whoopsie.
This bug still persists. Ubuntu MATE 20.04.4, network-manager 1.22.10-1ubuntu2.3 -- 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/1008213 Title: Missing depends on whoopsie. Status in network-manager package in Ubuntu: Confirmed Bug description: By depends I mean one of Suggests/Recommends/Depends. Currently, with no other changes, I'd say you need Depends. Thus I think you should change part of your package to accommodate for systems that don't have whoopsie installed. /etc/dbus-1/system.d/org.freedesktop.NetworkManager.conf:91: This leads to... arcadia:~# cat /var/log/upstart/dbus.log Unknown username "whoopsie" in message bus configuration file It's not an error and it doesn't break anything, but it should be easy for you to change things a little. One option is to create this user, though I'd coordinate that with the whoopsie developer. A perhaps better solution is to split this configuration out so that is will only be included if/when whoopsie is installed or the whoopsie user is available. Thank you. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-23.31-lowlatency-pae 3.2.14 Uname: Linux 3.2.0-23-lowlatency-pae i686 ApportVersion: 2.0.1-0ubuntu8 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Sun Jun 3 15:05:40 2012 IpRoute: default via 192.168.172.100 dev eth2 metric 100 169.254.0.0/16 dev eth2 scope link metric 1000 192.168.172.0/24 dev eth2 proto kernel scope link src 192.168.172.26 IwConfig: Error: [Errno 2] No such file or directory NetDevice.eth2: Error: [Errno 2] No such file or directory X: INTERFACE_MAC=f4:6d:04:2c:0a:e1 NetDevice.lo: Error: [Errno 2] No such file or directory X: INTERFACE_MAC=00:00:00:00:00:00 NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=false RfKill: Error: [Errno 2] No such file or directory SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-01-03 (152 days ago) WpaSupplicantLog: nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Auto eth8 759a3094-00a2-4699-bcb0-99d4662887a6 802-3-ethernet0never no no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth2 802-3-ethernetunmanaged /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0asleep disabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1008213/+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 1273258] Re: Hundreds of dbus-daemon processes
Happens on 20.04. Eventually swap is 100% full and machine is rebooted by watchdog due to high (>240) load average. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1273258 Title: Hundreds of dbus-daemon processes Status in dbus package in Ubuntu: Confirmed Bug description: I find a growing number of root owned dbus-daemon processes. Eventually, this results in a 'too many processes' error preventing something to fork, e.g. a login. They get created by batches of 4, every 30 minutes on my box. My box is a puppet client, so that these 30 minutes are not in a local cron tab. The pids are 11 units apart (when the box is otherwise idle). The command line is: //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session ~# ps -fu root | grep dbus-daemon | grep -v grep | tail -8 root 17509 1 0 11:25 ?00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session root 17520 1 0 11:25 ?00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session root 17531 1 0 11:25 ?00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session root 17542 1 0 11:25 ?00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session root 17972 1 0 11:55 ?00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session root 17983 1 0 11:55 ?00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session root 17994 1 0 11:55 ?00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session root 18005 1 0 11:55 ?00:00:00 //bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session I reported this first to https://bugs.freedesktop.org/show_bug.cgi?id=74114 and was told to report it to ubuntu instead. Here were some additional comments: The symptoms you described probably mean that something running as root is either running /usr/bin/dbus-launch, or attempting to access a D-Bus session via the autolaunch: transport while under a transient X11 session, 4 times every 30 minutes. If this machine does not intentionally run an X11 GUI or a D-Bus session, uninstalling the dbus-x11 package or making /usr/bin/dbus- launch non-executable might work around this. Don't do that if you use an X11 GUI environment, though. Since 1.4.8, dbus autolaunch has only been effective when DISPLAY is set and non-empty, so if this is autolaunch, an X11 session must be involved somehow. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dbus 1.4.18-1ubuntu1.4 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Jan 27 14:51:19 2014 MarkForUpload: True ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1273258/+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 1956447] [NEW] "No DNS servers known" in /run/systemd/resolve/resolv.conf
Public bug reported: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd: Installed: 245.4-4ubuntu3.13 Candidate: 245.4-4ubuntu3.13 3) What you expected to happen /etc/network/interfaces: auto lo iface lo inet loopback dns-nameservers 1.1.1.1 8.8.8.8 auto eth0 iface eth0 inet static address ip/24 mtu 1500 post-up route add default gw gw_ip || true pre-down route del default gw gw_ip || true When system rebooted I expected in /run/resolvconf/resolv.conf: nameserver 1.1.1.1 nameserver 8.8.8.8 nameserver 127.0.0.53 and in /run/systemd/resolve/resolv.conf: nameserver 1.1.1.1 nameserver 8.8.8.8 This is stated in "man 8 systemd-resolved": systemd-resolved maintains the /run/systemd/resolve/resolv.conf file for compatibility with traditional Linux programs 4) What happened instead /run/systemd/resolve/resolv.conf: # No DNS servers known. But after restarting systemd-resolved it update this file correctly. 5) Also The system behaves correctly when DHCP is used. So when in /etc/network/interfaces: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Then /run/systemd/resolve/resolv.conf updated correctly straight without restart. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1956447 Title: "No DNS servers known" in /run/systemd/resolve/resolv.conf Status in systemd package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 20.04.3 LTS Release: 20.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center systemd: Installed: 245.4-4ubuntu3.13 Candidate: 245.4-4ubuntu3.13 3) What you expected to happen /etc/network/interfaces: auto lo iface lo inet loopback dns-nameservers 1.1.1.1 8.8.8.8 auto eth0 iface eth0 inet static address ip/24 mtu 1500 post-up route add default gw gw_ip || true pre-down route del default gw gw_ip || true When system rebooted I expected in /run/resolvconf/resolv.conf: nameserver 1.1.1.1 nameserver 8.8.8.8 nameserver 127.0.0.53 and in /run/systemd/resolve/resolv.conf: nameserver 1.1.1.1 nameserver 8.8.8.8 This is stated in "man 8 systemd-resolved": systemd-resolved maintains the /run/systemd/resolve/resolv.conf file for compatibility with traditional Linux programs 4) What happened instead /run/systemd/resolve/resolv.conf: # No DNS servers known. But after restarting systemd-resolved it update this file correctly. 5) Also The system behaves correctly when DHCP is used. So when in /etc/network/interfaces: auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Then /run/systemd/resolve/resolv.conf updated correctly straight without restart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1956447/+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 1934501] Re: CVE-2018-15473 patch introduce user enumeration vulnerability
Hi. I believe my Ubuntu systems just received this patch and I believe it
failed to install:
Can't exec "/tmp/openssh-server.config.neW0Pf": Permission denied at
/usr/share/perl/5.26/IPC/Open3.pm line 178.
open2: exec of /tmp/openssh-server.config.neW0Pf configure 1:7.6p1-4ubuntu0.3
failed: Permission denied at /usr/share/perl5/Debconf/ConfModule.pm line 59.
-
I think this is due to the fact I have noexec on /tmp.
Is it possible to bundle the changes in the package instead of putting a random
temporary file in /tmp and attempt to execute it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1934501
Title:
CVE-2018-15473 patch introduce user enumeration vulnerability
Status in openssh package in Ubuntu:
Fix Released
Bug description:
I was recently using a 18.04 machine and noticed that the result of
connecting to ssh with an arbitrary public key varied depending if the
user was valid.
After some investigation, it appears to only be present when
CVE-2018-15473.patch has been applied.
Directly pulling a 18.04 docker image and installing openssh server
(currently 1:7.6p1-4ubuntu0.3) results in a trivial user enumeration
vulnerability in the default config.
Below shows the setup of environment:
$ docker pull ubuntu:18.04
18.04: Pulling from library/ubuntu
Digest:
sha256:139b3846cee2e63de9ced83cee7023a2d95763ee2573e5b0ab6dea9dfbd4db8f
Status: Image is up to date for ubuntu:18.04
docker.io/library/ubuntu:18.04
$ docker run -t -i --rm -e TERM=${TERM} ubuntu:18.04
root@75569fbf0b03:/# apt update
...snip...
root@75569fbf0b03:/# apt install openssh-server
...snip...
root@75569fbf0b03:/# dpkg-query -l openssh\*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version
Architecture Description
+++--=-=-=
ii openssh-client 1:7.6p1-4ubuntu0.3amd64
secure shell (SSH) client, for secure access to remote
machines
ii openssh-server 1:7.6p1-4ubuntu0.3amd64
secure shell (SSH) server, for secure access from remote
machines
ii openssh-sftp-server 1:7.6p1-4ubuntu0.3amd64
secure shell (SSH) sftp server module, for SFTP access from
remote machines
root@75569fbf0b03:/# mkdir /run/sshd
root@75569fbf0b03:/# /usr/sbin/sshd -D
Then to perform user enumeration, connecting with a public key results in
user enumeration:
* in the following id_rsa-dummy.pub is removed as it slightly changes message
flow
* I have not checked different versions of the ssh client
$ ssh -V
OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020
$ ssh-keygen -t rsa -C dummy -P '' -f id_rsa-dummy
$ rm id_rsa-dummy.pub
$ ssh -i id_rsa-dummy invalid@172.17.0.2
Connection closed by 172.17.0.2 port 22
$ ssh -i id_rsa-dummy root@172.17.0.2
root@172.17.0.2's password:
That is, when invalid users are provided to public key auth the
connection is closed by the server. Otherwise, it will move onto the
next auth method. This can be improved by adding "ssh -o
PasswordAuthentication=no" when connecting to avoid password prompt
and get an easy to script error message.
I have verified that this behaviour is present after starting with
original source and only applying CVE-2018-15473.patch from the
openssh_7.6p1-4ubuntu0.3.debian.tar.xz archive. Without this patch
this behaviour is not present.
$ md5sum openssh-7.6p1.tar.gz debian/patches/CVE-2018-15473.patch
06a88699018e5fef13d4655abfed1f63 openssh-7.6p1.tar.gz
6101d47f542690b0c5e354ec8b8a70a1 debian/patches/CVE-2018-15473.patch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1934501/+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 1877987] Re: apt search coredumping
This bug affects apt 2.0.3 $ apt search openjdk Sorting... Done Segmentation fault (core dumped) $ apt --version apt 2.0.3 (amd64) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1877987 Title: apt search coredumping Status in apt package in Ubuntu: Fix Released Status in apt source package in Focal: Triaged Bug description: root@citoyx:/var/crash# apt search jdk Sorting... Done Segmentation fault (core dumped) May 11 12:34:25 citoyx kernel: [ 1354.337907] apt[10418]: segfault at 7f67292dcfc0 ip 7f6309ce4997 sp 7ffdab880930 error 4 in libapt-pkg.so.6.0.0[7f6309bb5000+147000] May 11 12:34:25 citoyx kernel: [ 1354.337916] Code: 48 8b 45 18 48 8b 04 d0 48 83 c4 08 5b 5d c3 0f 1f 40 00 f3 0f 1e fa 55 48 89 fd 53 48 89 f3 48 83 ec 08 48 8b 06 48 8b 4e 08 <8b> 10 48 8d 04 d5 00 00 00 00 48 29 d0 48 8b 51 60 48 8d 04 c2 0f root@citoyx:/var/crash# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" apt search is coredumping While apt install/upgrade/update is running fine crash file in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1877987/+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 1882034] Re: cannot start X session with NIS account
altough LightDM solve the login problem, it's not solution, becouse the NIS user can not shutdown/reboot the computer from the gnome session. so I switch back to gdm and try the nscd hint .. looks like this solve both problem for me! -- 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/1882034 Title: cannot start X session with NIS account Status in gdm3 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: When login with a NIS account, X does not start, or more precisely it starts and exits immediately. Only errors in logs is: (EE) systemd-logind: failed to get session: PID 4335 does not belong to any known session X11/gdm login works fine with local accounts. SSH/terminal console login with NIS accounts works fine. /etc/X11/Xwrapper.config: allowed_users=anybody I've seen several reports of such problems under other versions (eg 19.10), but no working solutions was found. It seems that the problem is the same with lightdm. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 08:59:25 2020 InstallationDate: Installed on 2019-11-26 (190 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1882034/+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 1882034] Re: cannot start X session with NIS account
same problem here. problem solved by switch to LightDM so I'm not sure that it is systemd fault -- 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/1882034 Title: cannot start X session with NIS account Status in systemd package in Ubuntu: Confirmed Bug description: When login with a NIS account, X does not start, or more precisely it starts and exits immediately. Only errors in logs is: (EE) systemd-logind: failed to get session: PID 4335 does not belong to any known session X11/gdm login works fine with local accounts. SSH/terminal console login with NIS accounts works fine. /etc/X11/Xwrapper.config: allowed_users=anybody I've seen several reports of such problems under other versions (eg 19.10), but no working solutions was found. It seems that the problem is the same with lightdm. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 4 08:59:25 2020 InstallationDate: Installed on 2019-11-26 (190 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2020-04-24 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1882034/+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 1885969] [NEW] package tzdata 2020a-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128
Public bug reported: I dont know what is it and how debug it. All screen is down. DOWN. I dont know how fix it. Problemm... ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tzdata 2020a-0ubuntu0.20.04 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 2 02:38:14 2020 DuplicateSignature: package:tzdata:2020a-0ubuntu0.20.04 Setting up tzdata (2020a-0ubuntu0.20.04) ... Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134. dpkg: error processing package tzdata (--configure): installed tzdata package post-installation script subprocess returned error exit status 128 ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-07-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tzdata Title: package tzdata 2020a-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1885969 Title: package tzdata 2020a-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128 Status in tzdata package in Ubuntu: New Bug description: I dont know what is it and how debug it. All screen is down. DOWN. I dont know how fix it. Problemm... ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tzdata 2020a-0ubuntu0.20.04 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jul 2 02:38:14 2020 DuplicateSignature: package:tzdata:2020a-0ubuntu0.20.04 Setting up tzdata (2020a-0ubuntu0.20.04) ... Use of uninitialized value $ret in string eq at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 134. dpkg: error processing package tzdata (--configure): installed tzdata package post-installation script subprocess returned error exit status 128 ErrorMessage: installed tzdata package post-installation script subprocess returned error exit status 128 InstallationDate: Installed on 2020-07-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tzdata Title: package tzdata 2020a-0ubuntu0.20.04 failed to install/upgrade: installed tzdata package post-installation script subprocess returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1885969/+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 1846709] [NEW] pcscd crashed with SIGSEGV in usb_claim_interface()
Public bug reported: iBank token and driver was used ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1846709 Title: pcscd crashed with SIGSEGV in usb_claim_interface() Status in pcsc-lite package in Ubuntu: New Bug description: iBank token and driver was used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1846709/+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 1773682] Re: Skype notification area icon corrupted
** Patch added: "statusicon-create-pixbuf-at-correct-size.patch" https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1773682/+attachment/5279534/+files/statusicon-create-pixbuf-at-correct-size.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1773682 Title: Skype notification area icon corrupted Status in Ubuntu MATE: Invalid Status in gtk+3.0 package in Ubuntu: New Status in gtk+3.0 package in Debian: Unknown Bug description: System Version: Ubuntu MATE 18.04 Package: mate-panel 1.20.1-3ubuntu1 How to reproduce: - log in with new user profile - install Skype from Software Boutique - launch Skype => icon in nofitication area is corrupted (see screenshot) This is already noticeable on default panel size, enlarging the panel makes it even more obvious with lots of duplicate Skype icons appearing. This bug does not appear on the GTK2-based Ubuntu MATE 16.04 running the exact same Skype version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1773682/+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 1773682] Re: Skype notification area icon corrupted
This is a bug in GtkStatusIcon, not in Skype. Here is the patch for gtk+3.0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910635#26 ** Bug watch added: Debian Bug tracker #910635 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910635 ** Also affects: gtk+3.0 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910635 Importance: Unknown Status: Unknown ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1773682 Title: Skype notification area icon corrupted Status in Ubuntu MATE: Invalid Status in gtk+3.0 package in Ubuntu: New Status in gtk+3.0 package in Debian: Unknown Bug description: System Version: Ubuntu MATE 18.04 Package: mate-panel 1.20.1-3ubuntu1 How to reproduce: - log in with new user profile - install Skype from Software Boutique - launch Skype => icon in nofitication area is corrupted (see screenshot) This is already noticeable on default panel size, enlarging the panel makes it even more obvious with lots of duplicate Skype icons appearing. This bug does not appear on the GTK2-based Ubuntu MATE 16.04 running the exact same Skype version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1773682/+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 1824804] Re: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages
How to get fix for Bionic? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1824804 Title: Unattended upgrades falls back to adjust all upgradable packages in attempt to install held packages Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: [Impact] * The fix for LP: #1821101 allowed installing packages for which APT's resolver could not find solution for without adjusting other packages, but also tries to adjust many packages to install packages which are held back. [Test Case] * Set up a system where systemd (or a package that can't be upgraded without also upgrading other packages) need to be upgraded to the version in -security. * Mark systemd on hold apt mark hold systemd * Observe u-u falling back to adjusting all upgradable packages in unfixed versions and adjusting only a few in fixed versions: # unattended-upgrade --verbose --debug ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to marking libnss-systemd, then adjusting changes package libnss-systemd upgradable but fails to be marked for upgrade (E:Unable to correct problems, you have held broken packages.) falling back to adjusting all packages adjusting candidate version: 2ping=4.1-1 ... Fixed: ... adjusting candidate version: libnss-systemd=237-3ubuntu10.19 falling back to adjusting libnss-systemd's dependencies recursively adjusting candidate version: libnss-systemd=237-3ubuntu10.19 adjusting candidate version: libkmod2=24-1ubuntu3 adjusting candidate version: mount=2.31.1-0.4ubuntu3 adjusting candidate version: libmount1=2.31.1-0.4ubuntu3 ... [Regression Potential] * The less extensive fallback may not find solutions for installing packages with special relationships that the full fallback could have found, but I don't know about such special cases in the archive and the autopkgtest cover a fair set of popular packages. Keeping back those packages seems to be better than spending a lot of CPU time on finding a few solutions - which still was not enough to find _all_ solutions. [Other Info] Originally reported at: https://bugs.launchpad.net/ubuntu/+source /unattended-upgrades/+bug/1396787/comments/21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1824804/+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 1396787] Re: checking trust of archives eats a lot of cpu
@rbalint I've collect logs from both u-u packages. Latest u-u stucks in a loop. Please see zip attached. I have hold packages $ apt-mark showhold linux-generic linux-headers-generic linux-image-generic linux-libc-dev papirus-icon-theme ** Attachment added: "uu.zip" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1396787/+attachment/5255891/+files/uu.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1396787 Title: checking trust of archives eats a lot of cpu Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] * Unattended-upgrades consumes tens of seconds or even minutes of CPU time to verify the origin of the packages * Using excessive amount of CPU is unpleasant for desktop/laptop users and also wastes computation time on servers/cloud instances. * Unattended-upgrades' algorithm for checking and adjusting package origins is redesigned to visit and adjust less packages. [Test Case] * The added upgrade-all-security autopkgtest measure the time u-u needs for upgrading security updates on the tested release starting with no security updates applied to the point where all security updates are applied but all packages are left upgradable from -updates. The test also measures the time needed for --dry-run to find no updates to be installed unattended. * Please run autopkgtests and look for the to time results: ... All upgrades installed 44.41user 3.06system 0:48.35elapsed 98%CPU (0avgtext+0avgdata 164872maxresident)k 208inputs+192376outputs (0major+642657minor)pagefaults 0swaps ... No packages found that can be upgraded unattended and no pending auto-removals 2.83user 0.11system 0:02.98elapsed 98%CPU (0avgtext+0avgdata 79308maxresident)k [Regression Potential] * Due to algorithm redesign there is a risk that packages from allowed origins are not upgraded. There were unit tests for testing the selection of the right packages to upgrade already, but a new autopkgtest is also introduce to verify u-u's behavior on current real-life security-updates. [Original bug text] (System: Ubuntu 14.04, up to date packages) I noticed that unattended-upgrades spends a significant amount of time in phases where it runs at 100% cpu. On a slower machine (core 2 t7200 2GHz) this goes on for minutes rather than seconds. This interferes with using the machine for other tasks. Using the --debug option to unattended-upgrades shows that the program outputs a lot of lines like the following during these 100% cpu phases: matching 'a'='trusty-updates' against ' From this output I guess the operation executed is not so complicated that it should require so much cpu power. ?? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Nov 26 21:53:57 2014 InstallationDate: Installed on 2014-08-28 (90 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1396787/+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 1396787] Re: checking trust of archives eats a lot of cpu
After update to 1.1ubuntu1.18.04.10 on Bionic "unattended-upgrades --download-only" using up 100% CPU and hangs. I tried to install previous version 1.1ubuntu1.18.04.9 and this issue is gone. ** Attachment added: "top-screenshot.png" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1396787/+attachment/5255628/+files/top-screenshot.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1396787 Title: checking trust of archives eats a lot of cpu Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] * Unattended-upgrades consumes tens of seconds or even minutes of CPU time to verify the origin of the packages * Using excessive amount of CPU is unpleasant for desktop/laptop users and also wastes computation time on servers/cloud instances. * Unattended-upgrades' algorithm for checking and adjusting package origins is redesigned to visit and adjust less packages. [Test Case] * The added upgrade-all-security autopkgtest measure the time u-u needs for upgrading security updates on the tested release starting with no security updates applied to the point where all security updates are applied but all packages are left upgradable from -updates. The test also measures the time needed for --dry-run to find no updates to be installed unattended. * Please run autopkgtests and look for the to time results: ... All upgrades installed 44.41user 3.06system 0:48.35elapsed 98%CPU (0avgtext+0avgdata 164872maxresident)k 208inputs+192376outputs (0major+642657minor)pagefaults 0swaps ... No packages found that can be upgraded unattended and no pending auto-removals 2.83user 0.11system 0:02.98elapsed 98%CPU (0avgtext+0avgdata 79308maxresident)k [Regression Potential] * Due to algorithm redesign there is a risk that packages from allowed origins are not upgraded. There were unit tests for testing the selection of the right packages to upgrade already, but a new autopkgtest is also introduce to verify u-u's behavior on current real-life security-updates. [Original bug text] (System: Ubuntu 14.04, up to date packages) I noticed that unattended-upgrades spends a significant amount of time in phases where it runs at 100% cpu. On a slower machine (core 2 t7200 2GHz) this goes on for minutes rather than seconds. This interferes with using the machine for other tasks. Using the --debug option to unattended-upgrades shows that the program outputs a lot of lines like the following during these 100% cpu phases: matching 'a'='trusty-updates' against ' From this output I guess the operation executed is not so complicated that it should require so much cpu power. ?? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Nov 26 21:53:57 2014 InstallationDate: Installed on 2014-08-28 (90 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1396787/+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 1821929] Re: Bluetooth mouse is not able to connect
** Attachment added: "HCI trace captured by btmon" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1821929/+attachment/5249821/+files/hcitrace.snoop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1821929 Title: Bluetooth mouse is not able to connect Status in bluez package in Ubuntu: New Bug description: I recently bought not expensive wireless mouse with bluetooth support: https://www.aliexpress.com/item/Wireless-Mouse-Bluetooth-Mouse-Silent-Computer-Mouse-PC-Mause-Wireless-Rechargeable-Ergonomic-Optical-USB-Mice-2/32879862474.html?spm=a2g0s.12269583.0.0.36ab310dUGrVZS I works in MacOS X and Windows but doesn't work in Linux. I suppose I can debug that mouse under Windows to collect more information if I have proper instructions. I collected some information about that mouse: # uname -a Linux asus-N752VX 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # lsb_release -a Distributor ID:Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename:bionic # lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 0bda:8763 Realtek Semiconductor Corp. (BT usb) Bus 001 Device 002: ID 0bda:57f6 Realtek Semiconductor Corp. (Web cam) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # usb-devices T: Bus=01 Lev=01 Prnt=01 Port=08 Cnt=04 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 2.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=8763 Rev=02.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb # bluetoothctl --version bluetoothctl: 5.48 # hciconfig -a hci0:Type: Primary Bus: USB BD Address: 94:E9:79:1A:89:1D ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN RX bytes:1604 acl:0 sco:0 events:170 errors:0 TX bytes:28036 acl:0 sco:0 commands:166 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'asus-N752VX' Class: 0x1c010c Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0xe3e LMP Version: 4.0 (0x6) Subversion: 0x4380 Manufacturer: Realtek Semiconductor Corporation (93) # bluetoothctl [NEW] Controller 94:E9:79:1A:89:1D asus-N752VX [default] [NEW] Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0 # show Controller 94:E9:79:1A:89:1D (public) Name: asus-N752VX Alias: asus-N752VX Class: 0x001c010c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0530 Discovering: no # devices Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0 # info 5A:4B:3C:0E:07:B2 Device 5A:4B:3C:0E:07:B2 (public) Name: Bluetooth Mouse 4.0 Alias: Bluetooth Mouse 4.0 Class: 0x2580 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb)
[Touch-packages] [Bug 1821929] [NEW] Bluetooth mouse is not able to connect
Public bug reported: I recently bought not expensive wireless mouse with bluetooth support: https://www.aliexpress.com/item/Wireless-Mouse-Bluetooth-Mouse-Silent-Computer-Mouse-PC-Mause-Wireless-Rechargeable-Ergonomic-Optical-USB-Mice-2/32879862474.html?spm=a2g0s.12269583.0.0.36ab310dUGrVZS I works in MacOS X and Windows but doesn't work in Linux. I suppose I can debug that mouse under Windows to collect more information if I have proper instructions. I collected some information about that mouse: # uname -a Linux asus-N752VX 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux # lsb_release -a Distributor ID:Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename:bionic # lsusb Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 0bda:8763 Realtek Semiconductor Corp. (BT usb) Bus 001 Device 002: ID 0bda:57f6 Realtek Semiconductor Corp. (Web cam) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # usb-devices T: Bus=01 Lev=01 Prnt=01 Port=08 Cnt=04 Dev#= 6 Spd=12 MxCh= 0 D: Ver= 2.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=8763 Rev=02.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=500mA I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb # bluetoothctl --version bluetoothctl: 5.48 # hciconfig -a hci0:Type: Primary Bus: USB BD Address: 94:E9:79:1A:89:1D ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN RX bytes:1604 acl:0 sco:0 events:170 errors:0 TX bytes:28036 acl:0 sco:0 commands:166 errors:0 Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Name: 'asus-N752VX' Class: 0x1c010c Service Classes: Rendering, Capturing, Object Transfer Device Class: Computer, Laptop HCI Version: 4.0 (0x6) Revision: 0xe3e LMP Version: 4.0 (0x6) Subversion: 0x4380 Manufacturer: Realtek Semiconductor Corporation (93) # bluetoothctl [NEW] Controller 94:E9:79:1A:89:1D asus-N752VX [default] [NEW] Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0 # show Controller 94:E9:79:1A:89:1D (public) Name: asus-N752VX Alias: asus-N752VX Class: 0x001c010c Powered: yes Discoverable: no Pairable: yes UUID: Headset AG(1112--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: Headset (1108--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0530 Discovering: no # devices Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0 # info 5A:4B:3C:0E:07:B2 Device 5A:4B:3C:0E:07:B2 (public) Name: Bluetooth Mouse 4.0 Alias: Bluetooth Mouse 4.0 Class: 0x2580 Icon: input-mouse Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) Modalias: usb:v0A5Cp0001d0129 # paired-devices Device 5A:4B:3C:0E:07:B2 Bluetooth Mouse 4.0 # trust 5A:4B:3C:0E:07:B2 Changing 5A:4B:3C:0E:07:B2 trust succeeded # connect 5A:4B:3C:0E:07:B2 Attempting to connect to 5A:4B:3C:0E:07:B2 Failed to connect: org.bluez.Error.Failed # rfkill list 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no /var/log/syslog: 16:34:35 asus-N752VX bluetoothd[1313]: src/device.c:connect_profiles() /org/bluez/hci0/dev_5A_4B_3C_0E_07_B2 (all), client :1.197 16:34:35 asus-N752VX bluetoothd[1313]:
[Touch-packages] [Bug 1802149] [NEW] redir to an empty variable
Public bug reported:
Redirection to an empty variable causes `dash` to exit abnormally via
SIGSEGV.
1) $ lsb_release -rd
Description:Ubuntu 16.04.5 LTS
Release:16.04
2) $ apt-cache policy dash
dash:
Installed: 0.5.8-2.1ubuntu2
Candidate: 0.5.8-2.1ubuntu2
Version table:
*** 0.5.8-2.1ubuntu2 500
500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
3) Script to reproduce:
$ cat test.sh
foobar() {
local a=$1
echo abc >&$a
}
foobar
4) Result:
$ dash ~/cloudlinux/kernelcare/test.sh
Segmentation fault (core dumped)
** Affects: dash (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dash in Ubuntu.
https://bugs.launchpad.net/bugs/1802149
Title:
redir to an empty variable
Status in dash package in Ubuntu:
New
Bug description:
Redirection to an empty variable causes `dash` to exit abnormally via
SIGSEGV.
1) $ lsb_release -rd
Description: Ubuntu 16.04.5 LTS
Release: 16.04
2) $ apt-cache policy dash
dash:
Installed: 0.5.8-2.1ubuntu2
Candidate: 0.5.8-2.1ubuntu2
Version table:
*** 0.5.8-2.1ubuntu2 500
500 http://ua.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
3) Script to reproduce:
$ cat test.sh
foobar() {
local a=$1
echo abc >&$a
}
foobar
4) Result:
$ dash ~/cloudlinux/kernelcare/test.sh
Segmentation fault (core dumped)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1802149/+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 1288182]
poppler version 0.45.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince: Unknown Status in Poppler: Unknown Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: "Кириллица"' Upd. Still actual for Ubuntu 16.04 x64 Evince 3.18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+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 1288182]
Guy, do you have any updates? I am experiencing the same issue with okular. Okular version 0.25.0 (KDE 4.14.24) I can assist with anything may help you to fix this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1288182 Title: Cyrillic not displayed in the input field Status in Evince: Unknown Status in Poppler: Unknown Status in evince package in Ubuntu: Triaged Status in poppler package in Ubuntu: Invalid Bug description: Ubuntu 14.04 x64 Evince 3.10.3 Cyrillic not displayed in the input field. In attach screenshot: input field with text 'This сyrillic: "Кириллица"' Upd. Still actual for Ubuntu 16.04 x64 Evince 3.18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1288182/+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 1062534]
Created attachment 130585 A hack to remove an optimization that is thread unsafe Originally posted here: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1062534 by Alessandro Pignotti -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1062534 Title: Thread unsafe access to internal linked list, breaks Origin games in Wine Status in xlibs: Unknown Status in libx11 package in Ubuntu: Triaged Bug description: In file src/xlibi18n/lcConv.c the following linked list head is defined static XlcConverterList conv_list = NULL; Which is then modified by _XlcSetConverter and get_converter in a non thread-safe manner. Inside get_converter the list is reorderder to increase the efficiency of looking up the same element the next time, but this is especially dangerous since a seemingly read-only method is actually modifying the data. Modifying the list in such thread unsafe manner does case the list to become garbled in some workloads and causes infinite loops when the get_converter is invoked. The solution I suggest is to add a mutex or spinlock around accesses to the linked list, I would it myself but I'm not sure about what is the usual mutex implementation for this project. To manage notifications about this bug go to: https://bugs.launchpad.net/xlibs/+bug/1062534/+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 1062534]
Appended two patches from Alessandro Pignotti originally posted on the Ubuntu Bugzilla. They may or may not still be valid. According to Alessandro's words, "They should be considered hacks to make the problem more clear." Trying to attract some attention to this bug because I face it on a regular basis playing Lord of the Rings Online on Wine still after 5 years a patch has been proposed. I'm a bit experienced in programming but only in Pascal and Python so I'm trying to find someone more experienced who could possibly fix it. If nobody responds, maybe I'll try to fix it myself… -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1062534 Title: Thread unsafe access to internal linked list, breaks Origin games in Wine Status in xlibs: Unknown Status in libx11 package in Ubuntu: Triaged Bug description: In file src/xlibi18n/lcConv.c the following linked list head is defined static XlcConverterList conv_list = NULL; Which is then modified by _XlcSetConverter and get_converter in a non thread-safe manner. Inside get_converter the list is reorderder to increase the efficiency of looking up the same element the next time, but this is especially dangerous since a seemingly read-only method is actually modifying the data. Modifying the list in such thread unsafe manner does case the list to become garbled in some workloads and causes infinite loops when the get_converter is invoked. The solution I suggest is to add a mutex or spinlock around accesses to the linked list, I would it myself but I'm not sure about what is the usual mutex implementation for this project. To manage notifications about this bug go to: https://bugs.launchpad.net/xlibs/+bug/1062534/+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 1062534]
Created attachment 130584 A hack to improve the thread safety of the libX11 localization Originally posted here: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1062534 by Alessandro Pignotti -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1062534 Title: Thread unsafe access to internal linked list, breaks Origin games in Wine Status in xlibs: Unknown Status in libx11 package in Ubuntu: Triaged Bug description: In file src/xlibi18n/lcConv.c the following linked list head is defined static XlcConverterList conv_list = NULL; Which is then modified by _XlcSetConverter and get_converter in a non thread-safe manner. Inside get_converter the list is reorderder to increase the efficiency of looking up the same element the next time, but this is especially dangerous since a seemingly read-only method is actually modifying the data. Modifying the list in such thread unsafe manner does case the list to become garbled in some workloads and causes infinite loops when the get_converter is invoked. The solution I suggest is to add a mutex or spinlock around accesses to the linked list, I would it myself but I'm not sure about what is the usual mutex implementation for this project. To manage notifications about this bug go to: https://bugs.launchpad.net/xlibs/+bug/1062534/+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 1777425] Re: Skype snap segfaults GNOME Shell on Wayland
This also happens for me every time I start skype from gnome wayland session. Please let me know if I can provide you some info that can help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1777425 Title: Skype snap segfaults GNOME Shell on Wayland Status in gnome-shell package in Ubuntu: Incomplete Status in wayland package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The Skype snap segfaults GNOME Shell on Wayland, crashing the session and sending the user back to the login screen. ``` $ snap info skype tracking: stable refresh-date: today at 11:31 BST installed: 8.22.0.2 (33) 143MB classic $ snap version snap2.33 snapd 2.33 series 16 ubuntu 18.04 kernel 4.15.0-23-generic $ snap info core tracking: beta refresh-date: 10 days ago, at 18:50 BST installed: 16-2.33(4830) 91MB core ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Mon Jun 18 12:15:54 2018 DistUpgraded: 2018-04-22 07:24:16,565 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3] InstallationDate: Installed on 2017-08-03 (318 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 2347GU8 MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=ce8cd4c6-3ada-4004-acbf-e169ca40b394 ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: Upgraded to bionic on 2018-04-22 (57 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO 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.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1777425/+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 1783445] Re: Gdebi-gtk does not work on ubuntu 18.04
*** This bug is a duplicate of bug 1734477 *** https://bugs.launchpad.net/bugs/1734477 ** This bug has been marked a duplicate of bug 1734477 LubuntuNext 17.10 - When not run from terminal, fails upon "Install" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1783445 Title: Gdebi-gtk does not work on ubuntu 18.04 Status in gdebi package in Ubuntu: New Bug description: The gdebi-gtk program does not work when used on the desktop. But being called by the terminal, it works normally. As in the ubuntu version 18.04 it does not have the gksu package, I tried adding the "admin: //" method in the "Exec =" field of the desktop entry. What did not work and the bug still remains! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1783445/+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 1783170] [NEW] package unattended-upgrades 1.1ubuntu1.18.04.4 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error
Public bug reported: 789 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-29.31-lowlatency 4.15.18 Uname: Linux 4.15.0-29-lowlatency x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sat Jul 21 18:28:51 2018 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 UpgradeStatus: Upgraded to bionic on 2018-05-13 (71 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-20T23:44:01.023912 ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1783170 Title: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to install/upgrade: installed unattended-upgrades package post- installation script subprocess returned error exit status 128 Status in unattended-upgrades package in Ubuntu: New Bug description: 789 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.4 ProcVersionSignature: Ubuntu 4.15.0-29.31-lowlatency 4.15.18 Uname: Linux 4.15.0-29-lowlatency x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sat Jul 21 18:28:51 2018 ErrorMessage: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.4 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 128 UpgradeStatus: Upgraded to bionic on 2018-05-13 (71 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-06-20T23:44:01.023912 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1783170/+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 1782101] Re: lightdm nonfunctional on active screen switch
** Summary changed: - gdm nonfunctional on active screen switch + lightdm nonfunctional on active screen switch -- 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/1782101 Title: lightdm nonfunctional on active screen switch Status in lightdm package in Ubuntu: New Bug description: I have double screen configuration (2 monitors). I face such issue: 1. I lock computer by pressing (Win+L) or it lock itself by timer 2. Mouse goes out of current monitor (password input field switches to second screen) 3. Upper buttons becomes nonfunctional such as language selection button, power indicator, volume control button, logging control button. It happens to both screens. 4. I cannot to unlock computer if language dosn't match language of password. The hard-reset is only option possible. I use Unity without switches to Gnome Shell. I tried to log gnome session (it's named Ubuntu) and I couldn't reproduce the issue. If lock computer I got completely different login page. There is no switch to the password input field if I move mouse pointer to the second screen. The password input field is fixed to the main screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.3 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jul 17 11:57:02 2018 InstallationDate: Installed on 2017-04-03 (469 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-05-03 (74 days ago) mtime.conffile..etc.gdm3.custom.conf: 2017-10-23T17:14:02.815788 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1782101/+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 1775723] [NEW] Resolved resolution delay when interacting with dnsmasq
Public bug reported: After hitting a problem with lxd on a server install (see https://github.com/lxc/lxd/issues/4631) I was adviced by Stéphane Graber to report a bug here. The gist of the bug is the following: - lxd snap uses internally dnsmasq - the 18.04 server install defaults to using systemd-resolved - upon (re)boot, the lxd stap fails to start because of systemd-resolved not resolving shortly after boot. To keep this bug report short, please kindly refer to https://github.com/lxc/lxd/issues/4631 for a complete set of logs and a "how to replicate" guide. Thanks for looking into this, cheers, Pavel ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: dnsmasq lxd systemd-resolved -- 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/1775723 Title: Resolved resolution delay when interacting with dnsmasq Status in systemd package in Ubuntu: New Bug description: After hitting a problem with lxd on a server install (see https://github.com/lxc/lxd/issues/4631) I was adviced by Stéphane Graber to report a bug here. The gist of the bug is the following: - lxd snap uses internally dnsmasq - the 18.04 server install defaults to using systemd-resolved - upon (re)boot, the lxd stap fails to start because of systemd-resolved not resolving shortly after boot. To keep this bug report short, please kindly refer to https://github.com/lxc/lxd/issues/4631 for a complete set of logs and a "how to replicate" guide. Thanks for looking into this, cheers, Pavel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1775723/+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 1773710] [NEW] package libxml2-utils 2.9.4+dfsg1-6.1ubuntu1 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить
Private bug reported: / ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libxml2-utils 2.9.4+dfsg1-6.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon May 28 01:09:15 2018 ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его следует переустановить InstallationDate: Installed on 2018-05-20 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Нет такого файла или каталога: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: libxml2 Title: package libxml2-utils 2.9.4+dfsg1-6.1ubuntu1 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libxml2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1773710 Title: package libxml2-utils 2.9.4+dfsg1-6.1ubuntu1 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить Status in libxml2 package in Ubuntu: New Bug description: / ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libxml2-utils 2.9.4+dfsg1-6.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Mon May 28 01:09:15 2018 ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его следует переустановить InstallationDate: Installed on 2018-05-20 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Нет такого файла или каталога: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: libxml2 Title: package libxml2-utils 2.9.4+dfsg1-6.1ubuntu1 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1773710/+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 1740666] Re: systemd-timesyncd doesn't sync time after resume from hibernate
#1744988 bug not resolved this for me. -- 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/1740666 Title: systemd-timesyncd doesn't sync time after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced: $ timedatectl status Local time: Вс 2017-12-31 13:46:16 +05 Universal time: Вс 2017-12-31 08:46:16 UTC RTC time: Вс 2017-12-31 08:46:16 Time zone: Asia/Yekaterinburg (+05, +0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no I've tried waiting a bit, but this persisted for some minutes, so I forced an update with systemctl restart systemd-timesyncd.service And afterwards the time was (apparently) correctly synced. Please, let me know what further informations are needed to debug the issue, and I would be happy to do some other test. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 31 13:41:51 2017 InstallationDate: Installed on 2017-06-05 (208 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740666/+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 1579580] Re: ureadahead reports relative path errors in journalctl output
These messages were produced on my system after upgrading Lubuntu 17.10 to 18.04 beta. One wants to hunt issues in syslog after upgrade, but one has to fight with these obtrusive messages. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+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 175316] Re: no IDN in nslookup and host
But Bionic are not released yet: https://wiki.ubuntu.com/Releases And Artful are not LTS release type. Effectively meaning Xenial are latest LTS release up-to-date and still supported until April 2021. Does by any chance this can be fixed in currently active LTS release, i.e. Xenial? I don't think that would require a lot of efforts to re-compile packages with IDN support and push the update. Why this can't be done with Xenial? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/175316 Title: no IDN in nslookup and host Status in BIND: New Status in bind9 package in Ubuntu: Confirmed Status in iputils package in Ubuntu: Fix Released Status in bind9 package in Debian: New Bug description: Binary package hint: bind9 Neither nslookup or host supports IDN. If you try , for example, to get the IP for "registrera-domän.se" it fails every time. As the use of IDN is increasing I think it would be a good thing if these tools supported this. To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/175316/+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 175316] Re: no IDN in nslookup and host
Why it is "fix released" while it's still affects Xenial? Xenial are LTS and supported until 04-2021 and it should be fixed in Xenial. Every other major distro has support for IDN for years. But for some reason Ubuntu maintainers are ignoring this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/175316 Title: no IDN in nslookup and host Status in BIND: New Status in bind9 package in Ubuntu: Confirmed Status in iputils package in Ubuntu: Fix Released Status in bind9 package in Debian: New Bug description: Binary package hint: bind9 Neither nslookup or host supports IDN. If you try , for example, to get the IP for "registrera-domän.se" it fails every time. As the use of IDN is increasing I think it would be a good thing if these tools supported this. To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/175316/+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 1758725] [NEW] network-manager applet up/down arrows when connected to wifi only
Public bug reported: I have an issue with the network-manager applet that shows up and down arrows (wired connection?) when connected to wifi only. I still have internet connectivity, but unable to choose a wifi network. The computer: Toshiba Satellite L55W-C5320. The OS: Ubuntu 16.04.4. Thank you, Pavel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 25 11:27:15 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-25 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.23 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH shrek4 1 a8c323eb-6312-4287-924a-ce4567222530 802-11-wireless 1522002319 Sun 25 Mar 2018 11:25:19 AM PDT yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/0 shrek4 1a8c323eb-6312-4287-924a-ce4567222530 /org/freedesktop/NetworkManager/ActiveConnection/2 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1758725 Title: network-manager applet up/down arrows when connected to wifi only Status in network-manager package in Ubuntu: New Bug description: I have an issue with the network-manager applet that shows up and down arrows (wired connection?) when connected to wifi only. I still have internet connectivity, but unable to choose a wifi network. The computer: Toshiba Satellite L55W-C5320. The OS: Ubuntu 16.04.4. Thank you, Pavel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 25 11:27:15 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-25 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.23 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH shrek4 1 a8c323eb-6312-4287-924a-ce4567222530 802-11-wireless 1522002319 Sun 25 Mar 2018 11:25:19 AM PDT yes 0 no /org/freedesktop/NetworkMan
[Touch-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
This happens my Mint too. Bluetooth keyboard is working after resume from suspend but mouse (Logitech M720 Triatlon) is not. bluetoothctl says Connected: yes .. no .. yes .. no But bluetoothctl: agent off/on helps (no need to use power and pair commands). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1246981 Title: Bluetooth mouse fails to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+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 1743018] Re: Unable to install mesa-opencl-icd because of unmet dependencies on Xenial
Hello, Timo. I can confirm that mesa-opencl-icd from xenial-proposed installs without problems. mesa-opencl-icd/xenial-proposed,now 17.2.4-0ubuntu1~16.04.4 amd64 [installed] free implementation of the OpenCL API -- ICD runtime ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1743018 Title: Unable to install mesa-opencl-icd because of unmet dependencies on Xenial Status in mesa package in Ubuntu: Invalid Status in mesa source package in Xenial: Fix Committed Bug description: Steps to reproduce: 1. Install Ubuntu 16.04 LTS 2. Try to install `mesa-opencl-icd` with $ sudo apt-get install mesa-opencl-icd [sudo] password for user: Reading package lists... Done Building dependency tree Reading state information... Done Expected results: * mesa-opencl-icd is installed successfully Actual results: * got errors as follow 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: mesa-opencl-icd : Depends: libclc-r600 (>= 0.2.0+git20170330-3) but it is not going to be installed Depends: libclc-amdgcn (>= 0.2.0+git20170330-3) but it is not going to be installed E: Unable to correct problems, you have held broken packages. Note: inspired by this AskUbuntu question - https://askubuntu.com/q/995274/66509 . ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mesa-opencl-icd (not installed) ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98 Uname: Linux 4.4.0-109-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,mousepoll,move,gnomecompat,wall,regex,place,resize,snap,session,imgpng,vpswitch,grid,unitymtgrabhandles,animation,expo,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: MATE Date: Fri Jan 12 21:22:22 2018 DistUpgraded: 2017-04-16 02:19:02,541 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:2135] InstallationDate: Installed on 2014-02-07 (1434 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) MachineType: ASUSTeK COMPUTER INC. UX32A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic root=UUID=1e3c78e2-1a6e-4afe-8249-40fe7fa81a86 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to xenial on 2017-04-15 (271 days ago) dmi.bios.date: 02/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX32A.216 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX32A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX32A.216:bd02/12/2014:svnASUSTeKCOMPUTERINC.:pnUX32A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX32A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX32A dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 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.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Jan 12 20:32:41 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.7 xserver.video_driver: intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1743018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1740666] Re: systemd-timesyncd doesn't sync time after resume from hibernate
journalctl output after resume: https://paste.ubuntu.com/26337345/ -- 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/1740666 Title: systemd-timesyncd doesn't sync time after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced: $ timedatectl status Local time: Вс 2017-12-31 13:46:16 +05 Universal time: Вс 2017-12-31 08:46:16 UTC RTC time: Вс 2017-12-31 08:46:16 Time zone: Asia/Yekaterinburg (+05, +0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no I've tried waiting a bit, but this persisted for some minutes, so I forced an update with systemctl restart systemd-timesyncd.service And afterwards the time was (apparently) correctly synced. Please, let me know what further informations are needed to debug the issue, and I would be happy to do some other test. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 31 13:41:51 2017 InstallationDate: Installed on 2017-06-05 (208 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740666/+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 1740666] Re: systemd-timesyncd doesn't sync time after resume from hibernate
I can read hw clock: $ sudo hwclock --show 2018-01-02 13:54:07.249593+0500 -- 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/1740666 Title: systemd-timesyncd doesn't sync time after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced: $ timedatectl status Local time: Вс 2017-12-31 13:46:16 +05 Universal time: Вс 2017-12-31 08:46:16 UTC RTC time: Вс 2017-12-31 08:46:16 Time zone: Asia/Yekaterinburg (+05, +0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no I've tried waiting a bit, but this persisted for some minutes, so I forced an update with systemctl restart systemd-timesyncd.service And afterwards the time was (apparently) correctly synced. Please, let me know what further informations are needed to debug the issue, and I would be happy to do some other test. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 31 13:41:51 2017 InstallationDate: Installed on 2017-06-05 (208 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740666/+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 1740665] Re: systemd-timesyncd doesn't sync time after resume from hibernate
** This bug is no longer a duplicate of bug 1740666 systemd-timesyncd doesn't sync time after resume from hibernate ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1740665 Title: systemd-timesyncd doesn't sync time after resume from hibernate Status in systemd package in Ubuntu: Invalid Bug description: When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced: $ timedatectl status Local time: Вс 2017-12-31 13:46:16 +05 Universal time: Вс 2017-12-31 08:46:16 UTC RTC time: Вс 2017-12-31 08:46:16 Time zone: Asia/Yekaterinburg (+05, +0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no I've tried waiting a bit, but this persisted for some minutes, so I forced an update with systemctl restart systemd-timesyncd.service And afterwards the time was (apparently) correctly synced. Please, let me know what further informations are needed to debug the issue, and I would be happy to do some other test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1740665/+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 1740665] [NEW] systemd-timesyncd doesn't sync time after resume from hibernate
*** This bug is a duplicate of bug 1740666 *** https://bugs.launchpad.net/bugs/1740666 Public bug reported: When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced: $ timedatectl status Local time: Вс 2017-12-31 13:46:16 +05 Universal time: Вс 2017-12-31 08:46:16 UTC RTC time: Вс 2017-12-31 08:46:16 Time zone: Asia/Yekaterinburg (+05, +0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no I've tried waiting a bit, but this persisted for some minutes, so I forced an update with systemctl restart systemd-timesyncd.service And afterwards the time was (apparently) correctly synced. Please, let me know what further informations are needed to debug the issue, and I would be happy to do some other test. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1740666 systemd-timesyncd doesn't sync time after resume from hibernate -- 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/1740665 Title: systemd-timesyncd doesn't sync time after resume from hibernate Status in systemd package in Ubuntu: New Bug description: When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced: $ timedatectl status Local time: Вс 2017-12-31 13:46:16 +05 Universal time: Вс 2017-12-31 08:46:16 UTC RTC time: Вс 2017-12-31 08:46:16 Time zone: Asia/Yekaterinburg (+05, +0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no I've tried waiting a bit, but this persisted for some minutes, so I forced an update with systemctl restart systemd-timesyncd.service And afterwards the time was (apparently) correctly synced. Please, let me know what further informations are needed to debug the issue, and I would be happy to do some other test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1740665/+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 1740666] [NEW] systemd-timesyncd doesn't sync time after resume from hibernate
Public bug reported: When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced: $ timedatectl status Local time: Вс 2017-12-31 13:46:16 +05 Universal time: Вс 2017-12-31 08:46:16 UTC RTC time: Вс 2017-12-31 08:46:16 Time zone: Asia/Yekaterinburg (+05, +0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no I've tried waiting a bit, but this persisted for some minutes, so I forced an update with systemctl restart systemd-timesyncd.service And afterwards the time was (apparently) correctly synced. Please, let me know what further informations are needed to debug the issue, and I would be happy to do some other test. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 31 13:41:51 2017 InstallationDate: Installed on 2017-06-05 (208 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1740666 Title: systemd-timesyncd doesn't sync time after resume from hibernate Status in systemd package in Ubuntu: New Bug description: When resuming, the clock remains at the time when the hibernate happened, even if timedatectl claims that it is being synced: $ timedatectl status Local time: Вс 2017-12-31 13:46:16 +05 Universal time: Вс 2017-12-31 08:46:16 UTC RTC time: Вс 2017-12-31 08:46:16 Time zone: Asia/Yekaterinburg (+05, +0500) Network time on: yes NTP synchronized: yes RTC in local TZ: no I've tried waiting a bit, but this persisted for some minutes, so I forced an update with systemctl restart systemd-timesyncd.service And afterwards the time was (apparently) correctly synced. Please, let me know what further informations are needed to debug the issue, and I would be happy to do some other test. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.1 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 31 13:41:51 2017 InstallationDate: Installed on 2017-06-05 (208 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Gigabyte Technology Co., Ltd. P35-DS3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=1bda199b-5177-4ed2-babe-46c9ab503918 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 zswap.max_pool_percent=33 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-12-16 (14 days ago) dmi.bios.date: 06/18/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F14 dmi.board.name: P35-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF14:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P35-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1740666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1734858] [NEW] Xorg crash - Xwayland
Public bug reported: I am using two monitors for work. And when I moved aplication rhythmbox from first to second monitor, the screen session was logout and I have to login again. After it I found following error by dmesg >> dmesg [ 2753.218761] BUG: unable to handle kernel paging request at 09fffb9d8290 [ 2753.218811] IP: __radix_tree_lookup+0x0/0x130 [ 2753.218826] PGD 0 [ 2753.218827] P4D 0 [ 2753.218852] Oops: [#1] SMP [ 2753.218865] Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle xfrm_user xfrm_algo xt_addrtype ipt_MASQUERADE br_netfilter nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp aufs llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter binfmt_misc uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel snd_hda_codec_hdmi snd_hda_codec_conexant arc4 snd_hda_codec_generic aes_x86_64 crypto_simd glue_helper cryptd intel_cstate snd_hda_intel joydev snd_hda_codec input_leds iwldvm snd_hda_core [ 2753.219080] serio_raw snd_hwdep mac80211 snd_seq_midi snd_seq_midi_event snd_rawmidi iwlwifi snd_seq wmi_bmof snd_pcm intel_ips cfg80211 thinkpad_acpi nvram mei_me lpc_ich mei shpchp snd_seq_device snd_timer snd soundcore mac_hid nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre nf_nat nf_conntrack libcrc32c parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_generic usbhid hid i915 i2c_algo_bit mxm_wmi drm_kms_helper firewire_ohci psmouse syscopyarea sysfillrect firewire_core sysimgblt ahci fb_sys_fops libahci e1000e drm sdhci_pci sdhci crc_itu_t ptp pps_core video wmi [ 2753.219250] CPU: 3 PID: 9728 Comm: Web Content Tainted: G OE 4.13.0-17-generic #20-Ubuntu [ 2753.219277] Hardware name: LENOVO 4384BR2/4384BR2, BIOS 6MET81WW (1.41 ) 10/26/2010 [ 2753.219300] task: 8fc0a893ac00 task.stack: a27dc2e1 [ 2753.219320] RIP: 0010:__radix_tree_lookup+0x0/0x130 [ 2753.219336] RSP: :a27dc2e13cd8 EFLAGS: 00010246 [ 2753.219353] RAX: RBX: 09fffb9d8288 RCX: a27dc2e13ce0 [ 2753.219375] RDX: RSI: 0003fffe3f010f91 RDI: 09fffb9d8288 [ 2753.219397] RBP: a27dc2e13cf0 R08: 8fc04cd94000 R09: 7f95eec25010 [ 2753.219418] R10: 0083 R11: 7f95eec84290 R12: 0003fffe3f010f91 [ 2753.219440] R13: 09fffb9d8280 R14: 0003fffe3f010f91 R15: 8fc04cd94000 [ 2753.219463] FS: 7f9626bed1c0() GS:8fc0bbd8() knlGS: [ 2753.219487] CS: 0010 DS: ES: CR0: 80050033 [ 2753.219505] CR2: 09fffb9d8290 CR3: 0001b618c000 CR4: 06e0 [ 2753.219527] Call Trace: [ 2753.219539] ? radix_tree_lookup_slot+0x22/0x50 [ 2753.219559] find_get_entry+0x1e/0xd0 [ 2753.219573] pagecache_get_page+0x2c/0x210 [ 2753.219590] lookup_swap_cache+0x43/0x90 [ 2753.219605] do_swap_page+0x95/0x700 [ 2753.219618] ? do_wp_page+0x157/0x500 [ 2753.219632] __handle_mm_fault+0x70c/0x1020 [ 2753.219647] handle_mm_fault+0xb1/0x200 [ 2753.219663] __do_page_fault+0x24d/0x4d0 [ 2753.219677] do_page_fault+0x22/0x30 [ 2753.219693] page_fault+0x28/0x30 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 28 11:04:19 2017 DistUpgraded: 2017-10-03 22:32:45,006 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu DkmsStatus: virtualbox, 5.1.30, 4.13.0-16-generic, x86_64: installed virtualbox, 5.1.30, 4.13.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2015-11-01 (757 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. MachineType: LENOVO 4384BR2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine:
[Touch-packages] [Bug 1702347] Re: Graphical glitches in screen by default
... the problem persists, however, I have OK picture on the screen, no glitches, etc. There is just the reported annoying warning in dmesg output. -- 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/1702347 Title: Graphical glitches in screen by default Status in xorg package in Ubuntu: New Bug description: Ubuntu 17.10 development branch updated and dist-upgraded on 4 july 2017 Im having weird glitches in screen when scrolling or switching windows by default Graphics: Card: NVIDIA C77 [GeForce 9100M G] Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: modesetting,fbdev,vesa) Resolution: 1440x900@60.00hz GLX Renderer: Gallium 0.4 on NVAA GLX Version: 3.0 Mesa 17.1.2 installing nvidia-340 resulted in a black screen after login, so i had to purge nvidia* to get back to desktop. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Tue Jul 4 20:59:21 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-26-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation C77 [GeForce 9100M G] [10de:0844] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] C77 [GeForce 9100M G] [1025:014d] InstallationDate: Installed on 2017-06-13 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612) MachineType: Acer, inc. Aspire 7530 ProcEnviron: LANGUAGE=nl_BE:nl TERM=xterm-256color PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=e65dc3e3-3694-4b7c-b7c8-7e9cfe3cbd5a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3342 dmi.board.name: EI Capitan dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3342:bd10/01/2008:svnAcer,inc.:pnAspire7530:pvrNotApplicable:rvnAcer,Inc.:rnEICapitan:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 7530 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jul 4 20:45:53 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) event6 - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump detected and discarded. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702347/+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 1702347] Re: Graphical glitches in screen by default
Ubuntu 17.10, daily build 5 July 2017 System:Host: artberg Kernel: 4.10.0-26-generic x86_64 (64 bit) Desktop: Gnome 3.24.2 Distro: Ubuntu Artful Aardvark (development branch) Graphics: Card: NVIDIA GK107 [GeForce GT 640] Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: modesetting,fbdev,vesa) Resolution: 2560x1440@59.95hz GLX Renderer: Gallium 0.4 on NVE7 GLX Version: 3.0 Mesa 17.1.2 dmesg output follows: nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084 failed with error -2 nouveau :01:00.0: Direct firmware load for nouveau/nve7_fuc084d failed with error -2 nouveau :01:00.0: msvld: unable to load firmware data nouveau :01:00.0: msvld: init failed, -19 FYI: I have found in synaptic, that the package "nouveau-firmware" was not installed by default. I have installed the package and will restart... -- 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/1702347 Title: Graphical glitches in screen by default Status in xorg package in Ubuntu: New Bug description: Ubuntu 17.10 development branch updated and dist-upgraded on 4 july 2017 Im having weird glitches in screen when scrolling or switching windows by default Graphics: Card: NVIDIA C77 [GeForce 9100M G] Display Server: X.Org 1.19.3 drivers: nouveau (unloaded: modesetting,fbdev,vesa) Resolution: 1440x900@60.00hz GLX Renderer: Gallium 0.4 on NVAA GLX Version: 3.0 Mesa 17.1.2 installing nvidia-340 resulted in a black screen after login, so i had to purge nvidia* to get back to desktop. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CompositorRunning: None Date: Tue Jul 4 20:59:21 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.10.0-26-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation C77 [GeForce 9100M G] [10de:0844] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] C77 [GeForce 9100M G] [1025:014d] InstallationDate: Installed on 2017-06-13 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170612) MachineType: Acer, inc. Aspire 7530 ProcEnviron: LANGUAGE=nl_BE:nl TERM=xterm-256color PATH=(custom, no user) LANG=nl_BE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=UUID=e65dc3e3-3694-4b7c-b7c8-7e9cfe3cbd5a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/01/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3342 dmi.board.name: EI Capitan dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3342:bd10/01/2008:svnAcer,inc.:pnAspire7530:pvrNotApplicable:rvnAcer,Inc.:rnEICapitan:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 7530 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.2-2ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.2-2ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jul 4 20:45:53 2017 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) event6 - (EE) SynPS/2 Synaptics TouchPad: (EE) kernel bug: Touch jump detected and discarded. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1702347/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
I can confirm, after update to 17.04 I don't have this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Incomplete Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. 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 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader 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 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome
I got Ubuntu 16.04 and same problem, but I do not use 2 step verification, still got same problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1687019 Title: Cannot add a Google account using Online Accounts in Ubuntu Gnome Status in gnome-online-accounts package in Ubuntu: Confirmed Status in gnome-online-accounts package in Arch Linux: New Bug description: With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I cannot add a Google account using Online-Accounts. If I choose to add a new Google account in Online Accounts, a window appears where I can enter my Google email. After entering my email and pressing the Next button, a window appears where I can enter my Google password. After entering the password and pressing the Next button, an empty window appears and nothing else happens. I expected this to show something useful, and actually add the Google account to my Gnome environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1687019/+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 1173915] Re: initctl continuously takes 100% of CPU
I was bitten by this on 16.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1173915 Title: initctl continuously takes 100% of CPU Status in upstart : Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: Many programs are fairly slow to start on my computer, despite it being relatively new (core i5). Suspecting a heavy CPU usage, I started gnome-system-monitor: all processes were displayed at 0% CPU, but the overall load was 1.33; 1.33; 1.34. Using the "top" command, however, revealed the real CPU use, with the "initctl" process taking 100%CPU, even 1 hour after startup. I upgraded to roaring ringtail before checking this but the symptoms were the same with quantal quetzal, so there is a fair chance the causes were identical. Regards ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: upstart 1.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CheckboxSubmission: 2deefc5fd2f1f0ae2fdd4bd781248a2a CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b Date: Sun Apr 28 13:04:05 2013 ExecutablePath: /sbin/initctl InstallationDate: Installed on 2012-12-15 (133 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True ProcEnviron: ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=fa624f8f-d9d0-4b09-af8b-88b106aaaf5b ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: Upgraded to raring on 2013-04-28 (0 days ago) UpstartBugCategory: System To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1173915/+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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space
** Also affects: update-manager Importance: Undecided Status: New -- 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/798414 Title: update-initramfs should produce a more helpful error when there isn't enough free space Status in initramfs-tools: Confirmed Status in Software Updater: New Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: In Progress Bug description: Binary package hint: initramfs-tools When generating a new initramfs there is no check for available free space, subsequently its possible for update-initramfs to fail due to a lack of free space. This is resulting in package installation failures for initramfs-tools. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 WORKAROUND: Remove unused kernels using computer janitor (not in repositories for 14.04 or later) or manually free space on your partition containing the /boot file system. See instructions here https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 1660447] [NEW] package slapd 2.4.42+dfsg-2ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Public bug reported: An error has occurred in the transition from version 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: slapd 2.4.42+dfsg-2ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Jan 30 23:43:39 2017 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2014-05-09 (997 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: openldap Title: package slapd 2.4.42+dfsg-2ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: Upgraded to xenial on 2017-01-30 (0 days ago) ** Affects: openldap (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 openldap in Ubuntu. https://bugs.launchpad.net/bugs/1660447 Title: package slapd 2.4.42+dfsg-2ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 Status in openldap package in Ubuntu: New Bug description: An error has occurred in the transition from version 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: slapd 2.4.42+dfsg-2ubuntu3.1 ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35 Uname: Linux 3.13.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Jan 30 23:43:39 2017 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2014-05-09 (997 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: openldap Title: package slapd 2.4.42+dfsg-2ubuntu3.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: Upgraded to xenial on 2017-01-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1660447/+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 219057] Re: Bluetooth does not coexist with WiFi
Hi everyone, I had the same wifi/bluetooth interference problem. My setup is as follows: - Ubuntu 14.04 with custom-built vanilla kernel 4.3.0 - Lenovo B50 laptop having QCA9565 / AR9565 Wireless Network Adapter (ath9k) onboard - Linksys WRT-54GL router running DD-WRT v24-sp2 (10/10/09) mini - Marshall Acton bluetooth speaker Initially when I was streaming audio to the speaker, wifi degraded dramatically. After doing some research, I have successfully resolved the issue. What I have done is: * On my laptop: - added ``` Enable=Source Disable=Socket AutoConnect=True ``` to /etc/bluetooth/audio.conf - Added ``` options iwlwifi 11n_disable=1 bt_coex_active=1 ``` to /etc/modprobe.d/iwlwifi.conf However, since I'm not using iwlwifi, I'm not sure whether this had had any effect whatsoever. * On my router: - Under Wireless / Advanced Settings, I set "Bluetooth Coexistence Mode" to "Preemption" Then I've rebooted everything just in case. FYI, I encourage you to read through https://wireless.wiki.kernel.org/en/users/documentation/bluetooth- coexistence to find out what bluetooth coexistence is, and I wonder why everybody keeps switching it off (by setting bt_coex_active=0). On the contrary, this technique is designed to defeat interference problem. Also, you may find nice to add "load-module module-switch-on-connect" to /etc/pulse/default.pa so that audio starts streaming to bluetooth speaker automatically when it connects (and then back to laptop speakers when it disconnects.) Cheers, PD. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/219057 Title: Bluetooth does not coexist with WiFi Status in bluez package in Ubuntu: Confirmed Bug description: On my system bluetooth and wifi are unusable together. I have a built- in CSR-based bluetooth module in my laptop, and an Atheros wifi. Wifi transfers slow to a halt whenever there is BT traffic. For example, if I play a music file from another machine through the network using a BT headset, only the first few seconds of the file will play until the player runs out of buffered data. No further data is downloaded. Web pages also do not download, and I even lose connection to AP from time to time. At the same time, it looks like AFH is trying to work. If I monitor the value returned by 'hcitool afh', it changes. But this seems to have little effect on connection quality. Is this a problem with my hardware, or the AFH implementation? Is there a way to force bluetooth to not use the channels in use by WiFi? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/219057/+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 346386] Re: [MASTER] Update fails with invalid package files with "Encountered a section with no Package: header"
** Changed in: apt (Ubuntu) Assignee: (unassigned) => Pavel muhlheim (procomp26) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/346386 Title: [MASTER] Update fails with invalid package files with "Encountered a section with no Package: header" Status in apt package in Ubuntu: Fix Released Status in apt source package in Natty: Fix Released Status in apt source package in Precise: Fix Released Status in apt package in Debian: Fix Released Bug description: Binary package hint: adept-updater Pertinent data printed when attempting to run Updater as follows: An unresolvable problem occurred while initializing the package information. Please report this bug against the 'update-manager' package and include the following error message: 'E:Encountered a section with no Package: header, E:Problem with MergeList /var/lib/apt/lists/us.archive.ubuntu .com_ubuntu_dists_intrepid_universe_binary-amd64_Packages, E:The package lists or status file could not be parsed or opened.' WORKAROUND: Remove problematic files from /var/lib/apt/lists/ and rerun apt-get update. In the event that one is connected to a network with a proxy server that returns html pages (like a web page requesting you to login) and not package list files. Those html files will get downloaded to /var/lib/apt/lists/ and prevent someone from using a package manager until the problem html pages are removed. TEST CASE: 1) download the dummy-proxy attachment from this bug report 2) run dummy-proxy (python dummy-proxy) on a precise system (this simulates a proxy that is not allowing access to archive.ubuntu.com and gives you garbage html instead) 2.5) Execute 'sudo -i' in a terminal 3) Execute 'http_proxy=http://localhost:8080 apt-get update' in same terminal 4) Observe the following error messages in your terminal: W: GPG error: http://archive.ubuntu.com precise InRelease: File /var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_precise_InRelease doesn't start with a clearsigned message W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/precise/multiverse/i18n/Index No Hash entry in Release file /var/lib/apt/lists/partial/ archive.ubuntu.com_ubuntu_dists_precise_multiverse_i18n_Index W: Failed to fetch gzip:/var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_precise_multiverse_source_Sources Encountered a section with noPackage: header 5) Stop dummy-proxy 6) Execute 'sudo apt-get update' in a terminal 7) Observe the following error message: Reading package lists... Done W: GPG error: http://archive.ubuntu.com precise Release: The following signatures were invalid: BADSIG 40976EAF437D05B5 Ubuntu Archive Automatic Signing Key <ftpmas...@ubuntu.com> 8) Remove the problematic files in /var/lib/apt/lists (sudo rm /var/lib/apt/lists/*) Install apt from -proposed 1) run dummy-proxy (python dummy-proxy) on a precise system (this simulates a proxy that is not allowing access to archive.ubuntu.com and gives you garbarge html instead) 1.5) Execute 'sudo -i' in a terminal 2) Execute 'http_proxy=http://localhost:8080 apt-get update' in same terminal 3) Observe the following error messages in your terminal: W: A error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http:// archive.ubuntu.com precise Release: The following signatures were invalid: NODATA 1 NODATA 2 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/precise/Release W: Some index files failed to download. They have been ignored, or old ones used instead. 4) Stop dummy-proxy 5) Execute 'sudo apt-get update' in a terminal 6) Observe the update succeed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/346386/+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 434601] Re: Package descriptions etc display only in the language of whoever installed the OS
** Changed in: ubuntu-translations Assignee: (unassigned) => Pavel muhlheim (procomp26) ** Changed in: software-center (Ubuntu) Assignee: (unassigned) => Pavel muhlheim (procomp26) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/434601 Title: Package descriptions etc display only in the language of whoever installed the OS Status in Ubuntu Translations: Confirmed Status in apt package in Ubuntu: Confirmed Status in software-center package in Ubuntu: Confirmed Bug description: Binary package hint: software-store if the cache was geneated with a english locale and then is used by a user with german locale, the cache will be english only. this needs to be fixed by storting a language attribute in the cache and forcing a re-generation (or a generation of a new one) if they don't match. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/434601/+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 1648699] [NEW] package procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: The system works otherwise well. ProblemType: Package DistroRelease: elementary 0.4 Package: procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Thu Dec 8 22:53:09 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-11-27 (11 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: procps Title: package procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package loki third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1648699 Title: package procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in procps package in Ubuntu: New Bug description: The system works otherwise well. ProblemType: Package DistroRelease: elementary 0.4 Package: procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Thu Dec 8 22:53:09 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-11-27 (11 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: procps Title: package procps 2:3.3.10-4ubuntu2.3 [origin: Ubuntu] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1648699/+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 175316] Re: no IDN in nslookup and host
This should be changed to support for IDN in bind9 packages and iputils packages, especially dnsutils and iputils-ping packages. The IDN support nowadays are mandatory. Almost every major GNU/Linux distro currently supports IDN in ping/dig/nslookup/etc from the box. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/175316 Title: no IDN in nslookup and host Status in BIND: New Status in bind9 package in Ubuntu: Confirmed Status in iputils package in Ubuntu: Confirmed Status in bind9 package in Debian: New Bug description: Binary package hint: bind9 Neither nslookup or host supports IDN. If you try , for example, to get the IP for "registrera-domän.se" it fails every time. As the use of IDN is increasing I think it would be a good thing if these tools supported this. To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/175316/+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 175316] Re: no IDN in nslookup and host
** Also affects: bind Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iputils in Ubuntu. https://bugs.launchpad.net/bugs/175316 Title: no IDN in nslookup and host Status in BIND: New Status in bind9 package in Ubuntu: Confirmed Status in iputils package in Ubuntu: New Status in bind9 package in Debian: New Bug description: Binary package hint: bind9 Neither nslookup or host supports IDN. If you try , for example, to get the IP for "registrera-domän.se" it fails every time. As the use of IDN is increasing I think it would be a good thing if these tools supported this. To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/175316/+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 1586528] Re: Avahi-daemon withdraws address record
... I'm sure it's something between ubuntu and VirtualBox, but it'd be really nice to not have the usual one throwing the blame on the other, for once ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1586528 Title: Avahi-daemon withdraws address record Status in avahi package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Bug description: For some reason, if I leave my Ubuntu VM up for a prolonged period of time the machine will lose connection to the network. ip addr shows that the nic port no longer has an address and an examination of the syslog shows this: May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record for 10.0.2.15 on enp0s3. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast group on interface enp0s3.IPv4 with address 10.0.2.15. May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no longer relevant for mDNS. for no known reason. The only reliable way to get the network to come back (that I have found) is a full reboot. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:11:34 2016 InstallationDate: Installed on 2015-10-22 (218 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: avahi UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1586528/+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 1586528] Re: Avahi-daemon withdraws address record
I have the same problem; syslog doesn't tell much, but kern.log tells a bit more - "something" is restarting NetworkManager, and the restart results in losing network connection(s); see below; I have standard ubuntu 16.04 LTS 64bit kept up-to-date as a VM within VirtualBox with Win7/64 host and the latest Vbox version (this had been happening across several Vbox updates; but on the same Vbox version, it wasn't happening on ubuntu 14.10 VM until I removed that and installed a brand new 16.04 from scratch). I hoped the 16.04 would soon get a patch fixing this but that never happened. I have both the host and the VM running 24/7 and the frequency of losing the network is about this - ignore November/14, that was obviously unusual and not related to the problem. root@ostws0116886lu:~# LC_ALL=C egrep "whoopsi.*offline" /var/log/syslog* /var/log/syslog:Nov 22 15:57:38 ostws0116886lu whoopsie[617]: [15:57:38] offline /var/log/syslog:Nov 23 15:57:58 ostws0116886lu whoopsie[617]: [15:57:58] offline /var/log/syslog:Nov 25 09:21:11 ostws0116886lu whoopsie[617]: [09:21:11] offline /var/log/syslog.1:Nov 15 21:41:08 ostws0116886lu whoopsie[663]: [21:41:08] offline /var/log/syslog.1:Nov 16 22:02:29 ostws0116886lu whoopsie[663]: [22:02:29] offline root@ostws0116886lu:~# LC_ALL=C xzegrep "whoopsi.*offline" /var/log/syslog*.xz /var/log/syslog.2.xz:Nov 6 09:47:04 ostws0116886lu whoopsie[26233]: [09:47:04] offline /var/log/syslog.2.xz:Nov 9 08:03:06 ostws0116886lu whoopsie[637]: [08:03:06] offline /var/log/syslog.2.xz:Nov 9 08:04:43 ostws0116886lu whoopsie[640]: [08:04:43] offline /var/log/syslog.2.xz:Nov 10 15:57:30 ostws0116886lu whoopsie[685]: [15:57:30] offline /var/log/syslog.2.xz:Nov 14 10:02:59 ostws0116886lu whoopsie[641]: [10:02:59] offline /var/log/syslog.2.xz:Nov 14 10:03:31 ostws0116886lu whoopsie[626]: [10:03:31] offline /var/log/syslog.2.xz:Nov 14 10:25:23 ostws0116886lu whoopsie[721]: [10:25:23] offline /var/log/syslog.2.xz:Nov 14 10:26:02 ostws0116886lu whoopsie[618]: [10:26:02] offline /var/log/syslog.2.xz:Nov 14 10:26:25 ostws0116886lu whoopsie[656]: [10:26:25] offline /var/log/syslog.2.xz:Nov 14 10:46:50 ostws0116886lu whoopsie[663]: [10:46:50] offline /var/log/syslog.3.xz:Nov 2 11:53:15 ostws0116886lu whoopsie[666]: [11:53:15] offline /var/log/syslog.3.xz:Nov 3 11:53:26 ostws0116886lu whoopsie[666]: [11:53:26] offline /var/log/syslog.3.xz:Nov 4 12:02:52 ostws0116886lu whoopsie[666]: [12:02:52] offline /var/log/syslog.4.xz:Oct 25 02:02:43 ostws0116886lu whoopsie[693]: [02:02:43] offline /var/log/syslog.4.xz:Oct 27 15:45:18 ostws0116886lu whoopsie[693]: [15:45:18] offline /var/log/syslog.4.xz:Oct 28 10:21:56 ostws0116886lu whoopsie[647]: [10:21:56] offline /var/log/syslog.4.xz:Oct 29 10:22:09 ostws0116886lu whoopsie[647]: [10:22:09] offline kern.log: --- Nov 24 09:20:58 ostws0116886lu NetworkManager[632]: [1479979258.9094] caught SIGTERM, shutting down normally. Nov 24 09:20:58 ostws0116886lu NetworkManager[632]: [1479979258.9662] exiting (success) Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.2438] NetworkManager (version 1.2.2) is starting... Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.2483] Read config: /etc/NetworkManager/NetworkManager.conf (etc: default-wifi-powersave-on.conf) Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.2532] manager[0x24e21a0]: monitoring kernel firmware directory '/lib/firmware'. Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.2536] monitoring ifupdown state file '/run/network/ifstate'. Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.2603] dns-mgr[0x24f28b0]: set resolv-conf-mode: dnsmasq, plugin="dnsmasq" Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.2607] dns-mgr[0x24f28b0]: using resolv.conf manager 'resolvconf' Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.3473] init! Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.3521] management mode: unmanaged Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.3523] devices added (path: /sys/devices/pci:00/:00:03.0/virtio0/net/enp0s3, iface: enp0s3) Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.3524] device added (path: /sys/devices/pci:00/:00:03.0/virtio0/net/enp0s3, iface: enp0s3): no ifupdown configuration found. Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.3524] devices added (path: /sys/devices/virtual/net/lo, iface: lo) Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.3525] device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.3525] end _init. Nov 24 09:20:59 ostws0116886lu NetworkManager[3470]: [1479979259.3525] settings: loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager
[Touch-packages] [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Also subwoofer doesn't work in Ubuntu 16.04 LTS on Lenovo Y700-15ISK. How to solve this 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1638886] [NEW] network-manager after re-connect vpn network doesn't work
Public bug reported: I was disconnected from vpn network and I try to connect again, but when I do it correctly (I was connected without some warn/error message), the vpn network is unavailable. I have to reboot system or restart service network-manager to work correct. release: it is regression, because in previous version 16.04 it works good. Now the system is up to date Ubuntu 16.10 network-manager 1.2.4-0ubuntu1 workaround: >> service network-manager restart Steps: 1) connect to vpn by GUI 2) disconnected 3) try to connect to vpn network by GUI again ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Summary changed: - network-manager after re-connect openvp vpn network doesn't work + network-manager after re-connect vpn network doesn'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/1638886 Title: network-manager after re-connect vpn network doesn't work Status in network-manager package in Ubuntu: New Bug description: I was disconnected from vpn network and I try to connect again, but when I do it correctly (I was connected without some warn/error message), the vpn network is unavailable. I have to reboot system or restart service network-manager to work correct. release: it is regression, because in previous version 16.04 it works good. Now the system is up to date Ubuntu 16.10 network-manager 1.2.4-0ubuntu1 workaround: >> service network-manager restart Steps: 1) connect to vpn by GUI 2) disconnected 3) try to connect to vpn network by GUI again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638886/+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 1627952] [NEW] package libssl1.0.0:amd64 1.0.1f-1ubuntu2.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29
Public bug reported: It is broken. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl1.0.0:amd64 1.0.1f-1ubuntu2.21 ProcVersionSignature: Ubuntu 4.4.0-36.55~14.04.1-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Sep 27 09:29:32 2016 DuplicateSignature: package:libssl1.0.0:amd64:1.0.1f-1ubuntu2.21:subprocess installed post-installation script returned error exit status 29 ErrorMessage: subprocess installed post-installation script returned error exit status 29 InstallationDate: Installed on 2016-01-22 (248 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: openssl Title: package libssl1.0.0:amd64 1.0.1f-1ubuntu2.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1627952 Title: package libssl1.0.0:amd64 1.0.1f-1ubuntu2.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 Status in openssl package in Ubuntu: New Bug description: It is broken. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl1.0.0:amd64 1.0.1f-1ubuntu2.21 ProcVersionSignature: Ubuntu 4.4.0-36.55~14.04.1-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Sep 27 09:29:32 2016 DuplicateSignature: package:libssl1.0.0:amd64:1.0.1f-1ubuntu2.21:subprocess installed post-installation script returned error exit status 29 ErrorMessage: subprocess installed post-installation script returned error exit status 29 InstallationDate: Installed on 2016-01-22 (248 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: openssl Title: package libssl1.0.0:amd64 1.0.1f-1ubuntu2.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1627952/+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 1627728] [NEW] package isc-dhcp-client 4.2.4-7ubuntu12.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29
Public bug reported: it is broken. crashes all the time. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: isc-dhcp-client 4.2.4-7ubuntu12.6 ProcVersionSignature: Ubuntu 4.4.0-36.55~14.04.1-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Mon Sep 26 14:04:32 2016 DhclientLeases: DuplicateSignature: package:isc-dhcp-client:4.2.4-7ubuntu12.6:subprocess installed post-installation script returned error exit status 29 ErrorMessage: subprocess installed post-installation script returned error exit status 29 InstallationDate: Installed on 2016-01-22 (248 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=bf08c049-914c-4ec5-b278-5813ac8667a7 ro quiet splash vt.handoff=7 SourcePackage: isc-dhcp Title: package isc-dhcp-client 4.2.4-7ubuntu12.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- 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/1627728 Title: package isc-dhcp-client 4.2.4-7ubuntu12.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 Status in isc-dhcp package in Ubuntu: New Bug description: it is broken. crashes all the time. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: isc-dhcp-client 4.2.4-7ubuntu12.6 ProcVersionSignature: Ubuntu 4.4.0-36.55~14.04.1-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Mon Sep 26 14:04:32 2016 DhclientLeases: DuplicateSignature: package:isc-dhcp-client:4.2.4-7ubuntu12.6:subprocess installed post-installation script returned error exit status 29 ErrorMessage: subprocess installed post-installation script returned error exit status 29 InstallationDate: Installed on 2016-01-22 (248 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=bf08c049-914c-4ec5-b278-5813ac8667a7 ro quiet splash vt.handoff=7 SourcePackage: isc-dhcp Title: package isc-dhcp-client 4.2.4-7ubuntu12.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 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/1627728/+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 1542033] Re: avahi-daemon doesn't start
Same here. Just upgraded from 14.04.5 to 16.04.1 Apparmor forbids avahi to create datagram socket, so it dies with an assertion: $ journalctl -ab0 | grep avahi авг 30 11:51:46 amanda audit[2230]: AVC apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/avahi-daemon" pid=2230 comm="apparmor_parser" авг 30 11:51:48 amanda avahi-daemon[2368]: Found user 'avahi' (UID 114) and group 'avahi' (GID 121). авг 30 11:51:48 amanda avahi-daemon[2368]: Successfully dropped root privileges. авг 30 11:51:48 amanda avahi-daemon[2368]: avahi-daemon 0.6.32-rc starting up. авг 30 11:51:48 amanda audit[2368]: AVC apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/avahi-daemon" name="/run/systemd/notify" pid=2368 comm="avahi-daemon" requested_mask="w" denied_mask="w" fsuid=114 ouid=0 авг 30 11:51:48 amanda avahi-daemon[2368]: Successfully called chroot(). авг 30 11:51:48 amanda avahi-daemon[2368]: Successfully dropped remaining capabilities. авг 30 11:51:48 amanda avahi-daemon[2368]: No service file found in /etc/avahi/services. авг 30 11:51:48 amanda audit[2368]: AVC apparmor="DENIED" operation="create" profile="/usr/sbin/avahi-daemon" pid=2368 comm="avahi-daemon" family="netlink" sock_type="dgram" protocol=0 requested_mask="create" denied_mask="create" авг 30 11:51:48 amanda avahi-daemon[2368]: on: starting up: iface-linux.c:380: avahi_interface_monitor_sync: Assertion `m' failed. авг 30 11:51:48 amanda avahi-daemon[2368]: netlink.c: socket(PF_NETLINK): Permission denied авг 30 11:51:48 amanda systemd[1]: avahi-daemon.service: Main process exited, code=killed, status=6/ABRT авг 30 11:51:48 amanda systemd[1]: avahi-daemon.service: Unit entered failed state. авг 30 11:51:48 amanda systemd[1]: avahi-daemon.service: Failed with result 'signal'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1542033 Title: avahi-daemon doesn't start Status in avahi package in Ubuntu: Confirmed Bug description: While upgrading from 14.04 to 16.04 yesterday, I notived that avahi- daemon doesn't start. Log: Feb 04 22:00:15 michis-ibm-haupt systemd[1]: Starting Avahi mDNS/DNS-SD Stack... -- Subject: Unit avahi-daemon.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit avahi-daemon.service has begun starting up. Feb 04 22:00:15 michis-ibm-haupt audit[13101]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/avahi-daemon" name="/etc/ld.so.preload" pid=13101 comm="avahi-daemon" requested_mask="r" denied_ma Feb 04 22:00:15 michis-ibm-haupt kernel: audit: type=1400 audit(1454619615.281:301): apparmor="DENIED" operation="open" profile="/usr/sbin/avahi-daemon" name="/etc/ld.so.preload" pid=13101 comm="avahi-da Feb 04 22:00:15 michis-ibm-haupt kernel: audit: type=1400 audit(1454619615.285:302): apparmor="DENIED" operation="chown" profile="/usr/sbin/avahi-daemon" name="/run/avahi-daemon/" pid=13101 comm="avahi-d Feb 04 22:00:15 michis-ibm-haupt audit[13101]: AVC apparmor="DENIED" operation="chown" profile="/usr/sbin/avahi-daemon" name="/run/avahi-daemon/" pid=13101 comm="avahi-daemon" requested_mask="w" denied_m Feb 04 22:00:15 michis-ibm-haupt avahi-daemon[13101]: Failed to create runtime directory /var/run/avahi-daemon/. Feb 04 22:00:15 michis-ibm-haupt systemd[1]: avahi-daemon.service: Main process exited, code=exited, status=255/n/a Feb 04 22:00:15 michis-ibm-haupt systemd[1]: Failed to start Avahi mDNS/DNS-SD Stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1542033/+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 726033] Re: does not display icons until hovered
** Changed in: mesa (Ubuntu) Status: Triaged => Invalid -- 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/726033 Title: does not display icons until hovered Status in Mesa: Confirmed Status in Nux: Fix Released Status in Unity: Fix Released Status in mesa package in Ubuntu: Invalid Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: Binary package hint: unity-place-applications while unity-places-files and the unity launcher display their content on launching, unity-place-applications does not display anything until the respecting elements were activated (hovering, clicking). see screenshot for the look, where only a few icons were hovered. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: unity-place-applications 0.2.34-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic i686 Architecture: i386 Date: Sun Feb 27 14:13:47 2011 LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227) ProcEnviron: LANGUAGE=de_DE:en LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: unity-place-applications --- Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,scale,session,unityshell] CompositorRunning: compiz DRM.card0.LVDS.1: status: connected enabled: enabled dpms: On modes: 1400x1050 1400x1050 1280x1024 1280x1024 1280x960 1280x854 1280x800 1280x720 1152x768 1024x768 1024x768 800x600 800x600 848x480 720x480 640x480 640x480 edid-base64: AP///wAwrkNPAQOAHhd46q8AmVhTjColUFQhCACBgAEBAQEBAQEBAQEBAQEBMCp4IFEaEEAwcBMAMeQQAAAYKCN4IFEaEEAwcBMAMeQQAAAYDwCQQzKQQygUBgAyDAAA/gBMUDE1MEUwNS1BMgogAJs= DRM.card0.VGA.1: status: disconnected enabled: disabled dpms: On modes: edid-base64: DistUpgraded: Fresh install DistroCodename: natty DistroRelease: Ubuntu 11.04 DistroVariant: ubuntu GdmLog1: GdmLog2: GraphicsCard: ATI Technologies Inc M66GL [ATI Mobility FireGL V5250] [1002:71d4] (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20a4] LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227) LiveMediaBuild_: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227) LiveMediaBuild__: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110227) MachineType: LENOVO 2007FVG Package: unity 3.4.6-0ubuntu1 PackageArchitecture: i386 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=de_DE:en LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 ProcVersionSignature_: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 ProcVersionSignature__: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Renderer: Unknown Tags: natty running-unity natty running-unity natty running-unity ubuntu compiz-0.9 Uname: Linux 2.6.38-5-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/12/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 79ETE3WW (2.23 ) dmi.board.name: 2007FVG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn2007FVG:pvrThinkPadT60p:rvnLENOVO:rn2007FVG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2007FVG dmi.product.version: ThinkPad T60p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.4-0ubuntu1 version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1~git20110215.cc1636b6-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu8 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu11 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/726033/+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 1591644] Re: Regression: YOTA LU150 modem does not work in 16.04
** Changed in: bash (Ubuntu) Assignee: (unassigned) => Pavel (metalarchus) ** Package changed: bash (Ubuntu) => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1591644 Title: Regression: YOTA LU150 modem does not work in 16.04 Status in linux-meta package in Ubuntu: New Bug description: On the Ubuntu 15.10 and older versions YOTA LU150 modem work fine, but on Ubuntu 16.04 it does not work. lsusb on 15.10: Bus 002 Device 007: ID 1076:8002 GCT Semiconductor, Inc. LU150 LTE Modem [Yota LU150] Bus 002 Device 005: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter Bus 002 Device 004: ID 192f:0916 Avago Technologies, Pte. Bus 002 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory 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 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg on 15.10: [ 2849.691015] usb 2-1.6: new high-speed USB device number 11 using ehci-pci [ 2849.783810] usb 2-1.6: New USB device found, idVendor=1076, idProduct=8002 [ 2849.783815] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2849.783818] usb 2-1.6: Product: Modem Yota [ 2849.783820] usb 2-1.6: Manufacturer: GCT SEMICONDUCTOR Inc [ 2849.784907] rndis_host 2-1.6:1.0: dev can't take 1558 byte packets (max 1458), adjusting MTU to 1400 [ 2849.785881] rndis_host 2-1.6:1.0 eth1: register 'rndis_host' at usb-:00:1d.0-1.6, RNDIS device, 00:09:3b:f0:1a:40 lsusb on 16.04 freezes, ^C does not kill it. dmesg on 16.04: [ 50.355199] usb 2-1.6: new high-speed USB device number 6 using ehci-pci [ 50.447992] usb 2-1.6: New USB device found, idVendor=1076, idProduct=8001 [ 50.447997] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 50.448000] usb 2-1.6: Product: Modem Yota [ 50.448002] usb 2-1.6: Manufacturer: GCT SEMICONDUCTOR Inc [ 50.448229] usb-storage 2-1.6:1.0: USB Mass Storage device detected [ 50.448634] scsi host5: usb-storage 2-1.6:1.0 [ 51.447979] scsi 5:0:0:0: CD-ROMGDM Mass PQ: 0 ANSI: 0 CCS [ 51.472471] sr 5:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy [ 51.472475] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 51.472662] sr 5:0:0:0: Attached scsi CD-ROM sr0 [ 51.472752] sr 5:0:0:0: Attached scsi generic sg2 type 5 [ 52.460550] usb 2-1.6: USB disconnect, device number 6 [ 52.460999] cdrom: issuing MRW background format suspend [ 53.427117] usb 2-1.6: new high-speed USB device number 7 using ehci-pci [ 53.519890] usb 2-1.6: New USB device found, idVendor=1076, idProduct=8002 [ 53.519895] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 53.519898] usb 2-1.6: Product: Modem Yota [ 53.519900] usb 2-1.6: Manufacturer: GCT SEMICONDUCTOR Inc [ 53.545260] usbcore: registered new interface driver cdc_ether [ 53.552769] BUG: unable to handle kernel NULL pointer dereference at 0003 [ 53.552805] IP: [] usbnet_generic_cdc_bind+0x171/0x710 [cdc_ether] [ 53.552834] PGD 0 [ 53.552843] Oops: [#1] SMP [ 53.552858] Modules linked in: rndis_host(+) cdc_ether usbnet mii zram lz4_compress intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_via snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec irqbypass ppdev snd_seq_midi crct10dif_pclmul snd_hda_core crc32_pclmul snd_seq_midi_event snd_hwdep snd_pcm aesni_intel snd_rawmidi joydev input_leds aes_x86_64 snd_seq lrw gf128mul snd_seq_device parport_pc glue_helper parport snd_timer shpchp ablk_helper ie31200_edac snd cryptd mac_hid serio_raw mei_me edac_core 8250_fintek soundcore mei lpc_ich intel_smartconnect autofs4 squashfs overlay nls_utf8 isofs dm_mirror dm_region_hash dm_log amdkfd amd_iommu_v2 hid_generic radeon i2c_algo_bit psmouse ttm drm_kms_helper syscopyarea sysfillrect pata_acpi sysimgblt [ 53.553175] fb_sys_fops usbhid uas hid drm usb_storage atl1c video fjes [ 53.553208] CPU: 2 PID: 3092 Comm: systemd-udevd Not tainted 4.4.0-21-generic #37-Ubuntu [ 53.553235] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-VS, BIOS P2.70 09/10/2012 [ 53.553267] task: 8800c03b6040 ti: 8800be168000 task.ti: 8800be168000 [ 53.553292] RIP: 0010:[] [] usbnet_generic_cdc_bind+0x171/0x710 [cdc_ether] [ 53.553328] RSP: 0018:8800be16b960 EFLAGS: 00010286 [ 53.553346] RAX: RBX: 8800d96a3840 RCX: [ 53.553369] RDX: RSI: 8800d582ec00 RDI: 8800d99d6800 [ 53.553393] RBP: 8800be16ba20 R08: 8800d82f01
[Touch-packages] [Bug 1591644] [NEW] Regression: YOTA LU150 modem does not work in 16.04
Public bug reported: On the Ubuntu 15.10 and older versions YOTA LU150 modem work fine, but on Ubuntu 16.04 it does not work. lsusb on 15.10: Bus 002 Device 007: ID 1076:8002 GCT Semiconductor, Inc. LU150 LTE Modem [Yota LU150] Bus 002 Device 005: ID 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter Bus 002 Device 004: ID 192f:0916 Avago Technologies, Pte. Bus 002 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory 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 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg on 15.10: [ 2849.691015] usb 2-1.6: new high-speed USB device number 11 using ehci-pci [ 2849.783810] usb 2-1.6: New USB device found, idVendor=1076, idProduct=8002 [ 2849.783815] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2849.783818] usb 2-1.6: Product: Modem Yota [ 2849.783820] usb 2-1.6: Manufacturer: GCT SEMICONDUCTOR Inc [ 2849.784907] rndis_host 2-1.6:1.0: dev can't take 1558 byte packets (max 1458), adjusting MTU to 1400 [ 2849.785881] rndis_host 2-1.6:1.0 eth1: register 'rndis_host' at usb-:00:1d.0-1.6, RNDIS device, 00:09:3b:f0:1a:40 lsusb on 16.04 freezes, ^C does not kill it. dmesg on 16.04: [ 50.355199] usb 2-1.6: new high-speed USB device number 6 using ehci-pci [ 50.447992] usb 2-1.6: New USB device found, idVendor=1076, idProduct=8001 [ 50.447997] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 50.448000] usb 2-1.6: Product: Modem Yota [ 50.448002] usb 2-1.6: Manufacturer: GCT SEMICONDUCTOR Inc [ 50.448229] usb-storage 2-1.6:1.0: USB Mass Storage device detected [ 50.448634] scsi host5: usb-storage 2-1.6:1.0 [ 51.447979] scsi 5:0:0:0: CD-ROMGDM Mass PQ: 0 ANSI: 0 CCS [ 51.472471] sr 5:0:0:0: [sr0] scsi3-mmc drive: 0x/0x caddy [ 51.472475] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 51.472662] sr 5:0:0:0: Attached scsi CD-ROM sr0 [ 51.472752] sr 5:0:0:0: Attached scsi generic sg2 type 5 [ 52.460550] usb 2-1.6: USB disconnect, device number 6 [ 52.460999] cdrom: issuing MRW background format suspend [ 53.427117] usb 2-1.6: new high-speed USB device number 7 using ehci-pci [ 53.519890] usb 2-1.6: New USB device found, idVendor=1076, idProduct=8002 [ 53.519895] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 53.519898] usb 2-1.6: Product: Modem Yota [ 53.519900] usb 2-1.6: Manufacturer: GCT SEMICONDUCTOR Inc [ 53.545260] usbcore: registered new interface driver cdc_ether [ 53.552769] BUG: unable to handle kernel NULL pointer dereference at 0003 [ 53.552805] IP: [] usbnet_generic_cdc_bind+0x171/0x710 [cdc_ether] [ 53.552834] PGD 0 [ 53.552843] Oops: [#1] SMP [ 53.552858] Modules linked in: rndis_host(+) cdc_ether usbnet mii zram lz4_compress intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_via snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec irqbypass ppdev snd_seq_midi crct10dif_pclmul snd_hda_core crc32_pclmul snd_seq_midi_event snd_hwdep snd_pcm aesni_intel snd_rawmidi joydev input_leds aes_x86_64 snd_seq lrw gf128mul snd_seq_device parport_pc glue_helper parport snd_timer shpchp ablk_helper ie31200_edac snd cryptd mac_hid serio_raw mei_me edac_core 8250_fintek soundcore mei lpc_ich intel_smartconnect autofs4 squashfs overlay nls_utf8 isofs dm_mirror dm_region_hash dm_log amdkfd amd_iommu_v2 hid_generic radeon i2c_algo_bit psmouse ttm drm_kms_helper syscopyarea sysfillrect pata_acpi sysimgblt [ 53.553175] fb_sys_fops usbhid uas hid drm usb_storage atl1c video fjes [ 53.553208] CPU: 2 PID: 3092 Comm: systemd-udevd Not tainted 4.4.0-21-generic #37-Ubuntu [ 53.553235] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H61M-VS, BIOS P2.70 09/10/2012 [ 53.553267] task: 8800c03b6040 ti: 8800be168000 task.ti: 8800be168000 [ 53.553292] RIP: 0010:[] [] usbnet_generic_cdc_bind+0x171/0x710 [cdc_ether] [ 53.553328] RSP: 0018:8800be16b960 EFLAGS: 00010286 [ 53.553346] RAX: RBX: 8800d96a3840 RCX: [ 53.553369] RDX: RSI: 8800d582ec00 RDI: 8800d99d6800 [ 53.553393] RBP: 8800be16ba20 R08: 8800d82f0112 R09: 88011a001400 [ 53.553416] R10: 8800be2e4800 R11: 3ae9 R12: 8800d582ec00 [ 53.553440] R13: 0001 R14: c05c1068 R15: 8800d96a3938 [ 53.553464] FS: 7fc9f00088c0() GS:88011ed0() knlGS: [ 53.553490] CS: 0010 DS: ES: CR0: 80050033 [ 53.553509] CR2: 0003 CR3: 00011581b000 CR4: 001406e0 [ 53.553533] Stack: [ 53.553541] 0001 8800d96a32a0 [
[Touch-packages] [Bug 1580062] [NEW] package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: After installing system and a lot of other packages, using proprietary nvidia driver and intel microcode. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue May 10 09:42:16 2016 Df: Dmesg: ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2016-05-10 (0 days ago) InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160421 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1580062 Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in initramfs-tools package in Ubuntu: New Bug description: After installing system and a lot of other packages, using proprietary nvidia driver and intel microcode. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue May 10 09:42:16 2016 Df: Dmesg: ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2016-05-10 (0 days ago) InstallationMedia: Xubuntu Core 16.04 - amd64 - 20160421 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1580062/+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 1558331] Re: message "The repository is insufficiently signed by key (weak digest)" is poorly worded
Ubuntu 16.04 LTS xenial beta amd64 (2016 0416) - i have only problem with SHA1 while installing www.webmin.com W: http://webmin.mirror.somersettechsolutions.co.uk/repository/dists/sarge/Release.gpg: Signature by key 1719003ACE3E5A41E2DE70DFD97A3AE911F63C51 uses weak digest algorithm (SHA1) W: http://download.webmin.com/download/repository/dists/sarge/Release.gpg: Signature by key 1719003ACE3E5A41E2DE70DFD97A3AE911F63C51 uses weak digest algorithm (SHA1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1558331 Title: message "The repository is insufficiently signed by key (weak digest)" is poorly worded Status in apt package in Ubuntu: Fix Released Bug description: The title pretty much says it all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1558331/+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 1565542] Re: init scripts don't set console fonts
Please fix this trouble. How long can you keep in open? I remember this bug for at least 5 years! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1565542 Title: init scripts don't set console fonts Status in console-setup package in Ubuntu: Confirmed Bug description: 1) lsb_release -rd Description: Ubuntu 15.10 Release: 15.10 2) apt-cache policy keyboard-configuration keyboard-configuration: Installed: 1.108ubuntu9 Candidate: 1.108ubuntu9 Version table: *** 1.108ubuntu9 0 500 http://ru.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected to have cyrillic font for consoles (/dev/tty[1-6]) after sudo dpkg-reconfigure console-setup and reboot 4) I have cyrrilic font until I reboot. After reboot I have black boxes instead cyrillic chars. If I do: setfont /etc/console-setup/Uni2-TerminusBold16.psf.gz then I have cyrrilic font in current console I found that these scripts /usr/share/initramfs-tools/scripts/init-top/console_setup /lib/udev/console-setup-tty cannot properly set console fonts. They don't recognize option CODESET="guess" and FONTSIZE="*x*" and check if exist only *.psf file, but we have *.psf.gz I get part of code from /bin/setupcon and paste it in /usr/share/initramfs-tools/scripts/init-top/console_setup /lib/udev/console-setup-tty and add extra test for psf.gz and acm.gz files The attachment contain original scripts, fixed scripts and patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1565542/+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 1562366] [NEW] Keyboard does not work after resume from suspend mode
Public bug reported: After resuming from suspend on a HP laptop running Ubuntu 15.10 x86_64 the keyboard no longer accepts any input on the login screen. When choosing switch user from the top menu, virtual keyboard can be displayed to login, but the keyboard still does not work afterwards. After reboot everything works normally again. I could reproduce this behaviour several times. Thanks for any help. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 26 18:39:04 2016 InstallationDate: Installed on 2015-05-02 (328 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lightdm UpgradeStatus: Upgraded to wily on 2015-11-09 (137 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1562366 Title: Keyboard does not work after resume from suspend mode Status in lightdm package in Ubuntu: New Bug description: After resuming from suspend on a HP laptop running Ubuntu 15.10 x86_64 the keyboard no longer accepts any input on the login screen. When choosing switch user from the top menu, virtual keyboard can be displayed to login, but the keyboard still does not work afterwards. After reboot everything works normally again. I could reproduce this behaviour several times. Thanks for any help. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: lightdm 1.16.7-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 26 18:39:04 2016 InstallationDate: Installed on 2015-05-02 (328 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: lightdm UpgradeStatus: Upgraded to wily on 2015-11-09 (137 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1562366/+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 1539513] Re: networkmanager segfaults with 3.2.21-1ubuntu1
I hope you can resolve/ revert this ASAP as it brings network down and finding information on how to fix it becomes very complicated. Anyway another solution to revert to the working packages is: if you have an Ubuntu USB stick somewhere 1. Boot "try out Ubuntu" 2. mkdir installation 3. sudo mount /dev/sdXX installation # where sdXX is your ubuntu root partition 4. sudo chroot installation 5. apt-get install libnl-3-200=3.2.21-1 libnl-genl-3-200=3.2.21-1 libnl-route-3-200=3.2.21-1 this saves you manually downloading and copying the packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1539513 Title: networkmanager segfaults with 3.2.21-1ubuntu1 Status in libnl3 package in Ubuntu: Confirmed Bug description: Description:Ubuntu 14.04.3 LTS Release:14.04 After upgrading to 3.2.21-1ubuntu1 network-manager 0.9.8.8-0ubuntu7.2 segfaults: [ 21.367977] init: network-manager main process (1000) killed by SEGV signal [ 21.367989] init: network-manager main process ended, respawning [ 21.424932] init: network-manager main process (1060) killed by SEGV signal [ 21.424943] init: network-manager main process ended, respawning [ 21.451519] init: network-manager main process (1066) killed by SEGV signal [...] xxx@yyy:/tmp/bla# gdb /usr/sbin/NetworkManager CoreDump [...] Reading symbols from /usr/sbin/NetworkManager...(no debugging symbols found)...done. [New LWP 3550] [New LWP 3551] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `NetworkManager'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00469fee in nm_netlink_monitor_attach () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1539513/+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 1373070] Re: full fix for disconnected path (paths)
** Also affects: rsyslog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1373070 Title: full fix for disconnected path (paths) Status in cups package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in rsyslog package in Ubuntu: New Bug description: With the apparmor 3 RC1 upload, there is an incomplete bug fix for disconnected paths. This bug is to track that work. This denial may be related: Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 audit(1411485050.722:2862): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" name="dev/log" pid=7011 comm="logger" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 This is related to bug 1375410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1373070/+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 1373070] Re: full fix for disconnected path (paths)
I'm affected by this bug too at Trusty + Vivid HWE # lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 # uname -a Linux amanda 3.19.0-42-generic #48~14.04.1-Ubuntu SMP Fri Dec 18 10:25:23 UTC 2015 i686 i686 i686 GNU/Linux # dpkg -l | grep linux-image-generic ii linux-image-generic 3.13.0.74.80 i386 Generic Linux kernel image ii linux-image-generic-lts-vivid 3.19.0.42.27 i386 Generic Linux kernel image # dpkg -l | grep -e rsyslog -e apparmor ii apparmor2.8.95~2430-0ubuntu5.3 i386 User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.3 all Profiles for AppArmor Security policies ... ii rsyslog 7.4.4-1ubuntu2.6 i386 reliable system and kernel logging daemon # grep 'audit:' /var/log/syslog | grep DENIED Dec 26 09:39:48 amanda kernel: [11627.614510] audit: type=1400 audit(145988.687:54): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" name="dev/log" pid=20376 comm="logger" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1373070 Title: full fix for disconnected path (paths) Status in cups package in Ubuntu: Fix Released Status in linux package in Ubuntu: Triaged Status in rsyslog package in Ubuntu: New Bug description: With the apparmor 3 RC1 upload, there is an incomplete bug fix for disconnected paths. This bug is to track that work. This denial may be related: Sep 23 10:10:50 localhost kernel: [40262.517799] audit: type=1400 audit(1411485050.722:2862): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/rsyslogd" name="dev/log" pid=7011 comm="logger" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 This is related to bug 1375410 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1373070/+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 1521931] [NEW] apparmor-profile-load returns 1 if apparmor not installed
Public bug reported: Environment: ubuntu 15.04 with upstart and without apparmor I tried to upgrade my ubuntu image to 15.10 and upgrading breaks on rsyslog: start: Job failed to start i checked dmesg and found this: [ 525.832963] init: rsyslog pre-start process (3078) [ 525.833007] init: rsyslog state changed from pre-starting to pre-start [ 525.834464] init: rsyslog pre-start process (3078) terminated with status 1 [ 525.834639] init: rsyslog goal changed from start to stop so i looked in pre-start: pre-start script /lib/init/apparmor-profile-load usr.sbin.rsyslogd end script and then in /lib/init/apparmor-profile-load: #!/bin/sh [ -x /lib/apparmor/profile-load ] && exec /lib/apparmor/profile-load "$@" in my case where is no "/lib/apparmor/profile-load" file, so this scripts return 1, which breaks pre-start and breaks rsyslog starting I guess that if /lib/init/apparmor-profile-load script checks if file exists, it should return 0 in case then file doesn't exist ** Affects: init-system-helpers (Ubuntu) Importance: Undecided Status: New ** Affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Also affects: rsyslog (Ubuntu) Importance: Undecided Status: New ** Description changed: Environment: ubuntu 15.04 with upstart and without apparmor I tried to upgrade my ubuntu image to 15.10 and upgrading breaks on rsyslog: start: Job failed to start i checked dmesg and found this: [ 525.832963] init: rsyslog pre-start process (3078) [ 525.833007] init: rsyslog state changed from pre-starting to pre-start [ 525.834464] init: rsyslog pre-start process (3078) terminated with status 1 [ 525.834639] init: rsyslog goal changed from start to stop so i looked in pre-start: pre-start script - /lib/init/apparmor-profile-load usr.sbin.rsyslogd + /lib/init/apparmor-profile-load usr.sbin.rsyslogd end script and then in /lib/init/apparmor-profile-load: #!/bin/sh [ -x /lib/apparmor/profile-load ] && exec /lib/apparmor/profile-load "$@" + in my case where is no "/lib/apparmor/profile-load" file, so this + scripts return 1, which breaks pre-start and breaks rsyslog starting - in my case where is no "/lib/apparmor/profile-load" file, so this scripts return 1, - which breaks pre-start and breaks rsyslog starting - - I guess that if /lib/init/apparmor-profile-load script checks if file exists, - it should return 0 in case then file doesn't exist + I guess that if /lib/init/apparmor-profile-load script checks if file + exists, it should return 0 in case then file doesn't exist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1521931 Title: apparmor-profile-load returns 1 if apparmor not installed Status in init-system-helpers package in Ubuntu: New Status in rsyslog package in Ubuntu: New Bug description: Environment: ubuntu 15.04 with upstart and without apparmor I tried to upgrade my ubuntu image to 15.10 and upgrading breaks on rsyslog: start: Job failed to start i checked dmesg and found this: [ 525.832963] init: rsyslog pre-start process (3078) [ 525.833007] init: rsyslog state changed from pre-starting to pre-start [ 525.834464] init: rsyslog pre-start process (3078) terminated with status 1 [ 525.834639] init: rsyslog goal changed from start to stop so i looked in pre-start: pre-start script /lib/init/apparmor-profile-load usr.sbin.rsyslogd end script and then in /lib/init/apparmor-profile-load: #!/bin/sh [ -x /lib/apparmor/profile-load ] && exec /lib/apparmor/profile-load "$@" in my case where is no "/lib/apparmor/profile-load" file, so this scripts return 1, which breaks pre-start and breaks rsyslog starting I guess that if /lib/init/apparmor-profile-load script checks if file exists, it should return 0 in case then file doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1521931/+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 1521931] Re: apparmor-profile-load returns 1 if apparmor not installed
This fixes issues for me: /lib/init/apparmor-profile-load: #!/bin/sh [ -x /lib/apparmor/profile-load ] || exit 0 exec /lib/apparmor/profile-load "$@" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1521931 Title: apparmor-profile-load returns 1 if apparmor not installed Status in init-system-helpers package in Ubuntu: New Status in rsyslog package in Ubuntu: New Bug description: Environment: ubuntu 15.04 with upstart and without apparmor I tried to upgrade my ubuntu image to 15.10 and upgrading breaks on rsyslog: start: Job failed to start i checked dmesg and found this: [ 525.832963] init: rsyslog pre-start process (3078) [ 525.833007] init: rsyslog state changed from pre-starting to pre-start [ 525.834464] init: rsyslog pre-start process (3078) terminated with status 1 [ 525.834639] init: rsyslog goal changed from start to stop so i looked in pre-start: pre-start script /lib/init/apparmor-profile-load usr.sbin.rsyslogd end script and then in /lib/init/apparmor-profile-load: #!/bin/sh [ -x /lib/apparmor/profile-load ] && exec /lib/apparmor/profile-load "$@" in my case where is no "/lib/apparmor/profile-load" file, so this scripts return 1, which breaks pre-start and breaks rsyslog starting I guess that if /lib/init/apparmor-profile-load script checks if file exists, it should return 0 in case then file doesn't exist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1521931/+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 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
I am getting this in 16.04 development version. [ 87.068463] systemd-logind[2155]: Failed to start user service: Unknown unit: user@1000.service (could be because this is a fresh upgrade from earlier version, but yes, it is still here) ** Description changed: - ATTENTION: This bug is fully understood, there is *no need* to add even - more comments about "me too" here. - [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in NULL Project: Invalid Status in systemd package in Ubuntu: Won't Fix Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Utopic: Won't Fix Status in systemd-shim source package in Utopic: Won't Fix Status in systemd-shim package in Debian: New Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [
[Touch-packages] [Bug 1506527] Re: app doesn't support gps position
No, I am talking about webaspps https://developer.ubuntu.com/en/web /ubuntu-webapps-guide/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1506527 Title: app doesn't support gps position Status in webbrowser-app package in Ubuntu: Invalid Bug description: I tried to create app that need gps position, but it isn't possible. Created app doesn't have right to read position. How can I do it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1506527/+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 1506527] [NEW] app doesn't support gps position
Public bug reported: I tried to create app that need gps position, but it isn't possible. Created app doesn't have right to read position. How can I do it? ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1506527 Title: app doesn't support gps position Status in webbrowser-app package in Ubuntu: New Bug description: I tried to create app that need gps position, but it isn't possible. Created app doesn't have right to read position. How can I do it? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1506527/+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 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
It seems that issue is gone with this fix. 1. Installed the package from trusty-proposed # LANG=C apt-cache policy rsyslog rsyslog: Installed: 7.4.4-1ubuntu2.6 Candidate: 7.4.4-1ubuntu2.6 Version table: *** 7.4.4-1ubuntu2.6 0 400 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main amd64 Packages 100 /var/lib/dpkg/status 7.4.4-1ubuntu2.5 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 7.4.4-1ubuntu2.3 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.4.4-1ubuntu2 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 2. commented out the workaround /dev/log rwl, from /etc/apparmor.d/local/usr.sbin.rsyslogd 3. Rebooted to the latest Utopic HWE kernel # uname -a Linux emma 3.16.0-37-generic #51~14.04.1-Ubuntu SMP Wed May 6 15:23:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux 4. The issue is gone: # dmesg | grep DENIED # -- 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/1425398 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Fix Released Status in apparmor source package in Trusty: In Progress Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Invalid Status in rsyslog source package in Trusty: Fix Committed Bug description: [rsyslog impact] This bug prevents rsyslog from receiving all events from other services on trusty when the utopic-hwe (and newer) kernels are used. The rsyslog SRU adds an additional permission (read access to /dev/log) to the rsyslog apparmor policy to allow this to work. [rsyslog test case] (1) Ensure the rsyslog apparmor policy is set to enforce; it should show up listed in the XX profiles are in enforce mode. section reported by sudo aa-status (if it's disabled, do sudo aa-enforce rsyslogd). (2) Install the utopic or newer hwe enablement stack reboot into the kernel. Using the logger(1) utility should generate log messages (e.g. logger foo) that are recorded in syslog; with this bug, they will be blocked (grep DENIED /var/log/syslog). [rsyslog regression potential] The only change to rsyslog in the SRU is a slight loosening of the rsyslog apparmor policy. The risk of an introduced regression is small. [rsyslog addition info] The qa-regression-testing script is useful for verifying that rsyslog is still functioning properly (http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/view/head:/scripts/test-rsyslog.py) [Original description] I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii
[Touch-packages] [Bug 1431846] Re: white screen on boot right before login promt
*** This bug is a duplicate of bug 1428884 *** https://bugs.launchpad.net/bugs/1428884 It is a duplicate of the bug 1428884. The title of that bug not good - Xorg crash, even though no crash is described. Anyway, the symptoms are the same. ** This bug has been marked a duplicate of bug 1428884 White screen on boot or logout, goes away on mouse click -- 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/1431846 Title: white screen on boot right before login promt Status in xorg package in Ubuntu: New Bug description: Power on or restart the machine. Right before the login promt appears the screen goes white. Then i have to click once anywhere on the screen . After clicking , white screen dissapears and i can see the login promt and log normaly. lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 apt-cache policy xorg xorg: Installed: 1:7.7+1ubuntu8.1 Candidate: 1:7.7+7ubuntu3 Version table: 1:7.7+7ubuntu3 0 500 http://gr.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages *** 1:7.7+1ubuntu8.1 0 100 /var/lib/dpkg/status Bug Report guidelines 3 4 : Obviusly the white screen shouldnt be there and i should be able to see the login promt. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 13 14:34:52 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-02 (10 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to vivid on 2015-03-02 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1431846/+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 1428884] Re: Xorg crash
I confirm the bug. I'm using Lubuntu x86_64. I upgraded it from 14.10 to the current prerelease 15.04 and I have that bug too. My system is a laptop on dock (Lenovo T440p), the dock is connected to a monitor. The bug is only seen if the laptop is docked. The easiest way to reproduce the bug is to log out. ** Summary changed: - Xorg crash + White screen on boot or logout, goes away on mouse click -- 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/1428884 Title: White screen on boot or logout, goes away on mouse click Status in xorg package in Ubuntu: Confirmed Bug description: On a fresh install of Ubuntu MATE 15.04 (packages updates during install allowed, install completed about 1 hour ago) I experience that I cannot log to the user I created during install. When I try, the screen(s) turn white (actually, a very light grey) and stay(s) that way until I click, after which I am returned to the login screen. Guest login works fine. xorg is selected based on a quick read of RindRightPackage. Successful guest login seems to indicate that this is not a driver problem. I have reinstalled, but still experience this problem. I'm not sure if sufficient hardware information is included automatically, otherwise please ask. 1) Ubuntu MATE 15.04 beta 2) xorg 1:7.7+7ubuntu2 3) After log in screen, I expected to see the desktop 4) I see white screen and am returned to login screen after user input ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Mar 5 23:46:27 2015 InstallationDate: Installed on 2015-03-05 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 Vivid Vervet - Alpha amd64 (20150225) SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1428884/+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 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
Also if you read comments of other Ubuntu _developers_, they are rather confident that the bug is in Utopic HWE for Trusty -- 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/1425398 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Fix Released Status in apparmor source package in Trusty: Invalid Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Invalid Status in rsyslog source package in Trusty: Triaged Bug description: Hi. I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+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 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
As I said before, I don't use Vivid, I use Trusty which is stated to be supported until 2019! The bug is against trusty, please don't close it as fixed in an non-LTS release -- 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/1425398 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Fix Released Status in apparmor source package in Trusty: Invalid Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Invalid Status in rsyslog source package in Trusty: Triaged Bug description: Hi. I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+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 1389021] Re: Does not detect hotplugged storage device (exfat)
Why is it not fixed in utopic repo when fixed package is already available ?!! -- 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/1389021 Title: Does not detect hotplugged storage device (exfat) Status in util-linux package in Ubuntu: Fix Released Bug description: It used to work then stopped for some reason. Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x7c367968 Device Boot Start End Sectors Size Id Type /dev/sdb1 63 488392064 488392002 232.9G 7 HPFS/NTFS/exFAT exfatfsck /dev/sdb1 finds no error mount -t exfat works, it's just auto-mounting that doesn't. '-t' is required though, not sure if that's normal: mount: /dev/sdb1: more filesystems detected. This should not happen, use -t type to explicitly specify the filesystem type or use wipefs(8) to clean up the device. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gvfs 1.20.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 4 00:39:03 2014 HotplugNewDevices: /dev/sdb1 /dev/sdb HotplugNewMounts: InstallationDate: Installed on 2014-10-03 (31 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: gvfs Symptom: storage Title: Does not detect hotplugged storage device UpgradeStatus: Upgraded to utopic on 2014-10-24 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1389021/+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 641225] Re: tracker-miner-fs crashed with SIGSEGV in g_slice_alloc()
Still in Vivid.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/641225 Title: tracker-miner-fs crashed with SIGSEGV in g_slice_alloc() Status in tracker package in Ubuntu: Confirmed Bug description: Binary package hint: tracker unexpected crash ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: tracker-miner-fs 0.8.17-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-21.31-generic 2.6.35.4 Uname: Linux 2.6.35-21-generic i686 NonfreeKernelModules: slamr Architecture: i386 Date: Fri Sep 17 13:31:32 2010 ExecutablePath: /usr/lib/tracker/tracker-miner-fs ProcCmdline: /usr/lib/tracker/tracker-miner-fs ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x9c3c7b g_slice_alloc+251: mov0x4(%eax),%edx PC (0x009c3c7b) ok source 0x4(%eax) (0x0044) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: g_slice_alloc () from /lib/libglib-2.0.so.0 g_slist_prepend () from /lib/libglib-2.0.so.0 ?? () from /usr/lib/libtracker-miner-0.8.so.0 ?? () from /usr/lib/libgio-2.0.so.0 g_simple_async_result_complete () from /usr/lib/libgio-2.0.so.0 Title: tracker-miner-fs crashed with SIGSEGV in g_slice_alloc() UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare scanner scard tape uml-net video x2gousers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/641225/+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 1437877] [NEW] Error!
Public bug reported: Could not find required OpenGL entry point 'glGetError' ! Either your video card is unsupported, or your OpenGL driver needs to be updated. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8.2 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: Sun Mar 29 20:53:30 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-33-generic, x86_64: installed nvidia-331-updates, 331.113, 3.16.0-33-generic, x86_64: installed nvidia-331-updates-uvm, 331.113, 3.16.0-33-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 650 Ti] [10de:11c6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3557] InstallationDate: Installed on 2015-03-28 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. GA-MA790X-DS4 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: GA-MA790X-DS4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd03/04/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790X-DS4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790X-DS4:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790X-DS4 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sun Mar 29 19:45:39 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Optical USB Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.16.0-1ubuntu1.3 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic -- 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/1437877 Title: Error! Status in xorg package in Ubuntu: New Bug description: Could not find required OpenGL entry point 'glGetError' ! Either your video card is unsupported, or your OpenGL driver needs to be updated. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8.2 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: Sun Mar 29 20:53:30 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-33-generic, x86_64: installed nvidia-331-updates, 331.113, 3.16.0-33-generic, x86_64: installed nvidia-331-updates-uvm, 331.113, 3.16.0-33-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 650 Ti] [10de:11c6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3557] InstallationDate: Installed on 2015-03-28 (0 days ago) InstallationMedia: Ubuntu
[Touch-packages] [Bug 1425914] Re: DTLS handshake broken - precise x64
Hello Brian, I confirm this issue is fixed with openssl package in proposed repository of version 1.0.1-4ubuntu5.22. Tested with scenario above. Thanks ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1425914 Title: DTLS handshake broken - precise x64 Status in OpenSSL cryptography and SSL/TLS toolkit: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Precise: Fix Committed Status in openssl source package in Trusty: Fix Released Status in openssl source package in Utopic: Fix Released Status in openssl source package in Vivid: Fix Released Bug description: Hi, there is a problem in DTLS handshake in OpenSSL library in Ubuntu 12.04 x86_64. The affected library version is libssl 1.0.1-4ubuntu5.21. The problem causes, that it is impossible to establish DTLS session with Chrome or Firefox when trying to perform a SIP call via WebRTC. The problem is fixed in OpenSSL upstream by commit https://github.com/openssl/openssl/commit/a20152bdaf7a99b006ff5a0eef081502e0e11553 committed April 4th 2012. 32bit version of Ubuntu 12.04 is not affected by this issue, because it doesn't support HMAC ciphers, which cause the problem. I've checked other distributions (Centos6, Centos7, Ubuntu 14.04 and especially Debian 7 - which should be close to Ubuntu 12.04) and all has this patch applied and thus WebRTC calls work. Please merge this upstream fix to Ubuntu 12.04 x86_64 libssl package. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1425914/+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 1427346] [NEW] [Upstream] Ambiance wrong color for text toolbar buttons in LibreOffice
Public bug reported: With Ambiance theme, text toolbar buttons in LibreOffice are colored as disabled (even when they are enabled). With Radiance theme their color seems correct. See attachment with screenshot taken from LibreOffice Calc Preview ** Affects: libreoffice (Ubuntu) Importance: Low Status: Triaged ** Attachment added: LO_ambiance.jpg https://bugs.launchpad.net/bugs/1427346/+attachment/4332496/+files/LO_ambiance.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1427346 Title: [Upstream] Ambiance wrong color for text toolbar buttons in LibreOffice Status in libreoffice package in Ubuntu: Triaged Bug description: With Ambiance theme, text toolbar buttons in LibreOffice are colored as disabled (even when they are enabled). With Radiance theme their color seems correct. See attachment with screenshot taken from LibreOffice Calc Preview To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1427346/+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 842194] Re: greeter doesn't start failed to load session file
Installing Precise from debootstrap, then kubuntu-desktop with APT::Install-Recommends false; then lightdm, lightdm-kde-greeter, xorg, linux-image-generic causes the similar problem with lightdm. [+0.21s] DEBUG: Failed to load session file /usr/share/xgreeters/default.desktop: No such file or directory In /usr/share/xgreeters I have lightdm-kde-greeter.desktop but the file /etc/lightdm/lightdm.conf does not exist! I will have to create it manually and to write there something like: [SeatDefaults] greeter-session=lightdm-gtk-greeter I think it should solve the problem. It is interesting that there is no package owns the /etc/lightdm/lightdm.conf file (if is has been generated automatically). Why is it created when recommends installation is switched on and has not been created automatically during the installation without recommends? What is responsible for generating the /etc/lightdm/lightdm.conf file? -- 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/842194 Title: greeter doesn't start failed to load session file Status in lightdm package in Ubuntu: Triaged Bug description: As of today, lightdm on oneiric doesn't show a login screen. I have verified the greeters are installed so this is different to bug 816646. The most likely lines in the log seem to be Failed to load session file /usr/share/xgreeters/.desktop: No such file or directory Failed to start greeter Stopping display I'm just left at a text screen with various stair-stepped log messages. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: lightdm 0.9.3-0ubuntu8 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic x86_64 Architecture: amd64 Date: Tue Sep 6 08:32:54 2011 EcryptfsInUse: Yes ProcEnviron: PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/zsh SourcePackage: lightdm UpgradeStatus: Upgraded to oneiric on 2011-08-23 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/842194/+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 1425914] Re: DTLS handshake broken - precise x64
Hi, unfortunately I don't have any separate little tool how to test it. The bug causes, that WebRTC calls in our proprieatry application - IceWarp server doesn't work. However we have a free demo, so you can test it like this: 0) Have Ubuntu 12.04 x86_64 1) Download http://linuxbuilds.icewarp.com/UBUNTU1204_x64/devel/2015-02-26-05-00-03/IceWarpServer-11.2.0.0_x64_20150226_UBUNTU1204.tar.gz 2) Unpack 3) Run install.sh with parameter -f 4) Confirm installation of all dependencies, libreoffice, java etc. 5) Install it to /opt/icewarp, create admin user, do not register license - it is not needed, you will get 30 days demo 6) Stop any HTTP and SIP server running on the machine 7) Start IceWarp server running /opt/icewarp/icewarpd.sh --start 8) Run firefox, go to localhost - webmail login page appears 9) Login using credentials admin/admin 10) Click the phone icon in the upper right corner - webphone will start 11) Type echo and click Call - You should hear echo service voice You can also try it on Ubuntu 12.04 i686 with http://linuxbuilds.icewarp.com/UBUNTU1204/devel/2015-02-26-05-00-03/IceWarpServer-11.2.0.0_20150226_UBUNTU1204.tar.gz - there it works normally. If needed, I'm able to test it using steps above on our side too. Just give me the fixed package. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1425914 Title: DTLS handshake broken - precise x64 Status in OpenSSL cryptography and SSL/TLS toolkit: Fix Released Status in openssl package in Ubuntu: Fix Released Status in openssl source package in Precise: Confirmed Status in openssl source package in Trusty: Fix Released Status in openssl source package in Utopic: Fix Released Status in openssl source package in Vivid: Fix Released Bug description: Hi, there is a problem in DTLS handshake in OpenSSL library in Ubuntu 12.04 x86_64. The affected library version is libssl 1.0.1-4ubuntu5.21. The problem causes, that it is impossible to establish DTLS session with Chrome or Firefox when trying to perform a SIP call via WebRTC. The problem is fixed in OpenSSL upstream by commit https://github.com/openssl/openssl/commit/a20152bdaf7a99b006ff5a0eef081502e0e11553 committed April 4th 2012. 32bit version of Ubuntu 12.04 is not affected by this issue, because it doesn't support HMAC ciphers, which cause the problem. I've checked other distributions (Centos6, Centos7, Ubuntu 14.04 and especially Debian 7 - which should be close to Ubuntu 12.04) and all has this patch applied and thus WebRTC calls work. Please merge this upstream fix to Ubuntu 12.04 x86_64 libssl package. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1425914/+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 842194] Re: greeter doesn't start failed to load session file
The file /etc/lightdm/ligtdm.conf is being created while running
postinst script from lightdm-{kde,gtk}-greeter package. The script needs
the /usr/lib/lightdm/lightdm-set-defaults binary. This binary is owned
by lightdm package so it is necessary to install lightdm package before
or at the same time with lightdm-{kde,gtk}-greeter. If lightdm package
was installed after one of the lightdm-greeter packages, you may run
dpkg-reconfigure lightdm-kde-greeter or dpkg-reconfigure lightdm-gtk-
greeter (depending on the greeter package you have installed) to
generate the proper /etc/lightdm/ligtdm.conf file. This method helped me
to solve the problem.
--
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/842194
Title:
greeter doesn't start failed to load session file
Status in lightdm package in Ubuntu:
Triaged
Bug description:
As of today, lightdm on oneiric doesn't show a login screen. I have
verified the greeters are installed so this is different to bug
816646. The most likely lines in the log seem to be
Failed to load session file /usr/share/xgreeters/.desktop: No such file or
directory
Failed to start greeter
Stopping display
I'm just left at a text screen with various stair-stepped log
messages.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: lightdm 0.9.3-0ubuntu8
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
Architecture: amd64
Date: Tue Sep 6 08:32:54 2011
EcryptfsInUse: Yes
ProcEnviron:
PATH=(custom, user)
LANG=en_AU.UTF-8
SHELL=/bin/zsh
SourcePackage: lightdm
UpgradeStatus: Upgraded to oneiric on 2011-08-23 (12 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/842194/+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 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
John, I'm using Ubuntu Trusty with Utopic HWE, so my apparmor is from Trusty. I didn't install anything from backports or Utopic by hand to not mess package system and LTS state of distribution. But somehow the system does not behave like trusty. Note that I've updated this system from 12.04 w/ Trusty HWE to 14.04 with do-release-upgrade few months ago. $ LANG=C apt-cache policy apparmor apparmor-profiles apparmor-utils apparmor: Installed: 2.8.95~2430-0ubuntu5.1 Candidate: 2.8.95~2430-0ubuntu5.1 Version table: *** 2.8.95~2430-0ubuntu5.1 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 2.8.95~2430-0ubuntu5 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages apparmor-profiles: Installed: 2.8.95~2430-0ubuntu5.1 Candidate: 2.8.95~2430-0ubuntu5.1 Version table: *** 2.8.95~2430-0ubuntu5.1 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 2.8.95~2430-0ubuntu5 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages apparmor-utils: Installed: 2.8.95~2430-0ubuntu5.1 Candidate: 2.8.95~2430-0ubuntu5.1 Version table: *** 2.8.95~2430-0ubuntu5.1 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 2.8.95~2430-0ubuntu5 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages -- 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/1425398 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: New Status in linux-lts-utopic package in Ubuntu: New Bug description: Hi. I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+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 1425914] [NEW] DTLS handshake broken - precise x64
Public bug reported: Hi, there is a problem in DTLS handshake in OpenSSL library in Ubuntu 12.04 x86_64. The affected library version is libssl 1.0.1-4ubuntu5.21. The problem causes, that it is impossible to establish DTLS session with Chrome or Firefox when trying to perform a SIP call via WebRTC. The problem is fixed in OpenSSL upstream by commit https://github.com/openssl/openssl/commit/a20152bdaf7a99b006ff5a0eef081502e0e11553 committed April 4th 2012. 32bit version of Ubuntu 12.04 is not affected by this issue, because it doesn't support HMAC ciphers, which cause the problem. I've checked other distributions (Centos6, Centos7, Ubuntu 14.04 and especially Debian 7 - which should be close to Ubuntu 12.04) and all has this patch applied and thus WebRTC calls work. Please merge this upstream fix to Ubuntu 12.04 x86_64 libssl package. Thanks ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, there is a problem in DTLS handshake in OpenSSL library in Ubuntu 12.04 x86_64. The affected library version is libssl 1.0.1-4ubuntu5.21. The problem causes, that it is impossible to establish DTLS session with - both Chrome and Firefox when trying to perform a SIP call via WebRTC. + Chrome or Firefox when trying to perform a SIP call via WebRTC. The problem is fixed in OpenSSL upstream by commit https://github.com/openssl/openssl/commit/a20152bdaf7a99b006ff5a0eef081502e0e11553 committed (April 4th 2012). 32bit version of Ubuntu 12.04 is not affected by this issue, because it doesn't support HMAC ciphers, which cause the problem. I've checked other distributions (Centos6, Centos7, Ubuntu 14.04 and especially Debian 7 - which should be close to Ubuntu 12.04) and all has this patch applied and thus WebRTC calls work. Please merge this upstream fix to Ubuntu 12.04 x86_64 libssl package. Thanks ** Description changed: Hi, there is a problem in DTLS handshake in OpenSSL library in Ubuntu 12.04 x86_64. The affected library version is libssl 1.0.1-4ubuntu5.21. The problem causes, that it is impossible to establish DTLS session with Chrome or Firefox when trying to perform a SIP call via WebRTC. The problem is fixed in OpenSSL upstream by commit https://github.com/openssl/openssl/commit/a20152bdaf7a99b006ff5a0eef081502e0e11553 - committed (April 4th 2012). + committed April 4th 2012. 32bit version of Ubuntu 12.04 is not affected by this issue, because it doesn't support HMAC ciphers, which cause the problem. I've checked other distributions (Centos6, Centos7, Ubuntu 14.04 and especially Debian 7 - which should be close to Ubuntu 12.04) and all has this patch applied and thus WebRTC calls work. Please merge this upstream fix to Ubuntu 12.04 x86_64 libssl package. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1425914 Title: DTLS handshake broken - precise x64 Status in openssl package in Ubuntu: New Bug description: Hi, there is a problem in DTLS handshake in OpenSSL library in Ubuntu 12.04 x86_64. The affected library version is libssl 1.0.1-4ubuntu5.21. The problem causes, that it is impossible to establish DTLS session with Chrome or Firefox when trying to perform a SIP call via WebRTC. The problem is fixed in OpenSSL upstream by commit https://github.com/openssl/openssl/commit/a20152bdaf7a99b006ff5a0eef081502e0e11553 committed April 4th 2012. 32bit version of Ubuntu 12.04 is not affected by this issue, because it doesn't support HMAC ciphers, which cause the problem. I've checked other distributions (Centos6, Centos7, Ubuntu 14.04 and especially Debian 7 - which should be close to Ubuntu 12.04) and all has this patch applied and thus WebRTC calls work. Please merge this upstream fix to Ubuntu 12.04 x86_64 libssl package. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1425914/+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 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
First of all, Trusty kernel worked somehow differently. It didn't complain for /dev/log. Yes, my /etc/apparmor.d/usr.sbin.rsyslogd does not have 'r' for /dev/log: /dev/log wl, So does it mean that the rsyslog profile has to be patched for trusty? Or at least some kind of Utopic HWE release notes has to be updated? I've updated /etc/apparmor.d/local/usr.sbin.rsyslogd and can confirm that message is gone with Utopic kernel. -- 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/1425398 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: New Status in linux-lts-utopic package in Ubuntu: New Bug description: Hi. I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo requested_mask=r denied_mask=r fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie requested_mask=r denied_mask=r fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor=DENIED operation=sendmsg profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd requested_mask=r denied_mask=r fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+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 1404475] Re: Multi-Arch support
Hi, I am getting to the same problem. The sound processing library I am working on depends on libopus0 and thus it cannot be installed for more than single architecture (i386 and amd64) at the same time. However the fixed release is only available for planned future release (vivid). Do you plan to provide the fixed 1.1-0ubuntu2 also for older ubuntu versions (14.04 LTS and 14.10)? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opus in Ubuntu. https://bugs.launchpad.net/bugs/1404475 Title: Multi-Arch support Status in opus package in Ubuntu: Fix Released Bug description: libopus0 package lacks multi-arch support as for ubuntu 14.10 Running 'sudo apt-get install libopus0 libopus0:i386' fails because of this And there is not signs of Multi-Arch: same when running 'apt-cache show libopus0' also To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opus/+bug/1404475/+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 1354924] Re: Networkmanager does not autoconnect to wireless network
I have same problem on on my Lenovo X240 laptop. WiFi never reconnect after sleep or reboot. -- 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/1354924 Title: Networkmanager does not autoconnect to wireless network Status in network-manager package in Ubuntu: Confirmed Bug description: When adding a net wireless network and enable connect automatically' networkmanager does not automatically connect to the network wenever possible. I'm running kubuntu 14.10 daily. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 21:30:03 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-11 (29 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) IpRoute: default via 192.168.0.2 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.213 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+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
