Re: [Touch-packages] [Bug 1674137] Re: ifdown unknown interface net-tools is broken

[Roger Lawhorn]

i am using 21.1
18 was a long time ago


On 1/29/24 11:01 AM, Ken Sharp wrote:
> Are you still seeing this issue?
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to net-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1674137

Title:
  ifdown unknown interface net-tools is broken

Status in Linux Mint:
  New
Status in net-tools package in Ubuntu:
  New

Bug description:
  System:Host: GT70-2PE Kernel: 4.5.4-040504-generic x86_64 (64 bit gcc: 
5.3.1)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9) Distro: Linux Mint 18.1 Serena
  Network:   Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller
     driver: alx port: d000 bus-ID: 03:00.0
     IF: enp3s0 state: up speed: 1000 Mbps duplex: full
     Card-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: 
ath9k bus-ID: 04:00.0
     IF: wlp4s0 state: up

  After mint 18.1 upgrade had various issues.
  After quite a few updates I started having issues with ifdown command.

  I use a script with qemu to setup a bridge (br0) with tap0 and the default 
wired connection enp3s0. The script began giving off unknown interface errors.
  Testing showed that the ifdown command changed behavior after the updates and 
now does this.
  The behavior is not limited to scripting.
  I changed the code from using ifdown to ifconfig enp3s0 down.
  This fails also within the script but with no error.
  It, however, works from a terminal just fine.
  I switched to using the ip command i.e. ip link set enp3s0 down.
  Same result, the interface does not go down, but no error.
  After the script is run and windows 7 boots in qemu I have to open a terminal 
and run the commands manually:
  >ifconfig enp3s0 down
  >ifconfig enp3s0 0.0.0.0 promisc up

  Then all is well.
  These commands will not run from within a script.
  The script is run as such:
  >sudo ./up.sh tap0

  It creates br0 and tap0 and adds enp3s0 and tap0 to the bridge.

  The fact that ifdown no longer recognizes any interfaces seems to
  point to a change in net-tools that has broken something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1674137/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

[Roger Nelson]

Indeed. I would have preferred to remain on LTS.

-- 
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/2036358

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

[Roger Nelson]

My shotgun approach may seem unorthodox but I've been frustrated since I
am confident the systemd update created this issue. However, I withdraw
my hesitation to use the word arbitrary. :D

Data point 1: Imaged a vanilla RPI4 with Ubuntu 22.04. The only thing I
changed was the netplan config to mimic my ethernet config for eth0 and
eth1 (USB3 dongle). Fails as before with systemd-networkd-wait-
online.service failing, and ~30 minute timeout before network was
available and able to ssh into the RPI4. Still eth1 USB dongle had to be
systemd-networkd restart to obtain IP address.

Data point 2: do-release-upgrade of newly imaged RPI4 to 23.04. Still
fails with systemd-networkd-wait-online.service failing but with only
~20 timeout and eth1 comes up with IP address after reboot.

Data point 3: do-release-upgrade of newly imaged RPI 23.04 to 23.10.
Works flawlessly. No timeout. Systemd-networkd-wait-online.service no
longer failing.

Data point 4: Performed the same do-release-upgrades on the original
failing RPI4 and the same resulted on 23.04 and now 23.10. I now have my
original RPI4 working like it was prior to the systemd update. I guess I
should be stoked, and I am happy to be relieved of that dreaded timeout
but I wanted to pass on this detail in case it sparked a level of
interest. I can't imagine that I am the only one that has experienced
this. And even if I am it is so curious. Best regards --any :D

-- 
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/2036358

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

[Roger Nelson]

Thank you Veli-Jussi for your comment and providing this information. It
appears this or similar problem has been around for a while but as I
stated in my earlier post I only encountered this timeout issue after
the update and it still exists in 249.11-0ubuntu3.11. After the dreaded
timeout (and for USB3 dongle eth1 a restart of systemd-networkd) both
eth0 and eth1 'networkct list' them as 'configured' as seen in previous
post so unless I'm misreading this both interfaces are managed by
networkd.

-- 
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/2036358

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

[Roger Nelson]

Thank you Steve, perhaps you are right and unrelated. I will open a
separate bug. What confused me (still) is why systemd-wait-
online.service fails same/similar???

sudo systemctl status systemd-networkd-wait-online.service
× systemd-networkd-wait-online.service - Wait for Network to be Configured
 Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; 
enabled-runtime; vendor preset: disabled)
 Active: failed (Result: exit-code) since Sun 2023-12-10 07:51:38 PST; 
11min ago
   Docs: man:systemd-networkd-wait-online.service(8)
Process: 1096 ExecStart=/lib/systemd/systemd-networkd-wait-online 
--timeout=5 --any (code=exited, status=1/FAILURE)
   Main PID: 1096 (code=exited, status=1/FAILURE)
CPU: 24ms

Dec 10 07:34:09 raspi2 systemd[1]: Starting Wait for Network to be Configured...
Dec 10 07:50:42 raspi2 systemd[1]: Dependency failed for Wait for Network to be 
Configured.
Dec 10 07:50:42 raspi2 systemd[1]: systemd-networkd-wait-online.service: Job 
systemd-networkd-wait-online.service/start failed with result 'dependency'.
Dec 10 07:51:38 raspi2 systemd-networkd-wait-online[1096]: Timeout occurred 
while waiting for network connectivity.
Dec 10 07:51:38 raspi2 systemd[1]: systemd-networkd-wait-online.service: Main 
process exited, code=exited, status=1/FAILURE
Dec 10 07:51:38 raspi2 systemd[1]: systemd-networkd-wait-online.service: Failed 
with result 'exit-code'.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2036358

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

[Roger Nelson]

I'm curious if this bug is still being investigated. RPI4 with wlan0,
eth0 and eth1 (USB3 using r8152 driver) definitely manifests this bug. I
need to wait ~30 minutes before either wlan0 or eth0 becomes available
in order to restart systemd-networkd to activate eth1 and then ip link
set up eth1. At that point the network appears stable until next reboot.

IDX LINK TYPE OPERATIONAL SETUP
  1 lo   loopback carrier unmanaged
  2 eth0 etherroutableconfigured
  4 wlan0wlan routableunmanaged
  5 tun0 none routableunmanaged
  6 docker0  bridge   routableunmanaged
  8 vethd334874  etherdegradedunmanaged
  9 eth1 etherroutableconfigured
 14 veth1a9ad92  etherdegradedunmanaged
 16 vethe09f689  etherdegradedunmanaged
 18 veth592971d  etherdegradedunmanaged
 19 macvlan-shim etherroutableunmanaged
 21 vethafb615d  etherdegradedunmanaged

I hesitate using the word arbitrary but given how RPI4 utilizes both
networkmanager and networkd it appears arbitrary to state that only
networkmanager should be used in a desktop installation - at least I
cannot find any documentation that supports not using both
simultaneously. That said, I have been running this configuration for at
least 2 years without issue *until* systemd was updated.

I'm a new Ubuntu-One user and this is my first post after waiting
patiently for post #52 & #58 to get responses from anyone - so please
forgive (and forget :). Constructive criticism humbly accepted.

-- 
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/2036358

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1381623] Re: CRITICAL: gtk_icon_info_get_filename: assertion 'icon_info != NULL' failed

[Roger Davis]

NOT fixed !!!

This message, among several others, repeats rapidly, hard drive continually 
seeks, system unusable.  Reboot, runs ok for a while (couple hours or so), then 
it starts again.  Sometimes I have to use the reset button to stop it, 
sometimes I can get to restart.
Just a very short set of sample4s below :

Aug 31 21:24:26 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:25:03 roger-desktop rtkit-daemon[1573]: Supervising 5 threads of 2 
processes of 1 users.
Aug 31 21:25:05 roger-desktop rtkit-daemon[1573]: message repeated 3 times: [ 
Supervising 5 threads of 2 processes of 1 users.]
Aug 31 21:25:26 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:25:26 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:25:26 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:25:26 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:25:26 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:25:26 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:25:50 roger-desktop PackageKit: daemon quit
Aug 31 21:25:50 roger-desktop systemd[1]: packagekit.service: Succeeded.
Aug 31 21:25:56 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:25:56 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:25:56 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:25:56 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:25:56 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:25:56 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:26:26 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:26:26 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:26:26 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:26:26 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:26:26 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:26:26 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:26:56 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:26:56 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:26:56 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:26:56 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:26:56 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:26:56 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:27:56 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:27:56 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:27:56 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:27:56 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:27:56 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:27:56 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:28:26 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:28:26 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:28:26 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:28:26 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:28:26 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:28:26 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:28:56 roger-desktop gnome-panel[2348]: gtk_icon_info_get_filename: 
assertion 'icon_info != NULL' failed
Aug 31 21:28:56 roger-desktop gnome-panel[2348]: g_object_unref: assertion 
'G_IS_OBJECT (object)' failed
Aug 31 21:28:56

[Touch-packages] [Bug 677139] Hello, 677139

[roger mateo]

https://bit.ly/31wE2Ox

-- 
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/677139

Title:
  [Realtek ID 275] Recording problem intenal micphone , internal laptop
  speacker no not work., however when you use speacker or micphone via
  jacks external audio works.

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  internal laptop micophone, internal laptop speackers do not work.
  external speackers and external micophone via jacks will work.
  this is the i386 10.04 desktop version. on sony laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roger  1563 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xdb40 irq 22'
 Mixer name : 'Intel G45 DEVIBX'
 Components : 'HDA:10ec0275,104d4100,0015 
HDA:80862804,104d4100,0010'
 Controls  : 8
 Simple ctrls  : 4
  Date: Thu Nov 18 13:43:31 2010
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [Realtek ID 275] Recording problem
  dmi.bios.date: 12/16/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0270Q3
  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:bvnINSYDE:bvrR0270Q3:bd12/16/2009:svnSonyCorporation:pnVPCS111FM:pvrC103WRC4:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCS111FM
  dmi.product.version: C103WRC4
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/677139/+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 1921484] Re: libedit no longer reads editrc

[roger espel llima]

Same here, mysql command line used to read bindings from .editrc in
previous versions of Ubuntu Server, now fails to honor them in 20.04
LTS.  Strace confirms that libedit is not opening the file .editrc.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libedit in Ubuntu.
https://bugs.launchpad.net/bugs/1921484

Title:
  libedit no longer reads editrc

Status in libedit package in Ubuntu:
  Confirmed

Bug description:
  strings /usr/lib/x86_64-linux-gnu/libedit.so.2.0.56 |grep editrc in
  Ubuntu 18.04 LTS returns /.editrc as expected but strings
  /usr/lib/x86_64-linux-gnu/libedit.so.2.0.63 |grep editrc in Ubuntu
  20.04 LTS comes back empty. Verified with strace'ing the mysql client
  as well: editrc is no longer picked up, making mysql rather irritating
  to use. Peeking at the source code, the problematic commit is d253f567
  which wraps the editrc code in an "#ifdef HAVE_ISSETUGID" which is BSD
  only. I am unable to find upstream in version control to help further.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libedit/+bug/1921484/+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 1919003] Re: Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3

[Roger Fischer]

My initial conclusion may not have been correct.

I now think that the fix in iproute2 4.15.0-2ubuntu1.3 made the problem
more apparent.

The Network Name Resolution service is not actually failing. It is being
stopped and restarted (based on the logs).

So the real problem seems to be a very aggressive approach to restarting
the Network Name Resolution service.

In our case, the DHCPClient request is not getting a response, yet the
Network Name Resolution service is still being restarted.

Mar 13 03:43:32 em-vf-ns1 dhclient[3443]: DHCPDISCOVER on nsblk01 to 
255.255.255.255 port 67 interval 5 (xid=0xe499a07d)
Mar 13 03:43:37 em-vf-ns1 dhclient[3443]: No DHCPOFFERS received.
Mar 13 03:43:37 em-vf-ns1 dhclient[3443]: No working leases in persistent 
database - sleeping.

Mar 13 03:43:37 em-vf-ns1 systemd[1]: Stopping Network Name Resolution...
Mar 13 03:43:37 em-vf-ns1 systemd[1]: Stopped Network Name Resolution.
Mar 13 03:43:37 em-vf-ns1 systemd[1]: Starting Network Name Resolution...
Mar 13 03:43:37 em-vf-ns1 systemd[1]: Started Network Name Resolution.
Mar 13 03:43:37 em-vf-ns1 systemd[1]: Starting 
resolvconf-pull-resolved.service...
Mar 13 03:43:37 em-vf-ns1 systemd[1]: Started resolvconf-pull-resolved.service.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1919003

Title:
  Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3

Status in iproute2 package in Ubuntu:
  New

Bug description:
  The following is repeated periodically in the syslog:

  Feb 28 20:25:02 em-cel1 systemd[1]: Started Network Name Resolution.
  Feb 28 20:25:02 em-cel1 systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Feb 28 20:25:02 em-cel1 systemd[1]: Started resolvconf-pull-resolved.service.
  Feb 28 20:25:19 em-cel1 systemd[1]: Stopping Network Name Resolution...
  Feb 28 20:25:19 em-cel1 systemd[1]: Stopped Network Name Resolution.
  Feb 28 20:25:19 em-cel1 systemd[1]: Starting Network Name Resolution...

  There is no log anywhere to indicate why the service failed.

  The service stopped failing when we downgraded iproute2 from
  4.15.0-2ubuntu1.3 to 4.15.0-2ubuntu1.1.

  The DHCPClient seems to be involved in the chain of events.

  At the same frequency as the service failures, we do an ifup on a non-
  auto dhcp interface. The ifup results in a DHCP request, which in this
  case does not get a response (the link to the DHCP server is down.

  When we stop the process that does the periodic ifup, the service
  remains up (with iproute2 4.15.0-2ubuntu1.3).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1919003/+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 1919003] [NEW] Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3

[Roger Fischer]

Public bug reported:

The following is repeated periodically in the syslog:

Feb 28 20:25:02 em-cel1 systemd[1]: Started Network Name Resolution.
Feb 28 20:25:02 em-cel1 systemd[1]: Starting resolvconf-pull-resolved.service...
Feb 28 20:25:02 em-cel1 systemd[1]: Started resolvconf-pull-resolved.service.
Feb 28 20:25:19 em-cel1 systemd[1]: Stopping Network Name Resolution...
Feb 28 20:25:19 em-cel1 systemd[1]: Stopped Network Name Resolution.
Feb 28 20:25:19 em-cel1 systemd[1]: Starting Network Name Resolution...

There is no log anywhere to indicate why the service failed.

The service stopped failing when we downgraded iproute2 from
4.15.0-2ubuntu1.3 to 4.15.0-2ubuntu1.1.

The DHCPClient seems to be involved in the chain of events.

At the same frequency as the service failures, we do an ifup on a non-
auto dhcp interface. The ifup results in a DHCP request, which in this
case does not get a response (the link to the DHCP server is down.

When we stop the process that does the periodic ifup, the service
remains up (with iproute2 4.15.0-2ubuntu1.3).

** Affects: iproute2 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1919003

Title:
  Network Name Resolution fails with iproute2 4.15.0-2ubuntu1.3

Status in iproute2 package in Ubuntu:
  New

Bug description:
  The following is repeated periodically in the syslog:

  Feb 28 20:25:02 em-cel1 systemd[1]: Started Network Name Resolution.
  Feb 28 20:25:02 em-cel1 systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Feb 28 20:25:02 em-cel1 systemd[1]: Started resolvconf-pull-resolved.service.
  Feb 28 20:25:19 em-cel1 systemd[1]: Stopping Network Name Resolution...
  Feb 28 20:25:19 em-cel1 systemd[1]: Stopped Network Name Resolution.
  Feb 28 20:25:19 em-cel1 systemd[1]: Starting Network Name Resolution...

  There is no log anywhere to indicate why the service failed.

  The service stopped failing when we downgraded iproute2 from
  4.15.0-2ubuntu1.3 to 4.15.0-2ubuntu1.1.

  The DHCPClient seems to be involved in the chain of events.

  At the same frequency as the service failures, we do an ifup on a non-
  auto dhcp interface. The ifup results in a DHCP request, which in this
  case does not get a response (the link to the DHCP server is down.

  When we stop the process that does the periodic ifup, the service
  remains up (with iproute2 4.15.0-2ubuntu1.3).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1919003/+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 677139] Fwd:

[roger mateo]

�� �� �� �� https://bitly.com/3ffH1ws �� �� ��


From: natopeacekeeper 

Sent: Saturday, June 13, 2020 12:39:09 PM

To: 677...@bugs.launchpad.net

Subject: 
��





http://www.bing.com/search?q==FUBMECYDTFWTZQW=QCBWHHWYPBMMYFZ

-- 
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/677139

Title:
  [Realtek ID 275] Recording problem intenal micphone , internal laptop
  speacker no not work., however when you use speacker or micphone via
  jacks external audio works.

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  internal laptop micophone, internal laptop speackers do not work.
  external speackers and external micophone via jacks will work.
  this is the i386 10.04 desktop version. on sony laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roger  1563 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xdb40 irq 22'
 Mixer name : 'Intel G45 DEVIBX'
 Components : 'HDA:10ec0275,104d4100,0015 
HDA:80862804,104d4100,0010'
 Controls  : 8
 Simple ctrls  : 4
  Date: Thu Nov 18 13:43:31 2010
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [Realtek ID 275] Recording problem
  dmi.bios.date: 12/16/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0270Q3
  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:bvnINSYDE:bvrR0270Q3:bd12/16/2009:svnSonyCorporation:pnVPCS111FM:pvrC103WRC4:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCS111FM
  dmi.product.version: C103WRC4
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/677139/+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 1880347] Re: Permanent pointer arrow at center of screen

[Roger Hsu]

Unfortunately, after a recent restart, the problem has returned, and my
prior trick of changing the Refresh Rate no longer fixes the problem.

-- 
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/1880347

Title:
  Permanent pointer arrow at center of screen

Status in xorg package in Ubuntu:
  New

Bug description:
  There is a permanent pointer arrow on my screen. I have included a
  screenshot. The pointer arrow in the center of the screen is *not* my
  mouse pointer. My mouse pointer functions normally but I can't get rid
  of the pointer arrow in the center of the screen. I have not tried
  restarting the system to see if it goes away as I wanted to file this
  bug first.

  OS Name: Ubuntu 20.04 LTS
  OS Type: 64-bit
  GNOME Version: 3.36.2
  Windowing System: X11

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34
  Uname: Linux 5.4.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 23 17:07:19 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [1002:67df] (rev e7) (prog-if 00 [VGA 
controller])
 Subsystem: Sapphire Technology Limited Nitro+ Radeon RX 570/580/590 
[1da2:e366]
  InstallationDate: Installed on 2020-05-23 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic 
root=UUID=2fd43526-0b59-4c37-890d-023522b1288c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.10
  dmi.board.name: AB350M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.10:bd08/30/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4:rvr:cvnToBeFilledByO.E.M.: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.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1880347/+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 1854595] [NEW] package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to install/upgrade: installed libssl1.1:amd64 package post-installation script subprocess returned error ex

[Roger Keller Celeste]

Public bug reported:

I was doing a partial upgrade

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5
ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
Uname: Linux 4.15.0-70-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
Date: Sat Nov 30 19:02:39 2019
ErrorMessage: installed libssl1.1:amd64 package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2015-06-13 (1631 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12
SourcePackage: openssl
Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to 
install/upgrade: installed libssl1.1:amd64 package post-installation script 
subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssl (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 openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1854595

Title:
  package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to
  install/upgrade: installed libssl1.1:amd64 package post-installation
  script subprocess returned error exit status 1

Status in openssl package in Ubuntu:
  New

Bug description:
  I was doing a partial upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  Uname: Linux 4.15.0-70-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  Date: Sat Nov 30 19:02:39 2019
  ErrorMessage: installed libssl1.1:amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-06-13 (1631 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.3
   apt  1.6.12
  SourcePackage: openssl
  Title: package libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.5 failed to 
install/upgrade: installed libssl1.1:amd64 package post-installation script 
subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1854595/+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 1532431] Re: NetworkManager interferes with unmanaged 802.11 monitor mode interfaces

[Roger James]

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

-- 
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/1532431

Title:
  NetworkManager interferes with unmanaged 802.11 monitor mode
  interfaces

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  If a virtual 802.11 interface of type monitor is created on a 802.11
  physical interface that already has a virtual interface of type
  managed created on it, then the managed interface is deleted.
  NetworkManager sets the type of the monitor interface to managed. This
  can be illustrated by the following commands. All the interface names
  have been listed in /etc/network/interfaces as follows so
  NetworkManager should not be managing them in any way.

  # Disable network manager on interface names I want to use for monitoring
  # related purposes
  iface eth1 inet manual
  iface BigTenda inet manual
  iface LittleBelkin inet manual
  iface LittleTenda inet manual
  iface Sinmax inet manual
  iface mon0 inet manual
  iface phy0.mon manual
  iface phy1.mon manual
  iface phy2.mon manual
  iface phy3.mon manual
  iface phy4.mon manual
  iface phy5.mon manual
  iface phy6.mon manual
  iface phy7.mon manual
  iface phy8.mon manual
  iface phy9.mon manual

  root@dragon:/home/roger# systemctl start NetworkManager
  root@dragon:/home/roger# iw dev
  phy#3
Interface Sinmax
ifindex 11
wdev 0x30001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw phy phy3 interface add phy2.mon type monitor 
flags otherbss
  root@dragon:/home/roger# iw dev
  phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 11
wdev 0x30001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw dev Sinmax del
  root@dragon:/home/roger# iw dev
  phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# systemctl stop NetworkManager
  root@dragon:/home/roger# iw dev
  phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# # Unplug the netwaork adapter for a few seconds
  root@dragon:/home/roger# iw dev
  phy#4
Interface Sinmax
ifindex 13
wdev 0x40001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw phy phy4 interface add phy2.mon type monitor 
flags otherbss
  root@dragon:/home/roger# iw dev
  phy#4
Interface phy2.mon
ifindex 14
wdev 0x40002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 13
wdev 0x40001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw dev Sinmax del
  root@dragon:/home/roger# iw dev
  phy#4
Interface phy2.mon
ifindex 14
wdev 0x40002
addr 00:0f:11:92:06:b2
type monitor

  This stops any running or future network traces on this interface
  working.

  This is another example of network manager interfering with interfaces
  it is not supposed to be managing. See bug #1314848 which is still
  unresolved.

  The above test was carried out on Ubuntu 15.10

  network-manager:
Installed: 1.0.4-0ubuntu5.2
Candidate: 1.0.4-0ubuntu5.2
Version table:
   *** 1.0.4-0ubuntu5.2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.4-0ubuntu5 0
  500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532431/+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 892918] Re: Cannot start jack using qjackctrl via dbus when playback only option is needed

[Roger James]

** Changed in: jackd2 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/892918

Title:
  Cannot start jack using qjackctrl via dbus when playback only option
  is needed

Status in jackd2 package in Ubuntu:
  Invalid

Bug description:
  My audio hardware requires the playback only option to be specified to
  successfully start jackd. However I cannot start jackd with this
  option via qjackctrl unless dbus startup option is disabled. I am
  guessing that qjacktrl causes a dbus jackd with default parameters to
  be started (and stopped) before it tries to start the one with the
  playback only parameter. Starting a jackd without the playback only
  parameter always results in a server that hang and doe not respond to
  any client requests. Catch 22.

  Ubuntu 11.10
  jackd2 1.9.7~dsfg-1ubuntu2
  qjackctl 0.3.8-1

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: jackd2 1.9.7~dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  Date: Mon Nov 21 01:32:38 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: jackd2
  UpgradeStatus: Upgraded to oneiric on 2011-10-15 (36 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/892918/+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 1759014] Re: Netplan has no way to control DHCP client

[Roger Mårtensson]

Is it possible to get this into 18.04.3 release? Not that fond of
waiting until January 2020 for the .4 release.

-- 
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/1759014

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1759014] Re: Netplan has no way to control DHCP client

[Roger Mårtensson]

Is it possible to get this into 18.04.3 release? Not that fond of
waiting until January 2020 for the .4 release.

-- 
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/1759014

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1272380] Re: Missing whitespace between generated man page refentrys

[Roger Light]

This is no longer an issue in recent Ubuntu releases.

** Changed in: libxslt (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxslt in Ubuntu.
https://bugs.launchpad.net/bugs/1272380

Title:
  Missing whitespace between generated man page refentrys

Status in libxslt package in Ubuntu:
  Fix Released

Bug description:
  I am generating man pages from docbook xml using xsltproc and
  /usr/share/xml/docbook/stylesheet/docbook-xsl/manpages/docbook.xsl

  My man page contains entries like this for the "See Also" section:

 
  mosquitto
  8
  
  
  mosquitto-conf
  5
  

  When I process the man pages using xsltproc from Saucy, the resulting
  code looks like:

  \fBmosquitto\fR(8)\fBmosquitto-conf\fR(5)

  When viewed in man, this looks like "mosquitto(8)mosquitto-conf(5)" -
  with no space between the two entries.

  On Precise, the output from the same man page is:

  \fBmosquitto\fR(8)
  \fBmosquitto-conf\fR(5)

  and when viewed in man this looks like "mosquitto(8) mosquitto-
  conf(5)" as expected.

  The xml man pages and Makefile to generate the troff output can be
  found in http://mosquitto.org/files/source/mosquitto-1.2.3.tar.gz in
  the man directory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1272380/+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 1822966] Re: apport-bug locks up when selecting "Cancel"

[Roger Light]

Just to confirm, because Brian had a slightly different version number,
this still exists on 2.20.10-0ubuntu26.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1822966

Title:
  apport-bug locks up when selecting "Cancel"

Status in apport package in Ubuntu:
  New

Bug description:
  To reproduce:

  * Run "apport-bug" from the command line
  * Select "Other problem" from the "What kind of problem do you want to 
report?", then click OK.
  * The "What display problem do you observe?" dialogue pops up, I realise that 
doesn't match anything that I want to report and click Cancel.
  * Apport becomes completely unresponsive.

  Traceback after Ctrl-C suggests that there is a problem with a thread
  lock:

  Exception ignored in: 
  Traceback (most recent call last):
File "/usr/lib/python3.7/threading.py", line 1281, in _shutdown
  t.join()
File "/usr/lib/python3.7/threading.py", line 1032, in join
  self._wait_for_tstate_lock()
File "/usr/lib/python3.7/threading.py", line 1048, in _wait_for_tstate_lock
  elif lock.acquire(block, timeout):
  KeyboardInterrupt

  This is on Kubuntu 19.04, apport 2.20.10-0ubuntu23

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1822966/+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 1769231] Re: wpa_cli -i flag and p2p_disabled=1 config broken

[Roger James]

The p2p-disabled flag is not supported until wpa-supplicant 2.5+.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1769231

Title:
  wpa_cli -i flag and p2p_disabled=1 config broken

Status in wpa package in Ubuntu:
  Confirmed

Bug description:
  When connecting to wpa_supplicant with wpa_cli -i interface command,
  the connection hangs and never completes.  This breaks various
  ifupdown integrations.

  Also, when p2p_disable=1 is set in wpa_supplicant.conf, the directive
  is not honored.

  I pulled the latest upstream hostap 2.6 source from git and built it
  using the same config file pulled from the deb source and tested to
  verify.  Oddly the bug is actually in the wpa_supplicant binary as
  starting 2.6 with the right flags allows both the 2.4 and the 2.6
  client to work correctly.  However, starting the 2.4 daemon provided
  by artful causes both wpa_cli -i connection flags to fail.

  Starting the packaged wpa_supplicant throws an odd warning as well,
  not the double prefix on the p2p-dev.

  /sbin/wpa_supplicant -B -P /run/wpa_supplicant.wlp4s0.pid -i wlp4s0 -W -D 
nl80211 -c /etc/wpa_supplicant/wpa_supplicant.conf
  Successfully initialized wpa_supplicant
  Could not read interface p2p-dev-wlp4s0 flags: No such device
  Failed to create interface p2p-dev-p2p-dev-wlp4s0: -22 (Invalid argument)
  nl80211: Failed to create a P2P Device interface p2p-dev-p2p-dev-wlp4s0
  P2P: Failed to enable P2P Device interface

  Also, in the presence of the p2p_disabled=1 flag, the 2.6 daemon
  provides the expected behavior of simply not creating the addition
  /run/wpa_supplicant/p2p-dev-wlp4s0 socket and unnamed device as seen
  by iw dev.  However, the packaged version still creates both,
  apparently leaving p2p enabled.

  root@mendota:~/code/hostap/wpa_supplicant# iw dev
  phy#0
  Unnamed/non-netdev interface
  wdev 0x5e
  addr e0:9d:31:d6:45:f3
  type P2P-device
  txpower 0.00 dBm
  Interface wlp4s0
  ifindex 3
  wdev 0x1
  addr e0:9d:31:d6:45:f2
  type managed
  txpower 22.00 dBm
  root@mendota:~/code/hostap/wpa_supplicant# ls -l /run/wpa_supplicant
  total 0
  srwxrwx--- 1 root dialout 0 May  4 12:49 p2p-dev-wlp4s0
  srwxrwx--- 1 root dialout 0 May  4 12:49 wlp4s0

  root@mendota:~/code/hostap/wpa_supplicant# wpa_cli -p /run/wpa_supplicant -i 
wlp4s0
  wpa_cli v2.4
  Copyright (c) 2004-2015, Jouni Malinen  and contributors

  This software may be distributed under the terms of the BSD license.
  See README for more details.


  Interactive mode

  Warning: Failed to attach to wpa_supplicant.
  Could not connect to wpa_supplicant: wlp4s0 - re-trying ...

  Note that 2.6 still allows a connection even when p2p_disabled is not
  set and the unnammed p2p dev and socket is created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: wpasupplicant 2.4-0ubuntu10
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Fri May  4 12:49:50 2018
  ProcEnviron:
   LANGUAGE=en_US
   TERM=screen.xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1769231/+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 1787645] [NEW] Most, but not all, boots from cold, I get a Low Graphics Mode error

[Roger Davis]

Public bug reported:

After an update (kernel?), I have begun to receive the message "Running
in Low Graphics Mode" at boot. I can tell it to use Default setting from
the options it offers, and get by it, after which things look and work
normally until a reboot, which may or may not occur correctly.

If I select extra graphics debug messages and display boot messages in
Xdiagnose, this problem DOES NOT occur.  If I deselect those, the
problem begins again.

I don't know which update caused it, but it was somewhere around mid or
early May.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
.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
Date: Fri Aug 17 12:02:03 2018
DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.38, 4.15.0-30-generic, x86_64: installed
 virtualbox, 5.1.38, 4.15.0-32-generic, x86_64: installed
 virtualbox, 5.1.38, 4.4.0-133-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
InstallationDate: Installed on 2014-07-07 (1502 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro quiet plymouth:debug=1 
plymouth:debug=1=1=1=1=1 splash plymouth:debug=1=1=1=1=1=1=1=1=1 
plymouth:debug=1=1=1=1=1=1=1=1=1=1=1=1=1 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-12-18 (607 days ago)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
dmi.board.name: DZ77BH-55K
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39008-400
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
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: Fri Aug 17 12:00:19 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4~16.04.1

** 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/1787645

Title:
  Most, but not all, boots from cold, I get a Low Graphics Mode error

Status in xorg package in Ubuntu:
  New

Bug description:
  After an update (kernel?), I have begun to receive the message
  "Running in Low Graphics Mode" at boot. I can tell it to use Default
  setting from the options it offers, and get by it, after which things
  look and work normally until a reboot, which may or may not occur
  correctly.

  If I select extra graphics debug messages and display boot messages in
  Xdiagnose, this problem DOES NOT occur.  If I deselect those, the
  problem begins again.

  I don't know which update caused it, but it was somewhere around mid
  or early May.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  .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
  Date: Fri Aug 17 12:02:03 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.1.38, 4.15.0-30-generic, x86_64: installed
   virtualbox, 5.1.38, 

[Touch-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

[Roger Davis]

I can't follow the above instruction, since before that date (6/5/18) I
have turned off all options in X-Diagnose, and the system boots every
time now.

BUT :
1) The boot process is now verbose, despite turning off all options, and I 
can't change this back to quiet, which could produce the problem again.
2) Occasionally upon reboot after a new kernel is installed, the system comes 
up in Ambiance theme, where I had it in Adwatia.  To get it back is not 
straighforward, I must either reboot into straight Ubuntu (not Gnome Flashback) 
and reset it, or cycle through the options a few times until it sticks.  This 
might be a clue?

-- 
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/1772386

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Expired

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  This problem shows up using GNOME Flashback or Unity.

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  WORKAROUND: Using x-diagnose, I selected all options under both Debug
  and Workarounds.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1413 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug drm.debug=0xe 
nopat vesafb.invalid=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (519 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon May 21 01:25:13 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772386/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Roger Bergling]

Adding this and downgrade the curl worked for me.
https://launchpad.net/~xapienz/+archive/ubuntu/curl34

My application that was the problem was sky from tel.red

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1754294

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

[Roger Davis]

Today, with Xdiagnose unused, I again had an error message "Running in
Low Graphics Mode", after about a dozen starts with no problem.

I again engaged Xdiagnose, checked the top 3 boxes about functions, and
also engaged "Disable bootloader graphics".

Back to checking results...

-- 
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/1772386

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1413 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug drm.debug=0xe 
nopat vesafb.invalid=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (519 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.

[Touch-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

[Roger Davis]

A) Regarding your comment:
>"sudo apt-get install --install-recommends linux-generic-hwe-16.04 
>xserver-xorg-hwe-16.04"

That doesn't confirm you are booted into the HWE kernel. That only shows
that certain packages are installed (which you provided already in a
previous comment).

If you want to demonstrate what kernel is being using currently type:
uname -a
roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 
12:56:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
roger@roger-desktop:~$ 

B) Regarding your comment:
>"...but now after additional other updates, and using Xdiagnose with various 
>settings, I haven't seen a boot problem for a few updates. I will continue to 
>monitor for a few days with Xdiagnose off to assure that problem is really 
>gone."

Sounds good.

B) Regarding your comment:
>"...actually causes a problem in my system. It sets and locks the theme to 
>Ambiance, even though the setting properly shows Adwaita."

Could be a bug, but that isn't the scope of this report. If you want it
fixed, you would have to file a new report.

C) Regarding your comment:
>"Please tell me before I deal with this if this is possibly something done by 
>Xdiagnose..."

Given you don't recall doing it, it was done by Xdiagnose when you
checked its checkboxes.
 Response - -----
A) roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 
12:56:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
roger@roger-desktop:~$

B) Will be checking for several days to confirm if I've just been lucky, or ???
- I'll hold off on filing a bug on Xdiagnose, I know how to fix it, and don't 
want to seem like I find too much fault.

C) ok - Sounds logical to me.

I'll continue to monitor, so please keep this bug report open for a
while.

Thanks!

-- 
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/1772386

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVers

Re: [Touch-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

[Roger Davis]

I understand - thanks !!!



The reasonable man adapts himself to the world.
The unreasonable man persists in trying to adapt the world to himself.
Therefore, all progress depends on the unreasonable man.
,-._,-.
\/)"(\/
(:o:)
  (!)
 


-Original Message-
From: Christopher M. Penalver 
To: rogerdavis 
Sent: Sun, Jun 3, 2018 11:50 pm
Subject: [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups 
- not all

Roger Davis:

a) You are responding multiple times to the same comment, causing confusion. 
Hence, it is best if you looked at the bug report (not email inbox) to confirm 
if you have already responded, and use the website to respond (not send emails):
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1772386

It is helpful if you use the website to "Hide" the duplicate comments
(#6, #9,  and #11) so others don't get confused.

b) Regarding your comment:
>"I'll hold off on filing a bug on Xdiagnose..."

Agreed. If you are using non-default kernel parameters, a potential
response would be "don't do that". However, if you have to use them so
the scope of this report doesn't happen, that's a different story.

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1772386

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  Installat

Re: [Touch-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

[Roger Davis]

A) roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.13.0-43-generic #48~16.04.1-Ubuntu SMP Thu May 17 
12:56:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

roger@roger-desktop:~$


B) Will be checking for several days to confirm if I've just been lucky, or ???
- I'll hold off on filing a bug on Xdiagnose, I know how to fix it, and don't 
want to seem like I find too much fault.
- Sounds logical to me.


I'll continue to monitor, so please keep this bug report open for a while.


Thanks!



-Original Message-
From: Christopher M. Penalver 
To: rogerdavis 
Sent: Sun, Jun 3, 2018 7:25 pm
Subject: [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups 
- not all

Roger Davis:

 A) Regarding your comment:
>"sudo apt-get install --install-recommends linux-generic-hwe-16.04 
>xserver-xorg-hwe-16.04"

That doesn't confirm you are booted into the HWE kernel. That only shows
that certain packages are installed (which you provided already in a
previous comment).

If you want to demonstrate what kernel is being using currently type:
uname -a

 B) Regarding your comment:
>"...but now after additional other updates, and using Xdiagnose with various 
>settings, I haven't seen a boot problem for a few updates. I will continue to 
>monitor for a few days with Xdiagnose off to assure that problem is really 
>gone."

Sounds good.

 B) Regarding your comment:
>"...actually causes a problem in my system. It sets and locks the theme to 
>Ambiance, even though the setting properly shows Adwaita."

Could be a bug, but that isn't the scope of this report. If you want it
fixed, you would have to file a new report.

 C) Regarding your comment:
>"Please tell me before I deal with this if this is possibly something done by 
>Xdiagnose..."

Given you don't recall doing it, it was done by Xdiagnose when you
checked its checkboxes.

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1772386

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Lin

[Touch-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

[Roger Davis]

In response to Christopher M. Penalver

1) same as 3 above

2) roger@roger-desktop:~$ ls -la /var/crash
total 8
drwxrwsrwt  2 root whoopsie 4096 May 29 03:46 .
drwxr-xr-x 15 root root 4096 Dec 17  2016 ..
roger@roger-desktop:~$ 

3) "To confirm, is there a reason you are using the non-default kernel 
parameters (i.e. WORKAROUND a problem):
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1"
- I'm not familiar with that line.  I can guess two possibilities:
- - Something very old in the system, perhaps done to deal with an earlier 
difficulty
- - Some connection with Xdiagnose, which I have been experimenting with 
previously in connection with this problem (now all settings inactivated as of 
today).

4) "If you remove the non-default kernel parameters does this influence the 
reported issue:
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 "
Please tell me before I deal with this if this is possibly something done by 
Xdiagnose, and how to best remove it if that seems advisable.

Thanks!

-- 
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/1772386

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1413 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr&

[Touch-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

[Roger Davis]

1) I cannot tell which update caused this.

2) Not sure how to boot to previous kernels, especially not wanting to
fowl up my settings.

3) roger@roger-desktop:~$ sudo apt-get install --install-recommends 
linux-generic-hwe-16.04 xserver-xorg-hwe-16.04 
[sudo] password for roger: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
linux-generic-hwe-16.04 is already the newest version (4.13.0.43.62).
xserver-xorg-hwe-16.04 is already the newest version (1:7.7+16ubuntu3~16.04.1).
The following packages were automatically installed and are no longer required:
  libqmi-glib1 libqpdf17 python3-notify2 python3-pexpect python3-pil
  python3-ptyprocess python3-pyqt4 python3-renderpm python3-reportlab
  python3-reportlab-accel python3-sip
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
roger@roger-desktop:~$ 

Or do you mean results as to boot with no problems?  - No change to that
on earlier experience, but now after additional other updates, and using
Xdiagnose with various settings, I haven't seen a boot problem for a few
updates.  I will continue to monitor for a few days to assure that
problem is really gone.

In retrospect, it appears likely to me that there was a borderline
timing problem in the boot sequence, and something in the meantime
(almost daily updates, or ???) may have changed that, or maybe I've just
been lucky the past 8 or 10 tries.  Continued watching is appropriate.

Also, the command " sudo apt-get install --install-recommends linux-
generic-hwe-16.04 xserver-xorg-hwe-16.04 "  actually causes a problem in
my system.  It sets and locks the theme to Ambiance, even though the
setting properly shows Adwaita.  It will not allow the theme to be reset
until I reboot into Unity desktop which then allows it to reset properly
to Adwaita.  I don't know if this is a bug, or just the way it works for
diagnostic purposes.  If it's just the way it works, it should be
described in the documentation along with the fix.  If it's a bug, I'll
leave it to others for now.

-- 
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/1772386

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode"

Re: [Touch-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

[Roger Davis]

1) roger@roger-desktop:~$ sudo apt-get install --install-recommends 
linux-generic-hwe-16.04 xserver-xorg-hwe-16.04
[sudo] password for roger:
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-generic-hwe-16.04 is already the newest version (4.13.0.43.62).
xserver-xorg-hwe-16.04 is already the newest version (1:7.7+16ubuntu3~16.04.1).
The following packages were automatically installed and are no longer required:
  libqmi-glib1 libqpdf17 python3-notify2 python3-pexpect python3-pil
  python3-ptyprocess python3-pyqt4 python3-renderpm python3-reportlab
  python3-reportlab-accel python3-sip
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
roger@roger-desktop:~$
Or do you mean results as to boot with no problems?  - No change to that on 
earlier experience, but now after additional other updates, and using Xdiagnose 
with various settings, I haven't seen a boot problem for a few updates.  I will 
continue to monitor for a few days with Xdiagnose off to assure that problem is 
really gone.
In retrospect, it appears likely to me that there was a borderline timing 
problem in the boot sequence, and something in the meantime (almost daily 
updates, or ???) may have changed that, or maybe I've just been lucky the past 
8 or 10 tries.  Continued watching is appropriate.
Also, the command " sudo apt-get install --install-recommends 
linux-generic-hwe-16.04 xserver-xorg-hwe-16.04 "  actually causes a problem in 
my system.  It sets and locks the theme to Ambiance, even though the setting 
properly shows Adwaita.  It will not allow the theme to be reset until I reboot 
into Unity desktop which then allows it to reset properly to Adwaita.  I don't 
know if this is a bug, or just the way it works for diagnostic purposes.  If 
it's just the way it works, it should be described in the documentation along 
with the fix.  If it's a bug, I'll leave it to others for now.

2) roger@roger-desktop:~$ ls -la /var/crash
total 8
drwxrwsrwt  2 root whoopsie 4096 May 29 03:46 .
drwxr-xr-x 15 root root 4096 Dec 17  2016 ..
roger@roger-desktop:~$ 

3) "To confirm, is there a reason you are using the non-default kernel 
parameters (i.e. WORKAROUND a problem):
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1"
- I'm not familiar with that line.  I can guess two possibilities:
- - Something very old in the system, perhaps done to deal with an earlier 
difficulty
- - Some connection with Xdiagnose, which I have been experimenting with 
previously in connection with this problem (now all settings inactivated as of 
today).

4) "If you remove the non-default kernel parameters does this influence the 
reported issue:
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1 "
Please tell me before I deal with this if this is possibly something done by 
Xdiagnose, and how to best remove it if that seems advisable.

Thanks!


-Original Message-
From: Christopher M. Penalver 
To: rogerdavis 
Sent: Sun, Jun 3, 2018 5:40 pm
Subject: [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups 
- not all

Roger Davis:

1) To clarify, when using the upgraded HWE stack, did this influence the
reported issue "message - Low Graphics mode - about 2/3 of startups -
not all"?

2) To narrow down, could you please provide the output of the following 
terminal command (not manually attach anything found):
ls -la /var/crash

3) To confirm, is there a reason you are using the non-default kernel 
parameters (i.e. WORKAROUND a problem):
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1

4) If you remove the non-default kernel parameters does this influence the 
reported issue:
plymouth:debug drm.debug=0xe nopat vesafb.invalid=1

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1772386

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 1144

[Touch-packages] [Bug 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

[Roger Davis]

1) I cannot tell which update caused this.

2) Not sure how to boot to previous kernels

3) roger@roger-desktop:~$ sudo apt-get install --install-recommends 
linux-generic-hwe-16.04 xserver-xorg-hwe-16.04 
[sudo] password for roger: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
linux-generic-hwe-16.04 is already the newest version (4.13.0.43.62).
xserver-xorg-hwe-16.04 is already the newest version (1:7.7+16ubuntu3~16.04.1).
The following packages were automatically installed and are no longer required:
  libqmi-glib1 libqpdf17 python3-notify2 python3-pexpect python3-pil
  python3-ptyprocess python3-pyqt4 python3-renderpm python3-reportlab
  python3-reportlab-accel python3-sip
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
roger@roger-desktop:~$ 

Or do you mean results as to boot with no problems?  - No change to
that.

-- 
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/1772386

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1413 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-

[Touch-packages] [Bug 1773485] [NEW] Supplement to 1772...@bugs.launchpad.net,

[Roger Davis]

Public bug reported:

Supplement to 1772...@bugs.launchpad.net,

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri May 25 22:06:57 2018
DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
InstallationDate: Installed on 2014-07-07 (1418 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug=1 splash quiet 
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-12-18 (524 days ago)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
dmi.board.name: DZ77BH-55K
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39008-400
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-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: Fri May 25 22:03:00 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

** 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/1773485

Title:
  Supplement to 1772...@bugs.launchpad.net,

Status in xorg package in Ubuntu:
  New

Bug description:
  Supplement to 1772...@bugs.launchpad.net,

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri May 25 22:06:57 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1418 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug=1 splash quiet 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (524 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 

[Touch-packages] [Bug 1772386] [NEW] message - Low Graphics mode - about 2/3 of startups - not all

[Roger Davis]

Public bug reported:

After a recent update (kernel?), I have begun to occasionally receive
the message "Running in Low Graphics Mode" at boot (maybe half the
time). I can tell it to use Default setting from the options it offers,
and get by it, after which things look and work normally until a reboot,
which may or may not occur correctly.

I also usually get "System error detected, Report? at the same time, so
I agree to report it.

Please note that I'm using 16.04 (fully updated), Gnome Flashback
Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]
. This problem shows up no matter which of the above I'm using, or
Unity.

roger@roger-desktop:~$ uname -a
Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

roger@roger-desktop:~$ free -m
total used free shared buff/cache available
Mem: 16013 3880 10410 363 1722 11443
Swap: 16348 0 16348

roger@roger-desktop:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 9.6M 1.6G 1% /run
/dev/sda1 902G 77G 779G 9% /
tmpfs 7.9G 127M 7.7G 2% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
cgmfs 100K 0 100K 0% /run/cgmanager/fs
tmpfs 1.6G 52K 1.6G 1% /run/user/1000

I have found a WORK-AROUND. Using x-diagnose, I selected all options
under both Debug and Workarounds.  After this, all works normally every
time.  However, I take this as a crutch, not a fix, and think other
action should be taken

Selecting "View Errors" shows no errors, so I never tried reporting from
that point.

This gives me a presumption that there is a bug in coding that interacts
badly with my system and a few others like it, which I encountered in my
search for a solution.

Also, if I simply go to 18.04 (I don't really want to just yet.) will it
likely fix this or might this block or damage the upgrade?

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
roger@roger-desktop:~$ lsb_release -rd
Description:Ubuntu 16.04.4 LTS
Release:16.04

2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center
roger@roger-desktop:~$ apt-cache policy pkgname
N: Unable to locate package pkgname
ALSO - I'm unable to locate this information in Software Center

3) What you expected to happen
Normal boot, no errors or problems

4) What happened instead
"Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME-Flashback:Unity
Date: Mon May 21 01:56:23 2018
DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
InstallationDate: Installed on 2014-07-07 (1413 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug drm.debug=0xe 
nopat vesafb.invalid=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-12-18 (519 days ago)
dmi.bios.date: 02/08/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
dmi.board.name: DZ77BH-55K
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG39008-400
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon May 21 01:25:13 2018
xserver.configfile: defa

[Touch-packages] [Bug 1732030] Re: 'apt update' dies with seccomp error

[Roger Light]

I've been hit by this problem as well, but for the pread64 syscall. It's
working for me now after playing with my apt conf, getting the bug fix
and then reverting my apt conf, but thought it was worth mentioning
anyway.

I'm on a system with nfs/autofs home directories and nis for logins,
which I bet is the contributing factor.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1732030

Title:
  'apt update' dies with seccomp error

Status in apt package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  $ apt-get update
  0% [Working]
    Seccomp prevented execution of syscall 78 on architecture amd64 

  Reading package lists... Done
  E: Method mirror has died unexpectedly!
  E: Sub-process mirror returned an error code (31)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6~alpha5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 23:10:57 2017
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  SourcePackage: apt
  UpgradeStatus: Upgraded to bionic on 2017-05-20 (177 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1732030/+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 1762818] Re: Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor

[Roger Binns]

A victim of some other fix.  This regression can be prevented by adding
amdgpu.dc=0 to the kernel command line.

-- 
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/1762818

Title:
  Regression: Upgrading from 17.10 to 18.04 reduces resolution available
  on monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Symptom: booting 18.04 kernel reduces resolution available while 17.10
  kernel (on 18.04) does not

  I have a 3 identical monitor setup - all at 2560x1600 native
  resolution.  If I boot the current 18.04 kernel 4.15.0-13-generic then
  the third monitor does not have the native resolution available.  If I
  reboot with the last 17.10 kernel 4.13.0-37-generic then all monitors
  have the native resolution available.

  On the video card the monitors are connected to HDMI, DisplayPort and
  DVI.  On the monitors themselves the connectors are HDMI, DisplayPort
  and HDMI.  (3rd monitor is using DVI to HDMI cable.)

  Xorg logs show identical EDID information between the kernels.
  18.04's just decides to not make 2560x1600 available, having 2048x1080
  or 1920x1200 as the highest.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Apr 10 12:17:31 2018
  DistUpgraded: 2018-03-31 12:24:30,098 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460] [1002:67ef] 
(rev e5) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Baffin [Radeon RX 460/560D / Pro 
450/455/460/560] [1458:230a]
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1456) killed by TERM signal
  MachineType: Supermicro C7Z170-SQ
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=725712a6-f0e0-4da1-b3d1-746a233eb459 ro rootflags=subvol=@
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-31 (9 days ago)
  dmi.bios.date: 12/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: Default string
  dmi.board.name: C7Z170-SQ
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/19/2016:svnSupermicro:pnC7Z170-SQ:pvr0123456789:rvnSupermicro:rnC7Z170-SQ:rvr1.01A:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: Default string
  dmi.product.name: C7Z170-SQ
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+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 1762818] Re: Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor

[Roger Binns]

** Attachment added: "Xorg log when booting with 18.04 kernel"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+attachment/5109717/+files/newkernel.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/1762818

Title:
  Regression: Upgrading from 17.10 to 18.04 reduces resolution available
  on monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Symptom: booting 18.04 kernel reduces resolution available while 17.10
  kernel (on 18.04) does not

  I have a 3 identical monitor setup - all at 2560x1600 native
  resolution.  If I boot the current 18.04 kernel 4.15.0-13-generic then
  the third monitor does not have the native resolution available.  If I
  reboot with the last 17.10 kernel 4.13.0-37-generic then all monitors
  have the native resolution available.

  On the video card the monitors are connected to HDMI, DisplayPort and
  DVI.  On the monitors themselves the connectors are HDMI, DisplayPort
  and HDMI.  (3rd monitor is using DVI to HDMI cable.)

  Xorg logs show identical EDID information between the kernels.
  18.04's just decides to not make 2560x1600 available, having 2048x1080
  or 1920x1200 as the highest.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Apr 10 12:17:31 2018
  DistUpgraded: 2018-03-31 12:24:30,098 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460] [1002:67ef] 
(rev e5) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Baffin [Radeon RX 460/560D / Pro 
450/455/460/560] [1458:230a]
  LightdmGreeterLogOld:
   ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
   ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf
   upstart: indicator-application main process (1456) killed by TERM signal
  MachineType: Supermicro C7Z170-SQ
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=725712a6-f0e0-4da1-b3d1-746a233eb459 ro rootflags=subvol=@
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-03-31 (9 days ago)
  dmi.bios.date: 12/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.0
  dmi.board.asset.tag: Default string
  dmi.board.name: C7Z170-SQ
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/19/2016:svnSupermicro:pnC7Z170-SQ:pvr0123456789:rvnSupermicro:rnC7Z170-SQ:rvr1.01A:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: Default string
  dmi.product.name: C7Z170-SQ
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1762818/+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 1762818] [NEW] Regression: Upgrading from 17.10 to 18.04 reduces resolution available on monitor

[Roger Binns]

Public bug reported:

Symptom: booting 18.04 kernel reduces resolution available while 17.10
kernel (on 18.04) does not

I have a 3 identical monitor setup - all at 2560x1600 native resolution.
If I boot the current 18.04 kernel 4.15.0-13-generic then the third
monitor does not have the native resolution available.  If I reboot with
the last 17.10 kernel 4.13.0-37-generic then all monitors have the
native resolution available.

On the video card the monitors are connected to HDMI, DisplayPort and
DVI.  On the monitors themselves the connectors are HDMI, DisplayPort
and HDMI.  (3rd monitor is using DVI to HDMI cable.)

Xorg logs show identical EDID information between the kernels.  18.04's
just decides to not make 2560x1600 available, having 2048x1080 or
1920x1200 as the highest.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue Apr 10 12:17:31 2018
DistUpgraded: 2018-03-31 12:24:30,098 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Radeon RX 460] [1002:67ef] (rev 
e5) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Baffin [Radeon RX 460/560D / Pro 
450/455/460/560] [1458:230a]
LightdmGreeterLogOld:
 ** Message: Starting lightdm-gtk-greeter 2.0.1 (Aug  7 2015, 01:24:18)
 ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf
 ** Message: [Configuration] Reading file: 
/etc/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf
 ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf
 upstart: indicator-application main process (1456) killed by TERM signal
MachineType: Supermicro C7Z170-SQ
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=725712a6-f0e0-4da1-b3d1-746a233eb459 ro rootflags=subvol=@
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-03-31 (9 days ago)
dmi.bios.date: 12/19/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0
dmi.board.asset.tag: Default string
dmi.board.name: C7Z170-SQ
dmi.board.vendor: Supermicro
dmi.board.version: 1.01A
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd12/19/2016:svnSupermicro:pnC7Z170-SQ:pvr0123456789:rvnSupermicro:rnC7Z170-SQ:rvr1.01A:cvnSupermicro:ct17:cvr0123456789:
dmi.product.family: Default string
dmi.product.name: C7Z170-SQ
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic resolution ubuntu

** Attachment added: "Xorg log when booting with 17.10 kernel"
   
https://bugs.launchpad.net/bugs/1762818/+attachment/5109700/+files/oldkernel.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/1762818

Title:
  Regression: Upgrading from 17.10 to 18.04 reduces resolution available
  on monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Symptom: booting 18.04 kernel reduces resolution available while 17.10
  kernel (on 18.04) does not

  I have a 3 identical monitor setup - all at 2560x1600 native
  resolution.  If I boot the current 18.04 kernel 4.15.0-13-generic then
  the third monitor does not have the native resolution available.  If I
  reboot with the last 17.10 kernel 4.13.0-37-generic then all monitors
  have the native resolution available.

  On the video card the monitors are connected to HDMI, DisplayPort and
  DVI.  On the monitors themselves the connectors are HDMI, DisplayPort
  and HDMI.  (3rd monitor is using DVI to HDMI cable.)

  Xorg logs show identical EDID information between the kernels.
  18.04's just decides to not make 2560x1600 available, having 2048x1080
  or 1920x1200 as the highest.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 

[Touch-packages] [Bug 1562875] Re: Totem can't play H264 on fresh 16.04 beta install

[Roger]

In ubuntu 17.10, this issue disappeared after I installed
gstreamer1.0-libav.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1562875

Title:
  Totem can't play H264 on fresh 16.04 beta install

Status in gstreamer1.0 package in Ubuntu:
  Fix Released

Bug description:
  Totem can't play neither find the correct codec to play H264 *.mp4
  video in last 16.04 beta.

  Terminal says :

  ** Message: Missing plugin: gstreamer|1.0|totem|H.264 (Main Profile)
  decoder|decoder-video/x-h264, stream-format=(string)avc,
  alignment=(string)au, level=(string)4, profile=(string)main, max-
  input-size=(int)51696, parsed=(boolean)true (H.264 (Main Profile)
  decoder)

  
  Totem tries to find the correct codec but fails, see attachment

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.0-1
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 28 15:51:47 2016
  InstallationDate: Installed on 2016-03-26 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
  LogAlsaMixer: Error: command ['/usr/bin/amixer'] failed with exit code 1: 
amixer: Mixer attach default error: No such file or directory
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1562875/+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 1504079] Re: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()

[Roger James]

I have raised this on Gnome Bugzilla. Bug number #787645.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1504079

Title:
  tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  i need

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: tracker-extract 1.4.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic i686
  ApportVersion: 2.19-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Oct  8 16:04:40 2015
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2015-09-13 (25 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xad14eb08 :mov
(%eax),%eax
   PC (0xad14eb08) ok
   source "(%eax)" (0x007c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   gst_video_info_to_caps () from /usr/lib/i386-linux-gnu/libgstvideo-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstlibav.so
   ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
   ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
   avcodec_decode_video2 () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
  Title: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1504079/+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 1504079] Re: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()

[Roger James]

My workaround for ubuntu setups. Is to put a file called .trackerignore
in any directories that contain avi files. The default configuration for
tracker appears to set this.

gsettings get org.freedesktop.Tracker.Miner.Files 
ignored-directories-with-content
['.git', '.trackerignore']

The bug itself needs to be (re)raised with gnome.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1504079

Title:
  tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  i need

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: tracker-extract 1.4.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic i686
  ApportVersion: 2.19-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Oct  8 16:04:40 2015
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2015-09-13 (25 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xad14eb08 :mov
(%eax),%eax
   PC (0xad14eb08) ok
   source "(%eax)" (0x007c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   gst_video_info_to_caps () from /usr/lib/i386-linux-gnu/libgstvideo-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstlibav.so
   ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
   ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
   avcodec_decode_video2 () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
  Title: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1504079/+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 1504079] Re: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()

[Roger James]

Also happening in 17.04. Started happening after a fsck repair following
a power failure. Could be related to lost/corrupt files.

Running tracker-extract manually on file shown in syslog gives the
following.

roger@dragon:~/Documents/Old Stuff/Camtasia Studio$ tracker extract 
--verbosity=detailed visualimpact.avi
Tracker-Message: Starting tracker-extract 1.12.0
Tracker-Message: General options:
Tracker-Message:   Verbosity    2
Tracker-Message:   Sched Idle  ...  1
Tracker-Message:   Max bytes (per file)  .  1048576
Setting priority nice level to 19
Loading extractor rules... (/usr/share/tracker/extract-rules)
Extractor rules loaded
MIME type guessed as 'video/x-msvideo' (from GIO)
gst_video_info_set_format: assertion 'format != GST_VIDEO_FORMAT_UNKNOWN' failed
gst_video_info_to_caps: assertion 'info->finfo->format != 
GST_VIDEO_FORMAT_UNKNOWN' failed

(tracker-extract:5311): GStreamer-CRITICAL **: gst_mini_object_unref: assertion 
'mini_object != NULL' failed
Call to 
gst_discoverer_discover_uri(file:///home/roger/Documents/Old%20Stuff/Camtasia%20Studio/visualimpact.avi)
 failed: Unable to allocate memory
file:///home/roger/Documents/Old%20Stuff/Camtasia%20Studio/visualimpact.avi: No 
metadata or extractor modules found to handle this file

There is an interesting comment in the man page for tracker-extract.

"The  actual  extraction  is done by a separate process. This is done to
isolate the calling process from any memory leaks or crashes in the
libraries Tracker uses to extract metadata."

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1504079

Title:
  tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  i need

  ProblemType: Crash
  DistroRelease: Ubuntu 15.10
  Package: tracker-extract 1.4.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic i686
  ApportVersion: 2.19-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Oct  8 16:04:40 2015
  ExecutablePath: /usr/lib/tracker/tracker-extract
  InstallationDate: Installed on 2015-09-13 (25 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  ProcCmdline: /usr/lib/tracker/tracker-extract
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0xad14eb08 <gst_video_info_to_caps+40>:mov
(%eax),%eax
   PC (0xad14eb08) ok
   source "(%eax)" (0x007c) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   gst_video_info_to_caps () from /usr/lib/i386-linux-gnu/libgstvideo-1.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/gstreamer-1.0/libgstlibav.so
   ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
   ?? () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
   avcodec_decode_video2 () from /usr/lib/i386-linux-gnu/libavcodec-ffmpeg.so.56
  Title: tracker-extract crashed with SIGSEGV in gst_video_info_to_caps()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1504079/+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 1681231] Re: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[roger warrenmortrest]

Where do I go from here

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1681231

Title:
  package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Confirmed
Status in cracklib2 package in Ubuntu:
  Triaged
Status in cracklib2 source package in Trusty:
  Incomplete
Status in cracklib2 source package in Xenial:
  Incomplete
Status in cracklib2 source package in Yakkety:
  Triaged
Status in cracklib2 source package in Zesty:
  Triaged
Status in cracklib2 package in Debian:
  New

Bug description:
  This seems to be the same problem as described in bug #1636262, only
  this time it happened during upgrade from 16.10 to 17.04. The setup
  process (do-release-upgrade -d) aborted and I had to finish it
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: cracklib-runtime 2.9.2-3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu3
  Architecture: amd64
  Date: Sun Apr  9 17:09:37 2017
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.4
  SourcePackage: cracklib2
  Title: package cracklib-runtime 2.9.2-3 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to zesty on 2017-04-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1681231/+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 1674137] Re: ifdown unknown interface net-tools is broken

[Roger Lawhorn]

UPDATE: 
Rewrote my scripts to set enp3s0 AFTER the bridge creation and deletion.
Issue with that part over.

ifdown still broken.
Unknown if script issue is related, but those scripts worked fine before the 
updates.
Perhaps more than one update changed how things work.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to net-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1674137

Title:
  ifdown unknown interface net-tools is broken

Status in Linux Mint:
  New
Status in net-tools package in Ubuntu:
  New

Bug description:
  System:Host: GT70-2PE Kernel: 4.5.4-040504-generic x86_64 (64 bit gcc: 
5.3.1)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9) Distro: Linux Mint 18.1 Serena
  Network:   Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller
     driver: alx port: d000 bus-ID: 03:00.0
     IF: enp3s0 state: up speed: 1000 Mbps duplex: full
     Card-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: 
ath9k bus-ID: 04:00.0
     IF: wlp4s0 state: up

  After mint 18.1 upgrade had various issues.
  After quite a few updates I started having issues with ifdown command.

  I use a script with qemu to setup a bridge (br0) with tap0 and the default 
wired connection enp3s0. The script began giving off unknown interface errors.
  Testing showed that the ifdown command changed behavior after the updates and 
now does this.
  The behavior is not limited to scripting.
  I changed the code from using ifdown to ifconfig enp3s0 down.
  This fails also within the script but with no error.
  It, however, works from a terminal just fine.
  I switched to using the ip command i.e. ip link set enp3s0 down.
  Same result, the interface does not go down, but no error.
  After the script is run and windows 7 boots in qemu I have to open a terminal 
and run the commands manually:
  >ifconfig enp3s0 down
  >ifconfig enp3s0 0.0.0.0 promisc up

  Then all is well.
  These commands will not run from within a script.
  The script is run as such:
  >sudo ./up.sh tap0

  It creates br0 and tap0 and adds enp3s0 and tap0 to the bridge.

  The fact that ifdown no longer recognizes any interfaces seems to
  point to a change in net-tools that has broken something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1674137/+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 1674137] Re: ifdown unknown interface net-tools is broken

[Roger Lawhorn]

UPDATE:
To reverify, ifdown command fails always. net-tools is broken after the update.

I have done extensive testing on my scripts adding Y/N questions to verify that 
each command succeeded. They do. 
Therefore, the ip and ifconfig commands do succeed inside of scripts (but not 
ifdown). I was incorrect about that.

What really happens:
At the point where the bridge is made and tap0 and enp3s0 are added to it the 
ipaddr of enp3s0 goes from 0.0.0.0 back to 192.168.1.130 thus breaking the 
bridge.
Both tap0 and enp3s0 must be 0.0.0.0. promiscuous mode, and up inside the 
bridge br0 to work properly.

I am digging deeper on why this happens.
As a temp fix I reset enp3s0 to the correct settings a 2nd time after the 
bridge is made.

Also, after the bridge is removed enp3s0 never performs dhcp to regain its 
original ipaddr.
That is also an issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to net-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1674137

Title:
  ifdown unknown interface net-tools is broken

Status in Linux Mint:
  New
Status in net-tools package in Ubuntu:
  New

Bug description:
  System:Host: GT70-2PE Kernel: 4.5.4-040504-generic x86_64 (64 bit gcc: 
5.3.1)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9) Distro: Linux Mint 18.1 Serena
  Network:   Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller
     driver: alx port: d000 bus-ID: 03:00.0
     IF: enp3s0 state: up speed: 1000 Mbps duplex: full
     Card-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: 
ath9k bus-ID: 04:00.0
     IF: wlp4s0 state: up

  After mint 18.1 upgrade had various issues.
  After quite a few updates I started having issues with ifdown command.

  I use a script with qemu to setup a bridge (br0) with tap0 and the default 
wired connection enp3s0. The script began giving off unknown interface errors.
  Testing showed that the ifdown command changed behavior after the updates and 
now does this.
  The behavior is not limited to scripting.
  I changed the code from using ifdown to ifconfig enp3s0 down.
  This fails also within the script but with no error.
  It, however, works from a terminal just fine.
  I switched to using the ip command i.e. ip link set enp3s0 down.
  Same result, the interface does not go down, but no error.
  After the script is run and windows 7 boots in qemu I have to open a terminal 
and run the commands manually:
  >ifconfig enp3s0 down
  >ifconfig enp3s0 0.0.0.0 promisc up

  Then all is well.
  These commands will not run from within a script.
  The script is run as such:
  >sudo ./up.sh tap0

  It creates br0 and tap0 and adds enp3s0 and tap0 to the bridge.

  The fact that ifdown no longer recognizes any interfaces seems to
  point to a change in net-tools that has broken something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1674137/+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 1674137] Re: ifdown unknown interface net-tools is broken

[Roger Lawhorn]

** Also affects: net-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 net-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1674137

Title:
  ifdown unknown interface net-tools is broken

Status in Linux Mint:
  New
Status in net-tools package in Ubuntu:
  New

Bug description:
  System:Host: GT70-2PE Kernel: 4.5.4-040504-generic x86_64 (64 bit gcc: 
5.3.1)
     Desktop: Cinnamon 3.2.7 (Gtk 3.18.9) Distro: Linux Mint 18.1 Serena
  Network:   Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller
     driver: alx port: d000 bus-ID: 03:00.0
     IF: enp3s0 state: up speed: 1000 Mbps duplex: full
     Card-2: Qualcomm Atheros AR9462 Wireless Network Adapter driver: 
ath9k bus-ID: 04:00.0
     IF: wlp4s0 state: up

  After mint 18.1 upgrade had various issues.
  After quite a few updates I started having issues with ifdown command.

  I use a script with qemu to setup a bridge (br0) with tap0 and the default 
wired connection enp3s0. The script began giving off unknown interface errors.
  Testing showed that the ifdown command changed behavior after the updates and 
now does this.
  The behavior is not limited to scripting.
  I changed the code from using ifdown to ifconfig enp3s0 down.
  This fails also within the script but with no error.
  It, however, works from a terminal just fine.
  I switched to using the ip command i.e. ip link set enp3s0 down.
  Same result, the interface does not go down, but no error.
  After the script is run and windows 7 boots in qemu I have to open a terminal 
and run the commands manually:
  >ifconfig enp3s0 down
  >ifconfig enp3s0 0.0.0.0 promisc up

  Then all is well.
  These commands will not run from within a script.
  The script is run as such:
  >sudo ./up.sh tap0

  It creates br0 and tap0 and adds enp3s0 and tap0 to the bridge.

  The fact that ifdown no longer recognizes any interfaces seems to
  point to a change in net-tools that has broken something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1674137/+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 1490347] Re: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes

[Roger Lawhorn]

UPDATE:

I created my own bluez 5.43 unsigned packages and installed them.
The issue is still present.

Here are the steps I took:

It was suggested that bluez 5.4 fixes the issue. However, that package
is not available for ubuntu 16.04. I was able to build my own unsigned
and upgradable package using the following steps and I have bluez 5.43.
Still does not connect though.

sudo  apt-get install debhelper devscripts dh-autoreconf flex bison
libdbus-glib-1-dev libglib2.0-dev  libcap-ng-dev libudev-dev
libreadline-dev libical-dev check dh-systemd libebook1.2-dev

wget https://launchpad.net/ubuntu/+archive/primary/+files/bluez_5.43.orig.tar.xz
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez_5.43-0ubuntu1.debian.tar.xz
wget 
https://launchpad.net/ubuntu/+archive/primary/+files/bluez_5.43-0ubuntu1.dsc

tar xf bluez_5.43.orig.tar.xz
cd bluez-5.43
tar xf ../bluez_5.43-0ubuntu1.debian.tar.xz
debchange --local=~lorenzen 'Backport to Xenial'
debuild -b -j4 -us -uc
cd ..
sudo dpkg -i *.deb

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490347

Title:
  [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy
  LMP Link Management Protocol) PIN codes

Status in Bluez Utilities:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1490347/+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 1490347] Re: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes

[Roger Lawhorn]

Same here.

Linux Mint 18.1 64bit Cinnamon Desktop (ubuntu 16.04), Bluetoothctl
v5.37.

After I wrote the below forum post I also implemented this udev change
which helped somewhat as I have an onboard bluetooth that I wanted to
disable after buying a "csr 4.0" usb dongle off of ebay. The GUI worked
better, but still no pair:

>sudo gedit /etc/udev/rules.d/81-bluetooth-hci.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0cf3", ATTRS{idProduct}=="3004", 
ATTR{authorized}="0"

Here is the article I posted in a facebook forum with all the gory
details:

Been unable to use bluetooth for many years and many laptops. Bought a CSR v4.0 
dongle off of ebay.
>lsusb Bus 003 Device 011: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
>Dongle (HCI mode)

Even worse results.

In bluetoothctl (skipping the GUI):
[bluetooth]# list
Controller 00:1A:7D:DA:71:13 GT70-2PE #1 [default]
Controller 48:5A:B6:19:7F:30 GT70-2PE

#1 is the usb dongle I bought.
The other is the built-in Atheros in the laptop.

[bluetooth]# power on
Changing power on succeeded

[bluetooth]# scan on
Discovery started
[CHG] Controller 00:1A:7D:DA:71:13 Discovering: yes
[CHG] Device 48:5A:B6:19:7F:30 RSSI: -64
[CHG] Device 00:07:62:18:3D:C5 RSSI: -51

[bluetooth]# info 00:07:62:18:3D:C5
Device 00:07:62:18:3D:C5
Name: iMT525
Alias: iMT525
Class: 0x240404
Icon: audio-card
Paired: no
Trusted: no
Blocked: no
Connected: no
LegacyPairing: yes
RSSI: -51

I am trying to connect to the iMT525 speaker phone by Altec Lansing.

[bluetooth]# pair 00:07:62:18:3D:C5
Attempting to pair with 00:07:62:18:3D:C5
[CHG] Device 00:07:62:18:3D:C5 Connected: yes
Failed to pair: org.bluez.Error.AuthenticationRejected
[CHG] Device 00:07:62:18:3D:C5 Connected: no

Cannot pair though the default pair code is  for a sound device.

Any ideas?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1490347

Title:
  [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy
  LMP Link Management Protocol) PIN codes

Status in Bluez Utilities:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1490347/+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 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

[roger]

Oh yeah ...my Lubuntu 12.04 came installed with "Gnome mplayer" but when I 
installed Gnome-Media-Player my problem "player did not initialize properly" 
went away and I could pay my wave files on Reverb Nation. I didn't have 
problems with video or flash or You Tube.
roger at blueshade44

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1643467

Title:
  Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Fix Released
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Fix Released
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Fix Released
Status in libav source package in Trusty:
  Fix Released

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/libav/+bug/1643467/+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 1643467] Re: Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

[roger]

I had this problem too. I'm running Lubuntu 12.04. I use plain 12.04 and not 
LTS because lubuntu 12.04 LTS requires PAE and won't work on my Pentium M 
Itronix go book 3. I have to keep running Lubuntu 12.04. Anyway the answer for 
me was to go to the Lubuntu Software center and install 
Gnome-Media-Player . While installing looking at the "programs to install" lo 
and behold at the top of the list...Libavcodec53 !!! PROBLEM SOLVED.
 roger at blueshade44

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1643467

Title:
  Firefox 50 blocks Ubuntu 12.04 and 14.04 LTS's version of libavcodec

Status in libav:
  Unknown
Status in firefox package in Ubuntu:
  Fix Released
Status in libav package in Ubuntu:
  Invalid
Status in firefox source package in Precise:
  Fix Released
Status in libav source package in Precise:
  Confirmed
Status in firefox source package in Trusty:
  Fix Released
Status in libav source package in Trusty:
  Fix Released

Bug description:
  Whenever it tries to play a video, Firefox 50 displays this message at the 
top of every page:
  "libavcodec may be vulnerable or is not supported, and should be updated to 
play video"

  https://dxr.mozilla.org/mozilla-central/source/browser/locales/en-
  
US/chrome/browser/browser.properties?q=%22libavcodec+may+be+vulnerable%22_type=single#742

  Firefox refuses any libavcodec version prior to 54.35.1 (unless
  media.libavcodec.allow-obsolete==true).

  https://dxr.mozilla.org/mozilla-
  central/source/dom/media/platforms/ffmpeg/FFmpegLibWrapper.cpp#60

  Users should not be subjected to this warning, as it is vague (does not 
instruct them how to fix it).
  Ubuntu 14.04 LTS should ship with an updated version of libavcodec.

  DistroRelease: Ubuntu 14.04
  Package: firefox 50.0+build2-0ubuntu0.14.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/libav/+bug/1643467/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Roger Joness]

Should I as just a user ignore this problem? Don't understand what is going
on really.

On Thu, 24 Nov 2016 at 04:45, Isiramen Akeeminemen <
1642...@bugs.launchpad.net> wrote:

> so is there any thing i can do to make things better, or should i think
> it is not a threat
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1643196).
> https://bugs.launchpad.net/bugs/1642966
>
> 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:
>   Confirmed
>
> Bug description:
>   This is in xenial-proposed, please block release to -updates
>   accordingly :)
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 16.04
>   Package: cups-daemon 2.1.3-4
>   ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
>   Uname: Linux 4.4.0-46-generic x86_64
>   NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
>   ApportVersion: 2.20.1-0ubuntu2.1
>   Architecture: amd64
>   CupsErrorLog:
>
>   Date: Fri Nov 18 11:13:15 2016
>   ErrorMessage: subprocess new pre-removal script returned error exit
> status 1
>   InstallationDate: Installed on 2016-05-02 (200 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   Lpstat: device for mallards-officejet-pro-8600:
> dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
>   MachineType: Dell Inc. XPS 15 9550
>   Papersize: a4
>   PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups
> 3.16.3
>   ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed
> root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed
> root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
>   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: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/07/2016
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 01.02.00
>   dmi.board.name: 0N7TVV
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: XPS 15 9550
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions
>
-- 
Sent from my IPad

-- 
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/1642966

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:
  Confirmed

Bug description:
  This is in xenial-proposed, please block release to -updates
  accordingly :)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24
  Uname: Linux 4.4.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Nov 18 11:13:15 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2016-05-02 (200 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lpstat: device for mallards-officejet-pro-8600: 
dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461
  MachineType: Dell Inc. XPS 15 9550
  Papersize: a4
  PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed 
root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7
  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: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 

[Touch-packages] [Bug 1643196] [NEW] I did not alter anything, package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Roger Joness]

Public bug reported:

I did not alter or do anything during software update install

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CupsErrorLog:
 
Date: Sat Nov 19 14:55:32 2016
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2015-10-23 (393 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Hewlett-Packard HP 255 G3 Notebook PC
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=8f005d4e-1a96-4aa1-98c0-084fd78e40ff ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=8f005d4e-1a96-4aa1-98c0-084fd78e40ff ro quiet splash vt.handoff=7
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-13 (98 days ago)
dmi.bios.date: 12/23/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.33
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 21F7
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 52.3A
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd12/23/2014:svnHewlett-Packard:pnHP255G3NotebookPC:pvr0990101600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 255 G3 Notebook PC
dmi.product.version: 0990101600087
dmi.sys.vendor: Hewlett-Packard
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-02-18T19:37:53

** 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/1643196

Title:
  I did not alter anything, 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:
  I did not alter or do anything during software update install

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups-daemon 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Nov 19 14:55:32 2016
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2015-10-23 (393 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Hewlett-Packard HP 255 G3 Notebook PC
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=8f005d4e-1a96-4aa1-98c0-084fd78e40ff ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic 
root=UUID=8f005d4e-1a96-4aa1-98c0-084fd78e40ff ro quiet splash vt.handoff=7
  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-13 (98 days ago)
  dmi.bios.date: 12/23/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 21F7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 52.3A
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.33:bd12/23/2014:svnHewlett-Packard:pnHP255G3NotebookPC:pvr0990101600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 255 G3 Notebook PC
  dmi.product.version: 0990101600087
  dmi.sys.vendor: Hewlett-Packard
  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: 

[Touch-packages] [Bug 1510570] Re: BLE pairing fail

[Roger Binns]

Based on comments here I can get the Microsoft Arc Touch Bluetooth to
pair.  But the Bluetooth manager doesn't think it is a mouse, or offer
connecting it to the input service.  How does one get an actual working
mouse?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1510570

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1510570/+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 1616614] [NEW] package openssh-server 1:7.2p2-4ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 102

[Roger Campbell]

Public bug reported:

I was trying to use ssh but it did not seem to be installed. the file
"/usr/bin/ssh" was installed the init files were missing. I decided to
add the init.d and rc5.d files. I was still unable to start ssh so I
decided to just re-install openssh. As you can this did not go well. It
seems I took careful aim at my foot and shot my kneecap off.


root@sunup:/etc/init.d# apt install openssh-server
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  ncurses-term openssh-sftp-server ssh-import-id
Suggested packages:
  rssh molly-guard monkeysphere
The following NEW packages will be installed:
  ncurses-term openssh-server openssh-sftp-server ssh-import-id
0 upgraded, 4 newly installed, 0 to remove and 17 not upgraded.
Need to get 636 kB of archives.
After this operation, 5,145 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu xenial/main amd64 ncurses-term all 
6.0+20160213-1ubuntu1 [249 kB]
Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
openssh-sftp-server amd64 1:7.2p2-4ubuntu2.1 [38.8 kB]
Get:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 openssh-server 
amd64 1:7.2p2-4ubuntu2.1 [338 kB]
Get:4 http://archive.ubuntu.com/ubuntu xenial/main amd64 ssh-import-id all 
5.5-0ubuntu1 [10.2 kB]
Fetched 636 kB in 1s (406 kB/s)   
Preconfiguring packages ...
Selecting previously unselected package ncurses-term.
(Reading database ... 217890 files and directories currently installed.)
Preparing to unpack .../ncurses-term_6.0+20160213-1ubuntu1_all.deb ...
Unpacking ncurses-term (6.0+20160213-1ubuntu1) ...
Selecting previously unselected package openssh-sftp-server.
Preparing to unpack .../openssh-sftp-server_1%3a7.2p2-4ubuntu2.1_amd64.deb ...
Unpacking openssh-sftp-server (1:7.2p2-4ubuntu2.1) ...
Selecting previously unselected package openssh-server.
Preparing to unpack .../openssh-server_1%3a7.2p2-4ubuntu2.1_amd64.deb ...
Unpacking openssh-server (1:7.2p2-4ubuntu2.1) ...
Selecting previously unselected package ssh-import-id.
Preparing to unpack .../ssh-import-id_5.5-0ubuntu1_all.deb ...
Unpacking ssh-import-id (5.5-0ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for systemd (229-4ubuntu7) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for ufw (0.35-0ubuntu2) ...
Setting up ncurses-term (6.0+20160213-1ubuntu1) ...
Setting up openssh-sftp-server (1:7.2p2-4ubuntu2.1) ...
Setting up openssh-server (1:7.2p2-4ubuntu2.1) ...
Creating SSH2 RSA key; this may take some time ...
2048 SHA256:ifVt+zEPQJaCEM41tTJ7ioq5Nd+zitMECWf48VxwPYY root@sunup (RSA)
Creating SSH2 DSA key; this may take some time ...
1024 SHA256:Ffmc6+U+bC44zWx96s/j1Emff2gXzm7JDtpoDdx7AnM root@sunup (DSA)
Creating SSH2 ECDSA key; this may take some time ...
256 SHA256:w0a+E7GIGMKbX8p5Ke5jWVMMwwwdzhMcQrnMrywTHCc root@sunup (ECDSA)
Creating SSH2 ED25519 key; this may take some time ...
256 SHA256:VufVRjr+gAaupx7MxVN6khhtBgDIecB48rm6Rc2YQbU root@sunup (ED25519)
insserv: warning: script is corrupt or invalid: /etc/init.d/../rc5.d/S02ssh
invoke-rc.d: not a symlink: /etc/rc5.d/S02ssh
dpkg: error processing package openssh-server (--configure):
 subprocess installed post-installation script returned error exit status 102
Setting up ssh-import-id (5.5-0ubuntu1) ...
Processing triggers for ureadahead (0.100.0-19) ...
Processing triggers for ufw (0.35-0ubuntu2) ...
Errors were encountered while processing:
 openssh-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

#
1)
root@sunup:/etc/init.d# lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04
2)
Unable to determine version information.
3)
I expected openssh server to be installed.
4)
Install of openssh failed (see the above)

Thank You for your time and effort on my behalf.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Wed Aug 24 14:28:32 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 102
InstallationDate: Installed on 2016-06-09 (75 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: openssh
Title: package openssh-server 1:7.2p2-4ubuntu2.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 102
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: openssh (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

-- 
You received this bug notification because you are a 

[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

[Roger Norton]

This bug also appears to affect my acer aspire VN7 792G.  I am unable to
use the internal stereo microphones, for skype for example, and they are
not shown on the input tab of the sound section of the system settings.
Please notify me when there is a fix to this bug.

-- 
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/1523100

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1584284] Re: Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

[Roger Merritt]

Sorry, I need to proofread more carefully. It's kernel 4.7rc6. The complete
line from the grub menu is:
Ubuntu, with Linux 4.7.0-0407004c6-generic

I've installed 4.4.13, and it, too, seems to be working normally.

On Thu, Jul 7, 2016 at 6:14 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> Roger Merritt:
> >"successfully installed the mainline kernel 4.6-rc6"
>
> Did you test 4.7-rc6, or 4.6-rc6?
>
> >"Apparently the problem is not in the kernel."
>
> The test you did wasn't enough to conclude that.
>
> Despite this, could you please test 4.4.13 (this is the kernel that
> Xenial is based off of) and advise to the results?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1584284
>
> Title:
>   Ubuntu 16.04 LiveCD does not boot on AMD A10 chip
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD
> A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no
> graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I
> try to boot I get an error message, "ERROR: no UMS support in radeon
> module." When I edit the boot command line to add the parameter 'nomodeset'
> I first get an error message, "No UMS support on radeon module," then the
> familiar aubergine background with the ubuntu logo and the five dots below
> it changing from white to red and back again. After twenty or thirty
> seconds the background goes to black, I get the error message "No UMS
> support in radeon module," and the ubuntu logo disappears but the five dots
> continue. After another twenty or thirty seconds of that the screen clears,
> at the top is a line: "ubuntu 16.04 ubuntu LTS tty1," below that the line
> "ubuntu login:" and after a second or less the screen goes black and I
> can't do anything except reboot. I've tried old Live CDs, from 10.10 to
> 15.10, and they all boot fine.
>   ---
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.19.1-0ubuntu5
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   DistUpgraded: Fresh install
>   DistroCodename: wily
>   DistroRelease: Ubuntu 15.10
>   DistroVariant: ubuntu
>   DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D]
> [1002:9901] (prog-if 00 [VGA controller])
>  Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD
> 7660D] [1002:9901]
>   InstallationDate: Installed on 2016-06-07 (27 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
>   Package: xorg 1:7.7+7ubuntu4
>   PackageArchitecture: amd64
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic
> root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
>   Tags:  wily ubuntu compiz-0.9
>   UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
>   Uname: Linux 4.2.0-36-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   _MarkForUpload: True
>   dmi.bios.date: 03/18/2013
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: F4
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: F2A75M-HD2
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.board.version: To be filled by O.E.M.
>   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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
>   version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.64-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
>   version.libgl1-mesa-dri-ex

Re: [Touch-packages] [Bug 1584284] Re: Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

[Roger Merritt]

Oh, boy. I did it again. That should have been ...040700*r*c6-generic.

On Thu, Jul 7, 2016 at 6:14 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> Roger Merritt:
> >"successfully installed the mainline kernel 4.6-rc6"
>
> Did you test 4.7-rc6, or 4.6-rc6?
>
> >"Apparently the problem is not in the kernel."
>
> The test you did wasn't enough to conclude that.
>
> Despite this, could you please test 4.4.13 (this is the kernel that
> Xenial is based off of) and advise to the results?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1584284
>
> Title:
>   Ubuntu 16.04 LiveCD does not boot on AMD A10 chip
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD
> A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no
> graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I
> try to boot I get an error message, "ERROR: no UMS support in radeon
> module." When I edit the boot command line to add the parameter 'nomodeset'
> I first get an error message, "No UMS support on radeon module," then the
> familiar aubergine background with the ubuntu logo and the five dots below
> it changing from white to red and back again. After twenty or thirty
> seconds the background goes to black, I get the error message "No UMS
> support in radeon module," and the ubuntu logo disappears but the five dots
> continue. After another twenty or thirty seconds of that the screen clears,
> at the top is a line: "ubuntu 16.04 ubuntu LTS tty1," below that the line
> "ubuntu login:" and after a second or less the screen goes black and I
> can't do anything except reboot. I've tried old Live CDs, from 10.10 to
> 15.10, and they all boot fine.
>   ---
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.19.1-0ubuntu5
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   DistUpgraded: Fresh install
>   DistroCodename: wily
>   DistroRelease: Ubuntu 15.10
>   DistroVariant: ubuntu
>   DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D]
> [1002:9901] (prog-if 00 [VGA controller])
>  Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD
> 7660D] [1002:9901]
>   InstallationDate: Installed on 2016-06-07 (27 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
>   Package: xorg 1:7.7+7ubuntu4
>   PackageArchitecture: amd64
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic
> root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
>   Tags:  wily ubuntu compiz-0.9
>   UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
>   Uname: Linux 4.2.0-36-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   _MarkForUpload: True
>   dmi.bios.date: 03/18/2013
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: F4
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: F2A75M-HD2
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.board.version: To be filled by O.E.M.
>   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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
>   version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.64-1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
>   version.xserver-xorg-c

Re: [Touch-packages] [Bug 1584284] Re: Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

[Roger Merritt]

Luckily I had a 32 GB SanDisk USB 3.0 flash drive on hand (the one that was
farkled by trying to upgrade 15.10 to 16.04), so I installed 15.10 on it
and upgraded. I didn't add any programs, so this is vanilla 15.10. I
followed the instructions at the link you gave and successfully installed
the mainline kernel 4.6-rc6. Restarting, I successfully used the new kernel
to boot into 15.10. I don't have any complex programs other than Mozilla
Firefox to run on this installation, but it seems to be working fine.
Apparently the problem is not in the kernel.

On Tue, Jul 5, 2016 at 6:15 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> Roger Merritt, to further narrow this down, could you please test the
> latest mainline kernel (4.7-rc6) following
> https://wiki.ubuntu.com/Kernel/MainlineBuilds and advise to the results?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1584284
>
> Title:
>   Ubuntu 16.04 LiveCD does not boot on AMD A10 chip
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD
> A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no
> graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I
> try to boot I get an error message, "ERROR: no UMS support in radeon
> module." When I edit the boot command line to add the parameter 'nomodeset'
> I first get an error message, "No UMS support on radeon module," then the
> familiar aubergine background with the ubuntu logo and the five dots below
> it changing from white to red and back again. After twenty or thirty
> seconds the background goes to black, I get the error message "No UMS
> support in radeon module," and the ubuntu logo disappears but the five dots
> continue. After another twenty or thirty seconds of that the screen clears,
> at the top is a line: "ubuntu 16.04 ubuntu LTS tty1," below that the line
> "ubuntu login:" and after a second or less the screen goes black and I
> can't do anything except reboot. I've tried old Live CDs, from 10.10 to
> 15.10, and they all boot fine.
>   ---
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.19.1-0ubuntu5
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   DistUpgraded: Fresh install
>   DistroCodename: wily
>   DistroRelease: Ubuntu 15.10
>   DistroVariant: ubuntu
>   DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D]
> [1002:9901] (prog-if 00 [VGA controller])
>  Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD
> 7660D] [1002:9901]
>   InstallationDate: Installed on 2016-06-07 (27 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
>   Package: xorg 1:7.7+7ubuntu4
>   PackageArchitecture: amd64
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic
> root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
>   Tags:  wily ubuntu compiz-0.9
>   UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
>   Uname: Linux 4.2.0-36-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   _MarkForUpload: True
>   dmi.bios.date: 03/18/2013
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: F4
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: F2A75M-HD2
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.board.version: To be filled by O.E.M.
>   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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
>   version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
>   version.ia32

Re: [Touch-packages] [Bug 1584284] Re: Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

[Roger Merritt]

Sorry, this version is even worse. After the grub menu the screen goes
black, than after about fifteen seconds it gores even blacker, indicating
that there is no longer any signal going to the monitor. A few seconds
after that the "No Signal" notice appears, and after it fades everything
sits quietly. At least with 16.04 there was some visible activity after the
grub menu until it went black. Thanks for the effort, though.

On Mon, Jul 4, 2016 at 10:28 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:

> Roger merritt, to see if this is already resolved, could you please test
> http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?
>
> ** Tags added: latest-bios-f4
>
> ** Changed in: xorg (Ubuntu)
>Importance: Low => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1584284
>
> Title:
>   Ubuntu 16.04 LiveCD does not boot on AMD A10 chip
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD
> A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no
> graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I
> try to boot I get an error message, "ERROR: no UMS support in radeon
> module." When I edit the boot command line to add the parameter 'nomodeset'
> I first get an error message, "No UMS support on radeon module," then the
> familiar aubergine background with the ubuntu logo and the five dots below
> it changing from white to red and back again. After twenty or thirty
> seconds the background goes to black, I get the error message "No UMS
> support in radeon module," and the ubuntu logo disappears but the five dots
> continue. After another twenty or thirty seconds of that the screen clears,
> at the top is a line: "ubuntu 16.04 ubuntu LTS tty1," below that the line
> "ubuntu login:" and after a second or less the screen goes black and I
> can't do anything except reboot. I've tried old Live CDs, from 10.10 to
> 15.10, and they all boot fine.
>   ---
>   .tmp.unity.support.test.0:
>
>   ApportVersion: 2.19.1-0ubuntu5
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   DistUpgraded: Fresh install
>   DistroCodename: wily
>   DistroRelease: Ubuntu 15.10
>   DistroVariant: ubuntu
>   DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
>   ExtraDebuggingInterest: Yes
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D]
> [1002:9901] (prog-if 00 [VGA controller])
>  Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD
> 7660D] [1002:9901]
>   InstallationDate: Installed on 2016-06-07 (27 days ago)
>   InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
>   MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
>   Package: xorg 1:7.7+7ubuntu4
>   PackageArchitecture: amd64
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic
> root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
>   Tags:  wily ubuntu compiz-0.9
>   UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
>   Uname: Linux 4.2.0-36-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups:
>
>   _MarkForUpload: True
>   dmi.bios.date: 03/18/2013
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: F4
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: F2A75M-HD2
>   dmi.board.vendor: Gigabyte Technology Co., Ltd.
>   dmi.board.version: To be filled by O.E.M.
>   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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
>   version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.

[Touch-packages] [Bug 1584284] xserver.outputs.txt

[Roger Merritt]

apport information

** Attachment added: "xserver.outputs.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695198/+files/xserver.outputs.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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] LightdmGreeterLogOld.txt

[Roger Merritt]

apport information

** Attachment added: "LightdmGreeterLogOld.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695183/+files/LightdmGreeterLogOld.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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 

[Touch-packages] [Bug 1584284] LightdmLog.txt

[Roger Merritt]

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695184/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] ProcInterrupts.txt

[Roger Merritt]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695190/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] ProcModules.txt

[Roger Merritt]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695191/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] XorgLog.txt

[Roger Merritt]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695194/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] xdpyinfo.txt

[Roger Merritt]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695197/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] Xrandr.txt

[Roger Merritt]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1584284/+attachment/4695196/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] XorgLogOld.txt

[Roger Merritt]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695195/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] UnitySupportTest.txt

[Roger Merritt]

apport information

** Attachment added: "UnitySupportTest.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695193/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] UdevDb.txt

[Roger Merritt]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1584284/+attachment/4695192/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] ProcEnviron.txt

[Roger Merritt]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695189/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] ProcCpuinfo.txt

[Roger Merritt]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695188/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] Lsusb.txt

[Roger Merritt]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1584284/+attachment/4695186/+files/Lsusb.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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  xserver.video_driver: 

[Touch-packages] [Bug 1584284] MonitorsUser.xml.txt

[Roger Merritt]

apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695187/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] Lspci.txt

[Roger Merritt]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1584284/+attachment/4695185/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  xserver.video_driver: 

[Touch-packages] [Bug 1584284] LightdmGreeterLog.txt

[Roger Merritt]

apport information

** Attachment added: "LightdmGreeterLog.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695182/+files/LightdmGreeterLog.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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1

[Touch-packages] [Bug 1584284] DpkgLog.txt

[Roger Merritt]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695178/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] Dependencies.txt

[Roger Merritt]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695177/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] LightdmDisplayLog.txt

[Roger Merritt]

apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695181/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1

[Touch-packages] [Bug 1584284] GconfCompiz.txt

[Roger Merritt]

apport information

** Attachment added: "GconfCompiz.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695179/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] JournalErrors.txt

[Roger Merritt]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1584284/+attachment/4695180/+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/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
  --- 
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroRelease: Ubuntu 15.10
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
  InstallationDate: Installed on 2016-06-07 (27 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: xorg 1:7.7+7ubuntu4
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
  Tags:  wily ubuntu compiz-0.9
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/18/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A75M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Tue Jul  5 00:55:16 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical Wheel Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1
  

[Touch-packages] [Bug 1584284] Re: Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

[Roger Merritt]

apport information

** Tags added: apport-collected compiz-0.9 ubuntu wily

** Description changed:

- I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD
- A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no
- graphics card -- the Radeon HD 7660D graphics are done by the CPU. When
- I try to boot I get an error message, "ERROR: no UMS support in radeon
- module." When I edit the boot command line to add the parameter
- 'nomodeset' I first get an error message, "No UMS support on radeon
- module," then the familiar aubergine background with the ubuntu logo and
- the five dots below it changing from white to red and back again. After
- twenty or thirty seconds the background goes to black, I get the error
- message "No UMS support in radeon module," and the ubuntu logo
- disappears but the five dots continue. After another twenty or thirty
- seconds of that the screen clears, at the top is a line: "ubuntu 16.04
- ubuntu LTS tty1," below that the line "ubuntu login:" and after a second
- or less the screen goes black and I can't do anything except reboot.
- I've tried old Live CDs, from 10.10 to 15.10, and they all boot fine.
+ I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD 
A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and no 
graphics card -- the Radeon HD 7660D graphics are done by the CPU. When I try 
to boot I get an error message, "ERROR: no UMS support in radeon module." When 
I edit the boot command line to add the parameter 'nomodeset' I first get an 
error message, "No UMS support on radeon module," then the familiar aubergine 
background with the ubuntu logo and the five dots below it changing from white 
to red and back again. After twenty or thirty seconds the background goes to 
black, I get the error message "No UMS support in radeon module," and the 
ubuntu logo disappears but the five dots continue. After another twenty or 
thirty seconds of that the screen clears, at the top is a line: "ubuntu 16.04 
ubuntu LTS tty1," below that the line "ubuntu login:" and after a second or 
less the screen goes black and I can't do anything except reboot. I've tried 
old Liv
 e CDs, from 10.10 to 15.10, and they all boot fine.
+ --- 
+ .tmp.unity.support.test.0:
+  
+ ApportVersion: 2.19.1-0ubuntu5
+ Architecture: amd64
+ CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
+ CompositorRunning: compiz
+ CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
+ CompositorUnredirectFSW: true
+ DistUpgraded: Fresh install
+ DistroCodename: wily
+ DistroRelease: Ubuntu 15.10
+ DistroVariant: ubuntu
+ DkmsStatus: virtualbox, 5.0.14, 4.2.0-36-generic, x86_64: installed
+ ExtraDebuggingInterest: Yes
+ GraphicsCard:
+  Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] 
(prog-if 00 [VGA controller])
+Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7660D] [1002:9901]
+ InstallationDate: Installed on 2016-06-07 (27 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
+ MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
+ Package: xorg 1:7.7+7ubuntu4
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-36-generic 
root=UUID=376cfbdb-7508-4e73-9b25-421ca397ab8a ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.2.0-36.42-generic 4.2.8-ckt8
+ Tags:  wily ubuntu compiz-0.9
+ UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
+ Uname: Linux 4.2.0-36-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 03/18/2013
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F4
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: F2A75M-HD2
+ dmi.board.vendor: Gigabyte Technology Co., Ltd.
+ dmi.board.version: To be filled by O.E.M.
+ 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.:bvrF4:bd03/18/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A75M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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.
+ version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
+ version.ia32-libs: ia32-libs N/A
+ version.libdrm2: libdrm2 2.4.64-1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
+ version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
+ version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
+ version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
+ 

[Touch-packages] [Bug 1596231] [NEW] problème écran externe

[Gofflot Roger]

Public bug reported:

Lenovo 50-70 avec ubuntu 16.04 LTS.
Mon écran externe HP est détecté mais ne reste noir (en veille).
Merci

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 lvmetad is not active yet, using direct activation during sysinit
 Scanning for Btrfs filesystems
 /dev/mapper/ubuntu--vg-root: recovering journal
 /dev/mapper/ubuntu--vg-root: clean, 474762/30236672 files, 21419007/120941568 
blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Jun 25 23:40:46 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-24-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
InstallationDate: Installed on 2016-06-24 (1 days ago)
InstallationMedia: cubuntu 16.04 215 intel - Release amd64
MachineType: LENOVO 80EU
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/23/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: 9DCN26WW(V2.07)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo B50-70
dmi.board.vendor: LENOVO
dmi.board.version: 31900058WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo B50-70
dmi.modalias: 
dmi:bvnLENOVO:bvr9DCN26WW(V2.07):bd09/23/2014:svnLENOVO:pn80EU:pvrLenovoB50-70:rvnLENOVO:rnLenovoB50-70:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoB50-70:
dmi.product.name: 80EU
dmi.product.version: Lenovo B50-70
dmi.sys.vendor: LENOVO
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.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
xserver.bootTime: Sat Jun 25 23:37:46 2016
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2.2

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages 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/1596231

Title:
  problème écran externe

Status in xorg package in Ubuntu:
  New

Bug description:
  Lenovo 50-70 avec ubuntu 16.04 LTS.
  Mon écran externe HP est détecté mais ne reste noir (en veille).
  Merci

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   lvmetad is not active yet, using direct activation during sysinit
   Scanning for Btrfs filesystems
   /dev/mapper/ubuntu--vg-root: recovering journal
   /dev/mapper/ubuntu--vg-root: clean, 474762/30236672 files, 
21419007/120941568 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Jun 25 23:40:46 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-24-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
  InstallationDate: Installed on 2016-06-24 (1 days ago)
  InstallationMedia: cubuntu 16.04 215 intel - Release amd64
  MachineType: LENOVO 80EU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-24-generic 
root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log 

[Touch-packages] [Bug 1584284] Re: Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

[Roger Merritt]

This is happening:  "... the screen goes blank after the splash screen
(about the time the login screen should come up), report the bug against
xorg."

** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1584284

Title:
  Ubuntu 16.04 LiveCD does not boot on AMD A10 chip

Status in xorg package in Ubuntu:
  New

Bug description:
  I want to boot a Ubuntu LiveCD of 16.04 on a desktop box with an AMD
  A10-5800K AGP,  Gigabyte FA-42A75M-HD2 motherboard, 8 GB of RAM, and
  no graphics card -- the Radeon HD 7660D graphics are done by the CPU.
  When I try to boot I get an error message, "ERROR: no UMS support in
  radeon module." When I edit the boot command line to add the parameter
  'nomodeset' I first get an error message, "No UMS support on radeon
  module," then the familiar aubergine background with the ubuntu logo
  and the five dots below it changing from white to red and back again.
  After twenty or thirty seconds the background goes to black, I get the
  error message "No UMS support in radeon module," and the ubuntu logo
  disappears but the five dots continue. After another twenty or thirty
  seconds of that the screen clears, at the top is a line: "ubuntu 16.04
  ubuntu LTS tty1," below that the line "ubuntu login:" and after a
  second or less the screen goes black and I can't do anything except
  reboot. I've tried old Live CDs, from 10.10 to 15.10, and they all
  boot fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1584284/+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 1511476] Re: Unstable unity session

[Roger Tri]

*** This bug is a duplicate of bug 1510970 ***
https://bugs.launchpad.net/bugs/1510970

This occurs mainly using libreoffice, but lately also using chrome, I
attach a crash file...

** Attachment added: "_opt_google_chrome_chrome.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1511476/+attachment/4567587/+files/_opt_google_chrome_chrome.1000.crash

-- 
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/1511476

Title:
  Unstable unity session

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  My unity session crash randomly, when I am working on my computer, or
  when nothing is done in my computer.

  This occurs repeatedly since I have installed ubuntu 15.10.

  This does not happen on my laptop. The main difference I noticed
  between my computer and my laptop is that my laptop has an NVidia
  Graphic card and my computer has an intel Core™ i5-2320 as CPU/GPU. So
  it has no Graphic Card.

  Here you will find my syslog file content, during the crash :

  Oct 29 18:23:10 choupchoup org.a11y.atspi.Registry[1438]: XIO:  fatal IO 
error 11 (Resource temporarily unavailable) on X server ":0"
  Oct 29 18:23:10 choupchoup org.a11y.atspi.Registry[1438]: after 5183 requests 
(5183 known processed) with 0 events remaining.
  Oct 29 18:23:10 choupchoup org.freedesktop.Notifications[1349]: 
(notify-osd:2595): Gdk-WARNING **: notify-osd: Fatal IO error 11 (Ressource 
temporairement non disponible) on X server :0.
  Oct 29 18:23:10 choupchoup gnome-session[1565]: 
(polkit-gnome-authentication-agent-1:1747): Gdk-WARNING **: 
polkit-gnome-authentication-agent-1: Fatal IO error 11 (Ressource 
temporairement non disponible) on X server :0.
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (nm-applet:1754): Gdk-WARNING 
**: nm-applet: Fatal IO error 11 (Ressource temporairement non disponible) on X 
server :0.
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (update-notifier:2058): 
Gdk-WARNING **: update-notifier: Fatal IO error 11 (Ressource temporairement 
non disponible) on X server :0.
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (telepathy-indicator:1933): 
Gdk-WARNING **: telepathy-indicator: Fatal IO error 11 (Ressource 
temporairement non disponible) on X server :0.
  Oct 29 18:23:10 choupchoup gnome-session[1565]: 
(unity-fallback-mount-helper:1751): Gdk-WARNING **: 
unity-fallback-mount-helper: Fatal IO error 11 (Ressource temporairement non 
disponible) on X server :0.
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (nautilus:1748): Gdk-WARNING 
**: nautilus: Fatal IO error 11 (Ressource temporairement non disponible) on X 
server :0.
  Oct 29 18:23:10 choupchoup org.ayatana.bamf[1349]: (bamfdaemon:1407): 
Gdk-WARNING **: bamfdaemon: Fatal IO error 11 (Ressource temporairement non 
disponible) on X server :0.
  Oct 29 18:23:10 choupchoup acpid: client 815[0:0] has disconnected
  Oct 29 18:23:10 choupchoup acpid: client connected from 3456[0:0]
  Oct 29 18:23:10 choupchoup acpid: 1 client rule loaded
  Oct 29 18:23:10 choupchoup org.freedesktop.Notifications[1349]: loading icon 
'notification-nm-no-connection' caused error: 'L'icône « 
notification-nm-no-connection » n'est pas présente dans le thème 
ubuntu-mono-dark'loading icon 'notification-nm-device-wired' caused error: 
'L'icône « notification-nm-device-wired » n'est pas présente dans le thème 
ubuntu-mono-dark'
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (deja-dup-monitor:2092): 
GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor 
org.gtk.Private.UDisks2VolumeMonitor disconnected from the bus; removing 
drives/volumes/mounts
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (deja-dup-monitor:2092): 
GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor 
org.gtk.Private.GPhoto2VolumeMonitor disconnected from the bus; removing 
drives/volumes/mounts
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (deja-dup-monitor:2092): 
GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor 
org.gtk.Private.MTPVolumeMonitor disconnected from the bus; removing 
drives/volumes/mounts
  Oct 29 18:23:10 choupchoup gnome-session[1565]: (deja-dup-monitor:2092): 
GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor 
org.gtk.Private.AfcVolumeMonitor disconnected from the bus; removing 
drives/volumes/mounts
  Oct 29 18:23:10 choupchoup gnome-session[1565]: gnome-session[1565]: 
GLib-GIO-WARNING: Error releasing name org.gnome.SessionManager: The connection 
is closed
  Oct 29 18:23:10 choupchoup gnome-session[1565]: GLib-GIO-WARNING: Error 
releasing name org.gnome.SessionManager: The connection is closed
  Oct 29 18:23:10 choupchoup org.gnome.zeitgeist.Engine[1349]: 
(zeitgeist-daemon:1902): GLib-GIO-WARNING **: Error releasing name 
org.gnome.zeitgeist.Engine: The connection is closed
  Oct 29 18:23:10 choupchoup org.gnome.zeitgeist.Engine[1349]: 
#033[31m[17:23:10.094000 

[Touch-packages] [Bug 1532431] Re: NetworkManager interferes with unmanaged 802.11 monitor mode interfaces

[Roger James]

Attached a NetworkManager log showing what happens when the interface is
deleted.

** Attachment added: "Network Manager log"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532431/+attachment/4547334/+files/test.log

-- 
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/1532431

Title:
  NetworkManager interferes with unmanaged 802.11 monitor mode
  interfaces

Status in network-manager package in Ubuntu:
  New

Bug description:
  If a virtual 802.11 interface of type monitor is created on a 802.11
  physical interface that already has a virtual interface of type
  managed created on it, then the managed interface is deleted.
  NetworkManager sets the type of the monitor interface to managed. This
  can be illustrated by the following commands. All the interface names
  have been listed in /etc/network/interfaces as follows so
  NetworkManager should not be managing them in any way.

  # Disable network manager on interface names I want to use for monitoring
  # related purposes
  iface eth1 inet manual
  iface BigTenda inet manual
  iface LittleBelkin inet manual
  iface LittleTenda inet manual
  iface Sinmax inet manual
  iface mon0 inet manual
  iface phy0.mon manual
  iface phy1.mon manual
  iface phy2.mon manual
  iface phy3.mon manual
  iface phy4.mon manual
  iface phy5.mon manual
  iface phy6.mon manual
  iface phy7.mon manual
  iface phy8.mon manual
  iface phy9.mon manual

  root@dragon:/home/roger# systemctl start NetworkManager
  root@dragon:/home/roger# iw dev
  phy#3
Interface Sinmax
ifindex 11
wdev 0x30001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw phy phy3 interface add phy2.mon type monitor 
flags otherbss
  root@dragon:/home/roger# iw dev
  phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 11
wdev 0x30001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw dev Sinmax del
  root@dragon:/home/roger# iw dev
  phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# systemctl stop NetworkManager
  root@dragon:/home/roger# iw dev
  phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# # Unplug the netwaork adapter for a few seconds
  root@dragon:/home/roger# iw dev
  phy#4
Interface Sinmax
ifindex 13
wdev 0x40001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw phy phy4 interface add phy2.mon type monitor 
flags otherbss
  root@dragon:/home/roger# iw dev
  phy#4
Interface phy2.mon
ifindex 14
wdev 0x40002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 13
wdev 0x40001
addr 00:0f:11:92:06:b2
type managed
  root@dragon:/home/roger# iw dev Sinmax del
  root@dragon:/home/roger# iw dev
  phy#4
Interface phy2.mon
ifindex 14
wdev 0x40002
addr 00:0f:11:92:06:b2
type monitor

  This stops any running or future network traces on this interface
  working.

  This is another example of network manager interfering with interfaces
  it is not supposed to be managing. See bug #1314848 which is still
  unresolved.

  The above test was carried out on Ubuntu 15.10

  network-manager:
Installed: 1.0.4-0ubuntu5.2
Candidate: 1.0.4-0ubuntu5.2
Version table:
   *** 1.0.4-0ubuntu5.2 0
  500 http://gb.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.4-0ubuntu5 0
  500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1532431/+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 1532431] [NEW] NetworkManager interferes with unmanaged 802.11 monitor mode interfaces

[Roger James]

Public bug reported:

If a virtual 802.11 interface of type monitor is created on a 802.11
physical interface that already has a virtual interface of type managed
created on it, then the managed interface is deleted. NetworkManager
sets the type of the monitor interface to managed. This can be
illustrated by the following commands. All the interface names have been
listed in /etc/network/interfaces as follows so NetworkManager should
not be managing them in any way.

# Disable network manager on interface names I want to use for monitoring
# related purposes
iface eth1 inet manual
iface BigTenda inet manual
iface LittleBelkin inet manual
iface LittleTenda inet manual
iface Sinmax inet manual
iface mon0 inet manual
iface phy0.mon manual
iface phy1.mon manual
iface phy2.mon manual
iface phy3.mon manual
iface phy4.mon manual
iface phy5.mon manual
iface phy6.mon manual
iface phy7.mon manual
iface phy8.mon manual
iface phy9.mon manual

root@dragon:/home/roger# systemctl start NetworkManager
root@dragon:/home/roger# iw dev
phy#3
Interface Sinmax
ifindex 11
wdev 0x30001
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# iw phy phy3 interface add phy2.mon type monitor flags 
otherbss
root@dragon:/home/roger# iw dev
phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 11
wdev 0x30001
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# iw dev Sinmax del
root@dragon:/home/roger# iw dev
phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# systemctl stop NetworkManager
root@dragon:/home/roger# iw dev
phy#3
Interface phy2.mon
ifindex 12
wdev 0x30002
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# # Unplug the netwaork adapter for a few seconds
root@dragon:/home/roger# iw dev
phy#4
Interface Sinmax
ifindex 13
wdev 0x40001
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# iw phy phy4 interface add phy2.mon type monitor flags 
otherbss
root@dragon:/home/roger# iw dev
phy#4
Interface phy2.mon
ifindex 14
wdev 0x40002
addr 00:0f:11:92:06:b2
type monitor
Interface Sinmax
ifindex 13
wdev 0x40001
addr 00:0f:11:92:06:b2
type managed
root@dragon:/home/roger# iw dev Sinmax del
root@dragon:/home/roger# iw dev
phy#4
Interface phy2.mon
ifindex 14
wdev 0x40002
addr 00:0f:11:92:06:b2
type monitor

This stops any running or future network traces on this interface
working.

This is another example of network manager interfering with interfaces
it is not supposed to be managing. See bug #1314848 which is still
unresolved.

The above test was carried out on Ubuntu 15.10

network-manager:
  Installed: 1.0.4-0ubuntu5.2
  Candidate: 1.0.4-0ubuntu5.2
  Version table:
 *** 1.0.4-0ubuntu5.2 0
500 http://gb.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.0.4-0ubuntu5 0
500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: iw mac80211 monitor networkmanager wifi

-- 
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/1532431

Title:
  NetworkManager interferes with unmanaged 802.11 monitor mode
  interfaces

Status in network-manager package in Ubuntu:
  New

Bug description:
  If a virtual 802.11 interface of type monitor is created on a 802.11
  physical interface that already has a virtual interface of type
  managed created on it, then the managed interface is deleted.
  NetworkManager sets the type of the monitor interface to managed. This
  can be illustrated by the following commands. All the interface names
  have been listed in /etc/network/interfaces as follows so
  NetworkManager should not be managing them in any way.

  # Disable network manager on interface names I want to use for monitoring
  # related purposes
  iface eth1 inet manual
  iface BigTenda inet manual
  iface LittleBelkin inet manual
  iface LittleTenda inet manual
  iface Sinmax inet manual
  iface mon0 inet manual
  iface phy0.mon manual
  iface phy1.mon manual
  iface phy2.mon manual
  iface phy3.mon manual
  iface phy4.mon manual
  iface phy5

[Touch-packages] [Bug 1455916] Re: Xorg unexpectedly crashed

[Roger Bonati]

also other crash-files are to be found:

** Attachment added: "usr_bin_gnome-panel crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535450/+files/_usr_bin_gnome-panel.1000.crash

-- 
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/1455916

Title:
  Xorg unexpectedly crashed

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xorg unexpectedly crashed bringing down down metacity and gnome-flashback too.
  This is the relevant section from the system logs:
  May 17 15:09:05 ultra-d gnome-session[1514]: Window manager warning: Log 
level 6: The program 'metacity' received an X Window System error.
  May 17 15:09:05 ultra-d gnome-session[1514]: This probably reflects a bug in 
the program.
  May 17 15:09:05 ultra-d gnome-session[1514]: The error was 'BadRegion 
(invalid Region parameter)'.
  May 17 15:09:05 ultra-d gnome-session[1514]: (Details: serial 508727326 
error_code 140 request_code 138 (XFIXES) minor_code 12)
  May 17 15:09:05 ultra-d gnome-session[1514]: (Note to programmers: normally, 
X errors are reported asynchronously;
  May 17 15:09:05 ultra-d gnome-session[1514]: that is, you will receive the 
error a while after causing it.
  May 17 15:09:05 ultra-d gnome-session[1514]: To debug your program, run it 
with the GDK_SYNCHRONIZE environment
  May 17 15:09:05 ultra-d gnome-session[1514]: variable to change this 
behavior. You can then get a meaningful
  May 17 15:09:05 ultra-d gnome-session[1514]: backtrace from your debugger if 
you break on the gdk_x_error() function.)
  May 17 15:09:05 ultra-d kernel: [276368.790571] traps: metacity[1688] trap 
int3 ip:7fb31d5d9d00 sp:7ffc0f98c740 error:0
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Child process 1688 was already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Child process 1688 was 
already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Application 'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Application 
'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
App 'metacity.desktop' respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: App 'metacity.desktop' 
respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: Unrecoverable failure in 
required component metacity.desktop
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: CRITICAL: 
We failed, but the fail whale is dead. Sorry
  May 17 15:09:19 ultra-d gnome-session[1514]: CRITICAL: We failed, but the 
fail whale is dead. Sorry
  May 17 15:09:20 ultra-d gnome-session[1514]: ICE default IO error handler 
doing an exit(), pid = 17669, errno = 11

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun May 17 15:56:28 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-15-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ca]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=/dev/mapper/system_vg-root_lv ro cryptdevice=/dev/sda2:system_crypt quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0FTJWD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FTJWD:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: 

[Touch-packages] [Bug 1455916] Re: Xorg unexpectedly crashed

[Roger Bonati]

usr_lib_chromium-browser_chromium-browser.1000.crash

** Attachment added: "usr_lib_chromium-browser_chromium-browser.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535454/+files/_usr_lib_chromium-browser_chromium-browser.1000.crash

-- 
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/1455916

Title:
  Xorg unexpectedly crashed

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xorg unexpectedly crashed bringing down down metacity and gnome-flashback too.
  This is the relevant section from the system logs:
  May 17 15:09:05 ultra-d gnome-session[1514]: Window manager warning: Log 
level 6: The program 'metacity' received an X Window System error.
  May 17 15:09:05 ultra-d gnome-session[1514]: This probably reflects a bug in 
the program.
  May 17 15:09:05 ultra-d gnome-session[1514]: The error was 'BadRegion 
(invalid Region parameter)'.
  May 17 15:09:05 ultra-d gnome-session[1514]: (Details: serial 508727326 
error_code 140 request_code 138 (XFIXES) minor_code 12)
  May 17 15:09:05 ultra-d gnome-session[1514]: (Note to programmers: normally, 
X errors are reported asynchronously;
  May 17 15:09:05 ultra-d gnome-session[1514]: that is, you will receive the 
error a while after causing it.
  May 17 15:09:05 ultra-d gnome-session[1514]: To debug your program, run it 
with the GDK_SYNCHRONIZE environment
  May 17 15:09:05 ultra-d gnome-session[1514]: variable to change this 
behavior. You can then get a meaningful
  May 17 15:09:05 ultra-d gnome-session[1514]: backtrace from your debugger if 
you break on the gdk_x_error() function.)
  May 17 15:09:05 ultra-d kernel: [276368.790571] traps: metacity[1688] trap 
int3 ip:7fb31d5d9d00 sp:7ffc0f98c740 error:0
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Child process 1688 was already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Child process 1688 was 
already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Application 'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Application 
'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
App 'metacity.desktop' respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: App 'metacity.desktop' 
respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: Unrecoverable failure in 
required component metacity.desktop
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: CRITICAL: 
We failed, but the fail whale is dead. Sorry
  May 17 15:09:19 ultra-d gnome-session[1514]: CRITICAL: We failed, but the 
fail whale is dead. Sorry
  May 17 15:09:20 ultra-d gnome-session[1514]: ICE default IO error handler 
doing an exit(), pid = 17669, errno = 11

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun May 17 15:56:28 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-15-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ca]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=/dev/mapper/system_vg-root_lv ro cryptdevice=/dev/sda2:system_crypt quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0FTJWD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FTJWD:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 

[Touch-packages] [Bug 1455916] Re: Xorg unexpectedly crashed

[Roger Bonati]

_usr_bin_vlc.1000.crash

** Attachment added: "_usr_bin_vlc.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535452/+files/_usr_bin_vlc.1000.crash

-- 
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/1455916

Title:
  Xorg unexpectedly crashed

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xorg unexpectedly crashed bringing down down metacity and gnome-flashback too.
  This is the relevant section from the system logs:
  May 17 15:09:05 ultra-d gnome-session[1514]: Window manager warning: Log 
level 6: The program 'metacity' received an X Window System error.
  May 17 15:09:05 ultra-d gnome-session[1514]: This probably reflects a bug in 
the program.
  May 17 15:09:05 ultra-d gnome-session[1514]: The error was 'BadRegion 
(invalid Region parameter)'.
  May 17 15:09:05 ultra-d gnome-session[1514]: (Details: serial 508727326 
error_code 140 request_code 138 (XFIXES) minor_code 12)
  May 17 15:09:05 ultra-d gnome-session[1514]: (Note to programmers: normally, 
X errors are reported asynchronously;
  May 17 15:09:05 ultra-d gnome-session[1514]: that is, you will receive the 
error a while after causing it.
  May 17 15:09:05 ultra-d gnome-session[1514]: To debug your program, run it 
with the GDK_SYNCHRONIZE environment
  May 17 15:09:05 ultra-d gnome-session[1514]: variable to change this 
behavior. You can then get a meaningful
  May 17 15:09:05 ultra-d gnome-session[1514]: backtrace from your debugger if 
you break on the gdk_x_error() function.)
  May 17 15:09:05 ultra-d kernel: [276368.790571] traps: metacity[1688] trap 
int3 ip:7fb31d5d9d00 sp:7ffc0f98c740 error:0
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Child process 1688 was already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Child process 1688 was 
already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Application 'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Application 
'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
App 'metacity.desktop' respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: App 'metacity.desktop' 
respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: Unrecoverable failure in 
required component metacity.desktop
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: CRITICAL: 
We failed, but the fail whale is dead. Sorry
  May 17 15:09:19 ultra-d gnome-session[1514]: CRITICAL: We failed, but the 
fail whale is dead. Sorry
  May 17 15:09:20 ultra-d gnome-session[1514]: ICE default IO error handler 
doing an exit(), pid = 17669, errno = 11

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun May 17 15:56:28 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-15-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ca]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=/dev/mapper/system_vg-root_lv ro cryptdevice=/dev/sda2:system_crypt quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0FTJWD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FTJWD:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  

[Touch-packages] [Bug 1455916] Re: Xorg unexpectedly crashed

[Roger Bonati]

Here is my metacity crush log, i experience this bug since upgrading
from 14.04 to 15.10!

** Attachment added: "metacity crash file"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535449/+files/_usr_bin_metacity.1000.crash

-- 
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/1455916

Title:
  Xorg unexpectedly crashed

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xorg unexpectedly crashed bringing down down metacity and gnome-flashback too.
  This is the relevant section from the system logs:
  May 17 15:09:05 ultra-d gnome-session[1514]: Window manager warning: Log 
level 6: The program 'metacity' received an X Window System error.
  May 17 15:09:05 ultra-d gnome-session[1514]: This probably reflects a bug in 
the program.
  May 17 15:09:05 ultra-d gnome-session[1514]: The error was 'BadRegion 
(invalid Region parameter)'.
  May 17 15:09:05 ultra-d gnome-session[1514]: (Details: serial 508727326 
error_code 140 request_code 138 (XFIXES) minor_code 12)
  May 17 15:09:05 ultra-d gnome-session[1514]: (Note to programmers: normally, 
X errors are reported asynchronously;
  May 17 15:09:05 ultra-d gnome-session[1514]: that is, you will receive the 
error a while after causing it.
  May 17 15:09:05 ultra-d gnome-session[1514]: To debug your program, run it 
with the GDK_SYNCHRONIZE environment
  May 17 15:09:05 ultra-d gnome-session[1514]: variable to change this 
behavior. You can then get a meaningful
  May 17 15:09:05 ultra-d gnome-session[1514]: backtrace from your debugger if 
you break on the gdk_x_error() function.)
  May 17 15:09:05 ultra-d kernel: [276368.790571] traps: metacity[1688] trap 
int3 ip:7fb31d5d9d00 sp:7ffc0f98c740 error:0
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Child process 1688 was already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Child process 1688 was 
already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Application 'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Application 
'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
App 'metacity.desktop' respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: App 'metacity.desktop' 
respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: Unrecoverable failure in 
required component metacity.desktop
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: CRITICAL: 
We failed, but the fail whale is dead. Sorry
  May 17 15:09:19 ultra-d gnome-session[1514]: CRITICAL: We failed, but the 
fail whale is dead. Sorry
  May 17 15:09:20 ultra-d gnome-session[1514]: ICE default IO error handler 
doing an exit(), pid = 17669, errno = 11

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun May 17 15:56:28 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-15-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ca]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=/dev/mapper/system_vg-root_lv ro cryptdevice=/dev/sda2:system_crypt quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0FTJWD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FTJWD:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  

[Touch-packages] [Bug 1455916] Re: Xorg unexpectedly crashed

[Roger Bonati]

_usr_bin_pidgin.1000.crash

** Attachment added: "_usr_bin_pidgin.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455916/+attachment/4535451/+files/_usr_bin_pidgin.1000.crash

-- 
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/1455916

Title:
  Xorg unexpectedly crashed

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xorg unexpectedly crashed bringing down down metacity and gnome-flashback too.
  This is the relevant section from the system logs:
  May 17 15:09:05 ultra-d gnome-session[1514]: Window manager warning: Log 
level 6: The program 'metacity' received an X Window System error.
  May 17 15:09:05 ultra-d gnome-session[1514]: This probably reflects a bug in 
the program.
  May 17 15:09:05 ultra-d gnome-session[1514]: The error was 'BadRegion 
(invalid Region parameter)'.
  May 17 15:09:05 ultra-d gnome-session[1514]: (Details: serial 508727326 
error_code 140 request_code 138 (XFIXES) minor_code 12)
  May 17 15:09:05 ultra-d gnome-session[1514]: (Note to programmers: normally, 
X errors are reported asynchronously;
  May 17 15:09:05 ultra-d gnome-session[1514]: that is, you will receive the 
error a while after causing it.
  May 17 15:09:05 ultra-d gnome-session[1514]: To debug your program, run it 
with the GDK_SYNCHRONIZE environment
  May 17 15:09:05 ultra-d gnome-session[1514]: variable to change this 
behavior. You can then get a meaningful
  May 17 15:09:05 ultra-d gnome-session[1514]: backtrace from your debugger if 
you break on the gdk_x_error() function.)
  May 17 15:09:05 ultra-d kernel: [276368.790571] traps: metacity[1688] trap 
int3 ip:7fb31d5d9d00 sp:7ffc0f98c740 error:0
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Child process 1688 was already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Child process 1688 was 
already dead.
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
Application 'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: Application 
'metacity.desktop' killed by signal 5
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: WARNING: 
App 'metacity.desktop' respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: WARNING: App 'metacity.desktop' 
respawning too quickly
  May 17 15:09:19 ultra-d gnome-session[1514]: Unrecoverable failure in 
required component metacity.desktop
  May 17 15:09:19 ultra-d gnome-session[1514]: gnome-session[1514]: CRITICAL: 
We failed, but the fail whale is dead. Sorry
  May 17 15:09:19 ultra-d gnome-session[1514]: CRITICAL: We failed, but the 
fail whale is dead. Sorry
  May 17 15:09:20 ultra-d gnome-session[1514]: ICE default IO error handler 
doing an exit(), pid = 17669, errno = 11

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun May 17 15:56:28 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.26, 3.19.0-15-generic, x86_64: installed
   virtualbox, 4.3.26, 3.19.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:04ca]
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (rev ff) (prog-if ff)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic 
root=/dev/mapper/system_vg-root_lv ro cryptdevice=/dev/sda2:system_crypt quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/03/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0FTJWD
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/03/2012:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FTJWD:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  

[Touch-packages] [Bug 1429427] Re: Unexplainable time jumps in CRON

[Roger Dueck]

I've had some of the same time jumps in CRON's syslog entries, but where
I really noticed it was during roughly the same time-frame in my apache2
logs.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1429427

Title:
  Unexplainable time jumps in CRON

Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  On my main server I see unexplainable time jumps backwards in the syslog. 
Those jumps affect CRON.
  Example:

  Feb 10 06:48:01 nostromo CRON[20351]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:49:01 nostromo CRON[20364]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20386]: (root) CMD (
/storage/exec/status-nostromo.sh >/dev/null 2>&1)
  Feb  7 05:40:01 nostromo CRON[20389]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20390]: (root) CMD (
/storage/exec/checkinternet.sh 2>/dev/null 1>/dev/null)
  Feb 10 06:50:01 nostromo CRON[20391]: (root) CMD (
/storage/exec/checkip.sh 2>/dev/null 1>/dev/null)

  For debugging I did the following:
  Start xclock and watch xclock and tail -f /var/log/syslog in parallel. When 
CRON logged a wrong time, xclock did NOT show any time jump but seemed to 
freeze for a fraction of a second.
  Open a screen and start a script that will once per second read the time (in 
unix seconds) and compare the read time with the time read a second ago. If the 
current time was smaller, the script would send an email with a process list 
from before and after the jump. The script also never detected any time jump.

  In summary, my current impression is that there might be a bug in CRON 
because no other programm seems to be able to see the "wrong" time. The server 
in question is syslog server for 4 servers and 3 network devices. The time 
jumps exclusively show in syslog entries from the local CRON instance. Not in 
any remote syslog entry and not in any other local syslog entry, e.g. from 
DHCPD, bind, tftpd, etc. etc.
  Also, after a reboot, things work ok for several days upto about 2 or 3 
weeks. Then the "time jumps" start to occur with increasing frequency.

  I don't use user crontabs but maintain all jobs in /etc/crontab. I
  have number of jobs which are triggered every minute and another
  number of jobs which are triggered every 5 minutes (maybe some CRON
  internal counter overflow problem?).

  Hardware:
  Asus P9D-V
  Intel Xeon E3-1240L V3
  16GB ECC RAM
  128GB SSD System
  3x3TB ZFS RaidZ2 storage
  1x3TB Misc. data

  CMOS battery already changed and board inspected.

  nostromo:~ # lsb_release -rd
  Description:Ubuntu 14.04.2 LTS
  Release:14.04

  nostromo:~ # apt-cache policy cron
  cron:
Installed: 3.0pl1-124ubuntu2
Candidate: 3.0pl1-124ubuntu2
Version table:
   *** 3.0pl1-124ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1429427/+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 619003] Re: GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache'

[Roger Davis]

14.04, 64 bit

Attempted todays update, got the following errors in the log:
---
Processing triggers for shared-mime-info (1.2-0ubuntu3) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
Processing triggers for gconf2 (3.2.6-0ubuntu2) ...
Processing triggers for libglib2.0-0:amd64 (2.40.2-0ubuntu1) ...
Processing triggers for libglib2.0-0:i386 (2.40.2-0ubuntu1) ...
Processing triggers for mime-support (3.54ubuntu1.1) ...
Processing triggers for gnome-menus (3.10.1-0ubuntu2) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for hicolor-icon-theme (0.13-1) ...

(gtk-update-icon-cache-3.0:4568): GdkPixbuf-WARNING **: Cannot open
pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-
pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
  gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.
Setting up libudev1:amd64 (204-5ubuntu20.15) ...
Setting up libudev1:i386 (204-5ubuntu20.15) ...
Setting up udev (204-5ubuntu20.15) ...
udev stop/waiting
udev start/running, process 4618
Removing 'diversion of /bin/udevadm to /bin/udevadm.upgrade by fake-udev'
update-initramfs: deferring update (trigger activated)
Setting up libsystemd-daemon0:amd64 (204-5ubuntu20.15) ...
---
Attempted running " gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache " as suggested :

roger@roger-desktop:~$ sudo gdk-pixbuf-query-loaders > 
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission 
denied
roger@roger-desktop:~$ 
---
Everything seems to be working, but the above is obviously not right.  Now what 
do I do ?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/619003

Title:
  GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib
  /gdk-pixbuf-2.0/2.10.0/loaders.cache'

Status in gdk-pixbuf package in Ubuntu:
  Incomplete
Status in gdk-pixbuf package in Debian:
  Incomplete

Bug description:
  During installation of updated version of libgdk-pixbuf2.0-0 on August
  10th 2010, the apt term.log contained multiple (>300) copies of the
  following warning:

  (gtk-update-icon-cache:4729): GdkPixbuf-WARNING **: Cannot open pixbuf
  loader module file '/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No
  such file or directory

  Nevertheless, the file complained about exists, and is readable in
  gedit.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: libgdk-pixbuf2.0-0 2.21.6-2ubuntu5
  ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
  Uname: Linux 2.6.35-15-generic x86_64
  Architecture: amd64
  CheckboxSubmission: 363004b1d940f0fc558ab8c98655a145
  CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
  Date: Mon Aug 16 18:13:29 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdk-pixbuf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/619003/+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 1447879] Re: fscking btrfs consisting of multiple partitions fails

[Roger Binns]

The mailing list eventually went nowhere, including someone helping me
out privately.  He seemed to think it was a udev issue, which was highly
amusing as the udev (and systemd) binaries were running from the very
devices they believed weren't ready yet.

Here is the final scorecard.  I have 3 systems, all using btrfs with
raid0 across two devices.  Both root and home are separate subvolumes on
that.

System 1 (workstation - above report): systemd brings the system up but
times out waiting to mount home.  Setting /home to nofail in fstab and
then running mount -a from a console works just fine.  This is the only
system where the two drives are identical - they are exactly the same
SSD models and firmware versions on the same controller.  (Note system
fails to boot if they are on different controllers which wasn't a
problem with earlier Ubuntu versions.)  Booting with upstart works fine
and is how I have now configured the system.

System 2 (laptop):  the two devices are wrapped in LUKS+dmcrypt.  They
are decrypted at boot and then there is a pause, and then finally
everything comes up.  Most of the time that pause is 3 minutes, but
sometimes is a few seconds.  Again no problems in earlier Ubuntu
releases.

System 3 (server): Like system 1, it is bare devices but in this case
they are about the same capacity but from different vendors.  Everything
works perfectly, and if anything boots a bit faster than earlier Ubuntu
releases.

-- 
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/1447879

Title:
  fscking btrfs consisting of multiple partitions fails

Status in systemd package in Ubuntu:
  New

Bug description:
  I have two SSDs in raid0 (striped) configuration with my root and home
  as separate subvolumes.  This setup has worked fine for several Ubuntu
  releases, but fails with systemd on 15.04.  systemd does manage to
  mount root, but then looks like it is trying to fsck the disk for
  home which is nonsensical.  After 90 seconds it drops into a useless
  shell where I can't fix things.

  Relevant lines from /etc/fstab

  UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /   btrfs   
defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@
 0   1
  UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home   btrfs   
defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@home
 0   2

  
  Note how the lines are identical except for the subvol value.  I originally 
didn't have the device= bits either but had to add it for root because of how 
`btrfs device scan` is run.  With or without it present doesn't make any 
difference for home.

  There is no such problem booting with upstart

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 23 19:45:38 2015
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic 
root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf 
nomdmonisw init=/sbin/upstart
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   1 overridden configuration files found.
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+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 677139] From: natopeacekeeper

[roger mateo]

Good afternoon

http://clintoncountydisposal.com/context.php?jack=mrw7wyv91wane6



natopeacekee...@gmail.com


Sent from my iPhone

-- 
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/677139

Title:
  [Realtek ID 275] Recording problem intenal micphone , internal laptop
  speacker no not work., however when you use speacker or micphone via
  jacks external audio works.

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  internal laptop micophone, internal laptop speackers do not work.
  external speackers and external micophone via jacks will work.
  this is the i386 10.04 desktop version. on sony laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: alsa-base 1.0.22.1+dfsg-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7
  Uname: Linux 2.6.32-25-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: HDA Generic [HDA Generic]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  roger  1563 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xdb40 irq 22'
 Mixer name : 'Intel G45 DEVIBX'
 Components : 'HDA:10ec0275,104d4100,0015 
HDA:80862804,104d4100,0010'
 Controls  : 8
 Simple ctrls  : 4
  Date: Thu Nov 18 13:43:31 2010
  InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SelectedCard: 0 Intel HDA-Intel - HDA Intel
  SourcePackage: alsa-driver
  Symptom: audio
  Title: [Realtek ID 275] Recording problem
  dmi.bios.date: 12/16/2009
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0270Q3
  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:bvnINSYDE:bvrR0270Q3:bd12/16/2009:svnSonyCorporation:pnVPCS111FM:pvrC103WRC4:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCS111FM
  dmi.product.version: C103WRC4
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/677139/+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 1462046] [NEW] Incorrect btrfs ready invocation 64-btrfs.rules

[Roger Binns]

Public bug reported:

/lib/udev/rules.d/64-btrfs.rules

This invokes btrfs ready $devnode.  However that will always give a
usage error.  The correct invocation is as follows (note added
device).

btrfs device ready $devnode

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: udev 219-7ubuntu5
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: XFCE
CustomUdevRuleFiles: 51-android.rules 60_smfpautoconf_samsung.rules 
61_smfpautoconf_samsung.rules 99-libsane-samsungmfp.rules 60-vboxdrv.rules
Date: Thu Jun  4 10:39:36 2015
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic 
root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf 
nomdmonisw init=/lib/systemd/systemd udev.log-priority=debug 
rd.udev.log-priority=debug
SourcePackage: systemd
UpgradeStatus: Upgraded to vivid on 2015-04-23 (41 days ago)
dmi.bios.date: 08/13/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2104
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug vivid

-- 
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/1462046

Title:
  Incorrect btrfs ready invocation 64-btrfs.rules

Status in systemd package in Ubuntu:
  New

Bug description:
  /lib/udev/rules.d/64-btrfs.rules

  This invokes btrfs ready $devnode.  However that will always give a
  usage error.  The correct invocation is as follows (note added
  device).

  btrfs device ready $devnode

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 219-7ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: XFCE
  CustomUdevRuleFiles: 51-android.rules 60_smfpautoconf_samsung.rules 
61_smfpautoconf_samsung.rules 99-libsane-samsungmfp.rules 60-vboxdrv.rules
  Date: Thu Jun  4 10:39:36 2015
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic 
root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf 
nomdmonisw init=/lib/systemd/systemd udev.log-priority=debug 
rd.udev.log-priority=debug
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (41 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1462046/+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 1462046] Re: Incorrect btrfs ready invocation 64-btrfs.rules

[Roger Binns]

Supposedly 'btrfs ready $devnode' is internal to udev and unrelated to
the similarly named btrfs device ready command

** Changed in: systemd (Ubuntu)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1462046

Title:
  Incorrect btrfs ready invocation 64-btrfs.rules

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  /lib/udev/rules.d/64-btrfs.rules

  This invokes btrfs ready $devnode.  However that will always give a
  usage error.  The correct invocation is as follows (note added
  device).

  btrfs device ready $devnode

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: udev 219-7ubuntu5
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: XFCE
  CustomUdevRuleFiles: 51-android.rules 60_smfpautoconf_samsung.rules 
61_smfpautoconf_samsung.rules 99-libsane-samsungmfp.rules 60-vboxdrv.rules
  Date: Thu Jun  4 10:39:36 2015
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-18-generic 
root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf 
nomdmonisw init=/lib/systemd/systemd udev.log-priority=debug 
rd.udev.log-priority=debug
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (41 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1462046/+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 1447879] Re: fscking btrfs consisting of multiple partitions fails

[Roger Binns]

I will ask on the mailing list.  It is failing to mount /home.  The
lines in /etc/fstab for root and /home are identical, except that one is
subvol=@ and one is subvol=@home.

Root mounts just fine.  When it comes time to mount /home, systemd is
trying to check the filesystem but that isn't going succeed as all the
parts are already mounted for root.

There are some logs included in earlier responses.  No clues as to the
actual problem though.  I will reboot and get the logs for your request.

-- 
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/1447879

Title:
  fscking btrfs consisting of multiple partitions fails

Status in systemd package in Ubuntu:
  New

Bug description:
  I have two SSDs in raid0 (striped) configuration with my root and home
  as separate subvolumes.  This setup has worked fine for several Ubuntu
  releases, but fails with systemd on 15.04.  systemd does manage to
  mount root, but then looks like it is trying to fsck the disk for
  home which is nonsensical.  After 90 seconds it drops into a useless
  shell where I can't fix things.

  Relevant lines from /etc/fstab

  UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /   btrfs   
defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@
 0   1
  UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home   btrfs   
defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@home
 0   2

  
  Note how the lines are identical except for the subvol value.  I originally 
didn't have the device= bits either but had to add it for root because of how 
`btrfs device scan` is run.  With or without it present doesn't make any 
difference for home.

  There is no such problem booting with upstart

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 23 19:45:38 2015
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic 
root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf 
nomdmonisw init=/sbin/upstart
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   1 overridden configuration files found.
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+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 1447879] Re: fscking btrfs consisting of multiple partitions fails

[Roger Binns]

** Attachment added: systemctl status of * (everything)
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+attachment/4405784/+files/status-all.txt

-- 
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/1447879

Title:
  fscking btrfs consisting of multiple partitions fails

Status in systemd package in Ubuntu:
  New

Bug description:
  I have two SSDs in raid0 (striped) configuration with my root and home
  as separate subvolumes.  This setup has worked fine for several Ubuntu
  releases, but fails with systemd on 15.04.  systemd does manage to
  mount root, but then looks like it is trying to fsck the disk for
  home which is nonsensical.  After 90 seconds it drops into a useless
  shell where I can't fix things.

  Relevant lines from /etc/fstab

  UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /   btrfs   
defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@
 0   1
  UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 /home   btrfs   
defaults,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1347095B97B4-part1,device=/dev/disk/by-id/ata-Crucial_CT960M500SSD1_1338094EA3CA-part1,autodefrag,compress=lzo,subvol=@home
 0   2

  
  Note how the lines are identical except for the subvol value.  I originally 
didn't have the device= bits either but had to add it for root because of how 
`btrfs device scan` is run.  With or without it present doesn't make any 
difference for home.

  There is no such problem booting with upstart

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Apr 23 19:45:38 2015
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic 
root=UUID=3ff68715-0daa-4e44-8de2-0997f36d8ab6 ro rootflags=subvol=@ nomdmonddf 
nomdmonisw init=/sbin/upstart
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   
   1 overridden configuration files found.
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (0 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447879/+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