Re: [Touch-packages] [Bug 1972131] Re: occasional flashing screen since upgrade to 22.04

2023-08-28 Thread Kent Frazier
I'm on 23.04 now (and now no longer have a touchscreen)  So can't 
test... sorry.

On 8/28/23 11:45, Oibaf wrote:
> Kent, Ubuntu 22.04 now has mesa 23.0.4-0ubuntu1~22.04.1, can you try it,
> is this still an issue for you?
>

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

Title:
  occasional flashing screen since upgrade to 22.04

Status in mesa package in Ubuntu:
  New

Bug description:
  Since upgrading to 22.04 I often experienced a flashing screen. I have
  noticed the issue in particular when I have an onboard keyboard
  displayed. Hiding the onboard keyboard and then showing the keyboard
  seems to resolve the flashing problem

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  8 17:20:13 2022
  InstallationDate: Installed on 2020-07-18 (659 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (9 days ago)
  VarLogDistupgradeTermlog:

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


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


[Touch-packages] [Bug 1972131] Re: occasional flashing screen since upgrade to 22.04

2022-05-15 Thread Kent Frazier
Problem seems to manifest itself most often after wake-up from
hibernate.

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

Title:
  occasional flashing screen since upgrade to 22.04

Status in mesa package in Ubuntu:
  New

Bug description:
  Since upgrading to 22.04 I often experienced a flashing screen. I have
  noticed the issue in particular when I have an onboard keyboard
  displayed. Hiding the onboard keyboard and then showing the keyboard
  seems to resolve the flashing problem

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  8 17:20:13 2022
  InstallationDate: Installed on 2020-07-18 (659 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (9 days ago)
  VarLogDistupgradeTermlog:

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


-- 
Mailing list: https://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 1972129] Re: user account show different users than "Users and Groups"

2022-05-09 Thread Kent Frazier
Have no idea. The pre-upgrade account worked as expected in 21.10 before 
upgrade, and I didn't make any manual changes that would have affected 
anything that I know of. I wasn't even aware of the file that holds the 
SystemAccount flag.

On 5/9/22 13:50, Sebastien Bacher wrote:
> Great! Do you have any idea how the account ended up being marked as
> SystemAccount=true?
>

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

Title:
  user account show different users than "Users and Groups"

Status in accountsservice package in Ubuntu:
  Incomplete

Bug description:
  upgraded from 21.10 to 22.04. Upgrade seemed to require creating a new
  (admin) id, which I did. When I now login the new account name is
  displayed but I have to list other users to be able to login with my
  pre-upgrade account. Going to system settings -> User Accounts shows
  only the new account. Once logged in, invoking "Users & Groups" shows
  both new id and pre-upgrade user account.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun May  8 16:30:27 2022
  InstallationDate: Installed on 2020-07-18 (659 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to jammy on 2022-04-29 (9 days ago)
  VarLogDistupgradeTermlog:

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


-- 
Mailing list: https://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 1972129] Re: user account show different users than "Users and Groups"

2022-05-09 Thread Kent Frazier
On 5/9/22 05:08, Sebastien Bacher wrote:
> /usr/libexec/accounts-daemon --debug
$ sudo /usr/libexec/accounts-daemon --debug 
(py310)
[sudo] password for frazier:
(accounts-daemon:734852): DEBUG: entering main loop
(accounts-daemon:734852): DEBUG: Changing permission of 
/var/lib/AccountsService/users/frazier to 0600
(accounts-daemon:734852): DEBUG: Changing permission of 
/var/lib/AccountsService/users/gnome-initial-setup to 0600
(accounts-daemon:734852): DEBUG: Changing permission of 
/var/lib/AccountsService/users/kfrazier to 0600
(accounts-daemon:734852): DEBUG: Changing permission of 
/var/lib/AccountsService/users/gdm to 0600
(accounts-daemon:734852): DEBUG: skipping user: root
(accounts-daemon:734852): DEBUG: skipping user: daemon
(accounts-daemon:734852): DEBUG: skipping user: bin
(accounts-daemon:734852): DEBUG: skipping user: sys
(accounts-daemon:734852): DEBUG: skipping user: sync
(accounts-daemon:734852): DEBUG: skipping user: games
(accounts-daemon:734852): DEBUG: skipping user: man
(accounts-daemon:734852): DEBUG: skipping user: lp
(accounts-daemon:734852): DEBUG: skipping user: mail
(accounts-daemon:734852): DEBUG: skipping user: news
(accounts-daemon:734852): DEBUG: skipping user: uucp
(accounts-daemon:734852): DEBUG: skipping user: proxy
(accounts-daemon:734852): DEBUG: skipping user: www-data
(accounts-daemon:734852): DEBUG: skipping user: backup
(accounts-daemon:734852): DEBUG: skipping user: list
(accounts-daemon:734852): DEBUG: skipping user: irc
(accounts-daemon:734852): DEBUG: skipping user: gnats
(accounts-daemon:734852): DEBUG: skipping user: nobody
(accounts-daemon:734852): DEBUG: skipping user: systemd-network
(accounts-daemon:734852): DEBUG: skipping user: systemd-resolve
(accounts-daemon:734852): DEBUG: skipping user: systemd-timesync
(accounts-daemon:734852): DEBUG: skipping user: messagebus
(accounts-daemon:734852): DEBUG: skipping user: syslog
(accounts-daemon:734852): DEBUG: skipping user: _apt
(accounts-daemon:734852): DEBUG: skipping user: tss
(accounts-daemon:734852): DEBUG: skipping user: uuidd
(accounts-daemon:734852): DEBUG: skipping user: tcpdump
(accounts-daemon:734852): DEBUG: skipping user: avahi-autoipd
(accounts-daemon:734852): DEBUG: skipping user: usbmux
(accounts-daemon:734852): DEBUG: skipping user: rtkit
(accounts-daemon:734852): DEBUG: skipping user: dnsmasq
(accounts-daemon:734852): DEBUG: skipping user: cups-pk-helper
(accounts-daemon:734852): DEBUG: skipping user: speech-dispatcher
(accounts-daemon:734852): DEBUG: skipping user: avahi
(accounts-daemon:734852): DEBUG: skipping user: kernoops
(accounts-daemon:734852): DEBUG: skipping user: saned
(accounts-daemon:734852): DEBUG: skipping user: nm-openvpn
(accounts-daemon:734852): DEBUG: skipping user: hplip
(accounts-daemon:734852): DEBUG: skipping user: whoopsie
(accounts-daemon:734852): DEBUG: skipping user: colord
(accounts-daemon:734852): DEBUG: skipping user: geoclue
(accounts-daemon:734852): DEBUG: skipping user: pulse
(accounts-daemon:734852): DEBUG: skipping user: gnome-initial-setup
(accounts-daemon:734852): DEBUG: skipping user: gdm
(accounts-daemon:734852): DEBUG: loaded user: frazier
(accounts-daemon:734852): DEBUG: skipping user: systemd-coredump
(accounts-daemon:734852): DEBUG: skipping user: sshd
(accounts-daemon:734852): DEBUG: skipping user: clamav
(accounts-daemon:734852): DEBUG: skipping user: postfix
(accounts-daemon:734852): DEBUG: skipping user: lightdm
(accounts-daemon:734852): DEBUG: skipping user: stunnel4
(accounts-daemon:734852): DEBUG: skipping user: sssd
(accounts-daemon:734852): DEBUG: skipping user: postgres
(accounts-daemon:734852): DEBUG: skipping user: cerebro
(accounts-daemon:734852): DEBUG: skipping user: libvirt-qemu
(accounts-daemon:734852): DEBUG: skipping user: libvirt-dnsmasq
(accounts-daemon:734852): DEBUG: skipping user: nginx
(accounts-daemon:734852): DEBUG: skipping user: lxc-dnsmasq
(accounts-daemon:734852): DEBUG: skipping user: systemd-oom
(accounts-daemon:734852): DEBUG: skipping user: swtpm
(accounts-daemon:734852): DEBUG: loaded user: kfrazier
(accounts-daemon:734852): DEBUG: loaded user: gnome-initial-setup
(accounts-daemon:734852): DEBUG: loaded user: gdm
(accounts-daemon:734852): DEBUG: failed to load gdms custom.conf: Key 
file does not have key “AutomaticLoginEnable” in group “daemon”
(accounts-daemon:734852): DEBUG: got NameLost, exiting
(accounts-daemon:734852): DEBUG: exiting

Could you to do # /usr/libexec/accounts-daemon --debug and see what that 
does display about your account? Note: the frazier account is the one 
that did not show up when I accessed "System Settings" -> "User 
Accounts" It is my account from pre-upgrade. Changing to 
frazier:SystemAccount=false has fixed the problem. Many Thanks!


root@frazier:/var/lib/AccountsService/users# grep -H System *
frazier:SystemAccount=true
gdm:SystemAccount=true
gnome-initial-setup:SystemAccount=true
kfrazier:SystemAccount=false

-- 
You received this bug notification 

[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

2021-08-25 Thread Kent Lin
Test pass with Dell DW5821e [413C:81D7] on hirsute

* The version of the packages tested:
   ModemManager: 1.16.6
   libmbim: 1.24.8
   libqmi: 1.28.6

** Attachment added: "DW5821e.log"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1934286/+attachment/5520406/+files/DW5821e.log

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Focal:
  Fix Committed
Status in libqmi source package in Focal:
  Fix Committed
Status in modemmanager source package in Focal:
  Fix Committed
Status in libmbim source package in Hirsute:
  Fix Committed
Status in libqmi source package in Hirsute:
  Fix Committed
Status in modemmanager source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from the -proposed
  component:

  $ sudo apt update
  $ sudo apt install modemmanager
  $ sudo apt install libqmi-utils

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.

  3. Check if the modem can be enabled

    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  = Certification Validation =

  Additionally to the aforementioned test cases, the Certification Team
  will perform some coverage testing across supported devices to make
  sure the other modems still work as expected.

  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  [Other Info]

  We need to upgrade to these 3 packages (in Impish) at the 

[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

2021-07-23 Thread Kent Lin
Test Pass on
WWAN Test: 
https://certification.canonical.com/hardware/202010-28324/submission/223136/
ACPI Stress Test: 
https://certification.canonical.com/hardware/202010-28324/submission/223167/

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Focal:
  Fix Committed
Status in libqmi source package in Focal:
  Fix Committed
Status in modemmanager source package in Focal:
  Fix Committed
Status in libmbim source package in Hirsute:
  Fix Committed
Status in libqmi source package in Hirsute:
  Fix Committed
Status in modemmanager source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from the -proposed
  component:

  $ sudo apt update
  $ sudo apt install modemmanager
  $ sudo apt install libqmi-utils

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.

  3. Check if the modem can be enabled

    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  = Certification Validation =

  Additionally to the aforementioned test cases, the Certification Team
  will perform some coverage testing across supported devices to make
  sure the other modems still work as expected.

  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  [Other Info]

  We need to upgrade to these 3 packages (in Impish) at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  To support the 

[Touch-packages] [Bug 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

2021-07-20 Thread Kent Lin
Test pass on
https://certification.canonical.com/hardware/202010-28320/submission/223095/

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Focal:
  Fix Committed
Status in libqmi source package in Focal:
  Fix Committed
Status in modemmanager source package in Focal:
  Fix Committed
Status in libmbim source package in Hirsute:
  Fix Committed
Status in libqmi source package in Hirsute:
  Fix Committed
Status in modemmanager source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

    The following images will be used to verify the version of the ModemManager 
suite:
    * Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
    * Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
    * Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

    The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
    We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

    The ModemManager suite will be installed from the -proposed
  component:

  $ sudo apt update
  $ sudo apt install modemmanager
  $ sudo apt install libqmi-utils

  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  4.3 List the detected modems

  $ mmcli --list-modems

  4.4 Check the modem’s status

  $ mmcli --modem 0

  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem
  only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

    The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
    If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

    The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
    The supported modems should be listed.

  3. Check if the modem can be enabled

    If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  = Certification Validation =

  Additionally to the aforementioned test cases, the Certification Team
  will perform some coverage testing across supported devices to make
  sure the other modems still work as expected.

  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  [Other Info]

  We need to upgrade to these 3 packages (in Impish) at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.8
  * libqmi : 1.28.6

  To support the mentioned 2 modems, the system needs to use kernels which 
include specific patches and  kernel config options .
  

[Touch-packages] [Bug 1913855] [NEW] Failure to pass system check and present login screen

2021-01-29 Thread Kent Lion
Public bug reported:

I'm reporting this against xorg, because of where the problem occurs, as
indicated below, I can't tell if the problem is with xorg, lightdm or
light-locker. The system is a Dell Optiplex 745 single-booting to
Xubuntu 20.04 up-to-date as of today.

I replaced one of 2 monitors, the one rotated to portrait orientation, with a 
higher resolution monitor. Started the system, logged in as another user and 
changed the desktop background however, when I then logged out and restarted 
the system, it behaved normally until it displayed the usual
/dev/sda1: clean, x/x files, /x blocks
on both monitors. The prompt remained for a few seconds, slowly blinked off and 
on 6 times, and then remained with no further activity. The system works fine 
if I boot from a Xubuntu 18.04 DVD (I didn't have a 20.04 DVD, and this is the 
only machine with a burner). On another machine, I determined that the system 
was booting, because the machine was visible on the network, and its shared 
folders were accessible.

I could get to a login prompt and log on using Alt+F1 to F6. Alt-F7
returned me to the file system check prompt. I was able to start xorg
after logging on with startx, and changing all settings for the new
monitor, everything worked normally until logging out, which of course
returned me to the command line where I had given the command startx.

If I log out requesting a restart, the system reboots, but still stops at the 
same place every time. That behavior hadn't changed the next day. I can use the 
machine, but only by selecting a terminal, logging as myself or the other user 
and giving the startx command. I have been unable to find anything on the 
Internet that corrects the problem. Since the problem first started, two 
crashes have occurred and I allowed them to be reported; however, they were 
light-locker crashes. I reinstalled lightdm and light-locker, but that made no 
difference. I installed gdm3, which works fine, but switching back to lightdm 
with:
sudo dpkg-reconfigure gdm3
sudo dpkg --configure lightdm
resulted in:
dpkg: error processing package lightdm (--configure):
 package lightdm is already installed and configured
Errors were encountered while processing:
 lightdm

So I can't really be sure if the problem is with xorg, lightdm or light-
locker, but since there are no error messages and everything else works
fine, it's clearly a bug, if a strange one. I do not relish the idea of
having to reinstall Xubuntu; so for the time being, I'll use gdm3,
though I prefer lightdm's ability to properly display backdrops and use
the two monitors properly extended (with gdm3, the mouse moves down the
left portrait monitor before moving onto the right monitor where gdm3
sees fit to put the logon dialog). The next thing I'll try is
autoremoving lightdm rebooting a few times and then reinstalling it...

Because of the absence of error messages and information even suggesting
why X isn't starting, I have no idea what other information about my
system might be useful to you, but if you need something additional,
I'll try to provide it.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: XFCE
Date: Fri Jan 29 22:12:37 2021
DistUpgraded: 2020-10-20 06:56:14,405 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.16, 5.4.0-62-generic, x86_64: installed
 virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV620 LE [Radeon HD 3450] [1002:95c5] 
(prog-if 00 [VGA controller])
   Subsystem: Dell OptiPlex 980 [1028:0342]
InstallationDate: Installed on 2019-11-29 (427 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. OptiPlex 780
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-65-generic 
root=UUID=68c4f426-dc84-48e8-be0f-cd1a5acfb729 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to focal on 2020-10-20 (101 days ago)
dmi.bios.date: 08/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A15
dmi.board.name: 0C27VV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd08/06/2013:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0C27VV:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 780
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 

[Touch-packages] [Bug 1912083] [NEW] the icons are longer

2021-01-16 Thread Kent Tai
Public bug reported:

the icons are longer than they should be

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 17 11:12:46 2021
DistUpgraded: 2021-01-17 10:47:32,279 DEBUG openCache()
DistroCodename: groovy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.16, 5.8.0-36-generic, x86_64: installed
 virtualbox, 6.1.16, 5.8.0-38-generic, x86_64: installed
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company UHD Graphics [103c:86cd]
ImageMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
 Bus 001 Device 002: ID 145f:021f Trust 2.4G Mouse
 Bus 001 Device 004: ID 8087:0026 Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP 348 G7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=aea93e03-8fb8-49c7-8081-a18a438e7864 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to groovy on 2021-01-17 (0 days ago)
dmi.bios.date: 06/11/2020
dmi.bios.release: 15.21
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 86CD
dmi.board.vendor: HP
dmi.board.version: 98.08
dmi.chassis.asset.tag: 5CG0351KMK
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 98.8
dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd06/11/2020:br15.21:efr98.8:svnHP:pnHP348G7:pvrType1ProductConfigId:rvnHP:rn86CD:rvr98.08:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5336AN HP Notebook
dmi.product.name: HP 348 G7
dmi.product.sku: 7HC08AV
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug groovy third-party-packages 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/1912083

Title:
  the icons are longer

Status in xorg package in Ubuntu:
  New

Bug description:
  the icons are longer than they should be

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  BootLog: Error: [Errno 13] 拒絕不符權限的操作: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 17 11:12:46 2021
  DistUpgraded: 2021-01-17 10:47:32,279 DEBUG openCache()
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.8.0-36-generic, x86_64: installed
   virtualbox, 6.1.16, 5.8.0-38-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company UHD Graphics [103c:86cd]
  ImageMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56c9 IMC Networks HP TrueVision HD Camera
   Bus 001 Device 002: ID 145f:021f Trust 2.4G Mouse
   Bus 001 Device 004: ID 8087:0026 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 348 G7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=aea93e03-8fb8-49c7-8081-a18a438e7864 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2021-01-17 (0 days ago)
  dmi.bios.date: 06/11/2020
  dmi.bios.release: 15.21
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 86CD
  dmi.board.vendor: HP
  dmi.board.version: 98.08
  dmi.chassis.asset.tag: 5CG0351KMK
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  

[Touch-packages] [Bug 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

2020-01-28 Thread kent christopher
Update: a kernel upgrade solved the mic white noise for me. I had been
running a 5.0 kernel. Updating to a 5.4 kernel fixed it.

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

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1827440] Re: [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

2020-01-28 Thread kent christopher
Tyler, did you ever find a solution to this? I'm having the same problem
with a the same laptop (X1 Carbon 6th gen) running Kubuntu 18.04. The
only "solution" I've found is to turn off "internal mic boost" using
alsa-mixer (hit F5 to show all channels, cursor all the way to the
right) and keep the mic capture level below 20%. So it works, but far
from ideal since the mic is low (but better than making the person on
the other end of a call hearing a shitload of white noise that's
produced otherwise).

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

Title:
  [X1 Carbon 6th, Realtek ALC285, Mic, Internal] Sound is distorted

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hopefully all the necessary info is in the extra stuff that
  automatically got sent.

  Basically, I didn't do anything fancy, but audio recorded with my
  microphone (through Skype, and arecord in the Terminal) has tons of
  static and the voice is distorted or saturated.

  Booting this computer on Windows doesn't have issues, so that's why I
  don't think it's the computer, I think it's the OS.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tyler  1499 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  2 19:04:55 2019
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [20KHS1TG00, Realtek ALC285, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET62W(1.37):bd02/19/2019:svnLENOVO:pn20KHS1TG00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1TG00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1TG00
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   tyler  1562 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tyler  1562 F...m pulseaudio
   /dev/snd/controlC0:  tyler  1562 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-09 (113 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KHS1TG00
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=c2e26270-73b4-4394-b77a-979175820906 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  Tags:  bionic
  Uname: Linux 4.15.0-48-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET62W (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1TG00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 

[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

2019-12-18 Thread Kent Lion
Perhaps this can help: The symptoms I experience started sometime during
the past year after an update (sudo apt update && sudo apt upgrade &&
sudo apt autoremove) are that some indefinite time (usually less than ½
hour) after I log on, the network disconnects without warning or error.
Clicking on the up/down arrows of the indicator plugin and selecting the
interface reconnects; however, I recently discovered that if, as soon as
I log on, I select "Disconnect" and then select the adapter to
reconnect, my session will be fine until I log out and back in again. So
perhaps the bug is not with network-manager, samba or ifupdown, but with
the logon process(es). My version is 18.04 and I'm using LiteDM GTK+. I
haven't the faintest idea where to look for a cause that might be
related to the logon process(s), but none of the very many "solutions"
offered on various web pages I found on the problem have fixed it for
me.

One other unexpected thing I've noticed is that in editing Ethernet
connections (I don't used wireless enough to have noticed a problem), I
can't edit (or delete) the one the system creates without first adding
another (even if it's the same, e.g., enp2s0, with the same settings)
and switching to it; however, after I did that the first time, and
deleted the system's entry ("Wired connection 1", I think it was
called), at some point the system added another entry, identical in
every way to the one I had added, but called "Ifupdown (enp2s0)" and
connects to that when I log on, not to the one I created (which I have
since deleted, but the original problem still occurs, and disconnecting
and reconnecting still prevents the random disconnect).

All of this applies to 2 other machines, also running up-to-date xubuntu
18.04, although on one of the other machines, the adapter is enp4s25. It
also occurs with xubuntu and xfce sessions. I suspect the difficutly in
finding the cause(s) is in part due to the confusing way samba/network
settings are stored, with the same setting sometimes stored in different
locations, entered via GUI or command line or both, possibly leading to
conflicts.

I have spent many hours on this problem, and have only the above work-
around, not a fix. Even though this problem has been around longer than
18.04, since 18.04, samba has clearly been broken, and until networking
is as reliable and as easy to set up as in Windows, (x/l/k)ubuntu will
not be suitable for typical home users.

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
    

[Touch-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

2019-11-23 Thread Kent Lion
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547

I'm posting here instead of the bug at: https://bugs.launchpad.net/bugs/1676547
because it got me on the path that may have solved the problem (time will tell).
My /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf also 
contained:
[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:wwan
When I cleared it out and rebooted, it was still empty and the problem was 
still there. At that point, I noticed that when I clicked on the Network 
Manager applet (↑↓) it displayed the lines:
Ethernet Network (gray title)
Wired connection 1
Disconnect
enp0s25
VPN Connections
Enable Networking (checkbox)
Connection Information
Edit Connections...

But the machine has only one ethernet card, so I chose Edit Connections... and 
changed the connection name to the device name enp0s25. Using ifdown -a worked 
fine, but ifup -a gave me a long pause followed by:
sudo unable to resolve host [hostname]: Resource temporarily unavailable
When I then clicked on the Network Manager applet it showed enp0s25 above AND 
below Disconnect. When I then clicked Disconnect and then clicked enp0s25, it 
reconnected just fine. If I delete or restore the original 
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf, it stops 
working; the file must be empty. On the machine I'm typing this on (also 
updated Bionic 64), 
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf is not empty, 
but I don't do file sharing on it. Now that the other machine is working, I 
find I can access its shared folders on my network without a problem.

So this bug probably has more than one cause. It's as if network
connection information is being taken from at least 2 different
locations, and one or more of them has/have been forgotten but should be
gone.

I do note that when I click Edit Connections... the connection
information does not necessarily agree with what's in
/etc/network/interfaces, in particular netmask refuses to keep the value
255.255.255.0 and reverts to 24 (could 24 refer to /24 in
192.168.15.109/24 ?), which is not the netmask /etc/network/interfaces
requires for a static IP setting.

My problem began with a clean install from a freshly downloaded ISO of
Xubuntu 18.04 LTS 64 bit desktop (not server). Networking and Internet
worked, but while setting it up for file sharing over the network (as
the machine it replaced had done), I eventually lost all network access,
and the network manager applet refused to connect, even when it said it
"connection established"...before changing to say "disconnected". I
previously reported a bug that suddenly disappeared by itself for a few
months and that then recently reappeared: after some minutes connected
to the Internet, my network connection would suddenly disconnect, and
I'd have to reconnect it in the Network Manager applet. So I just made
the change to it's name on that machine, and we'll see if that solves
the problem or not (it's a pain to reproduce, because it requires
rebooting and waiting an unknown amount of time.

Getting file sharing in Linux is like finding an Android app: multiple
choices to try, only to discover that none (or almost none) does the
minimum that is reasonable to expect from it.

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

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+subscriptions

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


[Touch-packages] [Bug 1792579] [NEW] Network Disconnecting Intermittantly

2018-09-14 Thread Kent Lion
Public bug reported:

On my machine (OPTIPLEX GX620, Xubuntu 18.04 LTS) my wired (Ethernet)
connection disconnects randomly. Everything was fine before the upgrade
from Xenial LTS. It's not yet reproducible (by me). There are no error
messages associated with it, the indicator plugin doesn't turn grey, and
I've noticed no pattern to when it occurs. The only way I know it is has
occurred is when something that uses the (Samba) network times out or
stops doing anything. If I click the indicator plugin and select "wired
connection 1", it reconnects immediately, But at some later time the
same thing may happen again; it could be after a few minutes or many
hours. This happens on another, the AMD machine I use as a file server,
too, so it looks like a bug in Bionic Beaver, not a software package.

 lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

I suppose the bug could have something to do with the compatibility of
Samba and 18.04 LTS, because after the upgrade, everything in /etc/fstab
that used the credentials option stopped working, but that's part of
another bug already reported by others but not yet solved.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Network Disconnecting Intermittantly

Status in network-manager package in Ubuntu:
  New

Bug description:
  On my machine (OPTIPLEX GX620, Xubuntu 18.04 LTS) my wired (Ethernet)
  connection disconnects randomly. Everything was fine before the
  upgrade from Xenial LTS. It's not yet reproducible (by me). There are
  no error messages associated with it, the indicator plugin doesn't
  turn grey, and I've noticed no pattern to when it occurs. The only way
  I know it is has occurred is when something that uses the (Samba)
  network times out or stops doing anything. If I click the indicator
  plugin and select "wired connection 1", it reconnects immediately, But
  at some later time the same thing may happen again; it could be after
  a few minutes or many hours. This happens on another, the AMD machine
  I use as a file server, too, so it looks like a bug in Bionic Beaver,
  not a software package.

   lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  I suppose the bug could have something to do with the compatibility of
  Samba and 18.04 LTS, because after the upgrade, everything in
  /etc/fstab that used the credentials option stopped working, but
  that's part of another bug already reported by others but not yet
  solved.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792579/+subscriptions

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


[Touch-packages] [Bug 1771749] Re: Ethernet connection lost after few minutes since starting

2018-09-13 Thread Kent Lion
XUbuntu 18.04 has been doing this since I upgraded a few days ago. No
error messages or any other sign that the Ethernet network connection
has been dropped. I first notice it when I try to do something on the
network and it times out. I haven't changed any network settings for
over a year, but this never happened with Xenial LTS, and I haven't
noticed any pattern to the occurrence vs what I happen to be doing at
the time, so I can't reproduce it at will.

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

Title:
  Ethernet connection lost after few minutes since starting

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  
  This is the same bug I notified at Bug #1770848 but with a more precise 
selection of (what I think it is) the package affected and a better description.

  I made a few days ago a fresh install of the Kubuntu 18.04 LTS and it
  is most everything Ok, but -I think that- the network-manager has a
  problem.

  In the last LTS version, Kubuntu 16.04, nor in any Linux version if I
  remember well, I never lost connection through Ethernet (the only
  Internet connection with our desktop PC), but the Bionic Beaver loses
  the connection every now and then, perhaps within few minutes or
  hours, but several times per day.

  When the connection is lost, I note that it disappears any info even
  mention to any network into the network window and the network manager
  icon becomes red color.

  Not matter if I unplug and then plug the ethernet cable again, the
  ethernet connection is not longer detected and only restarting the PC
  makes the connection to work again.

  Incidentally, I also have noticed with this version of Kubuntu 18.04
  that in my laptop there is also now a similar problem with the
  scanner: If I plug it in some USB port of the laptop once Kubuntu
  18.04 is already running, it's not detected by Xsane. I have to plug
  it in before than pressing the power button or at the time of starting
  the OS, for the scanner to be detected by the scanning program (and
  then only works with Xsane, not if I use Simple Scan or Skanlite, even
  when it works under Xsane), as I said in the Bug #1771525 and, evenly,
  if I unplug the scanner cable from the USB port it is not detected
  anymore when plugging it again, and only restarting the laptop makes
  it to be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu May 17 08:24:23 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-11 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev enp0s7 proto static metric 100 
   169.254.0.0/16 dev enp0s7 scope link metric 1000 
   192.168.1.0/24 dev enp0s7 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   enp0s7no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  PciNetwork:
   
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  ethernet  
1526538083  jue 17 may 2018 08:21:23 CEST  yes  4294967196
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s7  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp0s7  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  1cc37db8-0db8-3887-acf2-59fbbcd0cb1c  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ApportVersion: 

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-05-02 Thread James Kent
Reiterating the above experiences regarding the Dell XPS 9560.  Black
screen with nvidia drivers.  Cannot workaround this issue unless I
remove the drivers.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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


[Touch-packages] [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1

2018-03-02 Thread Kent Ross
> sudo apt remove libegl1

This cascaded to what turned out to be the entirety of ubuntu-desktop
for me. I would advise caution here, it can be a pain to get back.

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

Title:
  [regression] Missing Wayland login option and missing GL acceleration,
  after installing libegl1

Status in libglvnd package in Ubuntu:
  Confirmed
Status in mesa-demos package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I just updated bionic and suddenly:
    * No 'Ubuntu on Wayland' login option.
    * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe 
(software rendering)

  WORKAROUND: sudo apt remove libegl1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sat Feb 24 13:59:46 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-12-12 (73 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1731703] [NEW] The "Add a VPN Connection" menu entry is disabled even with VPN plugins installed

2017-11-11 Thread Stephen Kent
Public bug reported:

I am on Linux Mint 18.2 with network-manger-gnome version
1.2.6-0ubuntu0.16.04.4.

Steps to reproduce:

- Install a VPN plugin (such as the package network-manager-openvpn-gnome)
- Click the network manager applet to open the menu
- Select the "VPN Connections" submenu
- Observe the "Add a VPN Connection" menu entry is disabled

Expected behavior: The "Add a VPN Connection" menu entry is enabled and
works properly.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Screenshot"
   
https://bugs.launchpad.net/bugs/1731703/+attachment/5007684/+files/vpn-menu.png

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

Title:
  The "Add a VPN Connection" menu entry is disabled even with VPN
  plugins installed

Status in network-manager package in Ubuntu:
  New

Bug description:
  I am on Linux Mint 18.2 with network-manger-gnome version
  1.2.6-0ubuntu0.16.04.4.

  Steps to reproduce:

  - Install a VPN plugin (such as the package network-manager-openvpn-gnome)
  - Click the network manager applet to open the menu
  - Select the "VPN Connections" submenu
  - Observe the "Add a VPN Connection" menu entry is disabled

  Expected behavior: The "Add a VPN Connection" menu entry is enabled
  and works properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1731703/+subscriptions

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


[Touch-packages] [Bug 1713564] LightdmDisplayLog.txt

2017-08-28 Thread Kent Lion
apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1713564/+attachment/4940359/+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/1713564

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


[Touch-packages] [Bug 1713564] Re: Repeated problem on login with damaged problem report.

2017-08-28 Thread Kent Lion
Running apport-collect -p xorg 1713564 appears to have been successful.

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


[Touch-packages] [Bug 1713564] ProcCpuinfoMinimal.txt

2017-08-28 Thread Kent Lion
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1713564/+attachment/4940365/+files/ProcCpuinfoMinimal.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/1713564

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


[Touch-packages] [Bug 1713564] JournalErrors.txt

2017-08-28 Thread Kent Lion
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1713564/+attachment/4940358/+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/1713564

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


[Touch-packages] [Bug 1713564] CurrentDmesg.txt

2017-08-28 Thread Kent Lion
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1713564/+attachment/4940355/+files/CurrentDmesg.txt

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

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


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

2017-08-28 Thread Kent Lion
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1713564/+attachment/4940356/+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/1713564

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


[Touch-packages] [Bug 1713564] BootLog.txt

2017-08-28 Thread Kent Lion
apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1713564/+attachment/4940354/+files/BootLog.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/1713564

Title:
  Repeated problem on login with damaged problem report.

Status in xorg package in Ubuntu:
  New

Bug description:
  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to
  an invalid core dump with a warning referencing /tmp/apport_core. This
  has been going on for over a year, but doesn't seem to be a common
  problem, since I find only 2 similar bug references. Bugs #1424864 and
  #1507461 appear to be giving a similar but not identical error
  message, and the symptoms of neither match mine.

  Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
  InstallationDate: Installed on 2016-07-02 (422 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. OptiPlex GX620
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-93-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2006
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0PY423
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 15
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
  dmi.product.name: OptiPlex GX620
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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


[Touch-packages] [Bug 1713564] [NEW] Repeated problem on login with damaged problem report.

2017-08-28 Thread Kent Lion
Public bug reported:

Sometimes every time I log in to Xubuntu 16.04, sometimes every other
time, the first thing I get are 2 dialogs saying there has been a
problem and 2 requests for permission to submit a problem report. I
always give permission, and after I do, everything seems to work fine.
Every time I've ever looked at the details, I find something that says
the problem report is damaged and cannot be processed, and refers to an
invalid core dump with a warning referencing /tmp/apport_core. This has
been going on for over a year, but doesn't seem to be a common problem,
since I find only 2 similar bug references. Bugs #1424864 and #1507461
appear to be giving a similar but not identical error message, and the
symptoms of neither match mine.

Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
--- 
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: Fresh install
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
 virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
   Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:2291]
InstallationDate: Installed on 2016-07-02 (422 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Dell Inc. OptiPlex GX620
Package: xorg 1:7.7+13ubuntu3
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9b3768b1-7ec8-4d00-8047-4e66b6d7c008 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Tags:  xenial ubuntu
Uname: Linux 4.4.0-93-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/30/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0PY423
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 15
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX620:pvr:rvnDellInc.:rn0PY423:rvr:cvnDellInc.:ct15:cvr:
dmi.product.name: OptiPlex GX620
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2

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


** Tags: apport-collected ubuntu xenial

** Tags added: apport-collected ubuntu xenial

** Description changed:

  Sometimes every time I log in to Xubuntu 16.04, sometimes every other
  time, the first thing I get are 2 dialogs saying there has been a
  problem and 2 requests for permission to submit a problem report. I
  always give permission, and after I do, everything seems to work fine.
  Every time I've ever looked at the details, I find something that says
  the problem report is damaged and cannot be processed, and refers to an
  invalid core dump with a warning referencing /tmp/apport_core. This has
  been going on for over a year, but doesn't seem to be a common problem,
  since I find only 2 similar bug references. Bugs #1424864 and #1507461
  appear to be giving a similar but not identical error message, and the
  symptoms of neither match mine.
  
- Using instructions from bug #1424864, I tried apport-collect -p xorg
- 1424864, and was told to open another bug report.
+ Using instructions from bug #1424864, I tried apport-collect -p xorg 1424864, 
and was told to open another bug report.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.10
+ Architecture: amd64
+ CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
+ CompositorRunning: None
+ CurrentDesktop: XFCE
+ DistUpgraded: Fresh install
+ DistroCodename: xenial
+ DistroRelease: Ubuntu 16.04
+ DistroVariant: ubuntu
+ DkmsStatus:
+  virtualbox, 5.0.40, 4.4.0-92-generic, x86_64: installed
+  virtualbox, 5.0.40, 4.4.0-93-generic, x86_64: installed
+ GraphicsCard:
+  Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 

[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates

2017-06-26 Thread Kent Lin
** Changed in: oem-priority
   Importance: High => Critical

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

Title:
  No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  New
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions

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


[Touch-packages] [Bug 1690980] Re: No pop-up window to warn users that system should not reboot or shutdown while installing security updates

2017-05-18 Thread Kent Lin
** Also affects: oem-priority/xenial
   Importance: Undecided
   Status: New

** Changed in: oem-priority/xenial
   Importance: Undecided => Critical

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

Title:
  No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  New
Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions

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


[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress

2016-05-30 Thread Kent Lin
** Also affects: network-manager
   Importance: Undecided
   Status: New

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Also affects: oem-priority/xenial
   Importance: Undecided
   Status: New

** Changed in: oem-priority/xenial
   Importance: Undecided => Critical

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  WiFi malfunction after suspend & resume stress

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)   

 
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2

 
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=10 --s3-max-delay=10 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions

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


[Touch-packages] [Bug 1562822] Re: Bluetooth Browse Files... not working

2016-05-15 Thread Kent Lin
** Changed in: oem-priority
   Status: Won't Fix => New

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

Title:
  Bluetooth Browse Files... not working

Status in OEM Priority Project:
  New
Status in indicator-bluetooth package in Ubuntu:
  In Progress
Status in unity-control-center package in Ubuntu:
  In Progress

Bug description:
  * Impact
  The bluetooth settings include a non working "browse files..." items

  * Test case
  connect/pair a phone which does obex, open settings->bluetooth, the only 
action listed should be "send"

  * Regression potential
  none, it's removing a widget which was doing nothing

  --

  Mobile phone: LG L40 Android 4.4.2

  1. Connecting to Phone is successful shown.
  2. Click on Button  "Browse Files... " nothing happen.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160315-0ubuntu1
  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 13:31:39 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2016-02-04 (52 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160204)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1562822/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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: [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy) PIN codes

2016-05-12 Thread Kent Lin
** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Also affects: oem-priority/xenial
   Importance: Undecided
   Status: New

-- 
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:
  [Regresision] 16:04 + 15:10 - Cannot pair with devices using (Legacy)
  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

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 1574347] Re: WiFi network list disappears from network manager applet

2016-05-10 Thread Kent Lin
** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  WiFi network list disappears from network manager applet

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Issue is in Ubuntu 16.04 LTS amd64 version.

  Steps to reproduce: -

  1. Connect to a WiFi AP.
  2. Switch off the AP OR switch off the wifi in the computer.
  3. Switch point (2) back on.
  4. The network will get connected to the AP it was connected to in point (1).

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  
  Temporary Workaround:-
  Log out and again log back in.

  Please solve this issue asap.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.1.93-0ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Apr 24 23:15:34 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-04-23 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IpRoute:
   default via 192.168.1.1 dev wlp18s0  proto static  metric 600 
   169.254.0.0/16 dev wlp18s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp18s0  proto kernel  scope link  src 192.168.1.99  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  
AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE   STATE  ACTIVE-PATH
   Airtel-201  d263b201-9281-427e-94e2-762fa620813c  802-11-wireless  
1461519922  Sunday 24 April 2016 11:15:22 PM IST  yes  0
 no/org/freedesktop/NetworkManager/Settings/0  yes wlp18s0  
activated  /org/freedesktop/NetworkManager/ActiveConnection/8 
   Wired connection 1  142942d4-d247-4880-9bab-1eeafc29ca86  802-3-ethernet   
1461508904  Sunday 24 April 2016 08:11:44 PM IST  yes  4294966297   
 no/org/freedesktop/NetworkManager/Settings/2  no  --   --  
   --
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp18s0  wifi  connected/org/freedesktop/NetworkManager/Devices/1  
Airtel-201  d263b201-9281-427e-94e2-762fa620813c  
/org/freedesktop/NetworkManager/ActiveConnection/8 
   enp19s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
   lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  
--  ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+subscriptions

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


[Touch-packages] [Bug 1550423] Re: ERR_SSL_PROTOCOL_ERROR

2016-02-27 Thread Kent
Similar problem for me.

Chrome Version 45.0.2454.93 (64-bit)
 
lsb_release -a
LSB Version:
core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
Distributor ID: Ubuntu
Description:Ubuntu 14.04.3 LTS
Release:14.04
Codename:   trusty

Sites affected: 
anything Google (mail, maps, search [https://www.google.ca], 
youtube
Presumably because I'm signed in to my Google account on Chrome.

Not affected: 
Netflix

No problems encountered with Chromium Version 48.0.2564.82 Ubuntu 14.04
(64-bit)

Problems first encountered on 26 Feb 2016

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

Title:
  ERR_SSL_PROTOCOL_ERROR

Status in nss package in Ubuntu:
  Incomplete

Bug description:
  After update of ca-certicates chrome give me this error

  SSL connection error

  ERR_SSL_PROTOCOL_ERROR
  Hide details
  Unable to make a secure connection to the server. This may be a problem with 
the server, or it may be requiring a client authentication certificate that you 
don't have.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ca-certificates 20160104ubuntu0.15.10.1
  ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 26 18:16:06 2016
  InstallationDate: Installed on 2014-03-31 (696 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140331)
  PackageArchitecture: all
  SourcePackage: ca-certificates
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  UpgradeStatus: Upgraded to wily on 2015-09-19 (160 days ago)

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

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


[Touch-packages] [Bug 1490937] Re: Unavailable port selected by default

2015-09-01 Thread Kent Lin
** Also affects: pulseaudio
   Importance: Undecided
   Status: New

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  Unavailable port selected by default

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged

Bug description:
  In case one card has only unavailable ports, it might be still be
  selected as default, even though there are available ports on other
  cards.

  E g, on a HTPC which have only Headphone and HDMI outputs, and these
  two outputs are on separate cards, the headphone port might be
  selected even if the HDMI port is available and the headphone port is
  not.

  Probably PulseAudio's routing system needs to be rewritten to be more
  port based to fix this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1490937/+subscriptions

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


[Touch-packages] [Bug 1368063] Re: The photo captured by Camera app show darkness.

2014-09-23 Thread Kent Lin
** Changed in: oem-priority
   Importance: Undecided = High

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

Title:
  The photo captured by Camera app show darkness.

Status in Camera App:
  New
Status in OEM Priority Project:
  New
Status in “camera-app” package in Ubuntu:
  New

Bug description:
  Install Ubuntu 14.04 and boot into OS. 
  Opened Camera app from dash home.Clicked the roundness button to capture 
photos.
  View the photos in /home/pictures.Found the photos show darkness.

  Steps to Reproduce:
  1.Boot into OS.
  2.Opened Camera app from dash home.
  3.Clicked the roundness button to capture photos.
  4.View the photos in /home/pictures.
  5.Found the photos show darkness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/camera-app/+bug/1368063/+subscriptions

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


[Touch-packages] [Bug 1354987] Re: Can not stop wired network via All Setting-Network-Wired on Ubuntu OS

2014-08-10 Thread Kent Lin
** Also affects: oem-priority/trusty
   Importance: Undecided
   Status: New

** Description changed:

- Config an UUT and DASH Ubuntu OS. 
- After DASH pass and go through OOBE to desktop, connect wired network cable 
to the UUT, and then open All Setting-Network-Wired, find that the wired 
network can not be stopped.
+ Install Ubuntu 14.04 on the machine.
+ After installation complete and go through OOBE to desktop, connect wired 
network cable to the UUT, and then open All Setting-Network-Wired, find 
that the wired network can not be stopped.
  
  Please see the attached file for detail.
  
  Note:
  1 .Ubuntu 14.04 LTS
  2. Can start or stop wired network via check or uncheck Enable Networking 
item at the top right corner.
  
  Steps to Reproduce:
- 1.Config an UUT,DASH a Ubuntu OS.
+ 1.Install Ubuntu 14.04 on the machine.
  2.Go through OOBE to desktop.
  3.Connect wired network,try to stop wired network atAll 
Setting-Network-Wired.

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

Title:
  Can not stop wired network via All Setting-Network-Wired on Ubuntu
  OS

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in “network-manager” package in Ubuntu:
  New

Bug description:
  Install Ubuntu 14.04 on the machine.
  After installation complete and go through OOBE to desktop, connect wired 
network cable to the UUT, and then open All Setting-Network-Wired, find 
that the wired network can not be stopped.

  Please see the attached file for detail.

  Note:
  1 .Ubuntu 14.04 LTS
  2. Can start or stop wired network via check or uncheck Enable Networking 
item at the top right corner.

  Steps to Reproduce:
  1.Install Ubuntu 14.04 on the machine.
  2.Go through OOBE to desktop.
  3.Connect wired network,try to stop wired network atAll 
Setting-Network-Wired.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1354987/+subscriptions

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


[Touch-packages] [Bug 1069964] Re: Unable to mount Blank CD-R disc. Location is already mounted.

2014-08-10 Thread Kent Lin
** Changed in: oem-priority
   Importance: Undecided = High

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

Title:
  Unable to mount Blank CD-R disc. Location is already mounted.

Status in OEM Priority Project:
  New
Status in “glib2.0” package in Ubuntu:
  Confirmed
Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+subscriptions

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


[Touch-packages] [Bug 1354987] Re: Can not stop wired network via All Setting-Network-Wired on Ubuntu OS

2014-08-10 Thread Kent Lin
** Changed in: oem-priority
   Importance: Undecided = Medium

** Changed in: oem-priority/trusty
   Importance: Undecided = Medium

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

Title:
  Can not stop wired network via All Setting-Network-Wired on Ubuntu
  OS

Status in OEM Priority Project:
  New
Status in OEM Priority Project trusty series:
  New
Status in “network-manager” package in Ubuntu:
  New

Bug description:
  Install Ubuntu 14.04 on the machine.
  After installation complete and go through OOBE to desktop, connect wired 
network cable to the UUT, and then open All Setting-Network-Wired, find 
that the wired network can not be stopped.

  Please see the attached file for detail.

  Note:
  1 .Ubuntu 14.04 LTS
  2. Can start or stop wired network via check or uncheck Enable Networking 
item at the top right corner.

  Steps to Reproduce:
  1.Install Ubuntu 14.04 on the machine.
  2.Go through OOBE to desktop.
  3.Connect wired network,try to stop wired network atAll 
Setting-Network-Wired.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1354987/+subscriptions

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