[Touch-packages] [Bug 2056187] Re: fails to configure BOOTIF when using iscsi
It seems 0.142ubuntu19 would be exposed to the bug. To test whether or
not my use case would be affected by it, I've booted a Jammy instance
with initramfs-tools 0.142ubuntu19, and I can't hit the problem. It is
booting well through iscsi. My cmdline is as below, so it might not be
exposed to the issue (and hence, please ignore my comment above as a
valid test for the patch, given that I wasn't exposed to it to begin
with):
BOOT_IMAGE=/boot/vmlinuz-6.5.0-1018-oracle
root=UUID=2792ceda-655f-4995-bf29-6a714f9a200b ro console=tty1
console=ttyS0 nvme.shutdown_timeout=10 libiscsi.debug_libiscsi_eh=1
crash_kexec_post_notifiers
--
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/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Fix Committed
Status in open-iscsi package in Ubuntu:
Invalid
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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 2056187] Re: fails to configure BOOTIF when using iscsi
I've tested launching a Oracle Cloud baremetal instance (which boots
from iSCSI) using such patch, and all worked well:
https://pastebin.ubuntu.com/p/3cdFdYBVFG/
--
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/2056187
Title:
fails to configure BOOTIF when using iscsi
Status in initramfs-tools package in Ubuntu:
Triaged
Status in open-iscsi package in Ubuntu:
Invalid
Bug description:
we have a bad interaction between initramfs-tools and open-iscsi,
resulting in the boot interface not being configured.
when the iscsi has a static address, the script `local-top/iscsi` from
open-iscsi creates a /run/net-$DEVICE.conf file for the iscsi
interface. The existence of this file makes configure_networking()
skip configuring the BOOTIF later due to this code in
`scripts/functions`:
for x in /run/net-"${DEVICE}".conf /run/net-*.conf ; do
if [ -e "$x" ]; then
IP=done
break
fi
done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2056187/+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 2056194] Re: Networking broken in early boot on Oracle Native instances
I've tested the patch and it fixes the issue. I can confirm the MTU
settings are now correct and curl works fine. I also confirmed it
allowed cloud-init to run and fully complete the boot process:
https://pastebin.ubuntu.com/p/KfcP7wmjjV/
There are no cloud-init errors:
https://pastebin.ubuntu.com/p/jtkTWkDGVN/
https://pastebin.ubuntu.com/p/vZSyTJ3RsH/
All I noticed was a delay / hang during dhcp probe, followed by a
timeout and it worked in the first retry:
https://pastebin.ubuntu.com/p/hXWKYCypXM/
Overall, everything worked well.
--
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/2056194
Title:
Networking broken in early boot on Oracle Native instances
Status in cloud-images:
New
Status in cloud-init package in Ubuntu:
New
Status in initramfs-tools package in Ubuntu:
New
Bug description:
BACKGROUND:
cloud-init-local.service runs before networking has started. On non-
Oracle platforms, before networking has come up, cloud-init will
create an ephemeral connection to the cloud's IMDS using DHCP to
retrieve instance metadata. On Oracle, this normally isn't necessary
as we boot with connectivity to the IMDS out of the box. This can be
seen in the following Jammy instance using an SR-IOV NIC:
2024-03-05 14:09:05,351 - url_helper.py[DEBUG]: [0/1] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'timeout': 5.0, 'headers': {'User-Agent'
: 'Cloud-Init/23.3.3-0ubuntu0~22.04.1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-05 14:09:05,362 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 2663b) after 1 attempts
2024-03-05 14:09:05,362 - ephemeral.py[DEBUG]: Skip ephemeral DHCP setup,
instance has connectivity to {'url': 'http://169.254.169.254/opc/v2/instance/',
'headers': {'Authorization': 'Bearer Oracle'}, 'timeout': 5}
2024-03-05 14:09:05,362 - url_helper.py[DEBUG]: [0/3] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'headers': {'User-Agent': 'Cloud-Init/23
.3.3-0ubuntu0~22.04.1', 'Authorization': 'Bearer Oracle'}} configuration
2024-03-05 14:09:05,368 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 2663b) after 1 attempts
Notice the "Skip ephemeral DHCP setup, instance has connectivity".
This means that cloud-init has determined that it already has
connectivity and doesn't need to do any additional setup to retrieve
data from the IMDS.
We can also see the same behavior on a Noble paravirtualized instance:
2024-03-01 20:51:33,482 - url_helper.py[DEBUG]: [0/1] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'timeout': 5.0, 'headers': {'User-Agent':
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-01 20:51:33,488 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 3067b) after 1 attempts
2024-03-01 20:51:33,488 - ephemeral.py[DEBUG]: Skip ephemeral DHCP setup,
instance has connectivity to {'url': 'http://169.254.169.254/opc/v2/instance/',
'headers': {'Authorization': 'Bearer Oracle'}, 'timeout': 5}
2024-03-01 20:51:33,489 - url_helper.py[DEBUG]: [0/3] open
'http://169.254.169.254/opc/v2/instance/' with {'url':
'http://169.254.169.254/opc/v2/instance/', 'stream': False, 'allow_redirects':
True, 'method': 'GET', 'headers': {'User-Agent':
'Cloud-Init/24.1~7g54599148-0ubuntu1', 'Authorization': 'Bearer Oracle'}}
configuration
2024-03-01 20:51:33,500 - url_helper.py[DEBUG]: Read from
http://169.254.169.254/opc/v2/instance/ (200, 3067b) after 1 attempts
2024-03-01 20:51:33,501 - util.py[DEBUG]: Writing to
/run/cloud-init/cloud-id-oracle - wb: [644] 7 bytes
PROBLEM:
On a Noble instance using Hardware-assisted (SR-IOV) networking, this
is not working. cloud-init-local.service no longer has immediate
connectivity to the IMDS. Since it cannot connect, in then attempts to
create an ephemeral connection to the IMDS using DHCP. It is able to
obtain a DHCP lease, but then when it tries to connect to the IMDS,
the call just hangs. The call has no timeout, so this results in an
instance that cannot be logged into even via the serial console
because cloud-init is blocking the rest of boot. A simple cloud-init
workaround is to add something along the lines of `timeout=2` to
https://github.com/canonical/cloud-
init/blob/main/cloudinit/sources/DataSourceOracle.py#L349 . This
allows cloud-init to boot. Looking at the logs, we can see that cloud-
init is unable to connect to the IMDS:
2024-03-05
[Touch-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
Sorry for the late feedback, but sharing here: AWS docs regarding best practices regarding cpu-starvation [1] do not recommend disabling the irqbalance service. Quoting the doc: > "Note: we do not recommend disabling irqbalance service. ENA driver doesn’t provide affinity hints, and if device reset happens while irqbalance is disabled, this might cause undesirable IRQ distribution with multiple IRQs landing on the same CPU core." Other customers that have hit issues with irqbalance were running very specific workloads and were aware of the need to turn it off, so we would prefer to keep irqbalance. [1] https://github.com/amzn/amzn- drivers/blob/master/kernel/linux/ena/ENA_Linux_Best_Practices.rst#cpu- starvation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in Ubuntu on IBM z Systems: Confirmed Status in irqbalance package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hi Nafees, I discussed this with Mitchell and we are still looking into
the best possible way to move forward with this SRU. We'll keep this bug
update as soon as we have some more details to share.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
Won't Fix
Status in python2.7 source package in Jammy:
Won't Fix
Status in python2.7 source package in Kinetic:
Won't Fix
Status in python2.7 source package in Lunar:
Won't Fix
Status in python2.7 source package in Mantic:
Won't Fix
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 228077] Re: libgtk2 immodules has cedilla disabled in en locales
*** This bug is a duplicate of bug 518056 *** https://bugs.launchpad.net/bugs/518056 I was on 18.04 and that was not an issue for me. Using US intl. alt. keyboard I could always get ç (cedilha). Now that I've upgrade to 23.04, this problem came back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/228077 Title: libgtk2 immodules has cedilla disabled in en locales Status in gnome-control-center: Confirmed Status in GTK+: Invalid Status in gnome-control-center package in Ubuntu: Triaged Status in gtk+2.0 package in Ubuntu: Invalid Status in gnome-control-center package in Fedora: Won't Fix Bug description: Binary package hint: libgtk2.0-0 philsf@philsf-laptop:~$ lsb_release -rd Description: Ubuntu 8.04 Release: 8.04 philsf@philsf-laptop:~$ apt-cache policy libgtk2.0-0 libgtk2.0-0: Installed: 2.12.9-3ubuntu3 One can't use dead keys to input a c+cedilla in en_US (probably other en_* locales). I had this on Gutsy. Now in Hardy, I thought I should report, since it's annoying, and the fix is documented. Steps to reproduce: - enable deadkeys - Open gnome-terminal (or firefox) and enter ' + c What you should get: ç What you do get: ć Fix (got from http://ubuntuforums.org/showthread.php?p=3652628 ): Edit /usr/lib/gtk-2.0/2.10.0/immodule-files.d/libgtk2.0-0.immodules, and include ":en" in the cedilla line 6c6 < "cedilla" "Cedilla" "gtk20" "/usr/share/locale" "az:ca:co:fr:gv:oc:pt:sq:tr:wa" --- > "cedilla" "Cedilla" "gtk20" "/usr/share/locale" "az:ca:co:fr:gv:oc:pt:sq:tr:wa:en" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/228077/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hi Steve,
Would you and the SRU team reconsider the "won't fix" decision or
further elaborate on the regression problem, based on the comment above?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
Won't Fix
Status in python2.7 source package in Jammy:
Won't Fix
Status in python2.7 source package in Kinetic:
Won't Fix
Status in python2.7 source package in Lunar:
Won't Fix
Status in python2.7 source package in Mantic:
Won't Fix
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Another suggestion from one of our Engineers is that you can also set it
inside your python script, something like this:
```
from setuptools import setup, Extension
import sysconfig
extra_flags=sysconfig.get_config_var('CFLAGS').split()
setup(
name="test",
ext_modules=[Extension("test", sources=["testmodule.c"],
extra_compile_args=extra_flags
)],
zip_safe=False
)
```
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
Won't Fix
Status in python2.7 source package in Jammy:
Won't Fix
Status in python2.7 source package in Kinetic:
Won't Fix
Status in python2.7 source package in Lunar:
Won't Fix
Status in python2.7 source package in Mantic:
Won't Fix
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Alright, thanks for the information @Steve.
Hi @Nafees,
With the information above, it seems there's a regression risk if we fix
this bug in python2.7 in Focal, and the risk outstands the benefits of
the fix, as it seems to be an uncommon use-case and there's a workaround
for it, so we wouldn't be able to apply the patch.
As a workaround, you can:
1. Export the desired CFLAGS in ~/.bashrc:
i.e.:
export CFLAGS="-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g -fdebug-prefix-
map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. -fstack-protector-strong
-Wformat -Werror=format-security"
2. Source .bashrc and compile:
ubuntu@ip-172-31-43-65:~/testprog$ source ~/.bashrc
ubuntu@ip-172-31-43-65:~/testprog$ python2 setup.py build_ext --inplace
running build_ext
building 'test' extension
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -fno-strict-aliasing
-DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
creating build/lib.linux-aarch64-2.7
aarch64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv
-O2 -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security
-Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv
-O2 -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
build/temp.linux-aarch64-2.7/testmodule.o -o build/lib.linux-aarch64-2.7/test.so
copying build/lib.linux-aarch64-2.7/test.so ->
3. You will have the desired CFLAGS:
ubuntu@ip-172-31-43-65:~/testprog$ strings build/lib.linux-aarch64-2.7/test.so
| grep -- -O
GNU C17 9.4.0 -mlittle-endian -mabi=lp64 -g -g -O2 -fno-strict-aliasing -fwrapv
-fstack-protector-strong -fPIC -fasynchronous-unwind-tables
-fstack-protector-strong -fstack-clash-protection
Would that work for you moving forward?
Regards,
Fabio Martins
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
Won't Fix
Status in python2.7 source package in Jammy:
Won't Fix
Status in python2.7 source package in Kinetic:
Won't Fix
Status in python2.7 source package in Lunar:
Won't Fix
Status in python2.7 source package in Mantic:
Won't Fix
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubunt
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
It's also worth mentioning that, a patch was backported mentioning "#
DP: Allow setting BASECFLAGS, OPT and EXTRA_LDFLAGS (like, CC, CXX, CPP,
CFLAGS, CPPFLAGS, CCSHARED, LDSHARED) from the environment." [1], but
then OPT is not being added at all by the patch (which had just
mentioned adding it), which seems to point that this is a bug.
https://git.launchpad.net/ubuntu/+source/python2.7/tree/debian/patches/distutils-
sysconfig.diff?h=applied/ubuntu/focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
Won't Fix
Status in python2.7 source package in Jammy:
Won't Fix
Status in python2.7 source package in Kinetic:
Won't Fix
Status in python2.7 source package in Lunar:
Won't Fix
Status in python2.7 source package in Mantic:
Won't Fix
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hi Steve,
Thanks for looking into this SRU request.
Their original request was specifically to python2.7 on Ĵammy, which
matches your comment on the eligible releases.
The request is not to rebuild the python extensions, but to fix the
compiler so new modules getting compiled will inherit the right flags.
Based on the description and the proposed patches, this seems to be a
legitimate bug, so shouldn't we fix this? Especially considering that
Focal still have a long lifecycle ahead.
Also, if the issue is that python2.7 is in universe, can't we fix this
through esm-apps?
Regards,
Fabio Martins
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
Won't Fix
Status in python2.7 source package in Focal:
Won't Fix
Status in python2.7 source package in Jammy:
Won't Fix
Status in python2.7 source package in Kinetic:
Won't Fix
Status in python2.7 source package in Lunar:
Won't Fix
Status in python2.7 source package in Mantic:
Won't Fix
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hi Nafees,
I've discussed this case with our Engineering team and they are working
on the SRU process to get this fix released, however this should take
around 1 month before it gets published to -updates. Although we are
prioritizing it, the fix still needs to go to the -proposed repository
for QA / testing, before completing the SRU process, hence why the 1
month estimate (assuming that it doesn't hit a regression, that might
delay things a bit more).
In the meantime, if a user is being impacted, although not really
supported, they could modify the sysconfig.py file to "manually" fix it
with the steps below:
1) open the following file: /usr/lib/python2.7/distutils/sysconfig.py
2) change the following lines:
(cc, cxx, cflags, extra_cflags, basecflags,
ccshared, ldshared, so_ext, ar, ar_flags,
configure_cppflags, configure_cflags, configure_ldflags) = \
get_config_vars('CC', 'CXX', 'CFLAGS', 'EXTRA_CFLAGS', 'BASECFLAGS',
'CCSHARED', 'LDSHARED', 'SO', 'AR', 'ARFLAGS',
'CONFIGURE_CPPFLAGS', 'CONFIGURE_CFLAGS', 'CONFIGURE_LDFLAGS')
To:
(cc, cxx, cflags, extra_cflags, basecflags,
ccshared, ldshared, so_ext, ar, ar_flags,
configure_cppflags, configure_cflags, configure_ldflags, opt) = \
get_config_vars('CC', 'CXX', 'CFLAGS', 'EXTRA_CFLAGS', 'BASECFLAGS',
'CCSHARED', 'LDSHARED', 'SO', 'AR', 'ARFLAGS',
'CONFIGURE_CPPFLAGS', 'CONFIGURE_CFLAGS', 'CONFIGURE_LDFLAGS', 'OPT')
3) change the following lines:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags, extra_cflags)
if x)
ldshared = ldshared + ' ' + configure_cflags
if 'CPPFLAGS' in os.environ:
To:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, opt ,configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
if 'CPPFLAGS' in os.environ:
4) Thats it! After these changes the optimization should work fine on
ARM as well as x86
Note: watch out for the indentation! Make sure the indentation is the
same line per line as the line being replaced.
Please, let me know if this helps.
Regards,
Fabio Martins
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
In Progress
Status in python2.7 source package in Bionic:
In Progress
Status in python2.7 source package in Focal:
In Progress
Status in python2.7 source package in Jammy:
In Progress
Status in python2.7 source package in Kinetic:
In Progress
Status in python2.7 source package in Lunar:
In Progress
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure
[Touch-packages] [Bug 2008699] Re: fwupd-refresh.service always fails after hibernate
> BTW - fwupd already uses network-online.target for this unit. One could probably argue this is a systemd bug. Where? /usr/lib/systemd/system/fwupd-refresh.service only has After=network.target. Perhaps that'd be the fix. -- 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/2008699 Title: fwupd-refresh.service always fails after hibernate Status in fwupd package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: fwupd-refresh.service unit is set to After=network.target, however, in practice, the following happens: - Desktop is active, NetworkManager is connected. - Machine is hibernated. - On wakeup, systemd will start NetworkManager then fwupd-refresh.service. There's however, a race condition there: - NetworkManager starts first. - fwupd-refresh.service is started BEFORE NetworkManager has enough time to reconnect to network. - fwupd-refresh.service fails due to lack of network. - NetworkManager connects to network a couple seconds later. The following journal logs illustrate that: Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.0438] device (wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown kernel: r8169 :06:00.0 enp6s0: Link is Down Feb 27 11:27:27 brown fwupd[2459754]: 11:27:27:0099 GLib-GObject value "1818326128" of type 'guint' is invalid or out of range for property 'kind' of type 'guint' Feb 27 11:27:27 brown acpid[2037]: client connected from 4266[0:0] Feb 27 11:27:27 brown acpid[2037]: 1 client rule loaded Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2354] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2355] manager: NetworkManager state is now CONNECTED_LOCAL Feb 27 11:27:27 brown systemd[1]: man-db.service: Deactivated successfully. Feb 27 11:27:27 brown systemd[1]: Finished Daily man-db regeneration. Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2943] device (wlp5s0): supplicant interface state: internal-starting -> disconnected Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2943] device (p2p-dev-wlp5s0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2947] Wi-Fi P2P device controlled by interface wlp5s0 created Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2949] manager: (p2p-dev-wlp5s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/232) Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2951] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2953] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2956] device (p2p-dev-wlp5s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Feb 27 11:27:27 brown dbus-daemon[2047]: [system] Successfully activated service 'org.freedesktop.fwupd' Feb 27 11:27:27 brown systemd[1]: Starting Update APT News... Feb 27 11:27:27 brown systemd[1]: Started Firmware update daemon. Feb 27 11:27:27 brown systemd[1]: Starting Update the local ESM caches... Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.743: Emitting ::status-changed() [idle] Feb 27 11:27:27 brown fwupdmgr[2459622]: Updating lvfs Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.750: downloading https://cdn.fwupd.org/downloads/firmware.xml.gz.jcat Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.751: Emitting ::status-changed() [downloading] Feb 27 11:27:27 brown fwupdmgr[2459622]: Downloading…: 0% Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.751: Emitting ::status-changed() [idle] Feb 27 11:27:27 brown systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE Feb 27 11:27:27 brown systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Feb 27 11:27:27 brown systemd[1]: Failed to start Refresh fwupd metadata and update motd. Feb 27 11:27:27 brown systemd[1]: apt-news.service: Deactivated successfully. Feb 27 11:27:27 brown systemd[1]: Finished Update APT News. Feb 27 11:27:28 brown wpa_supplicant[2114]: wlp5s0: Reject scan trigger since one is already pending Feb 27 11:27:29 brown ModemManager[2147]: [base-manager] couldn't check support for device
[Touch-packages] [Bug 2008699] Re: fwupd-refresh.service always fails after hibernate
https://github.com/fwupd/fwupd/issues/5590 ** Bug watch added: github.com/fwupd/fwupd/issues #5590 https://github.com/fwupd/fwupd/issues/5590 -- 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/2008699 Title: fwupd-refresh.service always fails after hibernate Status in fwupd package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: fwupd-refresh.service unit is set to After=network.target, however, in practice, the following happens: - Desktop is active, NetworkManager is connected. - Machine is hibernated. - On wakeup, systemd will start NetworkManager then fwupd-refresh.service. There's however, a race condition there: - NetworkManager starts first. - fwupd-refresh.service is started BEFORE NetworkManager has enough time to reconnect to network. - fwupd-refresh.service fails due to lack of network. - NetworkManager connects to network a couple seconds later. The following journal logs illustrate that: Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.0438] device (wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown kernel: r8169 :06:00.0 enp6s0: Link is Down Feb 27 11:27:27 brown fwupd[2459754]: 11:27:27:0099 GLib-GObject value "1818326128" of type 'guint' is invalid or out of range for property 'kind' of type 'guint' Feb 27 11:27:27 brown acpid[2037]: client connected from 4266[0:0] Feb 27 11:27:27 brown acpid[2037]: 1 client rule loaded Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2354] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2355] manager: NetworkManager state is now CONNECTED_LOCAL Feb 27 11:27:27 brown systemd[1]: man-db.service: Deactivated successfully. Feb 27 11:27:27 brown systemd[1]: Finished Daily man-db regeneration. Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2943] device (wlp5s0): supplicant interface state: internal-starting -> disconnected Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2943] device (p2p-dev-wlp5s0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2947] Wi-Fi P2P device controlled by interface wlp5s0 created Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2949] manager: (p2p-dev-wlp5s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/232) Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2951] device (p2p-dev-wlp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2953] device (wlp5s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed') Feb 27 11:27:27 brown NetworkManager[2048]: [1677497247.2956] device (p2p-dev-wlp5s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed') Feb 27 11:27:27 brown dbus-daemon[2047]: [system] Successfully activated service 'org.freedesktop.fwupd' Feb 27 11:27:27 brown systemd[1]: Starting Update APT News... Feb 27 11:27:27 brown systemd[1]: Started Firmware update daemon. Feb 27 11:27:27 brown systemd[1]: Starting Update the local ESM caches... Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.743: Emitting ::status-changed() [idle] Feb 27 11:27:27 brown fwupdmgr[2459622]: Updating lvfs Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.750: downloading https://cdn.fwupd.org/downloads/firmware.xml.gz.jcat Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.751: Emitting ::status-changed() [downloading] Feb 27 11:27:27 brown fwupdmgr[2459622]: Downloading…: 0% Feb 27 11:27:27 brown fwupdmgr[2459622]: (fwupdmgr:2459622): Fwupd-DEBUG: 11:27:27.751: Emitting ::status-changed() [idle] Feb 27 11:27:27 brown systemd[1]: fwupd-refresh.service: Main process exited, code=exited, status=1/FAILURE Feb 27 11:27:27 brown systemd[1]: fwupd-refresh.service: Failed with result 'exit-code'. Feb 27 11:27:27 brown systemd[1]: Failed to start Refresh fwupd metadata and update motd. Feb 27 11:27:27 brown systemd[1]: apt-news.service: Deactivated successfully. Feb 27 11:27:27 brown systemd[1]: Finished Update APT News. Feb 27 11:27:28 brown wpa_supplicant[2114]: wlp5s0: Reject scan trigger since one is already pending Feb 27 11:27:29 brown ModemManager[2147]: [base-manager] couldn't check support for device '/sys/devices/pci:00/:00:01.2/:02:00.0/:03:04.0/:05:00.0': not supported by any plugin Feb 27 11:27:29
[Touch-packages] [Bug 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04
My error is quite annoying to, already the hotspot work on the SO, the activated the wifi and detect the wifi, but when my cellphone connected to the hotspot assigned a public ip, for been exactly assigned by default the DHCP the ip 10.42.0.189 with a mask subred 255.255.255.0, but the computer than is working like service DHCP already had 192.168.1.56, i'm undestand if this hotspot is working like a bridge appliance, but, this time didnt is the case, because the default router has the 192.168.1.254, so the subred mask of the segment of the red is from 192.168.1.0 - 192.168.1.255 wtf, why assign me a public IP, jajajaj, i will send the evidence. ** Attachment added: "hotspot problem2.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+attachment/5644473/+files/hotspot%20problem2.png -- 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/1971538 Title: My machine has Wi-Fi Hotspot broken after upgrade to 22.04 Status in network-manager package in Ubuntu: Confirmed Bug description: * Impact The hotspot feature fails to forward the data to the clients * Test case - log into an Ubuntu or GNOME session - connect the machine to an eth cable for internet - go to gnome-control-center -> wifi - enable the hotspot from the menu in the headerbar - connect another device to the wifi created -> the client should connect and access to internet work correctly Upon updating to 22.04, none of my machines can use the connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
@Nafees,
I'm sorry, I hadn't noticed that the file produced by python3 was
different (and I did have the test.so in my directory because I had
built it with python2 before, so I was just grepping the same file). I
see the problem now and I'm checking it with our Engineering team.
Regards,
Fabio Martins
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
New
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hi Nafees,
Thank you for the reproducer and instructions.
Per your comments, I would expect this to work well with python3 on
20.04, however, my tests indicated that python2 and python3 are both
behaving the same way. In the example below, I'm using python3 and I
also don't see the -O2 optimization:
ubuntu@ip-172-31-80-78:~/python-bug/testprog-python3-pip$ python3 setup.py
build_ext --inplace
running build_ext
building 'test' extension
creating build/temp.linux-aarch64-3.8
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security
-g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c testmodule.c
-o build/temp.linux-aarch64-3.8/testmodule.o
creating build/lib.linux-aarch64-3.8
aarch64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-Bsymbolic-functions
-Wl,-z,relro -g -fwrapv -O2 -g -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
build/temp.linux-aarch64-3.8/testmodule.o -o
build/lib.linux-aarch64-3.8/test.cpython-38-aarch64-linux-gnu.so
copying build/lib.linux-aarch64-3.8/test.cpython-38-aarch64-linux-gnu.so ->
ubuntu@ip-172-31-80-78:~/python-bug/testprog-python3-pip$ strings
test.so | grep -- -O
(output from the command above was empty)
On the other hand, I do see the -O2 with python2 in a 22.04 instance.
Can you clarify if this is the same for you and, if not, provide some
details on versions being used?
Regards,
Fabio Martins
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
New
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch t
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hello Nafees,
Can you share this setup.py that we can use to reproduce the problem and
investigate?
Regards,
Fabio Martins
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
New
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 1989618] [NEW] [Feature Request] Include support for LACP bonds in initramfs
Public bug reported: Feature Request: When installing a system over the network using live installer (subiquity), you can use the kernel cmdline option ip= [1] to provide the network configuration. In certain situations, it would be ideal to be able to configure a lacp bond during this process. Sometimes the network ports on the switch are configured with lacp bond (802.3ad) and the switch won't let an interface be brought up unless it sends lacpdus. I've discussed this through a subiquity bug [2] and it was mentioned that there doesn't seem to be any support in our initramfs for LACP bonds [3]. It was requested for a new bug to be filed at the initramfs- tools project for such functionality to get included. I don't have any use case at the moment, but I've received this request in the past when the customer was still using debian installer. For debian-installer this was once discussed via a debian bug [4] and a patch was proposed [5], but this was never accepted / merged. Considering that Tte new installer is an _entirely_ different codebase than d-i, the lacp support would have to come from the initramfs. [1] ip=: [2] https://bugs.launchpad.net/subiquity/+bug/1988480 [3] https://bugs.launchpad.net/subiquity/+bug/1988480/comments/17 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611250 [5] https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=611250;filename=bonding_v2.patch;msg=39 ** Affects: initramfs-tools (Ubuntu) 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/1989618 Title: [Feature Request] Include support for LACP bonds in initramfs Status in initramfs-tools package in Ubuntu: New Bug description: Feature Request: When installing a system over the network using live installer (subiquity), you can use the kernel cmdline option ip= [1] to provide the network configuration. In certain situations, it would be ideal to be able to configure a lacp bond during this process. Sometimes the network ports on the switch are configured with lacp bond (802.3ad) and the switch won't let an interface be brought up unless it sends lacpdus. I've discussed this through a subiquity bug [2] and it was mentioned that there doesn't seem to be any support in our initramfs for LACP bonds [3]. It was requested for a new bug to be filed at the initramfs-tools project for such functionality to get included. I don't have any use case at the moment, but I've received this request in the past when the customer was still using debian installer. For debian-installer this was once discussed via a debian bug [4] and a patch was proposed [5], but this was never accepted / merged. Considering that Tte new installer is an _entirely_ different codebase than d-i, the lacp support would have to come from the initramfs. [1] ip=: [2] https://bugs.launchpad.net/subiquity/+bug/1988480 [3] https://bugs.launchpad.net/subiquity/+bug/1988480/comments/17 [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611250 [5] https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=611250;filename=bonding_v2.patch;msg=39 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1989618/+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 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I've also updated the [Test Plan] section of the bug description
** Description changed:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
+
+ - Check that the ipconfig utility is able to obtain an IP through dhcp:
+
+ # ip l set dev ens9 down
+ # date; /usr/lib/klibc/bin/ipconfig ens9; date
+
+ - Check if it respects the timeout (i.e. 2 seconds in the example
+ below):
+
+ # ip l set dev ens9 down
+ # date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date
+
+ - The original issue is that timeout is being ignored when not receiving
+ any reply from a DHCP Server, so for this test you have to stop your
+ DHCP Server (i.e. dnsmasq) and then test the timeouts:
+
+ # ip l set dev ens9 down
+ # date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date
+
+ # ip l set dev ens9 down
+ # date; /usr/lib/klibc/bin/ipconfig -t 5 ens9; date
+
+ Make sure it times out respectivelly in 2 and 5 seconds.
[racb: pending agreement with the SRU team; please see comment 37]
Any situation where ipconfig encounters an error sending the DHCP
packet, it will automatically set a delay of 10 seconds, which could be
longer than the user-specified timeout. It can be reproduced by creating
a dummy interface and attempting to run ipconfig on it with a timeout
value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again later"
at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end up
extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had
actually waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually used
never exceeds the user-specified timeout.
[ Regression potential ]
This change ensures that user-specified timeouts are never exceeded, which is
a problem that appears to happen only in case of interface errors.
It may be that someone is relying on current behaviour where they receive
DHCP offers after their specified timeout (but within the 10-second error
timeout). However, 1) that is buggy behaviour and should be exposed. Such a
user would need to update their specified timeout to make it long enough to
receive the DHCP offer (setting the timeout to 10 would keep the existing
behaviour). 2) I think it is unlikely that such a scenario exists at all. The
10-second timeout problem happens when
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Hello Robie,
I've validated that the package from -proposed works well, testing in my
VM based environment. I haven't tested it on Oracle bare metal (where
the original issue happened) as that is a type of instance hard to get
access to. Given that the test packages had proven to fix the original
problem that we were targetting to address, I believe the package from
-proposed should also work well. Let me know if it is necessary to also
test that it addresses the original issue with Oracle BM host and I'll
get access to one and validate.
Regarding your question below:
> ...would it be practical and/or useful to verify that, with a timeout
of 2s, a DHCP reply sent after 1.5s works, but a DHCP reply sent after
2.5s does not?
That has been addressed in comment #30 (and now also in #39 with the
package from -proposed).
Regarding your question if upstream had accepted the patch, I would have
to defer that to Khaled, but I also agree that it seems a deliberate
upstream design decision not to accept it.
Regarding your comment below:
> In Ubuntu, we might decide to maintain the patch as a delta but then
drop that delta in subsequent releases when we no longer need that
functionality.
That is indeed just needed for Bionic. To confirm/clarify my
understanding, if this moves to -updates, in theory this is not going to
be reverted (from Bionic) in the future, right? Once it lands there, it
is expected that any newer klibc-utils packages that gets released to
Bionic will continue to carry this patch?
Thank you in advance!
Regards,
Fabio Martins
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
Won't Fix
Status in klibc source package in Bionic:
Fix Committed
Bug description:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
[racb: pending agreement with the SRU team; please see comment 37]
Any situation where ipconfig encounters an error sending the DHCP
packet, it will automatically set a delay of 10 seconds, which could
be longer than the user-specified timeout. It can be reproduced by
creating a dummy interface and attempting to run ipconfig on it with a
timeout value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_t
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I've tested the package from -proposed and I can confirm it fixes the problem: Installed from -proposed: root@ubuntu:~# apt-cache policy klibc-utils klibc-utils: Installed: 2.0.4-9ubuntu2.2 Candidate: 2.0.4-9ubuntu2.18.04.1 Version table: 2.0.4-9ubuntu2.18.04.1 500 500 http://ppa.launchpad.net/mfo/lp1947099/ubuntu bionic/main amd64 Packages *** 2.0.4-9ubuntu2.2 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 2.0.4-9ubuntu2.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 2.0.4-9ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages Working well without timeout: root@ubuntu:~# ip l set dev ens9 down root@ubuntu:~# date; /usr/lib/klibc/bin/ipconfig ens9; date Thu May 12 12:54:48 UTC 2022 IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP IP-Config: ens9 complete (dhcp from 192.168.150.2): address: 192.168.150.105 broadcast: 192.168.150.255 netmask: 255.255.255.0 gateway: 192.168.150.1dns0 : 192.168.150.2dns1 : 0.0.0.0 domain : sts.lab rootserver: 192.168.150.2 rootpath: filename : Thu May 12 12:55:01 UTC 2022 Timeout being honored: root@ubuntu:~# ip l set dev ens9 down root@ubuntu:~# date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date Thu May 12 12:55:44 UTC 2022 IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP Lowered timeout to match user request = (2 s) IP-Config: no response after 2 secs - giving up Thu May 12 12:55:46 UTC 2022 Testing the original issue (timeout being ignored when not receiving any reply from a DHCP Server), which is now also getting honored: root@ubuntu:~# ip l set dev ens9 down root@ubuntu:~# date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date Thu May 12 12:56:32 UTC 2022 IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP Lowered timeout to match user request = (2 s) IP-Config: no response after 2 secs - giving up Thu May 12 12:56:34 UTC 2022 root@ubuntu:~# ip l set dev ens9 down root@ubuntu:~# date; /usr/lib/klibc/bin/ipconfig -t 5 ens9; date Thu May 12 12:56:43 UTC 2022 IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP Lowered timeout to match user request = (5 s) IP-Config: no response after 5 secs - giving up Thu May 12 12:56:48 UTC 2022 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1947099 Title: ipconfig does not honour user-requested timeouts in some cases Status in klibc package in Ubuntu: Won't Fix Status in klibc source package in Bionic: Fix Committed Bug description: [Impact] In some cases, ipconfig can take a longer time than the user-specified timeouts, causing unexpected delays. [Test Plan] [racb: pending agreement with the SRU team; please see comment 37] Any situation where ipconfig encounters an error sending the DHCP packet, it will automatically set a delay of 10 seconds, which could be longer than the user-specified timeout. It can be reproduced by creating a dummy interface and attempting to run ipconfig on it with a timeout value of less than 10: # ip link add eth1 type dummy # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date Thu Nov 18 04:46:13 EST 2021 IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP IP-Config: no response after 2 secs - giving up Thu Nov 18 04:46:23 EST 2021 ^ Notice above, ipconfig thinks that it waited 2 seconds, but the timestamps show an actual delay of 10 seconds. [Where problems could occur] Please see reproduction steps above. We are seeing this in production too (see comment #2). [Other Info] A patch to fix the issue is being proposed here. It is a safe fix - it only checks before going into sleep that the timeout never exceeds the user-requested value. [Original Description] In some cases, ipconfig can take longer than the user-specified timeouts, causing unexpected delays. in main.c, in function loop(), the process can go into process_timeout_event() (or process_receive_event() ) and if it encounters an error situation, will set an attempt to "try again later" at time equal now + 10 seconds by setting s->expire = now + 10; This can happen at any time during the main event loop, which can end up extending the user-specified timeout if "now + 10" is greater than "start_time + user-specified-timeout". I believe a patch like the following is needed to avoid this problem: --- a/usr/kinit/ipconfig/main.c +++ b/usr/kinit/ipconfig/main.c @@ -437,6 +437,13 @@ static int loop(void) if (timeout > s->expire - now.tv_sec)
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Should this bug be changed to Fix Committed at this point?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
New
Status in klibc source package in Bionic:
Incomplete
Bug description:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
Any situation where ipconfig encounters an error sending the DHCP packet, it
will automatically set a delay of 10 seconds, which could be longer than the
user-specified timeout. It can be reproduced by creating a dummy interface and
attempting to run ipconfig on it with a timeout value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had
actually waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually
used never exceeds the user-specified timeout.
[ Regression potential ]
This change ensures that user-specified timeouts are never exceeded, which is
a problem that appears to happen only in case of interface errors.
It may be that someone is relying on current behaviour where they receive
DHCP offers after their specified timeout (but within the 10-second error
timeout). However, 1) that is buggy behaviour and should be exposed. Such a
user would need to update their specified timeout to make it long enough to
receive the DHCP offer (setting the timeout to 10 would keep the existing
behaviour). 2) I think it is unlikely that such a scenario exists at all. The
10-second timeout problem happens when there are problems with the interface
that prevent it from even sending out the DHCP request. I think it is very
unlikely (or even, impossible) that DHCP offers would be received on a dead
interface.
Based on the above points, I consider the regression potential to be
very low for this change. I do not expect anyone who is currently
using ipconfig successfully to notice this change.
I believe the only difference introduced by this is the reduction of
delays caused by dead or problematic network interfaces. Those error
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I've tested the new patch from ppa:mfo/lp1947099v2 and I can confirm it
resolves the problem:
- Without the patch:
https://pastebin.ubuntu.com/p/RksNcBGSzn/
It took 396,940865−220,447147 = 176,493718 seconds in the IP-Config section.
Total boot time:
ubuntu@gpu48-ubuntu18:~$ sudo systemd-analyze time
Startup finished in 4min 1.355s (firmware) + 2min 24.433s (loader) + 6min
8.464s (kernel) + 41.466s (userspace) = 13min 15.719s
graphical.target reached after 41.068s in userspace
- With the patch:
https://pastebin.ubuntu.com/p/46nVYCYyDZ/
It took 246,556749−212,019368 = 34,537381 seconds in the IP-Config
section. Total boot time:
ubuntu@gpu48-ubuntu18:~$ sudo systemd-analyze time
Startup finished in 4min 1.246s (firmware) + 2min 24.170s (loader) + 3min
42.915s (kernel) + 39.010s (userspace) = 10min 47.343s
graphical.target reached after 38.634s in userspace
ubuntu@gpu48-ubuntu18:~$ sudo apt-cache policy klibc-utils
klibc-utils:
Installed: 2.0.4-9ubuntu2.18.04.1
Candidate: 2.0.4-9ubuntu2.18.04.1
Version table:
*** 2.0.4-9ubuntu2.18.04.1 500
500 http://ppa.launchpad.net/mfo/lp1947099v2/ubuntu bionic/main amd64
Packages
100 /var/lib/dpkg/status
2.0.4-9ubuntu2.1 500
500 http://me-dubai-1-ad-1.clouds.archive.ubuntu.com/ubuntu
bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
2.0.4-9ubuntu2 500
500 http://me-dubai-1-ad-1.clouds.archive.ubuntu.com/ubuntu bionic/main
amd64 Packages
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
New
Status in klibc source package in Bionic:
Incomplete
Bug description:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
Any situation where ipconfig encounters an error sending the DHCP packet, it
will automatically set a delay of 10 seconds, which could be longer than the
user-specified timeout. It can be reproduced by creating a dummy interface and
attempting to run ipconfig on it with a timeout value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Thank you, Mauricio, for the build process details and for adding the
update here. I'm including some evidence of my tests showing that the
patch you suggested did work well:
Details of the build process:
https://pastebin.ubuntu.com/p/dmVWH2fxpy/
Test package installed:
https://pastebin.ubuntu.com/p/qxyWBGrm3P/
Working well without specifying a timeout:
https://pastebin.ubuntu.com/p/byftnFk33C/
Timeout is also being honored:
https://pastebin.ubuntu.com/p/spFsTRhXTz/
Testing the original issue (timeout being ignored when not receiving any reply
from a DHCP Server), which is now also getting honored:
https://pastebin.ubuntu.com/p/KHVRj7BdRw/
I'm working to get access to another instance to test that the boot time
optimiizations are still fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
New
Status in klibc source package in Bionic:
Incomplete
Bug description:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
Any situation where ipconfig encounters an error sending the DHCP packet, it
will automatically set a delay of 10 seconds, which could be longer than the
user-specified timeout. It can be reproduced by creating a dummy interface and
attempting to run ipconfig on it with a timeout value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had
actually waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually
used never exceeds the user-specified timeout.
[ Regression potential ]
This change ensures that user-specified timeouts are never exceeded, which is
a problem that appears to happen only in case of interface errors.
It may be that someone is relying on current behaviour where they receive
DHCP offers after their specified timeout (but within the 10-second error
timeout). However, 1) that is buggy behaviour and should be exposed. Such a
user would need to update their specified timeout to make it long enough to
receive the DHCP offer
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
@Łukasz / @Robie, do you think the above comments are enough to proceed
with this SRU?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
New
Status in klibc source package in Bionic:
Incomplete
Bug description:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
Any situation where ipconfig encounters an error sending the DHCP packet, it
will automatically set a delay of 10 seconds, which could be longer than the
user-specified timeout. It can be reproduced by creating a dummy interface and
attempting to run ipconfig on it with a timeout value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had
actually waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually
used never exceeds the user-specified timeout.
[ Regression potential ]
This change ensures that user-specified timeouts are never exceeded, which is
a problem that appears to happen only in case of interface errors.
It may be that someone is relying on current behaviour where they receive
DHCP offers after their specified timeout (but within the 10-second error
timeout). However, 1) that is buggy behaviour and should be exposed. Such a
user would need to update their specified timeout to make it long enough to
receive the DHCP offer (setting the timeout to 10 would keep the existing
behaviour). 2) I think it is unlikely that such a scenario exists at all. The
10-second timeout problem happens when there are problems with the interface
that prevent it from even sending out the DHCP request. I think it is very
unlikely (or even, impossible) that DHCP offers would be received on a dead
interface.
Based on the above points, I consider the regression potential to be
very low for this change. I do not expect anyone who is currently
using ipconfig successfully to notice this change.
I believe the only difference introduced by this is the reduction of
delays caused by dead or problematic
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I've tested the klibc-utils patch using Mauricio's ppa:
sudo add-apt-repository ppa:mfo/lp1947099
sudo apt install klibc-utils
sudo update-initramfs -u -k all
And I can confirm that it does improve the boot time in more than 3
minutes, without causing any noticeable issues.
- Without the patch:
https://pastebin.ubuntu.com/p/6M7M2FfCGQ/
root@ubuntu1804:~# sudo systemd-analyze time
Startup finished in 4min 2.098s (firmware) + 2min 23.684s (loader) + 6min 226ms
(kernel) + 38.766s (userspace) = 13min 4.776s
graphical.target reached after 38.374s in userspace
We can see it spent 6min 226ms in kernel, and looking through the serial
console (or dmesg) it was running the ipconfig commands for each of the
Mellanox NICs from 211.972259 up to 386.155116 = 174.182857 seconds
- With the patch:
https://pastebin.ubuntu.com/p/JxDs8WPqc4/
root@ubuntu1804:~# sudo systemd-analyze time
Startup finished in 4min 890ms (firmware) + 2min 23.278s (loader) + 3min
46.413s (kernel) + 40.734s (userspace) = 10min 51.317s
graphical.target reached after 40.354s in userspace
We can see the kernel time decreased to a bit more than 3 minutes and we
spent only 41 seconds (as opposed to 174 seconds) in the ipconfig
commands:
210.675050 to 252.432441 = 41.757391 seconds
That definitely has helped to resolve the issue we are chasing here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
New
Status in klibc source package in Bionic:
Incomplete
Bug description:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
Any situation where ipconfig encounters an error sending the DHCP packet, it
will automatically set a delay of 10 seconds, which could be longer than the
user-specified timeout. It can be reproduced by creating a dummy interface and
attempting to run ipconfig on it with a timeout value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had
actually waited for 10 seconds.
The suggested code-change ensures that the timeout that
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I tried using klibc-utils from the ppa (containing the patch):
root@ubuntu:~# sudo apt-cache policy klibc-utils
klibc-utils:
Installed: 2.0.4-9ubuntu2.18.04.1
Candidate: 2.0.4-9ubuntu2.18.04.1
Version table:
*** 2.0.4-9ubuntu2.18.04.1 500
500 http://ppa.launchpad.net/mfo/lp1947099/ubuntu bionic/main amd64
Packages
100 /var/lib/dpkg/status
2.0.4-9ubuntu2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
[1] But now when I try to obtain an IP using dhcp without specifying any
timeout, it dumps lots of "Lowered timeout to match user request"
messages. Is that expected?
https://pastebin.ubuntu.com/p/5Tpc5Rwdkq/
[2] Other than that, it worked well. We can see from the pastebin below
that the timeout is getting respected:
https://pastebin.ubuntu.com/p/TJbCzx7hFC/
[3] And also the main issue was the timeout being ignored when not receiving
any reply from a DHCP Server, which is now also getting honored:
https://pastebin.ubuntu.com/p/BvKk6fJJDc/
I will try to test this package in a OCI BM.GPU4.8 instance to see the
improvements with the main optimization, but it would be good to get
clarification on [1]
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1947099
Title:
ipconfig does not honour user-requested timeouts in some cases
Status in klibc package in Ubuntu:
New
Status in klibc source package in Bionic:
Incomplete
Bug description:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
Any situation where ipconfig encounters an error sending the DHCP packet, it
will automatically set a delay of 10 seconds, which could be longer than the
user-specified timeout. It can be reproduced by creating a dummy interface and
attempting to run ipconfig on it with a timeout value of less than 10:
# ip link add eth1 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
Thu Nov 18 04:46:13 EST 2021
IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
IP-Config: no response after 2 secs - giving up
Thu Nov 18 04:46:23 EST 2021
^ Notice above, ipconfig thinks that it waited 2 seconds, but the
timestamps show an actual delay of 10 seconds.
[Where problems could occur]
Please see reproduction steps above. We are seeing this in production too
(see comment #2).
[Other Info]
A patch to fix the issue is being proposed here. It is a safe fix - it only
checks before going into sleep that the timeout never exceeds the
user-requested value.
[Original Description]
In some cases, ipconfig can take longer than the user-specified
timeouts, causing unexpected delays.
in main.c, in function loop(), the process can go into
process_timeout_event() (or process_receive_event() ) and if it
encounters an error situation, will set an attempt to "try again
later" at time equal now + 10 seconds by setting
s->expire = now + 10;
This can happen at any time during the main event loop, which can end
up extending the user-specified timeout if "now + 10" is greater than
"start_time + user-specified-timeout".
I believe a patch like the following is needed to avoid this problem:
--- a/usr/kinit/ipconfig/main.c
+++ b/usr/kinit/ipconfig/main.c
@@ -437,6 +437,13 @@ static int loop(void)
if (timeout > s->expire - now.tv_sec)
timeout = s->expire - now.tv_sec;
+
+ /* Compensate for already-lost time */
+ gettimeofday(, NULL);
+ if (now.tv_sec + timeout > start + loop_timeout) {
+ timeout = loop_timeout - (now.tv_sec - start);
+ printf("Lowered timeout to match user request
= (%d s) \n", timeout);
+ }
}
I believe the current behaviour is buggy. This is confirmed when the
following line is executed:
if (loop_timeout >= 0 &&
now.tv_sec - start >= loop_timeout) {
printf("IP-Config: no response after %d "
"secs - giving up\n", loop_timeout);
rc = -1;
goto bail;
}
'loop_timeout' is the user-specified time-out. With a value of 2, in
case of error, this line prints:
IP-Config: no response after 2 secs - giving up
So it thinks that it waited 2 seconds - however, in reality it had
actually waited for 10 seconds.
The suggested code-change ensures that the timeout that is actually
used never exceeds the user-specified timeout.
[ Regression potential ]
This change ensures that user-specified timeouts are never
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
I've setup a Lab with dnsmasq acting as DHCP Server, which I can use the dhcp-reply-delay option to introduce a delay between the DHCPDISCOVER and DHCPOFFER, as in the example below: Mar 30 18:26:34 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPDISCOVER(ens3) 52:54:00:d7:10:13 Mar 30 18:26:34 focal-dhcpsrv dnsmasq-dhcp[2470]: 4195928115 reply delay: 3 Mar 30 18:26:37 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPOFFER(ens3) 192.168.150.119 52:54:00:d7:10:13 Just minor note that the delay only happens between DHCPDISCOVER and DHCPOFFER, but not between DHCPREQUEST and DHCPACK: Mar 30 18:22:13 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPREQUEST(ens3) 192.168.150.119 52:54:00:d7:10:13 Mar 30 18:22:13 focal-dhcpsrv dnsmasq-dhcp[2470]: DHCPACK(ens3) 192.168.150.119 52:54:00:d7:10:13 ubuntu So, if this is a new interface (new mac) looking for an IP, the delay will be added, but if this is an interface which was previously configured and is asking to re-use the same IP (DHCPREQUEST), there won't be any delays. I believe this Lab will help reproducing the issue with and without the proposed patch. 1. In a ideal scenario, where no delays were added (dhcp-reply-delay is commented out), ipconfig will take approximately to do its job: it sends a DHCPREQUEST, then DHCPDISCOVER and then another DHCPREQUEST in this process: - From the ipconfig perspective: root@ubuntu:/etc/dhcp# date; /usr/lib/klibc/bin/ipconfig ens9; date Wed Mar 30 19:25:44 UTC 2022 IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP IP-Config: ens9 complete (dhcp from 192.168.150.2): address: 192.168.150.105 broadcast: 192.168.150.255 netmask: 255.255.255.0 gateway: 192.168.150.1dns0 : 192.168.150.2dns1 : 0.0.0.0 domain : sts.lab rootserver: 192.168.150.2 rootpath: filename : Wed Mar 30 19:25:54 UTC 2022 - From the dhcp server perspective: Mar 30 19:25:45 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPREQUEST(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:25:45 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPACK(ens3) 192.168.150.105 52:54:00:f3:4e:0e ubuntu Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPDISCOVER(ens3) 52:54:00:f3:4e:0e Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPOFFER(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPREQUEST(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:25:54 focal-dhcpsrv dnsmasq-dhcp[2656]: DHCPACK(ens3) 192.168.150.105 52:54:00:f3:4e:0e 2. Adding a 5 seconds delay in dnsmasq (dhcp-reply-delay=5) and without enforcing a timeout in ipconfig: - From ipconfig perspective: root@ubuntu:/etc/dhcp# date; /usr/lib/klibc/bin/ipconfig ens9; date Wed Mar 30 19:34:09 UTC 2022 IP-Config: ens9 hardware address 52:54:00:f3:4e:0e mtu 1500 DHCP RARP IP-Config: ens9 complete (dhcp from 192.168.150.2): address: 192.168.150.105 broadcast: 192.168.150.255 netmask: 255.255.255.0 gateway: 192.168.150.1dns0 : 192.168.150.2dns1 : 0.0.0.0 domain : sts.lab rootserver: 192.168.150.2 rootpath: filename : Wed Mar 30 19:34:27 UTC 2022 - From the dhcpserver perspective: Mar 30 19:34:10 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPREQUEST(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:10 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPACK(ens3) 192.168.150.105 52:54:00:f3:4e:0e ubuntu Mar 30 19:34:19 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPDISCOVER(ens3) 52:54:00:f3:4e:0e Mar 30 19:34:19 focal-dhcpsrv dnsmasq-dhcp[2773]: 1004609631 reply delay: 5 Mar 30 19:34:24 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPOFFER(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:24 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPDISCOVER(ens3) 52:54:00:f3:4e:0e Mar 30 19:34:24 focal-dhcpsrv dnsmasq-dhcp[2773]: 1004609631 reply delay: 5 Mar 30 19:34:26 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPOFFER(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:26 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPDISCOVER(ens3) 52:54:00:f3:4e:0e Mar 30 19:34:26 focal-dhcpsrv dnsmasq-dhcp[2773]: 1004609631 reply delay: 5 Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPOFFER(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPREQUEST(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPACK(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPREQUEST(ens3) 192.168.150.105 52:54:00:f3:4e:0e Mar 30 19:34:28 focal-dhcpsrv dnsmasq-dhcp[2773]: DHCPACK(ens3) 192.168.150.105 52:54:00:f3:4e:0e It takes 18 seconds for the process to complete, as dnsmasq adds 3x 5 seconds delay in the process 3. Using the -t to specify a 15 seconds timeout (when the actual process takes 18 seconds): - From the ipconfig perspective: root@ubuntu:/etc/dhcp# date; /usr/lib/klibc/bin/ipconfig -t 15 ens9; date Wed Mar 30 19:37:11 UTC
[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases
Hi Robie, The user story here is about improving the time it takes to boot a Bionic instance on Oracle Cloud in a specific bare metal shape, called BM.GPU4.8. This is a pretty large instance, with 18x Ethernet controller [0200]: Mellanox Technologies MT28800 Family [ConnectX-5 Ex] [15b3:1019]: https://www.oracle.com/uk/cloud/compute/gpu.html Comparing the time it takes to boot Bionic with a CentOS instance we can see a big delta both in kernel and userspace: CentOS: Startup finished in 4min 3.548s (firmware) + 2min 23.525s (loader) + 3min 17.984s (kernel) + 1min 37.825s (initrd) + 38.723s (userspace) = 12min 1.608s multi-user.target reached after 38.714s in userspace Ubuntu: Startup finished in 4min 621ms (firmware) + 2min 23.174s (loader) + 7min 34.767s (kernel) + 5min 48.219s (userspace) = 19min 46.782s graphical.target reached after 5min 47.854s in userspace The userspace difference is a cloud-init problem that is being handled by other launchpad bugs. Here we are trying to focus on the kernel difference, which further was narrowed down to be related to klibc and it is what we are trying to address with this bug. Some details: Looking into details, here are the dmesg output from CentOS and Ubuntu, for kernel comparison: Ubuntu: https://pastebin.canonical.com/p/X7GFVjdV3b/ CentOS: https://pastebin.canonical.com/p/gNhFwJjyjw/ Looking there, one area that looks promising is around mlx5_core driver, where Ubuntu spends 218 seconds, while CentOS spends 44 seconds Khalid did a nice job investigating and found that the problem came from ipconfig from initramfs. Here are the details: The delay from the kernel side is due to the fact that every interface (18 in total) takes over 10 seconds each to initialize. The interfaces are brought up and used for DHCP as part of the iscsi initialization, during the initramfs stage. Specifically the script ```/usr/share/initramfs-tools/scripts/local-top/iscsi``` which is included in the initramfs and is installed as part of open-iscsi To initialize the network interfaces this script calls other helper functions that are part of the initramfs, specifically "configure_networking" in ```/usr/share/initramfs- tools/scripts/functions``` which is installed as part of initramfs- tools-core. The configure_networking function initializes networking by looping over all interfaces and issuing this call: ``` ipconfig -t 2 ``` where it is calling the ipconfig utility (part of klibc-utils) which also gets bundled in the initramfs. The -t 2 specifies a timeout of 2 seconds. This ipconfig tool attempts to perform DHCP on the given interface, within the specified timeout (always 2 seconds for each interface) Normally, ipconfig does not perform only one DHCP attempt - it performs multiple DHCP attempts, each attempt waiting for an exponentially increasing amount of time (1s, 2s, 4s, ..etc) up until the total amount of time has passed that is equal the user-specified timeout (2 in this case, so it should wait 1 second, followed by 1 second, for a total of 2 seconds). However, it appears ipconfig has a bug. In case it encounters an error sending a DHCP request on an interface (which is the case for 17 out of the 18 interfaces on this instance), it attempts to "try again later" and sets a timer of 10 seconds for the next attempt - ignoring completely the user-specified value (2 seconds). I believe this is a bug in ipconfig and have a working fix to limit the delay to the user- specified timeout so each interface actually takes a maximum of 2 seconds for initialization, even in error cases. The above is for bionic, which has the reported problem. In focal, even though the kernel and klibc-utils are identical to bionic, the version of initramfs-tools-core is different. In the focal version, configure_networking() has been reworked to avoid using ipconfig entirely. Instead, it uses ```dhclient```. And instead of doing that 18 times, dhclient is called only once with the full list of interfaces, as such: ``` dhclient -v -1 -cf /etc/dhcp/dhclient.conf.2 -pf /tmp/dhclient.pid.2 -4 enp12s0f0np0 enp12s0f1np1 enp138s0f0np0 enp138s0f1np1 enp148s0f0np0 enp148s0f1np1 enp195s0f0np0 enp195s0f1np1 enp209s0f0np0 enp209s0f1np1 enp22s0f0np0 enp22s0f1np1 enp45s0f0np0 enp45s0f1np1 enp72s0f0np0 enp72s0f1np1 enp76s0f0np0 enp76s0f1np1 ``` dhclient does DHCP on all those interfaces at the same time, asynchronously, and it daemonizes (goes in the background) as soon as it gets a DHCP response which happens relatively quickly (on interface enp45s0f0np0 usually) and so the boot-up continues *much* faster compared to bionic (180+ seconds are reduced to just 5-10 seconds). I'm sure there might be other use cases, but this is what we have been reported and are trying to work with. I hope this helps clarifying. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1947099
[Touch-packages] [Bug 1923115] Re: Networkd vs udev nic renaming race condition
Customer has provided a positive feedback that the package in -proposed fixed this bug -- 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/1923115 Title: Networkd vs udev nic renaming race condition Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Focal: Fix Released Bug description: [Impact] systemd-networkd renames nic just after udev renamed it e.g kernel: [ 2.827368] vmxnet3 :0b:00.0 ens192: renamed from eth0 kernel: [ 7.562729] vmxnet3 :0b:00.0 eth0: renamed from ens192 systemd-networkd[511]: ens192: Interface name change detected, ens192 has been renamed to eth0. This cause netplan or the other network management pkg can't find proper nic sometimes. This happens on Bionic Below commit seems to solve this issue. https://github.com/systemd/systemd/pull/11881/commits/30de2b89d125a8692c22579ef805b03f2054b30b There are bunch of related commits but above one the customer tested it worked. [Test Plan] The customer has issue and they could help us to test this. Internally they already test this and it worked. Please refer to github issue's reproduction step as well. https://github.com/systemd/systemd/issues/7293#issue-272917058 where the test plan is described as: "Reboot a couple of times. Sometimes the interface is renamed correctly. Sometimes it is not." [Where problems could occur] systemd-networkd should be restarted for this patch. systemd-networkd nic renaming could have issue. renaming may not be happening unexpectedly. e.g doesn't rename it properly or rename it when it should do. [Others] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923115/+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 1894371] [NEW] package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: upgrading from 18.04 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 5 15:03:23 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-09-05 (0 days ago) ** Affects: initramfs-tools (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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1894371 Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: upgrading from 18.04 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 5 15:03:23 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-09-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1894371/+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 1842255] [NEW] package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] failed to install/upgrade: package libnss3:amd64 is already installed and configured
Public bug reported: No more ProblemType: Package DistroRelease: elementary 0.4.1 Package: libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14.1 Architecture: amd64 Date: Sun Sep 1 13:00:20 2019 DuplicateSignature: package:libnss3:amd64:2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] Removing linux-modules-4.15.0-43-generic (4.15.0-43.46~16.04.1) ... dpkg: error processing package libnss3-nssdb (--configure): package libnss3-nssdb is already installed and configured ErrorMessage: package libnss3:amd64 is already installed and configured InstallationDate: Installed on 2018-05-26 (463 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: nss Title: package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] failed to install/upgrade: package libnss3:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nss (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed 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 nss in Ubuntu. https://bugs.launchpad.net/bugs/1842255 Title: package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] failed to install/upgrade: package libnss3:amd64 is already installed and configured Status in nss package in Ubuntu: New Bug description: No more ProblemType: Package DistroRelease: elementary 0.4.1 Package: libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 ProcVersionSignature: Ubuntu 4.15.0-58.64~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14.1 Architecture: amd64 Date: Sun Sep 1 13:00:20 2019 DuplicateSignature: package:libnss3:amd64:2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] Removing linux-modules-4.15.0-43-generic (4.15.0-43.46~16.04.1) ... dpkg: error processing package libnss3-nssdb (--configure): package libnss3-nssdb is already installed and configured ErrorMessage: package libnss3:amd64 is already installed and configured InstallationDate: Installed on 2018-05-26 (463 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: nss Title: package libnss3:amd64 2:3.28.4-0ubuntu0.16.04.6 [origin: Ubuntu] failed to install/upgrade: package libnss3:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1842255/+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 1815444] [NEW] Xorg crashed with SIGABRT in OsAbort()
Public bug reported: Release: Ubuntu 16.04 LTS Package: xserver-xorg-core-hwe-16.04 2:1.19.6-1ubuntu4.1~16.04.2 Archicteture:amd64 /usr/lib/xorg/Xorg:6:/lib/x86_64-linux- gnu/libc-2.23.so+35428:/lib/x86_64-linux- gnu/libc-2.23.so+3702a:/usr/lib/xorg/Xorg+1b891a:/usr/lib/xorg/Xorg+1be513:/usr/lib/xorg/Xorg+1bf32d:/usr/lib/xorgXorg+8b260/usr/lib/xorg/Xorg+990e0:/usr/lib/xorg/Xorg+582d6:/lib/x86_64 -linux-gnu/libc-2.23.so+20830:/usr/lib/xorg/Xorg+42449 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon Feb 11 08:44:05 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: broadcom-sta, 6.30.223.271, 4.15.0-42-generic, x86_64: installed broadcom-sta, 6.30.223.271, 4.15.0-43-generic, x86_64: installed broadcom-sta, 6.30.223.271, 4.15.0-45-generic, x86_64: installed broadcom-sta, 6.30.223.271, 4.4.0-142-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Haswell-ULT Integrated Graphics Controller [104d:90be] InstallationDate: Installed on 2017-06-26 (594 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Sony Corporation SVF15325CBB ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=10884db2-b372-43f6-9549-0e72c5ee1169 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/19/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: R1080DB dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnInsydeCorp.:bvrR1080DB:bd09/19/2014:svnSonyCorporation:pnSVF15325CBB:pvrC800KAXM:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: SVF1532 dmi.product.name: SVF15325CBB dmi.product.version: C800KAXM dmi.sys.vendor: Sony Corporation version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Feb 11 08:23:25 2019 xserver.configfile: default xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815444 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg package in Ubuntu: New Bug description: Release: Ubuntu 16.04 LTS Package: xserver-xorg-core-hwe-16.04 2:1.19.6-1ubuntu4.1~16.04.2 Archicteture:amd64 /usr/lib/xorg/Xorg:6:/lib/x86_64-linux- gnu/libc-2.23.so+35428:/lib/x86_64-linux- gnu/libc-2.23.so+3702a:/usr/lib/xorg/Xorg+1b891a:/usr/lib/xorg/Xorg+1be513:/usr/lib/xorg/Xorg+1bf32d:/usr/lib/xorgXorg+8b260/usr/lib/xorg/Xorg+990e0:/usr/lib/xorg/Xorg+582d6:/lib/x86_64 -linux-gnu/libc-2.23.so+20830:/usr/lib/xorg/Xorg+42449 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Mon Feb 11 08:44:05 2019 DistUpgraded: Fresh install
[Touch-packages] [Bug 1500193] Re: systemd-journald crashed with SIGABRT in dev_kmsg_record()
Happened today at the start of the system ** Tags added: cosmic -- 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/1500193 Title: systemd-journald crashed with SIGABRT in dev_kmsg_record() Status in systemd package in Ubuntu: Confirmed Bug description: I don't know details ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: systemd 225-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1 Uname: Linux 4.2.0-11-generic x86_64 ApportVersion: 2.19-0ubuntu1 Architecture: amd64 Date: Sun Sep 27 01:21:55 2015 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2015-09-26 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) Lsusb: Bus 003 Device 002: ID 8087:8000 Intel Corp. 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 002: ID 064e:c341 Suyin Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=el_GR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic.efi.signed root=UUID=38873c09-af33-49bc-a9cb-4762d8e857d1 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () __libc_start_main (main=0x55ee81dd0440, argc=1, argv=0x7fff46d4c1f8, init=, fini=, rtld_fini=, stack_end=0x7fff46d4c1e8) at libc-start.c:289 ?? () Title: systemd-journald crashed with SIGABRT in __libc_start_main() UdevLog: Error: [Errno 2] Δεν υπάρχει τέτοιο αρχείο ή κατάλογος: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/16/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.61 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2166 dmi.board.vendor: Hewlett-Packard dmi.board.version: 29.42 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.61:bd01/16/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr098B1140410620180:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion 15 Notebook PC dmi.product.version: 098B1140410620180 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1500193/+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 1790482] [NEW] [X550CC, Realtek ALC270, Speaker, Internal] No sound at all
Public bug reported: i can't listen any Sound from the speakers. if i use headphones i don't have any problem to hear music or anything, but without i can't neither choose the option speaker. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dibo 1094 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Sep 1 18:13:45 2018 InstallationDate: Installed on 2018-09-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dibo 1094 F...m pulseaudio /dev/snd/controlC0: dibo 1094 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X550CC, Realtek ALC270, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC 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.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1790482 Title: [X550CC, Realtek ALC270, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: i can't listen any Sound from the speakers. if i use headphones i don't have any problem to hear music or anything, but without i can't neither choose the option speaker. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dibo 1094 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Sep 1 18:13:45 2018 InstallationDate: Installed on 2018-09-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dibo 1094 F...m pulseaudio /dev/snd/controlC0: dibo 1094 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X550CC, Realtek ALC270, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC 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.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1790482/+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 1790328] [NEW] [X550CC, Realtek ALC270, Speaker, Internal] No sound at all
Public bug reported: Hello, i tried to reinstall Ubuntu thinking was something easy to solve but nothing. the problem persist. in also i did different try with different guides but i didnt manage since im new on linux and tried to fix it without result. the problem is: only headphones are showed on the list of outpout and the speakers, after using the command alsamixer -D hw:PCH i tried to increase the volume on the speakers, but nothing is changing. what do i suppose to do ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dibo 1094 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Sep 1 18:13:45 2018 InstallationDate: Installed on 2018-09-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dibo 1094 F...m pulseaudio /dev/snd/controlC0: dibo 1094 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X550CC, Realtek ALC270, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC 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.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1790328 Title: [X550CC, Realtek ALC270, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello, i tried to reinstall Ubuntu thinking was something easy to solve but nothing. the problem persist. in also i did different try with different guides but i didnt manage since im new on linux and tried to fix it without result. the problem is: only headphones are showed on the list of outpout and the speakers, after using the command alsamixer -D hw:PCH i tried to increase the volume on the speakers, but nothing is changing. what do i suppose to do ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dibo 1094 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Sep 1 18:13:45 2018 InstallationDate: Installed on 2018-09-01 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: dibo 1094 F...m pulseaudio /dev/snd/controlC0: dibo 1094 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [X550CC, Realtek ALC270, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC 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:
[Touch-packages] [Bug 1783527] [NEW] [X550CC, Realtek ALC270, Speaker, Internal] Playback problem
Public bug reported: Hello, i can't hear any sound neither from the test. the audio isn't working, and, i tried to configure the speakers but linux doesn't recognize the speakers of the laptop, infect, checking the settings,i can see only headphones listed and not speakers or any other option. ]what can i do? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vecio 1250 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jul 25 09:50:13 2018 InstallationDate: Installed on 2018-07-24 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [X550CC, Realtek ALC270, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC 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.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1783527 Title: [X550CC, Realtek ALC270, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: Hello, i can't hear any sound neither from the test. the audio isn't working, and, i tried to configure the speakers but linux doesn't recognize the speakers of the laptop, infect, checking the settings,i can see only headphones listed and not speakers or any other option. ]what can i do? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vecio 1250 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jul 25 09:50:13 2018 InstallationDate: Installed on 2018-07-24 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: None of the above Title: [X550CC, Realtek ALC270, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC 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.:bvrX550CC.212:bd05/29/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1783527/+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 1745822] Re: systemd-journald crashed with SIGABRT in journal_file_move_to_object()
*** This bug is a duplicate of bug 1717344 *** https://bugs.launchpad.net/bugs/1717344 ** Description changed: - crash just after session started, probably dup of #1723050 - + crash just after session started, ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CrashCounter: 1 Date: Sun Jan 28 11:52:33 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2016-10-30 (454 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=UUID=85588768-f139-4db0-8652-92f7319df86a ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: systemd StacktraceTop: - journal_file_move_to_object () from /lib/systemd/libsystemd-shared-235.so - ?? () from /lib/systemd/libsystemd-shared-235.so - ?? () from /lib/systemd/libsystemd-shared-235.so - journal_file_append_entry () from /lib/systemd/libsystemd-shared-235.so - ?? () + journal_file_move_to_object () from /lib/systemd/libsystemd-shared-235.so + ?? () from /lib/systemd/libsystemd-shared-235.so + ?? () from /lib/systemd/libsystemd-shared-235.so + journal_file_append_entry () from /lib/systemd/libsystemd-shared-235.so + ?? () SystemdDelta: - [EXTENDED] /lib/systemd/system/clamav-daemon.service → /etc/systemd/system/clamav-daemon.service.d/extend.conf - [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf - [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf - - 3 overridden configuration files found. + [EXTENDED] /lib/systemd/system/clamav-daemon.service → /etc/systemd/system/clamav-daemon.service.d/extend.conf + [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf + [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf + + 3 overridden configuration files found. Title: systemd-journald crashed with SIGABRT in journal_file_move_to_object() UpgradeStatus: Upgraded to bionic on 2018-01-08 (19 days ago) UserGroups: - + dmi.bios.date: 04/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GA-990FX-GAMING dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd04/06/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FX-GAMING:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. -- 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/1745822 Title: systemd-journald crashed with SIGABRT in journal_file_move_to_object() Status in systemd package in Ubuntu: New Bug description: crash just after session started, ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CrashCounter: 1 Date: Sun Jan 28 11:52:33 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2016-10-30 (454 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcCmdline: /lib/systemd/systemd-journald ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=UUID=85588768-f139-4db0-8652-92f7319df86a ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: systemd StacktraceTop: journal_file_move_to_object () from /lib/systemd/libsystemd-shared-235.so ?? () from /lib/systemd/libsystemd-shared-235.so ?? () from /lib/systemd/libsystemd-shared-235.so journal_file_append_entry () from /lib/systemd/libsystemd-shared-235.so ?? () SystemdDelta: [EXTENDED] /lib/systemd/system/clamav-daemon.service → /etc/systemd/system/clamav-daemon.service.d/extend.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED]
[Touch-packages] [Bug 1741940] [NEW] package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Upgrading from Artful ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 Uname: Linux 4.15.0-999-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Mon Jan 8 17:47:35 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-10-30 (435 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-999-generic root=UUID=85588768-f139-4db0-8652-92f7319df86a ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/clamav-daemon.service → /etc/systemd/system/clamav-daemon.service.d/extend.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-01-08 (0 days ago) dmi.bios.date: 04/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GA-990FX-GAMING dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd04/06/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FX-GAMING:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1741940 Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned Status in systemd package in Ubuntu: New Bug description: Upgrading from Artful ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 Uname: Linux 4.15.0-999-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Mon Jan 8 17:47:35 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-10-30 (435 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-999-generic root=UUID=85588768-f139-4db0-8652-92f7319df86a ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.6~alpha5 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/clamav-daemon.service → /etc/systemd/system/clamav-daemon.service.d/extend.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-01-08 (0 days ago) dmi.bios.date: 04/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GA-990FX-GAMING dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd04/06/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FX-GAMING:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications
[Touch-packages] [Bug 1706936] Re: Wrong version of libgles1-mesa in Xenial-updates
I don't have a VLC ppa. I don't really understand what the problem is here, but if it's not Ubuntu-related I'll figure something out. Thanks. -- 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/1706936 Title: Wrong version of libgles1-mesa in Xenial-updates Status in mesa package in Ubuntu: Invalid Bug description: Xenial-updates has the following packages: - libgles1-mesa (12.0.6-0ubuntu0.16.04.1) - libglapi-mesa (17.0.7-0ubuntu0.16.04.1) The first one depends on libglapi-mesa (= 12.0.6-0ubuntu0.16.04.1), but libglapi-mesa has a higher version and so there's a conflict. I've had to remove libgles1-mesa for now, to avoid the conflict. I have Linux Mint 18.1 but I believe it affects anyone using xenial- updates. Source links I used to verify it's a xenial-updates problem: https://packages.ubuntu.com/xenial-updates/libs/libgles1-mesa https://packages.ubuntu.com/xenial-updates/libglapi-mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1706936/+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 1706936] [NEW] Wrong version of libgles1-mesa in Xenial-updates
Public bug reported: Xenial-updates has the following packages: - libgles1-mesa (12.0.6-0ubuntu0.16.04.1) - libglapi-mesa (17.0.7-0ubuntu0.16.04.1) The first one depends on libglapi-mesa (= 12.0.6-0ubuntu0.16.04.1), but libglapi-mesa has a higher version and so there's a conflict. I've had to remove libgles1-mesa for now, to avoid the conflict. I have Linux Mint 18.1 but I believe it affects anyone using xenial- updates. Source links I used to verify it's a xenial-updates problem: https://packages.ubuntu.com/xenial-updates/libs/libgles1-mesa https://packages.ubuntu.com/xenial-updates/libglapi-mesa ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1706936 Title: Wrong version of libgles1-mesa in Xenial-updates Status in mesa package in Ubuntu: New Bug description: Xenial-updates has the following packages: - libgles1-mesa (12.0.6-0ubuntu0.16.04.1) - libglapi-mesa (17.0.7-0ubuntu0.16.04.1) The first one depends on libglapi-mesa (= 12.0.6-0ubuntu0.16.04.1), but libglapi-mesa has a higher version and so there's a conflict. I've had to remove libgles1-mesa for now, to avoid the conflict. I have Linux Mint 18.1 but I believe it affects anyone using xenial- updates. Source links I used to verify it's a xenial-updates problem: https://packages.ubuntu.com/xenial-updates/libs/libgles1-mesa https://packages.ubuntu.com/xenial-updates/libglapi-mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1706936/+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 1643429] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: x ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Sun Nov 20 10:13:29 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-04-15 (585 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: HP-Pavilion FL398AA-ABZ m9461it Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic root=UUID=c339abd7-547a-4adf-ae37-ab7261a42727 ro quiet splash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic root=UUID=c339abd7-547a-4adf-ae37-ab7261a42727 ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-27 (85 days ago) dmi.bios.date: 09/05/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.30 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.30:bd09/05/2008:svnHP-Pavilion:pnFL398AA-ABZm9461it:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: FL398AA-ABZ m9461it dmi.sys.vendor: HP-Pavilion modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2015-04-17T00:15:58.864658 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1643429 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: x ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Sun Nov 20 10:13:29 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-04-15 (585 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: HP-Pavilion FL398AA-ABZ m9461it Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic root=UUID=c339abd7-547a-4adf-ae37-ab7261a42727 ro quiet splash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-49-generic root=UUID=c339abd7-547a-4adf-ae37-ab7261a42727 ro quiet splash RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-08-27 (85 days ago) dmi.bios.date: 09/05/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.30 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.30:bd09/05/2008:svnHP-Pavilion:pnFL398AA-ABZm9461it:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: FL398AA-ABZ m9461it dmi.sys.vendor: HP-Pavilion modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2015-04-17T00:15:58.864658 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1643429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1640233] [NEW] package libqt5dbus5:i386 (not installed) failed to install/upgrade: package libqt5dbus5:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured because libqt5dbus5:amd64 i
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libqt5dbus5:i386 (not installed) ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Mon Nov 7 11:17:39 2016 DuplicateSignature: package:libqt5dbus5:i386:(not installed) Unpacking mesa-utils:i386 (8.3.0-2) over (8.3.0-2) ... dpkg: error processing package libqt5core5a:i386 (--configure): package libqt5core5a:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured because libqt5core5a:amd64 is at a different version (5.6.1+dfsg-3ubuntu7~~xenialoverlay1~2) ErrorMessage: package libqt5dbus5:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured because libqt5dbus5:amd64 is at a different version (5.6.1+dfsg-3ubuntu7~~xenialoverlay1~2) InstallationDate: Installed on 2016-04-13 (209 days ago) InstallationMedia: RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: qtbase-opensource-src Title: package libqt5dbus5:i386 (not installed) failed to install/upgrade: package libqt5dbus5:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured because libqt5dbus5:amd64 is at a different version (5.6.1+dfsg-3ubuntu7~~xenialoverlay1~2) UpgradeStatus: Upgraded to yakkety on 2016-10-14 (25 days ago) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1640233 Title: package libqt5dbus5:i386 (not installed) failed to install/upgrade: package libqt5dbus5:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured because libqt5dbus5:amd64 is at a different version (5.6.1+dfsg- 3ubuntu7~~xenialoverlay1~2) Status in qtbase-opensource-src package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libqt5dbus5:i386 (not installed) ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Mon Nov 7 11:17:39 2016 DuplicateSignature: package:libqt5dbus5:i386:(not installed) Unpacking mesa-utils:i386 (8.3.0-2) over (8.3.0-2) ... dpkg: error processing package libqt5core5a:i386 (--configure): package libqt5core5a:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured because libqt5core5a:amd64 is at a different version (5.6.1+dfsg-3ubuntu7~~xenialoverlay1~2) ErrorMessage: package libqt5dbus5:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured because libqt5dbus5:amd64 is at a different version (5.6.1+dfsg-3ubuntu7~~xenialoverlay1~2) InstallationDate: Installed on 2016-04-13 (209 days ago) InstallationMedia: RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: qtbase-opensource-src Title: package libqt5dbus5:i386 (not installed) failed to install/upgrade: package libqt5dbus5:i386 5.6.1+dfsg-3ubuntu6~4 cannot be configured because libqt5dbus5:amd64 is at a different version (5.6.1+dfsg-3ubuntu7~~xenialoverlay1~2) UpgradeStatus: Upgraded to yakkety on 2016-10-14 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1640233/+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 1620806] Re: gedit edit window is transparent when using Ambiance and Radiance themes
Raising importance cuz isn't only aesthetic issue but it affect usability ** Changed in: gedit (Ubuntu) Importance: Low => Medium -- 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/1620806 Title: gedit edit window is transparent when using Ambiance and Radiance themes Status in gedit package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: In a freshly booted and fully updated Ubuntu 16.10 the edit window of gedit is transparent using the *Classic* colour scheme. Other colour schemes seem to work as intended. The text of loaded files shows against the desktop wallpaper but when no files are loaded gedit displays its edit window or pane as it should do. To clarify this bug is only apparent when a file is loaded. I don't know when this started as I don't normally used gedit to edit files. I haven't found any other application affected by this problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gedit 3.20.2-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 6 21:01:35 2016 InstallationDate: Installed on 2016-03-11 (179 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160311) SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1620806/+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 1631787] [NEW] Ubuntu ship by default Amazon launcher
Public bug reported: How many times encountered, Amazon requires its workers to too high pace of work, proving to not to be humanity for others. Please stop this shame. Man is not a machine. ** Affects: webapps-applications (Ubuntu) Importance: High Status: Confirmed ** Tags: rls-y-incoming yakkety ** Package changed: pulseaudio (Ubuntu) => webapps-applications (Ubuntu) ** Changed in: webapps-applications (Ubuntu) Importance: Undecided => High ** Changed in: webapps-applications (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1631787 Title: Ubuntu ship by default Amazon launcher Status in webapps-applications package in Ubuntu: Confirmed Bug description: How many times encountered, Amazon requires its workers to too high pace of work, proving to not to be humanity for others. Please stop this shame. Man is not a machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webapps-applications/+bug/1631787/+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 1631782] [NEW] Volume and Mic controls grayed out and not working
Public bug reported: Hallo testing Yakkety 08-10 buld on live session i have the controls of the volume locked and not working as shown in the attached screenshot. Even in sound setting I can-t set the desired volume, anyway it play sounds correctly. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CurrentDesktop: Unity Date: Sun Oct 9 17:53:10 2016 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: H55M-S2H 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.:bvrF7:bd08/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H55M-S2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: pulseaudio (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug rls-y-incoming yakkety ** Attachment added: "Screenshot from 2016-10-09 17-52-04.png" https://bugs.launchpad.net/bugs/1631782/+attachment/4758293/+files/Screenshot%20from%202016-10-09%2017-52-04.png ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1631782 Title: Volume and Mic controls grayed out and not working Status in pulseaudio package in Ubuntu: New Bug description: Hallo testing Yakkety 08-10 buld on live session i have the controls of the volume locked and not working as shown in the attached screenshot. Even in sound setting I can-t set the desired volume, anyway it play sounds correctly. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-2ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.379 CurrentDesktop: Unity Date: Sun Oct 9 17:53:10 2016 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7 dmi.board.name: H55M-S2H 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.:bvrF7:bd08/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-S2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-S2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H55M-S2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1631782/+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 1629088] Re: [Yakkety] WIFI disconnections, fail in reconnection introduced from Xenial
retenjin_EXT_EXT is home wifi VodafoneMobileWifi is the mobile modem -- 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/1629088 Title: [Yakkety] WIFI disconnections, fail in reconnection introduced from Xenial Status in network-manager package in Ubuntu: New Bug description: Hallo Wily with latest mainline kernel works great so I assume this issue is not related to linux. Starting from Xenial I cannot (or sometimes I can for few times and for few minutes) connect to my wireless, even the mobile modem frequently disconnect with problem reconnecting back. Even now I cannot reconnect to my mobile modem so I have to use the usb wire to it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.378 CurrentDesktop: Unity:Unity7 Date: Thu Sep 29 19:02:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlp4s1 proto static metric 600 169.254.0.0/16 dev wlp4s1 scope link metric 1000 192.168.0.0/24 dev wlp4s1 proto kernel scope link src 192.168.0.110 metric 600 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160929) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp4s1 wifi connected/org/freedesktop/NetworkManager/Devices/0 VodafoneMobileWiFi-CC8463 31bb378f-071e-49d9-96f5-600b2c1b511a /org/freedesktop/NetworkManager/ActiveConnection/15 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629088/+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 1629088] Re: [Yakkety] WIFI disconnections, fail in reconnection introduced from Xenial
** Summary changed: - [Yakkety] Disconnections, fail in reconnection introduced from Xenial + [Yakkety] WIFI disconnections, fail in reconnection introduced from 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/1629088 Title: [Yakkety] WIFI disconnections, fail in reconnection introduced from Xenial Status in network-manager package in Ubuntu: New Bug description: Hallo Wily with latest mainline kernel works great so I assume this issue is not related to linux. Starting from Xenial I cannot (or sometimes I can for few times and for few minutes) connect to my wireless, even the mobile modem frequently disconnect with problem reconnecting back. Even now I cannot reconnect to my mobile modem so I have to use the usb wire to it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.378 CurrentDesktop: Unity:Unity7 Date: Thu Sep 29 19:02:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlp4s1 proto static metric 600 169.254.0.0/16 dev wlp4s1 scope link metric 1000 192.168.0.0/24 dev wlp4s1 proto kernel scope link src 192.168.0.110 metric 600 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160929) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp4s1 wifi connected/org/freedesktop/NetworkManager/Devices/0 VodafoneMobileWiFi-CC8463 31bb378f-071e-49d9-96f5-600b2c1b511a /org/freedesktop/NetworkManager/ActiveConnection/15 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629088/+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 1629088] [NEW] [Yakkety] Disconnections, fail in reconnection introduced from Xenial
Public bug reported: Hallo Wily with latest mainline kernel works great so I assume this issue is not related to linux. Starting from Xenial I cannot (or sometimes I can for few times and for few minutes) connect to my wireless, even the mobile modem frequently disconnect with problem reconnecting back. Even now I cannot reconnect to my mobile modem so I have to use the usb wire to it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.378 CurrentDesktop: Unity:Unity7 Date: Thu Sep 29 19:02:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlp4s1 proto static metric 600 169.254.0.0/16 dev wlp4s1 scope link metric 1000 192.168.0.0/24 dev wlp4s1 proto kernel scope link src 192.168.0.110 metric 600 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160929) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp4s1 wifi connected/org/freedesktop/NetworkManager/Devices/0 VodafoneMobileWiFi-CC8463 31bb378f-071e-49d9-96f5-600b2c1b511a /org/freedesktop/NetworkManager/ActiveConnection/15 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug regression-release xenial yakkety ** Changed in: network-manager (Ubuntu) Importance: Undecided => High ** Tags added: regression-release 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/1629088 Title: [Yakkety] Disconnections, fail in reconnection introduced from Xenial Status in network-manager package in Ubuntu: New Bug description: Hallo Wily with latest mainline kernel works great so I assume this issue is not related to linux. Starting from Xenial I cannot (or sometimes I can for few times and for few minutes) connect to my wireless, even the mobile modem frequently disconnect with problem reconnecting back. Even now I cannot reconnect to my mobile modem so I have to use the usb wire to it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.378 CurrentDesktop: Unity:Unity7 Date: Thu Sep 29 19:02:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlp4s1 proto static metric 600 169.254.0.0/16 dev wlp4s1 scope link metric 1000 192.168.0.0/24 dev wlp4s1 proto kernel scope link src 192.168.0.110 metric 600 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160929) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp4s1 wifi connected/org/freedesktop/NetworkManager/Devices/0 VodafoneMobileWiFi-CC8463 31bb378f-071e-49d9-96f5-600b2c1b511a /org/freedesktop/NetworkManager/ActiveConnection/15 enp3s0 ethernet unavailable
[Touch-packages] [Bug 1629088] Re: [Yakkety] Disconnections, fail in reconnection introduced from Xenial
Attaching some logs with fail in reconnection during this report ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629088/+attachment/4751312/+files/syslog -- 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/1629088 Title: [Yakkety] Disconnections, fail in reconnection introduced from Xenial Status in network-manager package in Ubuntu: New Bug description: Hallo Wily with latest mainline kernel works great so I assume this issue is not related to linux. Starting from Xenial I cannot (or sometimes I can for few times and for few minutes) connect to my wireless, even the mobile modem frequently disconnect with problem reconnecting back. Even now I cannot reconnect to my mobile modem so I have to use the usb wire to it. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CasperVersion: 1.378 CurrentDesktop: Unity:Unity7 Date: Thu Sep 29 19:02:44 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlp4s1 proto static metric 600 169.254.0.0/16 dev wlp4s1 scope link metric 1000 192.168.0.0/24 dev wlp4s1 proto kernel scope link src 192.168.0.110 metric 600 LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160929) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp4s1 wifi connected/org/freedesktop/NetworkManager/Devices/0 VodafoneMobileWiFi-CC8463 31bb378f-071e-49d9-96f5-600b2c1b511a /org/freedesktop/NetworkManager/ActiveConnection/15 enp3s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1629088/+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 1299282] Re: need to restart network-manager after resume from suspend
*** This bug is a duplicate of bug 1252121 *** https://bugs.launchpad.net/bugs/1252121 This works perfectly on Ubuntu 16.04 with systemd: https://gist.github.com/nitely/3d5f10b4f686f5f96c95 -- 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/1299282 Title: need to restart network-manager after resume from suspend Status in systemd package in Ubuntu: Confirmed Bug description: possibly related to bug #1289884 , but when i resume from suspend none of my interfaces (wireless, wired usb, bluetooth connection) are visibile to network-manager until i restart it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 28 15:56:30 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-02-24 (32 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218) IpRoute: default via 10.9.0.1 dev eth0 proto static 10.9.0.0/24 dev eth0 proto kernel scope link src 10.9.0.38 metric 1 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm 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-dev: DEVICE TYPE STATE DBUS-PATH B0:79:94:D7:0E:0E bluetooth disconnected /org/freedesktop/NetworkManager/Devices/2 wlan0 802-11-wireless unavailable /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled disabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1299282/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
This works perfectly on Ubuntu 16.04 with systemd: https://gist.github.com/nitely/3d5f10b4f686f5f96c95 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd-shim/+bug/1252121/+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 1604433] Re: Listening audio does not work on the desktop
** Changed in: canonical-devices-system-image Status: Incomplete => Confirmed ** Changed in: unity8-desktop-session (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604433 Title: Listening audio does not work on the desktop Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: Playing any audio (eg. youtube video) does not produce any sound on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604433/+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 1604433] Re: Listening audio does not work on the desktop
Ok, thanks, here you are :) ** Attachment added: "application-click-com.ubuntu.music_music_2.4.1003.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604433/+attachment/4708875/+files/application-click-com.ubuntu.music_music_2.4.1003.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604433 Title: Listening audio does not work on the desktop Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Incomplete Bug description: Playing any audio (eg. youtube video) does not produce any sound on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604433/+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 1604433] Re: Listening audio does not work on the desktop
What package is giving me the music app? Is it a click? Because I have it in the dash but there's no such thing like a 'music-app' package installed on my system.. I'm not understanding what's going on.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604433 Title: Listening audio does not work on the desktop Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Incomplete Bug description: Playing any audio (eg. youtube video) does not produce any sound on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604433/+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 1604433] Re: Listening audio does not work on the desktop
Sorry, there actually was, but was not visible from Firefox in Libertine :/ Anyway there is no log there from the music-app (double checked) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604433 Title: Listening audio does not work on the desktop Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Incomplete Bug description: Playing any audio (eg. youtube video) does not produce any sound on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604433/+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 1604433] Re: Listening audio does not work on the desktop
Sorry, there is no upstart folder under ~/.cache.. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604433 Title: Listening audio does not work on the desktop Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Incomplete Bug description: Playing any audio (eg. youtube video) does not produce any sound on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604433/+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 1604433] Re: Listening audio does not work on the desktop
I tried installing qtubuntu-media and it made the dash go in a loop of crash and restart. I could not try the music-app because with qtubuntu- media was installed it crashed on startup. I purged the package, now the dash works correctly and I can even play music from the Music scope. Opening the Music app now works again, but no sound is produced. Using the webbrowser-app there was no audio neither with nor without qtubuntu- media package. Speakers are not muted. I tryed both with or withoud headphones, without any difference of result. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604433 Title: Listening audio does not work on the desktop Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Incomplete Bug description: Playing any audio (eg. youtube video) does not produce any sound on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604433/+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 1580472] Re: No visible cursor after logging in
I'm not sure I can use the nvidia card without the nvidia drivers as it's an optimus card. With just nouveau installed it works fine, anyaway. -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: Only when using the nvidia drivers, after logging in, the cursor is not drawn on the screen. I can see its effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else works. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again through lightdm. This works most of the time. --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1580472/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1580472] Re: No visible cursor after logging in
No, to my memory I just experienced this using the nvidia drivers and when enabling the nvidia card (I have an hybrid optimus card) -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental:
[Touch-packages] [Bug 1605663] [NEW] No webcam connection from camera-app in desktop-session
Public bug reported: In my laptop, if I launch the camera-app, I get the app running but the webcam input is totally black. I would have instead expected to see the input from my integrated webcam. ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Affects: unity8-desktop-session (Ubuntu) Importance: Undecided Status: New ** Also affects: camera-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 camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1605663 Title: No webcam connection from camera-app in desktop-session Status in camera-app package in Ubuntu: New Status in unity8-desktop-session package in Ubuntu: New Bug description: In my laptop, if I launch the camera-app, I get the app running but the webcam input is totally black. I would have instead expected to see the input from my integrated webcam. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1605663/+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 1604433] Re: Listening audio does not work on the desktop
I just tried with the Music app and there is still no sound -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604433 Title: Listening audio does not work on the desktop Status in Canonical System Image: New Status in qtubuntu-media package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: Playing any audio (eg. youtube video) does not produce any sound on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604433/+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 1590515] Re: AltGr composed keys don't work in the browser content
In the Italian keyboard I can't type the following (among others):
@#[]{}«»`~ which are quite common symbols.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1590515
Title:
AltGr composed keys don't work in the browser content
Status in qtubuntu package in Ubuntu:
New
Status in webbrowser-app package in Ubuntu:
Confirmed
Bug description:
As the title says. Those keys work fine in the address bar, but not in
any text fields inside the website. With a german layout I can't type
things like ~ \ { } [ ] etc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1590515/+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 1580472] MonitorsUser.xml.txt
apport information ** Attachment added: "MonitorsUser.xml.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704708/+files/MonitorsUser.xml.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704721/+files/xdpyinfo.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704714/+files/UdevDb.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental:
[Touch-packages] [Bug 1580472] NvidiaBugReportLog.txt
apport information ** Attachment added: "NvidiaBugReportLog.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704709/+files/NvidiaBugReportLog.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704713/+files/ProcModules.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704719/+files/Xrandr.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental:
[Touch-packages] [Bug 1580472] nvidia-settings.txt
apport information ** Attachment added: "nvidia-settings.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704720/+files/nvidia-settings.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704717/+files/XorgLog.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental:
[Touch-packages] [Bug 1580472] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704718/+files/XorgLogOld.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] UnitySupportTest.txt
apport information ** Attachment added: "UnitySupportTest.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704715/+files/UnitySupportTest.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] XorgConf.txt
apport information ** Attachment added: "XorgConf.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704716/+files/XorgConf.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704712/+files/ProcInterrupts.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704710/+files/ProcCpuinfo.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704711/+files/ProcEnviron.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704707/+files/Lspci.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental:
[Touch-packages] [Bug 1580472] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704706/+files/LightdmLog.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704702/+files/DpkgLog.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental:
[Touch-packages] [Bug 1580472] GconfCompiz.txt
apport information ** Attachment added: "GconfCompiz.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704703/+files/GconfCompiz.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704704/+files/JournalErrors.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704705/+files/LightdmDisplayLog.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704701/+files/Dependencies.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1580472] Re: No visible cursor after logging in
apport information ** Tags added: apport-collected compiz-0.9 ubuntu ** Description changed: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] + --- + .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' + .proc.driver.nvidia.registry: Binary: "" + .proc.driver.nvidia.version: + NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 + GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) + .tmp.unity_support_test.0: + + ApportVersion: 2.20.1-0ubuntu2.1 + Architecture: amd64 + BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks + 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 + DistUpgraded: Fresh install + DistroCodename: xenial + DistroRelease: Ubuntu 16.04 + DistroVariant: ubuntu + DkmsStatus: + bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed + bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed + bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed + nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed + nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed + EcryptfsInUse: Yes + ExtraDebuggingInterest: Yes + GraphicsCard: + Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) +Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] +Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] + InstallationDate: Installed on 2016-06-24 (27 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: ASUSTeK COMPUTER INC. X550JK + NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia + Package: xorg 1:7.7+13ubuntu3 + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 + ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 + Tags: xenial ubuntu compiz-0.9 + Uname: Linux 4.4.0-31-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/08/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: X550JK.303 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: X550JK + 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.name: X550JK + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. + version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 + version.ia32-libs: ia32-libs N/A + version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 + version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 + version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A + version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 + version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A + version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 +
[Touch-packages] [Bug 1580472] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1580472/+attachment/4704700/+files/CurrentDmesg.txt -- 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/1580472 Title: No visible cursor after logging in Status in xorg package in Ubuntu: Incomplete Bug description: After logging in, the cursor is not drawn on the screen. I can see it's effects while moving the mouse or touchpad, as items on the panel gets highlighted, or my unity panel becomes visible. I can even click on them and everything else just works, but I have to figure the cursor position. Workaround: Move to vt1 (CTRL + ALT + F1), log in, and restart the lightdm server: sudo service lightdm restart. Now log in again trough lightdm and cross your fingers, as it doesn't always work, but most of the times does. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 11 08:53:35 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-03-21 (416 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nvidia-graphics-drivers-361 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia-361_hybrid.conf: [deleted] --- .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: u'/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 361.42 Tue Mar 22 18:10:58 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: Ubuntu_LTS: clean, 842218/2048 files, 71321491/81919232 blocks 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 DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed bbswitch, 0.8, 4.4.0-28-generic, x86_64: installed bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-28-generic, x86_64: installed nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics Controller [1043:178d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:178d] InstallationDate: Installed on 2016-06-24 (27 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X550JK NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=35ffa5c6-747b-48ed-8546-3701daed4a97 ro quiet splash acpi_osi= vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.4.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550JK.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550JK 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.:bvrX550JK.303:bd10/08/2014:svnASUSTeKCOMPUTERINC.:pnX550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550JK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
[Touch-packages] [Bug 1604433] Re: Listening audio does not work on the desktop
I tried with webbrowser-app only (and in XApps, but for them it could be a different issue) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604433 Title: Listening audio does not work on the desktop Status in Canonical System Image: New Status in qtubuntu-media package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Status in unity8-desktop-session package in Ubuntu: Confirmed Bug description: Playing any audio (eg. youtube video) does not produce any sound on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604433/+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 1603183] Re: Right click from clickpad is handled as a left click
I tried with the bottom right corner too. -- 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/1603183 Title: Right click from clickpad is handled as a left click Status in Canonical System Image: New Status in Mir: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Incomplete Status in webbrowser-app package in Ubuntu: Invalid Bug description: Using the touchpad I was not able to trigger any right click, and I tought it was a problem of how unity8 handled the right clicks. Instead I just tried with a mouse and right click trigger different actions from left clicks. In the end the problem is that my touchpad right click is considered a left click by the system. This does not happen with an usb mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603183/+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 1603183] Re: Right click from clickpad is handled as a left click
Yes, it has no physical button -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603183 Title: Right click from clickpad is handled as a left click Status in Mir: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: Using the touchpad I was not able to trigger any right click, and I tought it was a problem of how unity8 handled the right clicks. Instead I just tried with a mouse and right click trigger different actions from left clicks. In the end the problem is that my touchpad right click is considered a left click by the system. This does not happen with an usb mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603183/+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 1604433] [NEW] Listening audio does not work on the desktop
Public bug reported: Playing any audio (eg. youtube video) does not produce any sound on the desktop ** Affects: unity8-desktop-session (Ubuntu) Importance: Undecided Status: New ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8-desktop-session (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/1604433 Title: Listening audio does not work on the desktop Status in unity8-desktop-session package in Ubuntu: New Status in webbrowser-app package in Ubuntu: New Bug description: Playing any audio (eg. youtube video) does not produce any sound on the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8-desktop-session/+bug/1604433/+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 1603186] Re: Apps scope not shown in the dash (but is installed)
This indeed solved the problem. I'm not sure if I ever removed it, but I can't exclude it -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1603186 Title: Apps scope not shown in the dash (but is installed) Status in unity-scope-click package in Ubuntu: Invalid Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: When opening the dash I just see Music, XApps and Videos scope. But there is no Apps scope. The only way to reach the Apps scope is opening the menu from the bottom edge and selecting it from there. So the scope is there and installed, the problem is that's not among the enabled (starred) scopes (and there's no way to enable it). This bug is not a duplicate of #1579551: - I am able to launch apps, I'm just missing the Apps scope - unity-scope-click is already installed, but the problem is still there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1603186/+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 1603186] Re: Apps scope not shown in the dash (but is installed)
Reinstalling unity-scope-click didn't change the situation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1603186 Title: Apps scope not shown in the dash (but is installed) Status in unity-scope-click package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: When opening the dash I just see Music, XApps and Videos scope. But there is no Apps scope. The only way to reach the Apps scope is opening the menu from the bottom edge and selecting it from there. So the scope is there and installed, the problem is that's not among the enabled (starred) scopes (and there's no way to enable it). This bug is not a duplicate of #1579551: - I am able to launch apps, I'm just missing the Apps scope - unity-scope-click is already installed, but the problem is still there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1603186/+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 1603186] Re: Apps scope not shown in the dash (but is installed)
I can even open it from the scope manager, it's just not shown among the enabled scopes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1603186 Title: Apps scope not shown in the dash (but is installed) Status in unity-scope-click package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: When opening the dash I just see Music, XApps and Videos scope. But there is no Apps scope. The only way to reach the Apps scope is opening the menu from the bottom edge and selecting it from there. So the scope is there and installed, the problem is that's not among the enabled (starred) scopes (and there's no way to enable it). This bug is not a duplicate of #1579551: - I am able to launch apps, I'm just missing the Apps scope - unity-scope-click is already installed, but the problem is still there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1603186/+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 1603186] Re: Apps scope not shown in the dash (but is installed)
Yes, it does. You can see it in the comment #4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1603186 Title: Apps scope not shown in the dash (but is installed) Status in unity-scope-click package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: When opening the dash I just see Music, XApps and Videos scope. But there is no Apps scope. The only way to reach the Apps scope is opening the menu from the bottom edge and selecting it from there. So the scope is there and installed, the problem is that's not among the enabled (starred) scopes (and there's no way to enable it). This bug is not a duplicate of #1579551: - I am able to launch apps, I'm just missing the Apps scope - unity-scope-click is already installed, but the problem is still there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1603186/+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 1603183] Re: Right click from touchpad is handled as a left click
** Description changed: - I'm used to have the contextual menus with the right button on the - desktop, while on unity8 they still appear pressing and holding (which - is fine for touch based devices). When I use the webbrowser-app I can't - even open links in different pages. + Using the touchpad I was not able to trigger any right click, and I + tought it was a problem of how unity8 handled the right clicks. Instead + I just tried with a mouse and right click trigger different actions from + left clicks. + + In the end the problem is that my touchpad right click is considered a + left click by the system. This does not happen with an usb mouse. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603183 Title: Right click from touchpad is handled as a left click Status in Mir: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Using the touchpad I was not able to trigger any right click, and I tought it was a problem of how unity8 handled the right clicks. Instead I just tried with a mouse and right click trigger different actions from left clicks. In the end the problem is that my touchpad right click is considered a left click by the system. This does not happen with an usb mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603183/+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 1603186] Re: Apps scope not shown in the dash (but is installed)
No problem ;) Current version of unity-scope-click is (0.1.1+16.10.20160705-0ubuntu1). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1603186 Title: Apps scope not shown in the dash (but is installed) Status in unity-scope-click package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: When opening the dash I just see Music, XApps and Videos scope. But there is no Apps scope. The only way to reach the Apps scope is opening the menu from the bottom edge and selecting it from there. So the scope is there and installed, the problem is that's not among the enabled (starred) scopes (and there's no way to enable it). This bug is not a duplicate of #1579551: - I am able to launch apps, I'm just missing the Apps scope - unity-scope-click is already installed, but the problem is still there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1603186/+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 1603183] Re: Right click from touchpad is handled as a left click
** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1603183 Title: Right click from touchpad is handled as a left click Status in Mir: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Using the touchpad I was not able to trigger any right click, and I tought it was a problem of how unity8 handled the right clicks. Instead I just tried with a mouse and right click trigger different actions from left clicks. In the end the problem is that my touchpad right click is considered a left click by the system. This does not happen with an usb mouse. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1603183/+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 1603183] Re: Right click in webbrowser-app doesn't do anything
I just tryed again with a mouse connected and the right click actually works, so the problem happens only with the touchpad's right click. ** Summary changed: - Right click in webbrowser-app doesn't do anything + Right click from touchpad is handled as a left click -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1603183 Title: Right click from touchpad is handled as a left click Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I'm used to have the contextual menus with the right button on the desktop, while on unity8 they still appear pressing and holding (which is fine for touch based devices). When I use the webbrowser-app I can't even open links in different pages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1603183/+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 1603183] Re: Right click in webbrowser-app doesn't do anything
It always work as a left click for me, even outside of the browser. Is there any scenario where a right click does a different action from left click, under unity8, that I can try to test if that's an input problem or just the way the system reacts to right clicks? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1603183 Title: Right click in webbrowser-app doesn't do anything Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I'm used to have the contextual menus with the right button on the desktop, while on unity8 they still appear pressing and holding (which is fine for touch based devices). When I use the webbrowser-app I can't even open links in different pages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1603183/+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
