date:20180212

** Changed in: ubuntu-themes
   Status: New => Confirmed

** Changed in: ubuntu-themes
   Importance: Undecided => Medium

** Changed in: ubuntu-themes (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Window buttons lack padding when scale is set to 200%

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Padding is small and often inconsistent, see screen-shot attached.

  Ubuntu 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1738762/+subscriptions

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

[Touch-packages] [Bug 1738762] Re: Window buttons lack padding when scale is set to 200%

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Confirmed

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

Title:
  Window buttons lack padding when scale is set to 200%

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Padding is small and often inconsistent, see screen-shot attached.

  Ubuntu 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1738762/+subscriptions

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

[Touch-packages] [Bug 1738762] Re: Window buttons lack padding when scale is set to 200%

** Summary changed:

- Window controls padding when scale is set to 200%
+ Window buttons lack padding when scale is set to 200%

** Tags added: visual-quality

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

Title:
  Window buttons lack padding when scale is set to 200%

Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  Padding is small and often inconsistent, see screen-shot attached.

  Ubuntu 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1738762/+subscriptions

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

[Touch-packages] [Bug 1740441] Re: Tag borders in nautilus search bar are truncated

** Summary changed:

- Tag borders in search bar looks halfway
+ Tag borders in nautilus search bar are truncated

** Also affects: nautilus (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Tag borders in nautilus search bar are truncated

Status in Ubuntu theme:
  New
Status in nautilus package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  
  ubuntu 17.10

  Nautilus search bar

  SS: https://i.hizliresim.com/rJWBP7.png

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1740441/+subscriptions

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

[Touch-packages] [Bug 1749075] Re: ubuntu light-theme doesn't correctly decorate menubar for widgets that are maximized

Can you please provide a screenshot or photo of the problem you're
describing?

** Changed in: ubuntu-themes (Ubuntu)
   Status: New => Incomplete

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

Title:
  ubuntu light-theme doesn't correctly decorate menubar for widgets that
  are maximized

Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  OS: Ubuntu 18.04

  light-themes includes Ambiance & Radiance, when opening a widget that
  contains menu toolbar (with global-menu disabled), the background
  color of menu toolbar only keeps coordinate with titlebar when the
  widget is not maximized. Once the widget is maximized, the background
  color of its menu toolbar becomes different which is ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Feb 13 14:02:20 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749075] [NEW] ubuntu light-theme doesn't correctly decorate menubar for widgets that are maximized

2018-02-12 Thread Cui Wei

Public bug reported:

OS: Ubuntu 18.04

light-themes includes Ambiance & Radiance, when opening a widget that
contains menu toolbar (with global-menu disabled), the background color
of menu toolbar only keeps coordinate with titlebar when the widget is
not maximized. Once the widget is maximized, the background color of its
menu toolbar becomes different which is ugly.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Feb 13 14:02:20 2018
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-themes (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  ubuntu light-theme doesn't correctly decorate menubar for widgets that
  are maximized

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  OS: Ubuntu 18.04

  light-themes includes Ambiance & Radiance, when opening a widget that
  contains menu toolbar (with global-menu disabled), the background
  color of menu toolbar only keeps coordinate with titlebar when the
  widget is not maximized. Once the widget is maximized, the background
  color of its menu toolbar becomes different which is ugly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180122.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Feb 13 14:02:20 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail

Being a HWE problem, and not completely patchable, it sounds like we may
have to consider a major upgrade of bluez to xenial. Assuming we can
avoid ABI/API breaks...

I don't think we want to do it, but if it comes to that then we may have
to.

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

Title:
Bluetooth LE pairing fail

Status in OEM Priority Project:
Confirmed
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Xenial:
Fix Committed

Bug description:
[Impact]

When the Bluetooth adapter is not powered on it is not possible to use
it in normal way. We used to have a hack to force powering on by using
an udev rule but this doe snot work anymore. Luckily the BlueZ has
introduced "AutoEnable" option that makes the stack power on adapters by
itself.

Backporting this to xenial will improve life of the desktop users and
will not require them to hack the solution on their own. The fix itself
uses the well known solution to this problem that is floating around
there for a while.

The upload fixes the bug by enabling the 'AutoEnable' option in the
bluetoothd config file.

[Original Report]

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

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

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

here is a commit with this parameter:
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

[Test Case]

On xenial install from ppa:
https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

Now reboot the machine. The BT adapter shall be
powered on.

[Regression Potential]

If things go wrong the adapter will not be powered on after the system
boots up. Therefore while testing please focus on the adapter state,
i.e. powered on or off.

[Other Info]

This fix is included in the development release, see:
http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

[What to upload]

For xenial as in:

) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
)
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

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

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

[Touch-packages] [Bug 1749072] [NEW] nm-applet from network-manager-gnome doesn't get fully translated into zh_CN.UTF-8

2018-02-12 Thread Cui Wei

Public bug reported:

For example:

Edit connections...
Create...
Add a VPN connection...
Additional static addresses:

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: language-pack-gnome-zh-hans 1:18.04+20180208
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Feb 13 13:08:59 2018
PackageArchitecture: all
SourcePackage: language-pack-gnome-zh-hans
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: language-pack-gnome-zh-hans (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to language-pack-gnome-zh-
hans in Ubuntu.
https://bugs.launchpad.net/bugs/1749072

Title:
  nm-applet from network-manager-gnome doesn't get fully translated into
  zh_CN.UTF-8

Status in language-pack-gnome-zh-hans package in Ubuntu:
  New

Bug description:
  For example:

  Edit connections...
  Create...
  Add a VPN connection...
  Additional static addresses:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: language-pack-gnome-zh-hans 1:18.04+20180208
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Feb 13 13:08:59 2018
  PackageArchitecture: all
  SourcePackage: language-pack-gnome-zh-hans
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-zh-hans/+bug/1749072/+subscriptions

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

[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail

2018-02-12 Thread Cyrus Lien

With bluez 5.37-0ubuntu5.2 Designer keyboard still can not connect on
4.13.0-32-generic.

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

Title:
Bluetooth LE pairing fail

Status in OEM Priority Project:
Confirmed
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Xenial:
Fix Committed

Bug description:
[Impact]

The upload fixes the bug by enabling the 'AutoEnable' option in the
bluetoothd config file.

[Original Report]

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

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

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

here is a commit with this parameter:
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

[Test Case]

On xenial install from ppa:
https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

Now reboot the machine. The BT adapter shall be
powered on.

[Regression Potential]

If things go wrong the adapter will not be powered on after the system
boots up. Therefore while testing please focus on the adapter state,
i.e. powered on or off.

[Other Info]

This fix is included in the development release, see:
http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

[What to upload]

For xenial as in:

) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
)
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

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

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

[Touch-packages] [Bug 1510570] Re: Bluetooth LE pairing fail

2018-02-12 Thread Cyrus Lien

Designer keyboard still can not connect on 4.13.0-32-generic.

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

Title:
Bluetooth LE pairing fail

Status in OEM Priority Project:
Confirmed
Status in bluez package in Ubuntu:
Fix Released
Status in bluez source package in Xenial:
Fix Committed

Bug description:
[Impact]

The upload fixes the bug by enabling the 'AutoEnable' option in the
bluetoothd config file.

[Original Report]

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

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

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

here is a commit with this parameter:
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

[Test Case]

On xenial install from ppa:
https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

Now reboot the machine. The BT adapter shall be
powered on.

[Regression Potential]

If things go wrong the adapter will not be powered on after the system
boots up. Therefore while testing please focus on the adapter state,
i.e. powered on or off.

[Other Info]

This fix is included in the development release, see:
http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

[What to upload]

For xenial as in:

) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
)
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

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

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

[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-12 Thread Yuriy Vidineev

Kai-Heng Feng, yes

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1718487] Re: package dnsmasq-base 2.75-1ubuntu0.16.04.1 failed to install/upgrade: пакет dnsmasq-base не готов к настройке настройка невозможна (текущее состояние: «half-install

[Expired for dnsmasq (Ubuntu) because there has been no activity for 60
days.]

** Changed in: dnsmasq (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package dnsmasq-base 2.75-1ubuntu0.16.04.1 failed to install/upgrade:
  пакет dnsmasq-base не готов к настройке  настройка невозможна (текущее
  состояние: «half-installed»)

Status in dnsmasq package in Ubuntu:
  Expired

Bug description:
  LTS 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dnsmasq-base 2.75-1ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Wed Sep 20 15:09:22 2017
  ErrorMessage: пакет dnsmasq-base не готов к настройке  настройка невозможна 
(текущее состояние: «half-installed»)
  InstallationDate: Installed on 2016-09-22 (362 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: dnsmasq
  Title: package dnsmasq-base 2.75-1ubuntu0.16.04.1 failed to install/upgrade: 
пакет dnsmasq-base не готов к настройке  настройка невозможна (текущее 
состояние: «half-installed»)
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1611945] Re: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks

2018-02-12 Thread WinEunuchs2Unix

I'm not sure of the ramifications of these error messages but I can
confirm they are still there.

On Mon, Feb 12, 2018 at 8:35 AM, Norman Henderson  wrote:
> Ladies and Gentlemen, The technical stuff is way over my head but I am
> getting the same syslog errors and the same inconsistent device paths on
> an HP Proliant ML110 G7 with Ubuntu 16.04.3 kernel 4.4.0-98-generic.
>
> It seems clear that no-one is taking ownership of this to fix it in an
> actual update that ordinary people like me can install in the normal
> course of system updates. The nature of open source software I guess.
>
> However could someone please let me know:
>  - is this just an annoying message that won't be fixed, or are there 
> operational implications?
>  - if there are implications, are they serious?
>  - if they are serious, could you explain (or point me at a resource that 
> explains) in detail, how to install the patch provided. I've never done that 
> before.
>
> Thank you in advance!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1611945
>
> Title:
>   /dev/disk/by-path not properly populated for (e)SATA port multiplier
>   disks
>
> Status in systemd package in Ubuntu:
>   Confirmed
>
> Bug description:
>   We have a just-installed Ubuntu 16.04 LTS machine with a number of
>   disks behind port-multiplier eSATA ports, all of them driven by a SiI
>   3124 controller (sata_sil24 kernel driver). Our machine sees all disks
>   on all channels, however under 16.04 only one disk from each channel
>   shows up in /dev/disk/by-path/ (all disks show up in /dev/disk/by-id
>   and /dev/disk/by-uuid). For our usage this is a severe defect because
>   we rotate disks in and out of the external enclosure and rely on
>   mounting specific slots in the external enclosure through /dev/disk
>   /by-path.
>
>   This did not happen in Ubuntu 12.04 LTS, the release that this machine
>   was previously running.
>
>   According to 'udevadm info --export-db' and 'udevadm test-builtin
>   path_id' and so on, systemd's udev stuff is assigning all drives
>   behind the same port the same disk/by-path data (ID_PATH et al). In
>   'udevadm info /sys/block/sdX', the 'P:' and 'E: DEVPATH=' values show
>   a difference in the target portion of PCI path, eg:
>
> P: 
> /devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
> P: 
> /devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:1:0/0:1:0:0/block/sdb
>
>   However the 'S: disk/by-path', 'E: DEVLINKS=', and 'E: ID_PATH'
>   portions do not. For both devices above, we see:
>
> S: disk/by-path/pci-:02:00.0-ata-1
> E: ID_PATH=pci-:02:00.0-ata-1
>
>   Naturally only one device can have a /dev/disk/by-
>   path/pci-:02:00.0-ata-1 symlink, so instead of four disks per
>   channel in /dev/disk/by-path we see one.
>
>   Ubuntu release: 16.04
>
>   Package versions from 'apt-cache policy udev systemd':
>   udev:
> Installed: 229-4ubuntu7
>   systemd:
> Installed: 229-4ubuntu7
>
>   'journalctl -b' reports that during boot systemd does report some
>   'appeared twice with different sysfs paths' notes, eg:
>
>   Aug 10 13:34:21 verdandi systemd[1]: dev-disk-by\x2dpath-
>   pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device: Dev dev-disk-by
>   \x2dpath-pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device appeared
>   twice with different sysfs paths
>   
> /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:3:0/0:3:0:0/block/sdd/sdd1
>   and
>   
> /sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1
>
>   However it doesn't seem to be reporting this for all port-multiplier
>   drives and their partitions.
>
>   If it would be useful I can attach full 'udevadm info --export-db'
>   output or the like.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1611945/+subscriptions

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

Title:
  /dev/disk/by-path not properly populated for (e)SATA port multiplier
  disks

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  We have a just-installed Ubuntu 16.04 LTS machine with a number of
  disks behind port-multiplier eSATA ports, all of them driven by a SiI
  3124 controller (sata_sil24 kernel driver). Our machine sees all disks
  on all channels, however under 16.04 only one disk from each channel
  shows up in /dev/disk/by-path/ (all disks show up in /dev/disk/by-id
  and /dev/disk/by-uuid). For our usage this is a severe defect because
  we rotate disks in and out of the external enclosure and rely on
  mounting specific slots in the external enclosure through /dev/disk
  /by-path.

[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-12 Thread Kai-Heng Feng

Is this 100% reproducible?

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1748620] Re: PulseAudio can not remember my settings between reboots

Oh I think I can guess what the problem is. Any settings remembered by
the GUI/daemon/session may get overridden by this in
/etc/pulse/default.pa:

### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794)
.ifexists module-switch-on-connect.so
load-module module-switch-on-connect
.endif 

If you remove that load-module line then it might do what you want.
Please try it.

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Incomplete

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- PulseAudio can not remember my settings between reboots 
+ PulseAudio always prefers USB mic over the internal mic

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

Title:
  PulseAudio always prefers USB mic over the internal mic

Status in gnome-control-center package in Ubuntu:
  Incomplete
Status in gnome-settings-daemon package in Ubuntu:
  Incomplete
Status in mate-control-center package in Ubuntu:
  Incomplete
Status in mate-settings-daemon package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Pulseaudio can not remember my settings between reboots. I have a usb mic 
named WUP-021-0 Analog Mono and i use for output Built-in Audio Analog Stereo. 
But every time i open my pc or reboot it my output setings will default to my 
mic WUP-021-0 Analog Mono.
  Tested in ubuntu 18.04 daily

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  apolihron   1590 F pulseaudio
   /dev/snd/controlC0:  apolihron   1590 F pulseaudio
   /dev/snd/controlC2:  apolihron   1590 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Feb 10 15:34:51 2018
  InstallationDate: Installed on 2018-02-10 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180210)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A88M-G/3.1
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1748620/+subscriptions

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

[Touch-packages] [Bug 1748828] Re: Bluetooth states off in systray while on

This sounds like bug 1738838. Please have a look at the video there and
tell us if you agree.

** Package changed: bluez (Ubuntu) => gnome-shell (Ubuntu)

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  Bluetooth states off in systray while on

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  The bluetooth indicator suggest that bluetooth is disabled (turned
  off) while this is not the case. See screenshot 1. Only after opening
  the bluetooth toggle, you can see the actual correct action: turn off.
  See screenshot 2.

  As far as I can remember, this behaviour has been introduced on 17.10.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748828/+subscriptions

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

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

** Branch linked: lp:~juliank/apport/lp1746874

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files). This issue was first mentioned in bug 1746653. But
  then I noticed my machine doing it too...

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1725921] Re: [regression] Combobox has gray text on gray background

This bug is a simple regression. So you can also work around it by
taking one step back. Just install:

https://launchpad.net/ubuntu/+archive/primary/+files/light-
themes_14.04+16.04.20160415-0ubuntu1_all.deb

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

Title:
  [regression] Combobox has gray text on gray background

Status in Ubuntu theme:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  See pictures.

  Application: pcbnew
  Version: no-vcs-found-0b1eb56~60~ubuntu17.04.1, release build
  Libraries:
  wxWidgets 3.0.3
  libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 
(+libidn2/2.0.2) librtmp/2.3
  Platform: Linux 4.13.0-16-generic x86_64, 64 bit, Little endian, wxGTK
  Build Info:
  wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
  Boost: 1.62.0
  Curl: 7.52.1
  Compiler: GCC 6.3.0 with C++ ABI 1010

  Build settings:
  USE_WX_GRAPHICS_CONTEXT=OFF
  USE_WX_OVERLAY=OFF
  KICAD_SCRIPTING=ON
  KICAD_SCRIPTING_MODULES=ON
  KICAD_SCRIPTING_WXPYTHON=ON
  KICAD_SCRIPTING_ACTION_MENU=ON
  BUILD_GITHUB_PLUGIN=ON
  KICAD_USE_OCE=ON
  KICAD_SPICE=ON

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1725921/+subscriptions

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

[Touch-packages] [Bug 1336663] Re: lightdm uses wrong ccache name on pam_krb5 credentials refresh

2018-02-12 Thread Russ Allbery

Yes, if KRB5CCNAME were set in the environment of the screen saver, it
would fix this problem.

To be clear, this isn't a bug in libpam-krb5, but in the means by which
the screen saver is launched without the user's environment set properly
(which should be created via the pam_setcred and pam_open_session steps
of the PAM call sequence, and the new user environment generated by
PAM).  Without KRB5CCNAME, there's no way for the PAM module to find the
user's ticket cache to renew it on subsequent unlocks; somehow, it does
need that information conveyed to it.

You can work around this by using a predictable ticket cache name that
embeds only the user's UID and setting that as the default ticket cache
(in various ways -- PAM configuration, Kerberos configuration, etc.).
But this isn't a general solution that can be adapted by the package
because it means every user session for the same user uses the same
Kerberos ticket cache, which means that, say, logging on to the system
via ssh and then logging out will delete the ticket cache underneath the
local console login.

** Changed in: libpam-krb5 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  lightdm uses wrong ccache name on pam_krb5 credentials refresh

Status in gdm:
  New
Status in Light Display Manager:
  Triaged
Status in libpam-krb5 package in Ubuntu:
  Invalid
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  As already noted by Brian Knoll in 
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1296276/comments/24
  lightdm 1.10.1-0ubuntu1 uses an inappropriate credentials cache, 
/tmp/krb5cc_0, when refreshing Kerberos credentials on screen unlock.

  I couldn't find the new bug Robert Ancell called for in
  https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1296276/comments/27
  so I'm opening one now.

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

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

[Touch-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

Michael von Glasow:

1) To clarify, did this issue start to happen after an update? If so,
which specifically?

2) Does this issue happen if you don't have any external displays, and
the laptop is not docked?

3) Regarding the internal laptop display going black for a few seconds,
how often does this occur per hour, day, etc.?

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Occasionally, the internal laptop display goes black for a few
  seconds, then comes back to life. The external display stays on. It
  looks as if power management were kicking in by error but affecting
  only the internal display.

  When I’m working with the external display, I need to move the mouse
  into the area managed by the internal display to wake it up again;
  else it seems to remain black (though I haven’t tested that behavior
  thoroughly).

  Most tests with the external display were made with the port
  replicator and an external display plugged into one of the DP ports
  via a DP–DVI adapter. I cannot tell for sure what the behavior is with
  the external display plugged directly into the laptop.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2014-12-09 (1158 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: CNU407CM0V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

** Tags removed: apport bios-outdated-1.42-collected
** Tags added: apport-collected bios-outdated-1.42

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Occasionally, the internal laptop display goes black for a few
  seconds, then comes back to life. The external display stays on. It
  looks as if power management were kicking in by error but affecting
  only the internal display.

  When I’m working with the external display, I need to move the mouse
  into the area managed by the internal display to wake it up again;
  else it seems to remain black (though I haven’t tested that behavior
  thoroughly).

  Most tests with the external display were made with the port
  replicator and an external display plugged into one of the DP ports
  via a DP–DVI adapter. I cannot tell for sure what the behavior is with
  the external display plugged directly into the laptop.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2014-12-09 (1158 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: CNU407CM0V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1748729] Re: Xorg freeze

BertN45:

1)
>"I kept the guests at 5.2.4"

To clarify, using a host with 5.2.6, if you use the Oracle guest
additions from version 5.2.4 this problem is not reproducible in Ubuntu
GNOME?

2)
>" I filed a bug report with Oracle"

Did you file a bug report with Oracle regarding the scope of this
report? If so, could you please provide the URL?

3)
>"Today I also tried the 'beta' version of 5.2.7 with Ubuntu 18.04"

To clarify, you have 5.2.7 on a Ubuntu 18.04 host, and then install the
5.2.7 guest additions in Ubuntu GNOME 18.04?

4)
>"That package had not been installed, but after installing that package"

To advise, you wouldn't have both the Oracle Guest Additions installed
and then install this package. If you did this, that will cause this
issue. virtualbox-guest-x11 is the guest additions that is made for
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/1748729

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Host: Ubuntu 18.04, Virtualbox 5.2.6
  Guest: Ubuntu GNOME 17.10 and 18.04

  The problem is the guest's screen almost freezes completely as soon as
  I maximise any window in the guest. Any mouse click takes 10-60
  seconds before the system reacts to it.

  Windows 7 and 10 work without any problem.

  WORKAROUND: Disable 3D acceleration.

  WORKAROUND: Use as a guest Ubuntu Mate or Xubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 06:31:52 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-12-22 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1748729] Re: Xorg freeze

** Description changed:

- I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the 
propriety Nvidia driver 340 as suggested by Ubuntu.
- The screen almost freezes completely as soon as I maximise any window in the 
guest OS Ubuntu 18.04. Any mouse click takes 10-60 seconds before the system 
reacts to it. It took a long time to generate this bug-report.
+ Host: Ubuntu 18.04, Virtualbox 5.2.6
+ Guest: Ubuntu GNOME 17.10 and 18.04
  
- I had the same problem with Ubuntu 17.10, while Guest OSes Ubuntu Mate
- 17.10, Xubuntu 17.10, and Peppermint 8. Windows 7 and 10 work without
- any problem.
+ The problem is the guest's screen almost freezes completely as soon as I
+ maximise any window in the guest. Any mouse click takes 10-60 seconds
+ before the system reacts to it.
+ 
+ Windows 7 and 10 work without any problem.
  
  WORKAROUND: Disable 3D acceleration.
+ 
+ WORKAROUND: Use as a guest Ubuntu Mate or Xubuntu.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 06:31:52 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-12-22 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Host: Ubuntu 18.04, Virtualbox 5.2.6
  Guest: Ubuntu GNOME 17.10 and 18.04

  The problem is the guest's screen almost freezes completely as soon as
  I maximise any window in the guest. Any mouse click takes 10-60
  seconds before the system reacts to it.

  Windows 7 and 10 work without any problem.

  WORKAROUND: Disable 3D acceleration.

  WORKAROUND: Use as a guest Ubuntu Mate or Xubuntu.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 06:31:52 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-12-22 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001

[Touch-packages] [Bug 1749036] Re: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has multiple installed in

2018-02-12 Thread Theodore Ts'o

Note that libcomerr2 has been renamed to libcom-err2 to conform with
Debian's packaging naming guidelines.   So libcomerr2 is now a
transitional package (arch=all) where previously it was a binary
package.

Why this is failing on Ubuntu is a complete mystery to me.  On Debian
Unstable, using "apt-get update --with-new-pkgs" it Just Works For
Me.

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

Title:
  package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all
  1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which
  has multiple installed instances

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  This happened during a partial upgrade of Bionic.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libcomerr2 1.43.8-2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Mon Feb 12 15:51:57 2018
  Dependencies:
   gcc-7-base 7.2.0-18ubuntu2
   libc6 2.26-0ubuntu2
   libgcc1 1:7.2.0-18ubuntu2
  DpkgTerminalLog:
   Preparing to unpack .../comerr-dev_2.1-1.43.9-1_amd64.deb ...
   Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack):
libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with 
libcomerr2 which has multiple installed instances
  DuplicateSignature:
   package:libcomerr2:1.43.8-2
   Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack):
libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with 
libcomerr2 which has multiple installed instances
  ErrorMessage: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable 
with libcomerr2 which has multiple installed instances
  InstallationDate: Installed on 2013-01-16 (1853 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: e2fsprogs
  Title: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 
1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has 
multiple installed instances
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 541970] Re: keymap.get_entries_for_keyval returns None when run inside an freenx nxserver

** Changed in: libgtk
   Status: New => Expired

** Changed in: pygtk
   Status: New => Expired

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

Title:
  keymap.get_entries_for_keyval returns None when run inside an freenx
  nxserver

Status in FreeNX Server:
  New
Status in LibGTK:
  Expired
Status in PyGTK:
  Expired
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Description:  Ubuntu 9.10
  Release:  9.10

  python-gtk2 2.16.0-0ubuntu1
  freenx-server: 0.7.3+teambzr104-0ubuntu1~karmic1

  michael@frigg:~$ python
  Python 2.6.4 (r264:75706, Dec  7 2009, 18:45:15)
  [GCC 4.4.1] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import gtk
  Xlib:  extension "Generic Event Extension" missing on display ":1000.0".
  Xlib:  extension "Generic Event Extension" missing on display ":1000.0".
  Xlib:  extension "Generic Event Extension" missing on display ":1000.0".
  Xlib:  extension "Generic Event Extension" missing on display ":1000.0".
  Xlib:  extension "Generic Event Extension" missing on display ":1000.0".
  >>> keymap = gtk.gdk.keymap_get_default()
  >>> print gtk.keysyms.Insert, 
keymap.get_entries_for_keyval(gtk.keysyms.Insert)
  65379 None
  >>>

  This may be an freenx bug, this may be a gtk or pygtk bug... This is
  when running an X session with freenx-server and connecting remotely.
  If I ssh to the machine, export my display to :0 (even though the
  machine is in a headless vm) and run the same test, it returns a
  proper value. I'm filing the bug under pygtk since that's the highest
  level package I can think of. This is causing gajim (as of the latest
  development versions) to crash on startup, with the traceback pointing
  to the keymap.get_entries_for_keyval command.

  Those Xlib warnings are because the freenx-server does not support the
  XGE extension.

To manage notifications about this bug go to:
https://bugs.launchpad.net/freenx-server/+bug/541970/+subscriptions

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

[Touch-packages] [Bug 1738581] Re: apport is leaking environment variables (including passwords!) to public bug reports

** Branch linked: lp:~ubuntu-core-dev/ubuntu/bionic/apport/ubuntu

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

Title:
  apport is leaking environment variables  (including passwords!) to
  public bug reports

Status in apport package in Ubuntu:
  In Progress

Bug description:
  See the bug report 
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1738564
  created with ubuntu-bug.

  Apport includes the file JournalErrors.txt
  This file includes e.g. the following line.
  Dez 16 19:11:31 hostname /usr/lib/gdm3/gdm-x-session[9679]: 
dbus-update-activation-environment: setting 
MPD_HOST=...@.xxx.org

  
  Normally it would be not problem that gdm-x-session write this to the 
journal, because the journal is not intended to be published on the internet. 

  Setting confidential informations via environment is maybe not the
  best idea, but a legal procedure and for `mpc` the only way to set
  this information.

  IMHO the apport utility is here the problem, because it includes the
  file with risky information to a public visible bug report.

  
  Note: I manually delete the attachment in the mentioned bug report. But how 
can I sure that a web crawlser hasn't read/preserved that attachment?

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

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

[Touch-packages] [Bug 1738581] Re: apport is leaking environment variables (including passwords!) to public bug reports

** Changed in: apport (Ubuntu)
   Status: New => In Progress

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: apport (Ubuntu)
   Importance: Undecided => High

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

Title:
  apport is leaking environment variables  (including passwords!) to
  public bug reports

Status in apport package in Ubuntu:
  In Progress

Bug description:
  See the bug report 
https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1738564
  created with ubuntu-bug.

  Apport includes the file JournalErrors.txt
  This file includes e.g. the following line.
  Dez 16 19:11:31 hostname /usr/lib/gdm3/gdm-x-session[9679]: 
dbus-update-activation-environment: setting 
MPD_HOST=...@.xxx.org

  
  Normally it would be not problem that gdm-x-session write this to the 
journal, because the journal is not intended to be published on the internet. 

  Setting confidential informations via environment is maybe not the
  best idea, but a legal procedure and for `mpc` the only way to set
  this information.

  IMHO the apport utility is here the problem, because it includes the
  file with risky information to a public visible bug report.

  
  Note: I manually delete the attachment in the mentioned bug report. But how 
can I sure that a web crawlser hasn't read/preserved that attachment?

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

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

[Touch-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

2018-02-12 Thread Michael von Glasow

Well, that didn’t take long: screen just went black again for somewhere
around a second. Let me know if you need further input from me.

BTW: currently working without a dock, with an external screen attached
via DP (which has also experienced the bug before the update)—so the
dock doesn’t make a difference.

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Occasionally, the internal laptop display goes black for a few
  seconds, then comes back to life. The external display stays on. It
  looks as if power management were kicking in by error but affecting
  only the internal display.

  When I’m working with the external display, I need to move the mouse
  into the area managed by the internal display to wake it up again;
  else it seems to remain black (though I haven’t tested that behavior
  thoroughly).

  Most tests with the external display were made with the port
  replicator and an external display plugged into one of the DP ports
  via a DP–DVI adapter. I cannot tell for sure what the behavior is with
  the external display plugged directly into the laptop.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2014-12-09 (1158 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: CNU407CM0V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

2018-02-12 Thread William Maddox

I experienced this problem when doing a *clean installation* of Ubuntu
GNOME 16.04.3.  I confirmed that the synaptics driver was in use.  apt-
get update; apt-get upgrade did not resolve the problem.

I was able to get the touchpad settings working by uninstalling the
synaptics driver and installing libinput.  I had to upgrade a held-back
dependency in order to do this, and I'm not sure if the result was
entirely kosher.

It seems like a clean installation should not have this problem, nor is
it clear to me how the synaptics support got dropped in Ubuntu GNOME
16.04.3 when the upstream version affected was 3.20, and 16.04.3 is
still documented as including GNOME 3.18.  I can understand how these
kinds of issues can occur in an upgrade to a new major version such as
17.10, but it's really a big boo-boo to have this sort of breakage in
the routine updates to an LTS release.  It would at least be helpful to
mention this issue in the release notes for UG 16.04.3.

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in xorg source package in Artful:
  Confirmed
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+subscriptions

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

[Touch-packages] [Bug 1749000] Re: [patch] please add "AssumedApparmorLabel=unconfined" to service file

2018-02-12 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  [patch] please add "AssumedApparmorLabel=unconfined" to service file

Status in systemd package in Ubuntu:
  New

Bug description:
  There was a recent change in apparmor
  (https://cgit.freedesktop.org/dbus/dbus/commit/?id=dc25979eb) that
  breaks snapd. The fix is simply to add the
  ++AssumedApparmorLabel=unconfined line to the service file so that
  activation works again.

  Attached is a debdiff with a possible fix.

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

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

[Touch-packages] [Bug 1748729] Re: Xorg freeze

2018-02-12 Thread BertN45

1. The host is using 5.2.6. I kept the guests at 5.2.4, because 5.2.6
did freeze during login or did enter a login loop dependent on the
distro. I filed a bug report with Oracle and many persons had the same
issue during login. The beta version 5.2.7 did solve the 5.2.6 login
issues.

Today I also tried the 'beta' version of 5.2.7 with Ubuntu 18.04 with
respect to maximising the window, but without success.

2. I did keep Guest additions 5.2.4 installed for all distros, but I do
not remember how 5.2.2 behaved. Probably I was still using Ubuntu 16.04
for both host and guest during that time.

3. I only have the window maximising problem with Ubuntu Gnome 17.10 and
18.04, but NOT with Ubuntu Mate 17.10; Xubuntu 17.10; Peppermint 8 nor
with Linux Mint 18.3.

4; That package had not been installed, but after installing that
package and 1 or 2 dependencies, the system hung during reboot directly
after starting the Gnome Display Manager. It looks like the bug of point
1 had been re-introduced, but now for both 3D enabled and 3D disabled. I
will try to remove the package again through ctrl+alt+F2 or restore a
back-up.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the 
propriety Nvidia driver 340 as suggested by Ubuntu.
  The screen almost freezes completely as soon as I maximise any window in the 
guest OS Ubuntu 18.04. Any mouse click takes 10-60 seconds before the system 
reacts to it. It took a long time to generate this bug-report.

  I had the same problem with Ubuntu 17.10, while Guest OSes Ubuntu Mate
  17.10, Xubuntu 17.10, and Peppermint 8. Windows 7 and 10 work without
  any problem.

  WORKAROUND: Disable 3D acceleration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 06:31:52 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-12-22 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1749036] Re: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has multiple installed in

2018-02-12 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all
  1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which
  has multiple installed instances

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  This happened during a partial upgrade of Bionic.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libcomerr2 1.43.8-2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Mon Feb 12 15:51:57 2018
  Dependencies:
   gcc-7-base 7.2.0-18ubuntu2
   libc6 2.26-0ubuntu2
   libgcc1 1:7.2.0-18ubuntu2
  DpkgTerminalLog:
   Preparing to unpack .../comerr-dev_2.1-1.43.9-1_amd64.deb ...
   Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack):
libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with 
libcomerr2 which has multiple installed instances
  DuplicateSignature:
   package:libcomerr2:1.43.8-2
   Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack):
libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with 
libcomerr2 which has multiple installed instances
  ErrorMessage: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable 
with libcomerr2 which has multiple installed instances
  InstallationDate: Installed on 2013-01-16 (1853 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: e2fsprogs
  Title: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 
1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has 
multiple installed instances
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749036] [NEW] package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has multiple installed

Public bug reported:

This happened during a partial upgrade of Bionic.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libcomerr2 1.43.8-2
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
Date: Mon Feb 12 15:51:57 2018
Dependencies:
 gcc-7-base 7.2.0-18ubuntu2
 libc6 2.26-0ubuntu2
 libgcc1 1:7.2.0-18ubuntu2
DpkgTerminalLog:
 Preparing to unpack .../comerr-dev_2.1-1.43.9-1_amd64.deb ...
 Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack):
  libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with 
libcomerr2 which has multiple installed instances
DuplicateSignature:
 package:libcomerr2:1.43.8-2
 Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack):
  libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with 
libcomerr2 which has multiple installed instances
ErrorMessage: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable 
with libcomerr2 which has multiple installed instances
InstallationDate: Installed on 2013-01-16 (1853 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu1
 apt  1.6~alpha7ubuntu1
SourcePackage: e2fsprogs
Title: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 
1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has 
multiple installed instances
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all
  1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which
  has multiple installed instances

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  This happened during a partial upgrade of Bionic.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libcomerr2 1.43.8-2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Mon Feb 12 15:51:57 2018
  Dependencies:
   gcc-7-base 7.2.0-18ubuntu2
   libc6 2.26-0ubuntu2
   libgcc1 1:7.2.0-18ubuntu2
  DpkgTerminalLog:
   Preparing to unpack .../comerr-dev_2.1-1.43.9-1_amd64.deb ...
   Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack):
libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with 
libcomerr2 which has multiple installed instances
  DuplicateSignature:
   package:libcomerr2:1.43.8-2
   Unpacking comerr-dev:amd64 (2.1-1.43.9-1) over (2.1-1.43.8-2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcomerr2_1.43.9-1_all.deb (--unpack):
libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable with 
libcomerr2 which has multiple installed instances
  ErrorMessage: libcomerr2:all 1.43.9-1 (Multi-Arch: no) is not co-installable 
with libcomerr2 which has multiple installed instances
  InstallationDate: Installed on 2013-01-16 (1853 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~alpha7ubuntu1
  SourcePackage: e2fsprogs
  Title: package libcomerr2 1.43.8-2 failed to install/upgrade: libcomerr2:all 
1.43.9-1 (Multi-Arch: no) is not co-installable with libcomerr2 which has 
multiple installed instances
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session

** Changed in: mutter
   Importance: High => Critical

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

Title:
  VA-API fails to initialize in a Gnome Shell Wayland session

Status in Libva:
  New
Status in Mutter:
  Confirmed
Status in Totem:
  Confirmed
Status in VLC media player:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Won't Fix
Status in libva package in Ubuntu:
  Triaged
Status in mpv package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and
  Gnome Shell). But it refuses to load when in a Wayland session:

  $ totem bbb_sunflower_1080p_60fps_normal.mp4
  libva error: va_getDriverName() failed with unknown libva 
error,driver_name=(null)

  $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4
  totem: intel_driver.c:112: intel_driver_init: Assertion 
`VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, 
VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed.
  Aborted (core dumped)

  $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4
  Press 'k' to see a list of keyboard shortcuts.
  Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  Redistribute latency...
  Redistribute latency...
  ERROR Internal error: could not render surface for 
file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4
  ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): 
gst_vaapisink_show_frame_unlocked (): 
/GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0

  WORKAROUNDS:

   * Use weston instead of gnome-shell; or
   * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463
   * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 
1701463
   * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ...
   * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: i965-va-driver 1.8.1-1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 13:40:38 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: intel-vaapi-driver
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1706070] Re: Xorg crash

João Gabriel, thanks for the response.

To advise, you may monitor the progress towards this issue via a live
environment of http://cdimage.ubuntu.com/daily-live/current/ that won't
disrupt your Windows install. The results of this test will help
determine if this is resolved in Ubuntu already.

** Summary changed:

- Xorg crash
+ [HP Pavilion x360 - 13-s104br] Xorg crash

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

Title:
  [HP Pavilion x360 - 13-s104br] Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu crashed and returned to login screen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jul 24 10:01:47 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80d1]
  InstallationDate: Installed on 2017-03-18 (127 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: HP HP Pavilion x360 Convertible
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic.efi.signed 
root=UUID=8352e01f-2580-4315-98ff-f584b17874d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D1
  dmi.board.vendor: HP
  dmi.board.version: 84.33
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd06/13/2017:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D1:rvr84.33:cvnHP:ct31:cvrChassisVersion:
  dmi.product.name: HP Pavilion x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Jul 24 09:28:26 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1706070] Re: Xorg crash

** Tags added: bios-outdated-f.24

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

Title:
  [HP Pavilion x360 - 13-s104br] Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu crashed and returned to login screen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jul 24 10:01:47 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80d1]
  InstallationDate: Installed on 2017-03-18 (127 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: HP HP Pavilion x360 Convertible
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic.efi.signed 
root=UUID=8352e01f-2580-4315-98ff-f584b17874d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D1
  dmi.board.vendor: HP
  dmi.board.version: 84.33
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd06/13/2017:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D1:rvr84.33:cvnHP:ct31:cvrChassisVersion:
  dmi.product.name: HP Pavilion x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Jul 24 09:28:26 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1708977] Re: Cannot boot after update

Robert W. King, thank you for reporting this and helping make Ubuntu
better.

1) Could you please advise which after which update specifically this
started to happen?

2) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to the results?

** Tags added: bios-outdated-80.24

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Cannot boot after update

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Following minor linux update cannot boot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  Uname: Linux 4.4.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog: /dev/sda1: clean, 223961/121970688 files, 8834593/487854592 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Aug  6 20:15:50 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK107 [GeForce GT 640 OEM] [10de:0fc0] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Pegatron GK107 [GeForce GT 640 OEM] [1b0a:90c5]
  MachineType: Hewlett-Packard 700-230qe
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic.efi.signed 
root=UUID=91d8e6ac-97d6-4068-a684-bc045f783fb5 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2013
  dmi.bios.vendor: AMI
  dmi.bios.version: 80.15
  dmi.board.name: 2AF3
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: 2MD3480GR8
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr80.15:bd09/19/2013:svnHewlett-Packard:pn700-230qe:pvr:rvnHewlett-Packard:rn2AF3:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: 700-230qe
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  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
  xserver.bootTime: Sun Aug  6 19:51:39 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.2
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1708983] Re: frozen screen

Peke Gandalera, thank you for reporting this and helping make Ubuntu
better.

1) Did this start to happen after an update? If so, which specifically?

2) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to the results?

** Tags added: latest-bios-a03

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  frozen screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Random freezing

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Aug  6 16:51:05 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0e) (prog-if 00 [VGA controller])
 Subsystem: Dell Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[1028:0667]
  InstallationDate: Installed on 2017-08-06 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0c45:64ad Microdia 
   Bus 001 Device 002: ID 8087:07e6 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 3531
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic 
root=UUID=53de4d80-8cca-40f7-a458-af49bc522162 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 00FTTX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/30/2014:svnDellInc.:pnInspiron3531:pvrA03:rvnDellInc.:rn00FTTX:rvrA00:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: Inspiron 3531
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://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 1706070] Re: Xorg crash

2018-02-12 Thread João Gabriel

Hello Christopher,

I answer in your message.

Best regards,
João Gabriel.

Em seg, 12 de fev de 2018 às 20:21, Christopher M. Penalver <
christopher.m.penal...@gmail.com> escreveu:

> João Gabriel, thank you for reporting this and helping make Ubuntu
> better.
>
> 1) Could you please provide the full computer model as noted on the
> sticker of the computer itself (not from the Bug Description, or the result
> of a terminal command)? For example:
> HP Pavilion 11-k100 x360 Convertible PC
>

HP Pavilion x360 13-S104BR

>
> 2) Is this something that started to happen after an update? If so,
> which specifically?
>
> I could not identify an event that caused the issue.


> 3) To see if this is already resolved in your release, could you please
> update your HWE stack as per
> https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
> results?
>
> I have migrated to Windows 10 6 months ago.
I can not make this test right now.
The instability was blocking my work and I needed to find a stable solution.

Thank you very much for your interest.


> ** Changed in: xorg (Ubuntu)
>Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1706070
>
> Title:
>   Xorg crash
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Ubuntu crashed and returned to login screen
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
>   Uname: Linux 4.10.0-27-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.10
>   Architecture: amd64
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Mon Jul 24 10:01:47 2017
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07)
> (prog-if 00 [VGA controller])
>  Subsystem: Hewlett-Packard Company Skylake Integrated Graphics
> [103c:80d1]
>   InstallationDate: Installed on 2017-03-18 (127 days ago)
>   InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
> (20170215.2)
>   MachineType: HP HP Pavilion x360 Convertible
>   ProcEnviron:
>LANGUAGE=pt_BR:pt:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=pt_BR.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic.efi.signed
> root=UUID=8352e01f-2580-4315-98ff-f584b17874d1 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   Symptom: display
>   Title: Xorg crash
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 06/13/2017
>   dmi.bios.vendor: Insyde
>   dmi.bios.version: F.21
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: 80D1
>   dmi.board.vendor: HP
>   dmi.board.version: 84.33
>   dmi.chassis.asset.tag: Chassis Asset Tag
>   dmi.chassis.type: 31
>   dmi.chassis.vendor: HP
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnInsyde:bvrF.21:bd06/13/2017:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D1:rvr84.33:cvnHP:ct31:cvrChassisVersion:
>   dmi.product.name: HP Pavilion x360 Convertible
>   dmi.product.version: Type1ProductConfigId
>   dmi.sys.vendor: HP
>   version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
>   version.xserver-xorg-core: xserver-xorg-core N/A
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
>   xserver.bootTime: Mon Jul 24 09:28:26 2017
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
>   xserver.video_driver: modeset
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1706070/+subscriptions
>

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu crashed and

[Touch-packages] [Bug 1722313] Re: Enable auditing in util-linux.

2018-02-12 Thread Joy Latten

Update on Artful regression analysis from comment #22.

1. Same as in comment #22. Hopefully these can be ignored as they were
for xenial.

2. Same as in comment #22. tests passed in different runs as stated
above. When the failures occurred, was because of time outs while
waiting for something. Failures appear to be intermittent and not
related to change made here.

3. gnocchi - appear to be a testcase usage message from python. Not
related to change made in this bug.

4. libdata-uuid-libuuid-perl (s390x) Julian did a test here using hello
and prior version of util-linux and they both failed with same error. So
this error is not related to this bug change. Something else changed
perhaps in testcase or test environment.

5. tracker passes on a re-run

6. nplan passes on a re-run

Conclusion: Hopefully above explanations result in regressions having
been resolved so util-linux in artful can be promoted.

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

Title:
  Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Committed
Status in util-linux source package in Zesty:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Committed
Status in util-linux package in Debian:
  New

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.

  Only the hwclock and the login commands within util-linux package have
  source code for auditing. But that source code is disabled by default
  and requires the config option, --with-audit to enable it. The login
  command is not built nor shipped in util-linux. Ubuntu uses the login
  command from shadow instead. Thus, only hwclock command would be
  affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged to /var/log/audit/audit.log,
  if auditd daemon is running. Otherwise, if the auditd is not running,
  like most log messages, it will get logged to /var/log/kern.log and|or
  /var/log/syslog if these services are enabled.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+subscriptions

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

[Touch-packages] [Bug 1714122] Re: latest skype update causes xorg to segfault

Yuriy Vidineev, closing as per your comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1714122/comments/7
noting this is resolved by updating.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  latest skype update causes xorg to segfault

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  After update skypeforlinux to 8.5.76.55323 I've started to get xorg segfaults 
when connected to 2 external monitors via docking station.
  My setup: Dell XPS 13 9360 + Dell DS1000 USB-C docking station+2 external 
FullHD Dell monitors.
  In xorg logs I can see:

  [ 17917.757] (II) LoadModule: "modesetting"
  [ 17917.757] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
  [ 17917.757] (II) Module modesetting: vendor="X.Org Foundation"
  [ 17917.757]compiled for 1.18.4, module version = 1.18.4
  [ 17917.757]Module class: X.Org Video Driver
  [ 17917.757]ABI class: X.Org Video Driver, version 20.0
  [ 17917.757] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
  [ 17917.759] (II) modeset(0): using drv /dev/dri/card0
  [ 17917.759] (EE) 
  [ 17917.759] (EE) Backtrace:
  [ 17917.759] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55c4f0526b6e]
  [ 17917.759] (EE) 1: /usr/lib/xorg/Xorg (0x55c4f0374000+0x1b6ef9) 
[0x55c4f052aef9]
  [ 17917.759] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fb6199e2000+0x354b0) 
[0x7fb619a174b0]
  [ 17917.759] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_next+0x118) [0x7fb61afd1a38]
  [ 17917.759] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_find_by_slot+0x3b) [0x7fb61afd1abb]
  [ 17917.759] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_vgaarb_init+0xaf) [0x7fb61afd37af]
  [ 17917.759] (EE) 6: /usr/lib/xorg/Xorg (0x55c4f0374000+0xb1a39) 
[0x55c4f0425a39]
  [ 17917.759] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55c4f03fe7a2]
  [ 17917.759] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0x968) [0x55c4f040cd58]
  [ 17917.759] (EE) 9: /usr/lib/xorg/Xorg (0x55c4f0374000+0x57be4) 
[0x55c4f03cbbe4]
  [ 17917.759] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fb619a02830]
  [ 17917.759] (EE) 11: /usr/lib/xorg/Xorg (_start+0x29) [0x55c4f03b6049]
  [ 17917.759] (EE) 
  [ 17917.759] (EE) Segmentation fault at address 0x0
  [ 17917.759] (EE) 
  Fatal server error:
  [ 17917.759] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 17917.759] (EE) 
  [ 17917.759] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 17917.759] (EE) Please also check the log file at "/var/log/Xorg.1.log" for 
additional information.
  [ 17917.759] (EE) 
  [ 17917.816] (EE) Server terminated with error (1). Closing log file.

  I'm not facing this issue when I'm not connected to external monitors.
  Any help will be much appretiated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 30 18:27:41 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2016-10-06 (328 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=f79f9409-625c-4f78-83af-cf2cf7928690 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version:

[Touch-packages] [Bug 1710322] Re: Xorg freeze

Jerry Quinn, thank you for reporting this and helping make Ubuntu
better.

1) Did this start to happen after an update? If so, which specifically?

2) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to the results?

** Tags added: bios-outdated-2.0b

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Display was wedged but ssh worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Aug 12 00:18:26 2017
  DistUpgraded: 2016-05-31 04:27:01,635 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/580] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb]
  InstallationDate: Installed on 2016-05-30 (438 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Supermicro X10DAi
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-32-generic 
root=/dev/mapper/vg--root-lvol0 ro quiet splash nomdmonddf nomdmonisw 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to xenial on 2016-05-31 (437 days ago)
  dmi.bios.date: 01/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.0c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X10DAI
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.0c:bd01/29/2015:svnSupermicro:pnX10DAi:pvr123456789:rvnSupermicro:rnX10DAI:rvr1.01:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: X10DAi
  dmi.product.version: 123456789
  dmi.sys.vendor: Supermicro
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Aug 12 00:07:34 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech Trackball   MOUSE, id 8
   inputLITE-ON Technology USB NetVista Full Width Keyboard. KEYBOARD, 
id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: amdgpu

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

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

[Touch-packages] [Bug 1710080] Re: sysem is all of a sudden very slow

farhad ameri, thank you for reporting this and helping make Ubuntu
better.

1) Could you please provide the full computer model as noted on the sticker of 
the computer itself (not from the Bug Description, or the result of a terminal 
command)? For example:
HP Pavilion dm4-1160eo Entertainment Notebook PC

2) Did this start to happen after an update? If so, which specifically?

3) Could you please provide a screen recording of the slowness?

4) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to the results?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  sysem is all of a sudden very slow

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  the system is all of a sudden  very slow and unresponsive

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   [[0;32m  OK  [0m] Started WPA supplicant.
   [[0;32m  OK  [0m] Started Automatic USB/Bluetooth printer setup 
(-devices-pci:00-:00:1d.0-usb2-2\x2d1-2\x2d1.1).
   [[0;32m  OK  [0m] Started LSB: Speech Dispatcher.
   [[0;32m  OK  [0m] Started LSB: Restore mixer settings from saved values..
   [[0;32m  OK  [0m] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Aug 10 23:52:07 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.40, 4.4.0-89-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:1650]
  InstallationDate: Installed on 2016-11-26 (257 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=0ee545f7-07fb-4a5a-8d44-ba5697d6b189 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1650
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 07.26
  dmi.chassis.asset.tag: CNU1390R4H
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.15:bd03/21/2012:svnHewlett-Packard:pnHPPaviliondm4NotebookPC:pvr067F21242F1620100:rvnHewlett-Packard:rn1650:rvrKBCVersion07.26:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm4 Notebook PC
  dmi.product.version: 067F21242F1620100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  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
  xserver.bootTime: Thu Aug 10 23:35:16 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5265 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.3

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

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

[Touch-packages] [Bug 1709918] Re: Freezes

emilram, thank you for reporting this and helping make Ubuntu better.

1) To clarify, is this something that started to happen after an update?
If so, which specifically?

2) When the computer freezes, for how long does it do so and what is the
impact precisely?

3) To see if this is already resolved in Ubuntu, could you please test
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?

** Tags added: bios-outdated-f5

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Freezes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  comp  freezes repeatedly

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-89.112~14.04.1-generic 4.4.76
  Uname: Linux 4.4.0-89-generic i686
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Aug 10 18:19:20 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2017-06-27 (43 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: Gigabyte Technology Co., Ltd. 945GCMX-S2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=2370472e-b9a6-4cb1-b26e-385e3d2f83bd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: 945GCMX-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/24/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GCMX-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCMX-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 945GCMX-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Aug 10 18:16:43 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSEMICCHIP Usb Mouse  MOUSE, id 8
   inputWebcam C170  KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12309 
   vendor DEL
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty2

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

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

[Touch-packages] [Bug 1709532] Re: Can't get the additional resolution

Anchal Bhargava, thank you for reporting this and helping make Ubuntu
better.

1) What is the full manufacturer and model of your external monitor?

2) How is the monitor connected to the computer HDMI, VGA, etc.?

3) Could you please provide the full computer model as noted on the
sticker of the computer itself (not from the Bug Description, or the
result of a terminal command)?

4) If you remove the nomodeset parameter, is this reproducible?

** Description changed:

- Hello,
+ I only have one screen resolution in display (1024x768).
  
- I am new to Linux, I have just installed Ubuntu 14, my problem is I am
- getting only one screen resolution in display(1024x768) and that's kind
- of uncomfortable to work.
- 
- I read that we do not need to install Graphics Driver then why isn't it
- showing me other screen resolutions?
- 
- One more thing, when I tried to install Ubuntu, after clicking on
- Install Ubuntu option, I got the time, volume option on the top right
- hand but the installation didn't start. I waited for around 15 minutes
- then restart the installation. I tried to install ubuntu 6-7 times with
- different versions too. But same thing happened every time.
- 
- So I read in a forum and some one said to use "nomodeset" option and
- after that ubuntu was installed. I hope this will help in rectifying the
- problem (also I will be very grateful if you can tell me why it wasn't
- working before and why it did install after that option, I am trying to
- learn how Linux works)
- 
- And I think that this doesn't have to do anything with it but still. I
- am using Intel XEON E5450 processor and don't have any external graphic
- card installed.
- 
- Thanks,
- Anchal Bhargava
+ I have kernel parameter nomodeset in use as I couldn't install Ubuntu
+ without it.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-89.112~14.04.1-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  .tmp.unity.support.test.1:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Aug  9 10:29:21 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
-Subsystem: Intel Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [8086:2a42]
-Subsystem: Intel Corporation Device [8086:2a42]
+  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Intel Corporation Mobile 4 Series Chipset Integrated Graphics 
Controller [8086:2a42]
+    Subsystem: Intel Corporation Device [8086:2a42]
  InstallationDate: Installed on 2017-08-09 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
-  LANGUAGE=en_IN:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_IN
-  SHELL=/bin/bash
+  LANGUAGE=en_IN:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_IN
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=7dac48a4-be03-4308-9a7f-9e2e4231dcee ro nomodeset quiet splash 
vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: GM45+ICH9+775 Series
  dmi.board.vendor: LORD ELECTRONICS CO.,LTD.LORD
  dmi.board.version: I1T65 V0.5
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: bio...@163.com
  dmi.chassis.version: Any Question, Please send mail
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd12/10/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnLORDELECTRONICSCO.,LTD.LORD:rnGM45+ICH9+775Series:rvrI1T65V0.5:cvnbio...@163.com:ct3:cvrAnyQuestion,Pleasesendmail:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A

[Touch-packages] [Bug 1709452] Re: Intell graphics

Agustin Samman, thank you for reporting this and helping make Ubuntu
better.

1) Did this start to happen after an update? If so, which specifically?

2) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to the results?

** Tags added: bios-outdated-a15

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Intell graphics

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The HDMI stopped working suddenly. I tried re-install Intell Graphic drivers 
and still nothing.
  I have a Dell Insipiron 5010 64 bit.
  I ran de apport bug as the helped stated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Aug  8 20:33:14 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.4.0-83-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-89-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 18) (prog-if 00 [VGA controller])
 Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0447]
  InstallationDate: Installed on 2014-10-05 (1038 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-89-generic 
root=UUID=cbde2fc0-7e9c-48f9-b588-ea7014e028ae ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0WXY9J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A07
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd07/26/2010:svnDellInc.:pnInspironN5010:pvrA07:rvnDellInc.:rn0WXY9J:rvrA07:cvnDellInc.:ct8:cvrA07:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A07
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.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
  xserver.bootTime: Tue Aug  8 20:28:05 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8940 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.3

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

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

[Touch-packages] [Bug 1706070] Re: Xorg crash

João Gabriel, thank you for reporting this and helping make Ubuntu
better.

1) Could you please provide the full computer model as noted on the sticker of 
the computer itself (not from the Bug Description, or the result of a terminal 
command)? For example:
HP Pavilion 11-k100 x360 Convertible PC

2) Is this something that started to happen after an update? If so,
which specifically?

3) To see if this is already resolved in your release, could you please
update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu crashed and returned to login screen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Jul 24 10:01:47 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80d1]
  InstallationDate: Installed on 2017-03-18 (127 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: HP HP Pavilion x360 Convertible
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic.efi.signed 
root=UUID=8352e01f-2580-4315-98ff-f584b17874d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D1
  dmi.board.vendor: HP
  dmi.board.version: 84.33
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd06/13/2017:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D1:rvr84.33:cvnHP:ct31:cvrChassisVersion:
  dmi.product.name: HP Pavilion x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Jul 24 09:28:26 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1709897] Re: Xorg crash

*** This bug is a duplicate of bug 1706070 ***
https://bugs.launchpad.net/bugs/1706070

** This bug has been marked a duplicate of bug 1706070
   Xorg crash

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu crashed and returned to login screen

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-30.34~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-30-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Aug 10 11:49:14 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80d1]
  InstallationDate: Installed on 2017-03-18 (145 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: HP HP Pavilion x360 Convertible
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-30-generic.efi.signed 
root=UUID=8352e01f-2580-4315-98ff-f584b17874d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D1
  dmi.board.vendor: HP
  dmi.board.version: 84.33
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd06/13/2017:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D1:rvr84.33:cvnHP:ct31:cvrChassisVersion:
  dmi.product.name: HP Pavilion x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Aug 10 11:48:28 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1711205] Re: Xorg freeze

GRC FAMILY NET, thank you for reporting this and helping make Ubuntu
better.

1) Regarding hardware acceleration being disabled, how do you do this
specifically?

2) If you disable hardware acceleration, is this still reproducible?

3) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to the results?

** Tags added: latest-bios-2501

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The screen freezes (with no corruption) when the PC enters standby or screen 
power saving.
  The event does not happen when the PC enters standby or screen power saving 
from the users selection screen.
  Once the problem happens the only way to recover normal operation is to 
switch to another VT (ctrl+alt+f*), login as any user and run "sudo service 
lightdm restart".

  Until some of the last updates, I was experiencing very serious
  episodes of screen corruptions that forced me to disable hardware
  acceleration. Now I can use acceleration with this residual problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.10.8-041008-lowlatency x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Aug 16 21:11:05 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   NVIDIA Corporation GF116 [GeForce GTX 550 Ti] [10de:1244] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GF116 [GeForce GTX 550 
Ti] [1462:809d]
  InstallationDate: Installed on 2016-04-23 (480 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.8-041008-lowlatency 
root=UUID=116cf640-f3d4-409e-bb36-c01299150422 ro noprompt persistent quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2501
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A99FX PRO R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd04/07/2014:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  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
  xserver.bootTime: Wed Aug 16 20:55:06 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.3
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1710508] Re: Xorg crash

*** This bug is a duplicate of bug 1706070 ***
https://bugs.launchpad.net/bugs/1706070

** This bug has been marked a duplicate of bug 1706070
   Xorg crash

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu crashed and returned to login screen while using libreoffice
  writer.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Aug 13 16:40:45 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:80d1]
  InstallationDate: Installed on 2017-03-18 (148 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: HP HP Pavilion x360 Convertible
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic.efi.signed 
root=UUID=8352e01f-2580-4315-98ff-f584b17874d1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80D1
  dmi.board.vendor: HP
  dmi.board.version: 84.33
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd06/13/2017:svnHP:pnHPPavilionx360Convertible:pvrType1ProductConfigId:rvnHP:rn80D1:rvr84.33:cvnHP:ct31:cvrChassisVersion:
  dmi.product.name: HP Pavilion x360 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Aug 13 16:40:06 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1714122] Re: latest skype update causes xorg to segfault

2018-02-12 Thread Yuriy Vidineev

Hi Christopher,
Thanks for your attention!
Like I said in previous comment I don't have this bug anymore after upgrading 
to linux 4.13

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

Title:
  latest skype update causes xorg to segfault

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After update skypeforlinux to 8.5.76.55323 I've started to get xorg segfaults 
when connected to 2 external monitors via docking station.
  My setup: Dell XPS 13 9360 + Dell DS1000 USB-C docking station+2 external 
FullHD Dell monitors.
  In xorg logs I can see:

  [ 17917.757] (II) LoadModule: "modesetting"
  [ 17917.757] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
  [ 17917.757] (II) Module modesetting: vendor="X.Org Foundation"
  [ 17917.757]compiled for 1.18.4, module version = 1.18.4
  [ 17917.757]Module class: X.Org Video Driver
  [ 17917.757]ABI class: X.Org Video Driver, version 20.0
  [ 17917.757] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
  [ 17917.759] (II) modeset(0): using drv /dev/dri/card0
  [ 17917.759] (EE) 
  [ 17917.759] (EE) Backtrace:
  [ 17917.759] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55c4f0526b6e]
  [ 17917.759] (EE) 1: /usr/lib/xorg/Xorg (0x55c4f0374000+0x1b6ef9) 
[0x55c4f052aef9]
  [ 17917.759] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fb6199e2000+0x354b0) 
[0x7fb619a174b0]
  [ 17917.759] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_next+0x118) [0x7fb61afd1a38]
  [ 17917.759] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_find_by_slot+0x3b) [0x7fb61afd1abb]
  [ 17917.759] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_vgaarb_init+0xaf) [0x7fb61afd37af]
  [ 17917.759] (EE) 6: /usr/lib/xorg/Xorg (0x55c4f0374000+0xb1a39) 
[0x55c4f0425a39]
  [ 17917.759] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55c4f03fe7a2]
  [ 17917.759] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0x968) [0x55c4f040cd58]
  [ 17917.759] (EE) 9: /usr/lib/xorg/Xorg (0x55c4f0374000+0x57be4) 
[0x55c4f03cbbe4]
  [ 17917.759] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fb619a02830]
  [ 17917.759] (EE) 11: /usr/lib/xorg/Xorg (_start+0x29) [0x55c4f03b6049]
  [ 17917.759] (EE) 
  [ 17917.759] (EE) Segmentation fault at address 0x0
  [ 17917.759] (EE) 
  Fatal server error:
  [ 17917.759] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 17917.759] (EE) 
  [ 17917.759] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 17917.759] (EE) Please also check the log file at "/var/log/Xorg.1.log" for 
additional information.
  [ 17917.759] (EE) 
  [ 17917.816] (EE) Server terminated with error (1). Closing log file.

  I'm not facing this issue when I'm not connected to external monitors.
  Any help will be much appretiated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 30 18:27:41 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2016-10-06 (328 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic 
root=UUID=f79f9409-625c-4f78-83af-cf2cf7928690 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.0
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.

[Touch-packages] [Bug 1711037] Re: Screen intermittently flickers

** Tags added: bios-outdated-2101

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

Title:
  Screen intermittently flickers

Status in xorg package in Ubuntu:
  New

Bug description:
  Using both my nvidia and radeon cards my 2560x1600 display flickers.
  The screen is fine in Windows.  This only seems to happen when I run
  the open source driver.

  Additionally, if I drop that screen to a lower 16:10 resolution like
  1920x1200 it goes black.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
  Uname: Linux 4.11.0-13-generic x86_64
  ApportVersion: 2.20.6-0ubuntu5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Tue Aug 15 22:32:41 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.11.0-10-generic, x86_64: installed
   bbswitch, 0.8, 4.11.0-13-generic, x86_64: installed
   nvidia-384, 384.59, 4.11.0-10-generic, x86_64: installed
   nvidia-384, 384.59, 4.11.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev 
cf) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Baffin [Polaris11] 
[1462:8a91]
  InstallationDate: Installed on 2017-08-07 (9 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170805)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-13-generic 
root=UUID=adb3a033-d515-4dfb-97d6-7c0ef12879cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1807
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P7P55D DELUXE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1807:bd07/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55DDELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.82-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.4-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Aug 14 07:40:51 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.3-1ubuntu2

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

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

[Touch-packages] [Bug 1714282] Re: Sorry something went wrong GDBus:

** Package changed: xorg (Ubuntu) => gnome-shell (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/1714282

Title:
  Sorry something went wrong GDBus:

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  After applying the latest update the Software-center now opens but
  still has a problem.

  For the Launch pad, software center, in Ubuntu 17.10 it reports this error 
when trying to open it.
  "Sorry something went wrong GDBus, error: freedesktop.DBus.error. unknown 
Method: No such
  interface` org.gnome.Shell.Extensions on object at path /org/gnome/shell".

  Some of the links to the software doesn't work.
  Some of the buttons of categories doesn't work.
  Updates never show "software to be updated" anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714282/+subscriptions

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

[Touch-packages] [Bug 1733870] Re: [Ubuntu 18.10] Add GDB support to access/display POWER8 registers

Any updates on the upstream code status?

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

Title:
  [Ubuntu 18.10] Add GDB support to access/display POWER8 registers

Status in The Ubuntu-power-systems project:
  Incomplete
Status in gdb package in Ubuntu:
  Incomplete

Bug description:
  This feature request is for GDB support for access to Power registers
  that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM
  registers.

  The feature is currently being worked on, so no upstream code is
  available yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733870/+subscriptions

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

[Touch-packages] [Bug 1711766] Re: Apps keep crashing

Ardit Saliasi, thank you for reporting this and helping make Ubuntu
better.

1) After an app crashes, are there crash files in /var/crash?

2) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to the results?

** Tags added: bios-outdated-a19

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Apps keep crashing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Every new app i install, even some previously installed keep crashing
  and do not open.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Aug 19 01:37:19 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0262]
 Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:0262]
  InstallationDate: Installed on 2017-08-16 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Latitude E5400
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 0D693C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd11/05/2009:svnDellInc.:pnLatitudeE5400:pvr:rvnDellInc.:rn0D693C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E5400
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1712005] Re: External displays blank, kernel errors from i915/drm driver

Maketsi, closing as per your comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1712005/comments/2
noting this is resolved.

** Tags added: bios-outdated-1.42

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

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

Title:
  External displays blank, kernel errors from i915/drm driver

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  My two external displayport connected displays worked fine until last 
thursday. After bringing my laptop to the same HP dock station three days 
later, they stayed blank no matter what.
  Displays are seen by X (other of them was powered off during the bug report) 
and detected correctly, but there is no picture.
  Displays worked with the current kernel 4.4.0-92-generic on thursday.
  Dmesg log is full of kernel errors from i915 driver, multiplied by me 
switching the monitors on and off while troubleshooting the issue.

  $ dmesg | fgrep WARNING
  [2.860874] WARNING: CPU: 0 PID: 1 at 
/build/linux-hVVhWi/linux-4.4.0/arch/x86/mm/ioremap.c:198 
__ioremap_caller+0x2c5/0x380()
  [  109.067969] WARNING: CPU: 2 PID: 78 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_dp_mst.c:493 
intel_dp_destroy_mst_connector+0xe7/0xf0 [i915]()
  [  109.384569] WARNING: CPU: 2 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  110.235437] WARNING: CPU: 2 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  142.534674] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  196.127732] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  211.875798] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  273.426829] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  273.728180] WARNING: CPU: 2 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  274.583122] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  290.154952] WARNING: CPU: 2 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  301.498593] WARNING: CPU: 0 PID: 172 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  326.124417] WARNING: CPU: 1 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  355.932899] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  356.032234] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  384.356500] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  384.458966] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  448.277935] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [  448.370419] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()

  
  When enabling OR disabling the external display via Displays applet, the 
following error happens:

  [ 1782.969654] WARNING: CPU: 3 PID: 1488 at 
/build/linux-hVVhWi/linux-4.4.0/drivers/gpu/drm/i915/intel_display.c:12746 
intel_modeset_check_state+0x563/0x8a0 [i915]()
  [ 1782.969657] encoder's enabled state mismatch (expected 1, found 0)
  [ 1782.969658] Modules linked in: vmnet(OE) vmw_vsock_vmci_transport vsock 
vmw_vmci vmmon(OE) rfcomm bnep binfmt_misc arc4 hp_wmi sparse_keymap intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iwlmvm kvm 
snd_hda_codec_hdmi mac80211 irqbypass snd_hda_codec_idt snd_hda_codec_generic 
joydev snd_hda_intel serio_raw snd_hda_codec

[Touch-packages] [Bug 1713500] Re: installer

conny, thank you for reporting this and helping make Ubuntu better.

1) Could you please provide a video or screenshot of the error message?

2) To clarify, does it hang indefinitely or for a period of time?

3) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to the results?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  installer

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  In the installation of google chrome or other programs, the installer
  hangs on some vwersucht but it can not

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Aug 28 14:58:02 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7480D] [1002:9993] 
(prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 
7480D] [1002:0123]
  InstallationDate: Installed on 2017-08-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=fa5128ac-0b1b-49e5-a14b-b8d3c1b10b12 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XM-DS2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd01/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Aug 28 14:47:58 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1712416] Re: Inastalé Driver y el no funcionó

chalosan, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect 1712416

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Inastalé Driver y el no funcionó

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Driver tarjeta gráfica no funciona: AMD-RADEON Dual-X R9 280X en
  ubuntu 17.10

  Gracias

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  ApportVersion: 2.20.6-0ubuntu6
  Architecture: amd64
  Date: Tue Aug 22 14:39:30 2017
  DistroCodename: artful
  DistroVariant: ubuntu
  InstallationDate: Installed on 2017-08-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820)
  ProcEnviron:
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   LANG=es_CO.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1712510] Re: Slow bootup

Douglas L. Turnbull, thank you for reporting this and helping make
Ubuntu better.

1) Could you please advise how long it takes to bootup in
seconds/minutes?

2) Is this something that started to happen after an update? If so,
which specifically?

3) To see if this is already resolved in your release, could you please
update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?

** Tags added: bios-outdated-1.4.4

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Slow bootup

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Could be a grub problem

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
  Uname: Linux 4.4.0-92-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 23 18:51:55 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0708]
 Subsystem: Dell GM204M [GeForce GTX 970M] [1028:0708]
  InstallationDate: Installed on 2017-08-16 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1bcf:2b8c Sunplus Innovation Technology Inc. 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 187c:0528 Alienware Corporation 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Alienware Alienware 15 R2
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-92-generic 
root=UUID=8e3659b0-7baf-41fc-af8b-0f93a2fac71a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2015
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.1.5
  dmi.board.name: Alienware 15 R2
  dmi.board.vendor: Alienware
  dmi.board.version: X01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.1.5:bd09/18/2015:svnAlienware:pnAlienware15R2:pvr1.1.5:rvnAlienware:rnAlienware15R2:rvrX01:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 15 R2
  dmi.product.version: 1.1.5
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  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
  xserver.bootTime: Wed Aug 23 18:49:52 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   Unknown chipset: NV124
   modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19528 
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.3

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

-- 
Mailing list: https://launchpad.net/~touch-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.

Kent Lion, thank you for reporting this and helping make Ubuntu better.

To see if this is already resolved in your release, could you please
update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?

** Tags added: latest-bios-a11

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

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 1713628] Re: My mouse doesn't work as expected

Petr Qvits, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you 
have the package xdiagnose installed, and that you click the Yes button for 
attaching additional debugging information:
apport-collect 1713628

When reporting xorg related bugs in the future, please do so via the
above method. You can learn more about this functionality at
https://wiki.ubuntu.com/ReportingBugs.

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  My mouse doesn't work as expected

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I have wireless touch mouse. Partially it detected as a keyboard, and
  i can't remap this gesture. This gesture has defined combination, but
  I want to change them.

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

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

[Touch-packages] [Bug 1714122] Re: latest skype update causes xorg to segfault

Yuriy Vidineev, thank you for reporting this and helping make Ubuntu
better.

To see if this is already resolved in your release, could you please
update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?

** Tags added: bios-outdated-2.4.2

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  latest skype update causes xorg to segfault

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After update skypeforlinux to 8.5.76.55323 I've started to get xorg segfaults 
when connected to 2 external monitors via docking station.
  My setup: Dell XPS 13 9360 + Dell DS1000 USB-C docking station+2 external 
FullHD Dell monitors.
  In xorg logs I can see:

  [ 17917.757] (II) LoadModule: "modesetting"
  [ 17917.757] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
  [ 17917.757] (II) Module modesetting: vendor="X.Org Foundation"
  [ 17917.757]compiled for 1.18.4, module version = 1.18.4
  [ 17917.757]Module class: X.Org Video Driver
  [ 17917.757]ABI class: X.Org Video Driver, version 20.0
  [ 17917.757] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
  [ 17917.759] (II) modeset(0): using drv /dev/dri/card0
  [ 17917.759] (EE) 
  [ 17917.759] (EE) Backtrace:
  [ 17917.759] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55c4f0526b6e]
  [ 17917.759] (EE) 1: /usr/lib/xorg/Xorg (0x55c4f0374000+0x1b6ef9) 
[0x55c4f052aef9]
  [ 17917.759] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fb6199e2000+0x354b0) 
[0x7fb619a174b0]
  [ 17917.759] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_next+0x118) [0x7fb61afd1a38]
  [ 17917.759] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_find_by_slot+0x3b) [0x7fb61afd1abb]
  [ 17917.759] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_vgaarb_init+0xaf) [0x7fb61afd37af]
  [ 17917.759] (EE) 6: /usr/lib/xorg/Xorg (0x55c4f0374000+0xb1a39) 
[0x55c4f0425a39]
  [ 17917.759] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55c4f03fe7a2]
  [ 17917.759] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0x968) [0x55c4f040cd58]
  [ 17917.759] (EE) 9: /usr/lib/xorg/Xorg (0x55c4f0374000+0x57be4) 
[0x55c4f03cbbe4]
  [ 17917.759] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf0) [0x7fb619a02830]
  [ 17917.759] (EE) 11: /usr/lib/xorg/Xorg (_start+0x29) [0x55c4f03b6049]
  [ 17917.759] (EE) 
  [ 17917.759] (EE) Segmentation fault at address 0x0
  [ 17917.759] (EE) 
  Fatal server error:
  [ 17917.759] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [ 17917.759] (EE) 
  [ 17917.759] (EE) 
  Please consult the The X.Org Foundation support 
   at http://wiki.x.org
   for help. 
  [ 17917.759] (EE) Please also check the log file at "/var/log/Xorg.1.log" for 
additional information.
  [ 17917.759] (EE) 
  [ 17917.816] (EE) Server terminated with error (1). Closing log file.

  I'm not facing this issue when I'm not connected to external monitors.
  Any help will be much appretiated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-33.37~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Aug 30 18:27:41 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2016-10-06 (328 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic

[Touch-packages] [Bug 1714146] Re: Touchpad scrolling not working

woodo, thank you for reporting this and helping make Ubuntu better.

1) Did the touchpad stop working as expected after an update? If so,
which?

2) To see if this is resolved in your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to the results?

** Summary changed:

- Touchpad scrolling and grub menu ubuntu troubleshooting screen not working
+ Touchpad scrolling not working

** Description changed:

- ubuntu 16.04.3 LTS
- "unable to locate package name"
- 
- expect touch pad to allow to scroll up and down and side to side with
- two fingers, expect to be able to enter rescue mode
- 
- Screen freezes when I choose Ubuntu rescue from grub menu
- touch-pad works like a mouse,
- 
- May be duplicates of other reported bugs which I have added my name to
- eg 1574341, 1480673, 1574028
+ I expect the touchpad to allow to scroll up and down and side to side
+ with two fingers, but it works like a mouse.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Aug 31 13:14:34 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) 
(prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Broadwell-U Integrated Graphics 
[1043:18fd]
+  Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) 
(prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Broadwell-U Integrated Graphics 
[1043:18fd]
  InstallationDate: Installed on 2017-08-21 (9 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK COMPUTER INC. T300CHI
  ProcEnviron:
-  LANGUAGE=en_AU:en
-  PATH=(custom, no user)
-  LANG=en_AU.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_AU:en
+  PATH=(custom, no user)
+  LANG=en_AU.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=9a7bb3ea-4a4d-4467-a0d1-d0f3d1cc7024 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T300CHI.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T300CHI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT300CHI.207:bd08/06/2015:svnASUSTeKCOMPUTERINC.:pnT300CHI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300CHI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: T300CHI
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Aug 30 07:41:43 2017
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Touchpad scrolling not working

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I expect the touchpad to allow to scroll up and down and side to side
  with two fingers, but it works like a mouse.

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

  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for

[Touch-packages] [Bug 1715749] Re: Intermittent black screen on HP EliteBook 840 G1

2018-02-12 Thread Michael von Glasow

Update done. I’ll keep an eye on this and report back if I encounter the
issue again (or do not encounter it for a longer time—being a sporadic
bug, it’s difficult to tell if it’s gone away for good).

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

Title:
  Intermittent black screen on HP EliteBook 840 G1

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Occasionally, the internal laptop display goes black for a few
  seconds, then comes back to life. The external display stays on. It
  looks as if power management were kicking in by error but affecting
  only the internal display.

  When I’m working with the external display, I need to move the mouse
  into the area managed by the internal display to wake it up again;
  else it seems to remain black (though I haven’t tested that behavior
  thoroughly).

  Most tests with the external display were made with the port
  replicator and an external display plugged into one of the DP ports
  via a DP–DVI adapter. I cannot tell for sure what the behavior is with
  the external display plugged directly into the laptop.

  The hard disk was originally installed with Ubuntu MATE 14.10 in a HP
  EliteBook 6930p, upgraded to 15.04, 15.10 and eventually 16.04 and
  finally moved to the EliteBook 840 G1.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Sep  8 00:53:24 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-12-09 (1002 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:198f]
  InstallationDate: Installed on 2014-12-09 (1158 days ago)
  InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Tags:  xenial ubuntu
  Uname: Linux 4.4.0-112-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: CNU407CM0V
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

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

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

[Touch-packages] [Bug 1734586] Re: Merge NetworkManager with Debian 1.10.0-1

2018-02-12 Thread Bryan Quigley

Python-dbusmock upstream - https://github.com/martinpitt/python-
dbusmock/issues/37

Although I don't think we should delay network-manager because of it..

** Bug watch added: github.com/martinpitt/python-dbusmock/issues #37
   https://github.com/martinpitt/python-dbusmock/issues/37

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

Title:
  Merge NetworkManager with Debian 1.10.0-1

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  Debian has packaged the latest major release of NetworkManager, 1.10.
  We should update to this version for Ubuntu 18.04 "bionic".

  I have prepared the merge at
  https://git.launchpad.net/network-manager?h=bionic

  The only thing missing is that this patch needs to be rebased or dropped:
  
https://git.launchpad.net/network-manager/tree/debian/patches/dns-manager-don-t-merge-split-DNS-search-domains.patch?h=bionic

  Otherwise, the build will fail:

  src/.libs/libNetworkManagerTest.a(src_libNetworkManager_la-nm-dns-manager.o):
  In function `merge_one_ip_config_data':
  ./src/dns/nm-dns-manager.c:417: undefined reference to
  `nm_ip4_config_get_never_default'
  ./src/dns/nm-dns-manager.c:419: undefined reference to
  `nm_ip4_config_get_never_default'

  There's been a lot of refactoring, but this commit looks important:
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=5c29945

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

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

[Touch-packages] [Bug 1714990] Re: Xorg freeze

cement_head, thanks for reporting this and helping make Ubuntu better.

To see if this is resolved for your release, could you please update
your HWE stack as per https://wiki.ubuntu.com/Kernel/LTSEnablementStack
and advise to the results?

** Tags added: regression-update

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After last kernel upgrade, machine freezes running any kind of video,
  doesn't always happen but is random.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-34.38~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Sep  4 11:58:31 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:2425]
  InstallationDate: Installed on 2016-04-28 (493 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 045e:007d Microsoft Corp. Notebook Optical Mouse
   Bus 001 Device 003: ID 5986:068f Acer, Inc 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System76, Inc. Lemur
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-34-generic 
root=UUID=52cc6985-56fb-43f9-8439-967a49db65bb ro quiet splash 
elevator=deadline vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06RS76
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Lemur
  dmi.board.vendor: System76, Inc.
  dmi.board.version: lemu6
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06RS76:bd11/29/2015:svnSystem76,Inc.:pnLemur:pvrlemu6:rvnSystem76,Inc.:rnLemur:rvrlemu6:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.name: Lemur
  dmi.product.version: lemu6
  dmi.sys.vendor: System76, Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Sep  4 11:57:12 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1715121] Re: cheese error message

** Package changed: xorg (Ubuntu) => cheese (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/1715121

Title:
  cheese error message

Status in cheese package in Ubuntu:
  New

Bug description:
  "there was an error playing video from webcam"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-94.117~14.04.1-generic 4.4.83
  Uname: Linux 4.4.0-94-generic i686
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Sep  5 13:26:57 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2017-06-27 (69 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04.2 LTS "Trusty Tahr" - Release i386 
(20150218.1)
  MachineType: Gigabyte Technology Co., Ltd. 945GCMX-S2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-94-generic 
root=UUID=2370472e-b9a6-4cb1-b26e-385e3d2f83bd ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: 945GCMX-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/24/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GCMX-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCMX-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 945GCMX-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Tue Sep  5 13:24:20 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSEMICCHIP Usb Mouse  MOUSE, id 8
   inputWebcam C170  KEYBOARD, id 9
   inputAT Translated Set 2 keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12309 
   vendor DEL
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty2

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

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

[Touch-packages] [Bug 1743797] Re: [HP Compaq nc6400] Blank screen on boot

Great Regan:

The last couple lines from the video until blank screen:
[OK] Started Light Display Manager.
 Starting WPA Supplicant...

taking this along with the boot up history didn't confirm the root cause
for me.

Despite this, as per your Bug Description, you noted this problem
started happening after an update. Could you please advise to which one
specifically?

** Attachment removed: "recording of boot without workaround"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1743797/+attachment/5052209/+files/Bug%201743797%20boot%20log%20trim.mov

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

Title:
  [HP Compaq nc6400] Blank screen on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  A few months after upgrading to Ubuntu 16.04, I got a black screen
  after booting.

  WORKAROUND: Use kernel parameter:
  radeon.modeset=0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jan 17 10:15:32 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV515/M52 [Mobility Radeon X1300] 
[1002:714a] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company RV515/M52 [Mobility Radeon X1300] 
[103c:30ac]
  InstallationDate: Installed on 2014-04-10 (1378 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  MachineType: Hewlett-Packard HP Compaq nc6400 (RB523UA#ABA)
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcEnviron:
   LANGUAGE=en_CA:en
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=123f436f-0331-4097-8a8e-54cc927298c4 ro radeon.modeset=0
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YCD Ver. F.08
  dmi.board.name: 30AC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 56.34
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YCDVer.F.08:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnc6400(RB523UA#ABA):pvrF.08:rvnHewlett-Packard:rn30AC:rvrKBCVersion56.34:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nc6400 (RB523UA#ABA)
  dmi.product.version: F.08
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jan 17 08:23:08 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1748729] Re: Xorg freeze

BertN45, given 3D acceleration is a WORKAROUND, Low is in line with its
definition noted in https://wiki.ubuntu.com/Bugs/Importance . To advise,
the potential difficulty in solving a bug has no impact on Importance.

Despite this:

1) What version of VirtualBox are you using on the host?

2) Did this issue start happening in the guest after an update from
either the guest, or host? If so, which specifically?

3) In your last comment, it appears you are indicating that this only
happens in 17.10 GNOME, but not with 17.10 Xubuntu. Could you please
clarify?

4) Does installing in the guest the package virtualbox-guest-x11 and
rebooting improve the situation?

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the 
propriety Nvidia driver 340 as suggested by Ubuntu.
  The screen almost freezes completely as soon as I maximise any window in the 
guest OS Ubuntu 18.04. Any mouse click takes 10-60 seconds before the system 
reacts to it. It took a long time to generate this bug-report.

  I had the same problem with Ubuntu 17.10, while Guest OSes Ubuntu Mate
  17.10, Xubuntu 17.10, and Peppermint 8. Windows 7 and 10 work without
  any problem.

  WORKAROUND: Disable 3D acceleration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 06:31:52 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-12-22 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1734586] Re: Merge NetworkManager with Debian 1.10.0-1

2018-02-12 Thread Bryan Quigley

Autopkgtets, The urfkill-intergration is failing because if you start
network-manager first, it clears the rfkill flags.

I think it should be safe to assume network-manager should start before
urfkill - in that case removing the last network-manager stop (and the
resulting start one) and I think we should be good for that test.

The python-dbusmock changes I believe are mostly due to upstream commit
6fde475b2705381eb54350f116e978659f28b004.  "...This basically uses
"wifi" in place of "802-11-wireless" and analogously..."

I was able to get the python file to do all pass with the changes listed
in https://pastebin.ubuntu.com/=BFwMCgTKkv/.

I plan to submit the python-dbusmock changes upstream.

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

Title:
  Merge NetworkManager with Debian 1.10.0-1

Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  Debian has packaged the latest major release of NetworkManager, 1.10.
  We should update to this version for Ubuntu 18.04 "bionic".

  I have prepared the merge at
  https://git.launchpad.net/network-manager?h=bionic

  The only thing missing is that this patch needs to be rebased or dropped:
  
https://git.launchpad.net/network-manager/tree/debian/patches/dns-manager-don-t-merge-split-DNS-search-domains.patch?h=bionic

  Otherwise, the build will fail:

  src/.libs/libNetworkManagerTest.a(src_libNetworkManager_la-nm-dns-manager.o):
  In function `merge_one_ip_config_data':
  ./src/dns/nm-dns-manager.c:417: undefined reference to
  `nm_ip4_config_get_never_default'
  ./src/dns/nm-dns-manager.c:419: undefined reference to
  `nm_ip4_config_get_never_default'

  There's been a lot of refactoring, but this commit looks important:
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=5c29945

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

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

[Touch-packages] [Bug 1749000] [NEW] [patch] please add "AssumedApparmorLabel=unconfined" to service file

2018-02-12 Thread Michael Vogt

Public bug reported:

There was a recent change in apparmor
(https://cgit.freedesktop.org/dbus/dbus/commit/?id=dc25979eb) that
breaks snapd. The fix is simply to add the
++AssumedApparmorLabel=unconfined line to the service file so that
activation works again.

Attached is a debdiff with a possible fix.

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

** Patch added: "possible fix"
   
https://bugs.launchpad.net/bugs/1749000/+attachment/5053897/+files/systemd_237-1ubuntu4.debdiff

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

Title:
  [patch] please add "AssumedApparmorLabel=unconfined" to service file

Status in systemd package in Ubuntu:
  New

Bug description:
  There was a recent change in apparmor
  (https://cgit.freedesktop.org/dbus/dbus/commit/?id=dc25979eb) that
  breaks snapd. The fix is simply to add the
  ++AssumedApparmorLabel=unconfined line to the service file so that
  activation works again.

  Attached is a debdiff with a possible fix.

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

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

[Touch-packages] [Bug 1748981] [NEW] [3680WKM, Conexant CX20585, Speaker, Internal] fails after a while

2018-02-12 Thread René Gailliaert

Public bug reported:

lenovo x201 ubuntu 16 lts; sound stops after playing normally

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
Uname: Linux 4.4.0-112-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  toko   1909 F pulseaudio
CurrentDesktop: Unity
Date: Mon Feb 12 20:58:22 2018
InstallationDate: Installed on 2016-08-22 (539 days ago)
InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Intern geluid - HDA Intel MID
Symptom_Jack: Speaker, Internal
Symptom_PulseAudioLog:
 
Symptom_Type: Sound works for a while, then breaks
Title: [3680WKM, Conexant CX20585, Speaker, Internal] fails after a while
UpgradeStatus: Upgraded to xenial on 2017-12-01 (72 days ago)
dmi.bios.date: 02/24/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET64WW (1.34 )
dmi.board.name: 3680WKM
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6QET64WW(1.34):bd02/24/2011:svnLENOVO:pn3680WKM:pvrThinkPadX201:rvnLENOVO:rn3680WKM:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 3680WKM
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 xenial

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

Title:
  [3680WKM, Conexant CX20585, Speaker, Internal] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  lenovo x201 ubuntu 16 lts; sound stops after playing normally

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  toko   1909 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb 12 20:58:22 2018
  InstallationDate: Installed on 2016-08-22 (539 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Intern geluid - HDA Intel MID
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog:
   
  Symptom_Type: Sound works for a while, then breaks
  Title: [3680WKM, Conexant CX20585, Speaker, Internal] fails after a while
  UpgradeStatus: Upgraded to xenial on 2017-12-01 (72 days ago)
  dmi.bios.date: 02/24/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET64WW (1.34 )
  dmi.board.name: 3680WKM
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET64WW(1.34):bd02/24/2011:svnLENOVO:pn3680WKM:pvrThinkPadX201:rvnLENOVO:rn3680WKM:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 3680WKM
  dmi.product.version: ThinkPad X201
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1748729] Re: Xorg freeze

2018-02-12 Thread BertN45

For me the problem is kind of important, since I moved all my work to 
specialised Virtual Machines; 
a. one for the normal office and web browsing work, 
b. one for banking and other financial apps, 
c. one to try out new and unknown apps,
d. one to try out Ubuntu 18.04.

The work around I use now, is: 
a. Peppermint 8 with 3D acceleration;  
b. For banking I can live with software rendering and Ubuntu 17.10;
c. Xubuntu 17.10 with 3D acceleration.

I would politely propose to increase the priority of the bug, since I
expect, it will be relatively simple to solve. Besides a desktop that
freezes, if you maximise a window, looks a little bit like the past of
e.g. Ubuntu 6.06 :)

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the 
propriety Nvidia driver 340 as suggested by Ubuntu.
  The screen almost freezes completely as soon as I maximise any window in the 
guest OS Ubuntu 18.04. Any mouse click takes 10-60 seconds before the system 
reacts to it. It took a long time to generate this bug-report.

  I had the same problem with Ubuntu 17.10, while Guest OSes Ubuntu Mate
  17.10, Xubuntu 17.10, and Peppermint 8. Windows 7 and 10 work without
  any problem.

  WORKAROUND: Disable 3D acceleration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 06:31:52 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-12-22 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1748956] [NEW] replace uses of net-tools with iproute2

2018-02-12 Thread Scott Moser

Public bug reported:

As ubuntu goes forward, net-tools is looking to be dropped.

Byobu currently depends on net-tools.  That code should be replaced by
iproute2.


Related bugs:
 * bug 925145: cloud-init  Use ip instead of ifconfig and route

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: byobu 5.124-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 12 13:34:27 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (935 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: byobu
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: byobu
 Importance: Undecided
 Status: New

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

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic wayland-session

** Also affects: byobu
   Importance: Undecided
   Status: New

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  replace uses of net-tools with iproute2

Status in byobu:
  New
Status in byobu package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  As ubuntu goes forward, net-tools is looking to be dropped.

  Byobu currently depends on net-tools.  That code should be replaced by
  iproute2.

  
  Related bugs:
   * bug 925145: cloud-init  Use ip instead of ifconfig and route

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: byobu 5.124-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 12 13:34:27 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (935 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: byobu
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1748952] [NEW] package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to install/upgrade: intentando sobreescribir el compartido `/usr/bin/unity-scope-loader', que es distinto de

2018-02-12 Thread Juan Maldonado

Public bug reported:

i lose my ubuntu store and unity tweak tool, so i install again store
software ubuntu.

when i try install unity tweak tool, don't work, and said broken pagetes

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libunity9 7.1.4+16.04.20160701-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Sun Feb 11 19:56:16 2018
ErrorMessage: intentando sobreescribir el compartido 
`/usr/bin/unity-scope-loader', que es distinto de otras instancias del paquetes 
libunity9:i386
InstallationDate: Installed on 2017-09-04 (161 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: libunity
Title: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/usr/bin/unity-scope-loader', que es distinto de otras instancias del paquetes 
libunity9:i386
UpgradeStatus: Upgraded to xenial on 2018-02-12 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to
  install/upgrade: intentando sobreescribir el compartido `/usr/bin
  /unity-scope-loader', que es distinto de otras instancias del paquetes
  libunity9:i386

Status in libunity package in Ubuntu:
  New

Bug description:
  i lose my ubuntu store and unity tweak tool, so i install again store
  software ubuntu.

  when i try install unity tweak tool, don't work, and said broken
  pagetes

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libunity9 7.1.4+16.04.20160701-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Feb 11 19:56:16 2018
  ErrorMessage: intentando sobreescribir el compartido 
`/usr/bin/unity-scope-loader', que es distinto de otras instancias del paquetes 
libunity9:i386
  InstallationDate: Installed on 2017-09-04 (161 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: libunity
  Title: package libunity9 7.1.4+16.04.20160701-0ubuntu1 failed to 
install/upgrade: intentando sobreescribir el compartido 
`/usr/bin/unity-scope-loader', que es distinto de otras instancias del paquetes 
libunity9:i386
  UpgradeStatus: Upgraded to xenial on 2018-02-12 (0 days ago)

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

** Changed in: systemd
   Status: Unknown => New

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

Title:
  systemd translations are not synced with upstream

Status in systemd:
  New
Status in Ubuntu Translations:
  New
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-12 Thread Gunnar Hjalmarsson

** Bug watch added: github.com/systemd/systemd/issues #8162
   https://github.com/systemd/systemd/issues/8162

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/8162
   Importance: Unknown
   Status: Unknown

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

Title:
  systemd translations are not synced with upstream

Status in systemd:
  Unknown
Status in Ubuntu Translations:
  New
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

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

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

[Touch-packages] [Bug 678421] Re: Error message for a faulty ~/.profile script

** Changed in: gdm
   Status: Confirmed => Won't Fix

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

Title:
  Error message for a faulty ~/.profile script

Status in gdm:
  Won't Fix
Status in gdm package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Fix Released
Status in gdm source package in Trusty:
  Fix Released
Status in lightdm source package in Trusty:
  Fix Released
Status in gdm source package in Utopic:
  Fix Released
Status in lightdm source package in Utopic:
  Fix Released
Status in gdm package in Debian:
  New

Bug description:
  trusty and utopic SRU requests
  ==

  [Impact]

  In case of a syntax error in either of ~/.profile or a few other
  similar files, the Xorg login is interrupted, and the user is taken
  back to the login screen without an explanation. Debugging this
  problem may be a time consuming exercise, especially for non-
  experienced users.

  With the proposed change, lightdm/gdm does not try to load such a
  file, but shows a warning dialog instead. (A warning dialog is also
  shown in case of some other type of error, which would not have caused
  the login to fail.)

  [Test Case]

  To reproduce:

  * Edit ~/.profile and add something bad, e.g. a non-closed parenthesis.
  * Log out and find that you can't log in to a graphical session.

  After installing the proposed lightdm/gdm version, you'll instead see
  the dialog and can log in.

  [Regression Potential]

  Since this is only about improved exception handling, it does not at
  all affect users with correct configuration files. The regression risk
  ought to be minimal.

  [Original description]

  Binary package hint: gdm

  After adding "function AddPath { PATH="$1:$PATH" }" to $HOME/.profile
  made the Xorg startup fail. (At that moment I had already forgotten
  the changes made to the .profile). As I had autologin that meant it
  kept trying to login and finally showed me the graphics
  reconfiguration screen. That sent me to a huge hunt for xorg conf and
  setup problems.

  Anyway finally tracked this down. I had used bash syntax in .profile
  file whereas it was run with sh.

  This is not a bug per se but I think a user mistake in ".profile"
  shouldn't bring the whole xorg startup to a halt as it does with
  autologin. I propose running user ".profile" and ".xprofile" scripts
  so that Xsession script continues running even if they have errors.
  I'm not sure whether this change would have some negative effects as
  well.

  1) Ubuntu Lucid, Linux egon-laptop 2.6.32-25-generic #45-Ubuntu SMP Sat Oct 
16 19:48:22 UTC 2010 i686 GNU/Linux
  2) gdm 2.30.2.is.2.30.0-0ubuntu4

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

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

[Touch-packages] [Bug 1748812] Re: cannot view wifi networks after resume from suspend

2018-02-12 Thread Yuriy Vidineev

Kai-Heng Feng, just closing the lid.

Shih-Yuan Lee, yes, I've installed by myself. I need recent kernel
version for USB C docking stations support

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

Title:
  cannot view wifi networks after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  On 2 laptops (Dell XPS13 9360 with ath10k and Lenovo T530 with iwlwifi) I 
have the same issue:
  After resume from suspend nm-applet doesn't show any information about 
connected/available wi-fi connections. Please see screenshot in attach.
  I can see current connection via CLI:

  nmcli dev
  DEVICE   TYPE  STATE  CONNECTION 
  docker0  bridgeconnected  docker0
  wlp58s0  wifi  connected  Turris 
  lo   loopback  unmanaged  -- 

  Now I have to run `killall nm-applet && nm-applet &` after every
  suspend. That fixes my issue

  I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source
  /network-manager/+bug/1589401 but I was asked to submit separate bug

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  Uname: Linux 4.15.0-041500rc9-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb 11 19:41:21 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  EcryptfsInUse: Yes
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-10-06 (493 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  IpRoute:
   default via 192.168.1.1 dev wlp58s0  proto static  metric 600 
   169.254.0.0/16 dev docker0  scope link  metric 1000 linkdown 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.0.1 linkdown 
   192.168.1.0/24 dev wlp58s0  proto kernel  scope link  src 192.168.1.137  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
  
   docker0  bridgeconnected  /org/freedesktop/NetworkManager/Devices/1  
docker0 440d4ade-78be-45c3-a821-903971861d0c  
/org/freedesktop/NetworkManager/ActiveConnection/0  
   wlp58s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/3  
Turris  e963-362e-4e4a-ac98-54af278d348d  
/org/freedesktop/NetworkManager/ActiveConnection/88 
   lo   loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --  
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1725921] Re: [regression] Combobox has gray text on gray background

2018-02-12 Thread Eldar Khayrullin

Fix #2 (use light menu in popup):
It is need to change in file /usr/share/themes/Ambiance/gtk-2.0/gtkrc the next 
line:
style "menu" = "dark" {
to
style "menu" = "white" {

Restart buggy application.

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

Title:
  [regression] Combobox has gray text on gray background

Status in Ubuntu theme:
  Triaged
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  See pictures.

  Application: pcbnew
  Version: no-vcs-found-0b1eb56~60~ubuntu17.04.1, release build
  Libraries:
  wxWidgets 3.0.3
  libcurl/7.55.1 OpenSSL/1.0.2g zlib/1.2.11 libidn2/2.0.2 libpsl/0.18.0 
(+libidn2/2.0.2) librtmp/2.3
  Platform: Linux 4.13.0-16-generic x86_64, 64 bit, Little endian, wxGTK
  Build Info:
  wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
  Boost: 1.62.0
  Curl: 7.52.1
  Compiler: GCC 6.3.0 with C++ ABI 1010

  Build settings:
  USE_WX_GRAPHICS_CONTEXT=OFF
  USE_WX_OVERLAY=OFF
  KICAD_SCRIPTING=ON
  KICAD_SCRIPTING_MODULES=ON
  KICAD_SCRIPTING_WXPYTHON=ON
  KICAD_SCRIPTING_ACTION_MENU=ON
  BUILD_GITHUB_PLUGIN=ON
  KICAD_USE_OCE=ON
  KICAD_SPICE=ON

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1725921/+subscriptions

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

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

Looking at the log file Daniel provided I'm not certain 30 seconds is
enough:

ERROR: apport (pid 1657) Mon Feb 5 12:02:48 2018: called for pid 923, signal 5, 
core limit 0, dump mode 1
ERROR: apport (pid 1657) Mon Feb 5 12:02:48 2018: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 1657) Mon Feb 5 12:02:48 2018: gdbus call error: Error: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 1657) Mon Feb 5 12:02:48 2018: debug: session gdbus call:
ERROR: apport (pid 1657) Mon Feb 5 12:03:04 2018: wrote report 
/var/crash/_usr_bin_gnome-shell.120.crash
ERROR: apport (pid 1946) Mon Feb 5 12:05:58 2018: another apport instance is 
already running, aborting
ERROR: apport (pid 1941) Mon Feb 5 12:05:55 2018: called for pid 1767, signal 
6, core limit 18446744073709551615, dump mode 1

It is strange though that the crash file is written at 12:03:04. I
wonder what is going on after that.

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files). This issue was first mentioned in bug 1746653. But
  then I noticed my machine doing it too...

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-12 Thread Martin Pitt

I committed the first hunk to Debian, this makes sense:
https://salsa.debian.org/systemd-team/systemd/commit/18d8c2df133b8af

The second is too hackish for a permanent downstream delta, IMHO: This
should rather be fixed upstream, as upstream polkit (as well as Debian's
and Ubuntu's older versions) have proper runtime gettext support.

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

Title:
  systemd translations are not synced with upstream

Status in Ubuntu Translations:
  New
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1707898/+subscriptions

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

[Touch-packages] [Bug 1748828] Re: Bluetooth states off in systray while on

** Package changed: ubuntu => bluez (Ubuntu)

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

Title:
  Bluetooth states off in systray while on

Status in bluez package in Ubuntu:
  New

Bug description:
  The bluetooth indicator suggest that bluetooth is disabled (turned
  off) while this is not the case. See screenshot 1. Only after opening
  the bluetooth toggle, you can see the actual correct action: turn off.
  See screenshot 2.

  As far as I can remember, this behaviour has been introduced on 17.10.

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

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

[Touch-packages] [Bug 1748828] [NEW] Bluetooth states off in systray while on

You have been subscribed to a public bug:

The bluetooth indicator suggest that bluetooth is disabled (turned off)
while this is not the case. See screenshot 1. Only after opening the
bluetooth toggle, you can see the actual correct action: turn off. See
screenshot 2.

As far as I can remember, this behaviour has been introduced on 17.10.

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


** Tags: bot-comment
-- 
Bluetooth states off in systray while on
https://bugs.launchpad.net/bugs/1748828
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez in Ubuntu.

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

[Touch-packages] [Bug 1748729] Re: Xorg freeze

** Description changed:

- I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the 
propriety Nvidia driver 340 as suggested by Ubuntu. 
+ I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the 
propriety Nvidia driver 340 as suggested by Ubuntu.
  The screen almost freezes completely as soon as I maximise any window in the 
guest OS Ubuntu 18.04. Any mouse click takes 10-60 seconds before the system 
reacts to it. It took a long time to generate this bug-report.
  
  I had the same problem with Ubuntu 17.10, while Guest OSes Ubuntu Mate
- 17.10, Xubuntu 17.10, Peppermint 8 and Windows 7 and 10 work without any
- problem.
+ 17.10, Xubuntu 17.10, and Peppermint 8. Windows 7 and 10 work without
+ any problem.
+ 
+ WORKAROUND: Disable 3D acceleration.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 06:31:52 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-12-22 (50 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.89-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I run Ubuntu 18.04 in Virtualbox 5.2.6 with as host OS; Ubuntu 17.10 with the 
propriety Nvidia driver 340 as suggested by Ubuntu.
  The screen almost freezes completely as soon as I maximise any window in the 
guest OS Ubuntu 18.04. Any mouse click takes 10-60 seconds before the system 
reacts to it. It took a long time to generate this bug-report.

  I had the same problem with Ubuntu 17.10, while Guest OSes Ubuntu Mate
  17.10, Xubuntu 17.10, and Peppermint 8. Windows 7 and 10 work without
  any problem.

  WORKAROUND: Disable 3D acceleration.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 06:31:52 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter

[Touch-packages] [Bug 1748660] Re: all bug

jaffar, thank you for reporting this and helping make Ubuntu better.

1) Could you please provide the full computer model as per the sticker
on the computer itself (not the result of a terminal command or from the
Bug Description)?

2) Could you please provide a screenshot of the error when you start
Ubuntu?

3) Is this error something that started after an update? If so, which
specifically?

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  all bug

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm having an error when I start ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Feb 10 12:51:14 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   evdi, 4.1.9, 4.13.0-32-generic, x86_64: installed
   evdi, 4.1.9, 4.4.0-112-generic, x86_64: installed
   openrazer-driver, 1.0.0, 4.13.0-32-generic, x86_64: installed
   openrazer-driver, 1.0.0, 4.4.0-112-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:806d]
 Subsystem: Hewlett-Packard Company GM108M [GeForce 930M] [103c:806d]
  InstallationDate: Installed on 2018-02-06 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0483:91d1 STMicroelectronics Sensor Hub
   Bus 001 Device 003: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP ENVY x360 m6 Convertible
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=a33e7fed-003a-4efd-8fca-025d5fb03453 ro iommu=soft quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/09/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 806D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.06:bd06/09/2015:svnHewlett-Packard:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHewlett-Packard:rn806D:rvr72.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY x360 m6 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1745027] Re: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-02-12 Thread Joshua Powers

>From your log:

Feb 11 14:57:02 de sshd[12337]: error: Bind to port X on 0.0.0.0 
failed: Address already in
Feb 11 14:57:02 de sshd[12337]: error: Bind to port X on :: failed: 
Address already in use.

The port you are trying to use already has something running on it.

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Started installing upgrade new kernels.
  But yesterday i did not finish seting up vlan.
  So in sshd config remained a address for vlan.
  in net conf was set up automatic vlan conf

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Tue Jan 23 21:47:25 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-11-12 (803 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1747416] Re: ibus-ui-gtk3 abrt on missing org.freedesktop.ibus.panel.emoji schemas

the corresponding e.u.c report is on
https://errors.ubuntu.com/problem/d3f3e3ff370d0cf25934939053f8c1c7b0781489

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

Title:
  ibus-ui-gtk3 abrt on missing org.freedesktop.ibus.panel.emoji schemas

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-ui-gtk3 crashed with signal 5
  After login, after boot.

  When loading desktop(Lxde)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-3.4-generic 4.14.0-rc6
  Uname: Linux 4.14.0-3-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Feb  5 10:19:38 2018
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2016-08-02 (551 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  Signal: 5
  SourcePackage: ibus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ()
  Title: ibus-ui-gtk3 crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2017-11-24 (72 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Touch-packages] [Bug 1748656] Re: Black Screen of Death after logging into Ubuntu Bionic: "Failed to acquire modesetting permission"

George, thank you for reporting this and helping make Ubuntu better.

1) Regarding the version of the nvidia drivers you attempted to use, it
appears you are using an upstream or 3rd party version. Could you please
mention where you obtained the driver from?

2) Could you please install a supported version of the nvidia driver
found at https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia and
advise to the results?

3) Do you have this issue if you don't install a proprietary nvidia
driver?

4) To advise, when attaching logs, please don't snip/grep/cut logs.
Attach logs in their entirety from the first entry of a boot to when the
issue is reproducible. Developers can't work with snips.

** Tags added: latest-bios-1.13

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

** Changed in: xorg (Ubuntu)
   Status: New => Incomplete

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

Title:
  Black Screen of Death after logging into Ubuntu Bionic: "Failed to
  acquire modesetting permission"

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  **Specs:** Ubuntu Bionic; NVidia GTX 1070 w/`nvidia-387` drivers.

  **Problem:** After installing a new GTX 1070 and installing
  `nvidia-387`, I get a black screen of death AFTER logging into Ubuntu
  (i.e., the login screen shows up just fine). I'm not even able to
  access other TTYs (the error logs below were retrieved via SSH).

  **/var/log/Xorg.0.log** There doesn't seem to be anything problematic
  in this file.

  **/var/log/Xorg.1.log** The problematic message seems to be:

  [26.455] (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission.
  [26.455] (EE) NVIDIA(0): Failing initialization of X screen 0
  [26.455] (II) UnloadModule: "nvidia"
  [26.455] (II) UnloadSubModule: "wfb"
  [26.455] (II) UnloadSubModule: "fb"
  [26.455] (EE) Screen(s) found, but none have a usable configuration.
  [26.455] (EE) 
  Fatal server error:
  [26.455] (EE) no screens found(EE) 
  [26.455] (EE) 
  Please consult the The X.Org Foundation support 
  at http://wiki.x.org
  for help. 
  [26.455] (EE) Please also check the log file at "/var/log/Xorg.1.log" 
for additional information.
  [26.455] (EE) 
  [26.457] (EE) Server terminated with error (1). Closing log file.

  **Conf files.** Here are my conf files:

  $ cd /usr/share/X11
  $ find . -name "*.conf"
  ./xorg.conf.d/glamoregl.conf
  ./xorg.conf.d/10-amdgpu.conf
  ./xorg.conf.d/40-libinput.conf
  ./xorg.conf.d/50-nvidia-drm-outputclass.conf
  ./xorg.conf.d/50-nvidia-drm-outputclass.conf/nvidia-drm-outputclass.conf
  ./xorg.conf.d/10-quirks.conf
  ./xorg.conf.d/10-radeon.conf
  ./xorg.conf.d/70-wacom.conf

  I tried deleting all of these except for the nvidia one and rebooting,
  and the error persists. In addition, I tried deleting all of them and
  generating a new one via `sudo X -configure` but get

  $ cd /usr/share/X11$ 
  $ sudo pkill X && sudo X -configure  
  _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
  _XSERVTransMakeAllCOTSServerListeners: server already running
  (EE) 
  Fatal server error:
  (EE) Cannot establish any listening sockets - Make sure an X server isn't 
already running(EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
  at http://wiki.x.org
  for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.

  **kms.** Finally, in case relevant:

  $ lsmod | grep kms
  drm_kms_helper167936  1 nvidia_drm
  syscopyarea16384  1 drm_kms_helper
  sysfillrect16384  1 drm_kms_helper
  sysimgblt  16384  1 drm_kms_helper
  fb_sys_fops16384  1 drm_kms_helper
  drm   356352  6 nvidia_drm,drm_kms_helper

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  387.34  Tue Nov 21 03:09:00 
PST 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-18ubuntu2)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires

[Touch-packages] [Bug 1611945] Re: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks

2018-02-12 Thread Norman Henderson

Ladies and Gentlemen, The technical stuff is way over my head but I am
getting the same syslog errors and the same inconsistent device paths on
an HP Proliant ML110 G7 with Ubuntu 16.04.3 kernel 4.4.0-98-generic.

It seems clear that no-one is taking ownership of this to fix it in an
actual update that ordinary people like me can install in the normal
course of system updates. The nature of open source software I guess.

However could someone please let me know:
 - is this just an annoying message that won't be fixed, or are there 
operational implications?
 - if there are implications, are they serious?
 - if they are serious, could you explain (or point me at a resource that 
explains) in detail, how to install the patch provided. I've never done that 
before.

Thank you in advance!

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

Title:
  /dev/disk/by-path not properly populated for (e)SATA port multiplier
  disks

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  We have a just-installed Ubuntu 16.04 LTS machine with a number of
  disks behind port-multiplier eSATA ports, all of them driven by a SiI
  3124 controller (sata_sil24 kernel driver). Our machine sees all disks
  on all channels, however under 16.04 only one disk from each channel
  shows up in /dev/disk/by-path/ (all disks show up in /dev/disk/by-id
  and /dev/disk/by-uuid). For our usage this is a severe defect because
  we rotate disks in and out of the external enclosure and rely on
  mounting specific slots in the external enclosure through /dev/disk
  /by-path.

  This did not happen in Ubuntu 12.04 LTS, the release that this machine
  was previously running.

  According to 'udevadm info --export-db' and 'udevadm test-builtin
  path_id' and so on, systemd's udev stuff is assigning all drives
  behind the same port the same disk/by-path data (ID_PATH et al). In
  'udevadm info /sys/block/sdX', the 'P:' and 'E: DEVPATH=' values show
  a difference in the target portion of PCI path, eg:

P: 
/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda
P: 
/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:1:0/0:1:0:0/block/sdb

  However the 'S: disk/by-path', 'E: DEVLINKS=', and 'E: ID_PATH'
  portions do not. For both devices above, we see:

S: disk/by-path/pci-:02:00.0-ata-1
E: ID_PATH=pci-:02:00.0-ata-1

  Naturally only one device can have a /dev/disk/by-
  path/pci-:02:00.0-ata-1 symlink, so instead of four disks per
  channel in /dev/disk/by-path we see one.

  Ubuntu release: 16.04

  Package versions from 'apt-cache policy udev systemd':
  udev:
Installed: 229-4ubuntu7
  systemd:
Installed: 229-4ubuntu7

  'journalctl -b' reports that during boot systemd does report some
  'appeared twice with different sysfs paths' notes, eg:

  Aug 10 13:34:21 verdandi systemd[1]: dev-disk-by\x2dpath-
  pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device: Dev dev-disk-by
  \x2dpath-pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device appeared
  twice with different sysfs paths
  
/sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:3:0/0:3:0:0/block/sdd/sdd1
  and
  
/sys/devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda/sda1

  However it doesn't seem to be reporting this for all port-multiplier
  drives and their partitions.

  If it would be useful I can attach full 'udevadm info --export-db'
  output or the like.

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

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

[Touch-packages] [Bug 1742941] Re: zlib: improve crc32 performance on P8

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

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

Title:
  zlib: improve  crc32 performance on P8

Status in The Ubuntu-power-systems project:
  Incomplete
Status in zlib package in Ubuntu:
  New

Bug description:
  Calculate the checksum of data that is 16 byte aligned and a multiple
  of  16 bytes.

  The first step is to reduce it to 1024 bits. We do this in 8 parallel
   chunks in order to mask the latency of the vpmsum instructions. If we
   have more than 32 kB of data to checksum we repeat this step multiple
   times, passing in the previous 1024 bits.

   The next step is to reduce the 1024 bits to 64 bits. This step adds
   32 bits of 0s to the end - this matches what a CRC does. We just
   calculate constants that land the data in this 32 bits.

   We then use fixed point Barrett reduction to compute a mod n over GF(2)
   for n = CRC using POWER8 instructions. We use x = 32.

   http://en.wikipedia.org/wiki/Barrett_reduction

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742941/+subscriptions

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

[Touch-packages] [Bug 1747416] Re: ibus-ui-gtk3 abrt on missing org.freedesktop.ibus.panel.emoji schemas

Those reports are a bit confusing, it's like the gsettings schemas
didn't include the new emojs key but the ibus package installed is the
new/correct version and there doesn't seem to be a local installation
taking over it in the procmaps table ... Could anyone having the issue
help debugging?

Guesses include the issue being transient in the middle of an upgrade or
the glib-compile-schemas update failing to generate an update file for
some reason

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

Title:
  ibus-ui-gtk3 abrt on missing org.freedesktop.ibus.panel.emoji schemas

Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-ui-gtk3 crashed with signal 5
  After login, after boot.

  When loading desktop(Lxde)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-3.4-generic 4.14.0-rc6
  Uname: Linux 4.14.0-3-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CrashCounter: 1
  Date: Mon Feb  5 10:19:38 2018
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2016-08-02 (551 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  Signal: 5
  SourcePackage: ibus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ()
  Title: ibus-ui-gtk3 crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2017-11-24 (72 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Touch-packages] [Bug 1552792] Re: gnome software leaves dependencies installed

2018-02-12 Thread AsciiWolf

As I wrote in the github PackageKit bug report: I offer 1 ETH (currently
~852 USD) to anyone who manages to implement (and gets upstreamed) a
working autoremove support for packages that are uninstalled using GNOME
Software on Ubuntu/Debian. ;-)

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

Title:
  gnome software leaves dependencies installed

Status in GNOME Software:
  Invalid
Status in Release Notes for Ubuntu:
  Fix Released
Status in aptdaemon package in Ubuntu:
  New
Status in gnome-software package in Ubuntu:
  Triaged
Status in packagekit package in Ubuntu:
  New

Bug description:
  Using gnome software (or another PackageKit or aptdaemon based UI) to
  install an application - removal of that package leaves behind
  dependencies

  Installing an application with ubuntu software centre only leaves
  behind config files (seen in synaptic labelled for complete removal).

  After installing and then removing alarm clock with USC -

  sudo apt-get autoremove
  [sudo] password for wolf:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade.

  After cleaning up and then reinstalling with gnome software, followed
  by the removal

  sudo apt-get autoremove
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED
    libappindicator1 libindicator7
  0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade.
  After this operation, 184 kB disk space will be freed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar  3 16:23:45 2016
  InstallationDate: Installed on 2015-10-29 (126 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029)
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-software/+bug/1552792/+subscriptions

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

[Touch-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

2018-02-12 Thread Timo Aaltonen

hwang: They need to be recreated to match what went in bionic, also the
artful version should be -2ubuntu3.1

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Confirmed
Status in pulseaudio source package in Artful:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+subscriptions

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

[Touch-packages] [Bug 1737662] Re: Unable to install ubuntu1804 build with Debootstrap warning on witherspoon system

** Changed in: ubuntu-power-systems
   Status: Fix Committed => Fix Released

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

Title:
  Unable to install ubuntu1804 build with Debootstrap warning on
  witherspoon system

Status in The Ubuntu-power-systems project:
  Fix Released
Status in busybox package in Ubuntu:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released

Bug description:
  Problem Description:
  ===
  Ubuntu1804 installer shows Debootstrap warning  messages and not able to 
proceed with installation

  Steps to re-create:
  ==
  > on Witherspoon test system, tried to install ubuntu1804 using netboot 
install.

  > Selected mirror path:http://10.xx.11.31:3128

  
 [!] Choose a mirror of the Ubuntu archive 
? ?
? Please select an Ubuntu archive mirror. You should use a mirror in  ?
? your country or region if you do not know which mirror has the best ?
? Internet connection to you. ?
? ?
? Usually, .archive.ubuntu.com is a good choice.   ?
? ?
? Ubuntu archive mirror:  ?
? ?
? us.ports.ubuntu.com ?
? ?
??
? ?
???

  
  > Able to select the disks

?? [!!] Partition disks ???
? ?
? Note that all data on the disk you select will be erased, but not   ?
? before you have confirmed that you really want to make the changes. ?
? ?
? Select disk to partition:   ?
? ?
?/dev/nvme0n1 - 409.6 GB Unknown  ?
?SCSI1 (0,0,0) (sda) - 3.8 TB ATA MTFDDAK3T8TCB   ?
?SCSI2 (0,0,0) (sdb) - 3.8 TB ATA MTFDDAK3T8TCB   ?
? ?
??
? ?
???

  
  > Started installing base system

??? Installing the base system 
? ?
?6%   ?
? ?
? Retrieving libc6... ?
? ?
???

  > Then seen Debootstrap warning messages as below

  
??? [!!] Install the base system ???
?  ? ??
?   ?   Debootstrap warning?  ?
?   ? Warning: Failure trying to run: chroot /target dpkg-deb -f   ?  ?
?   ? /var/cache/apt/archives/dpkg_1.19.0.4ubuntu1_ppc64el.deb Version ?  ?
? Ex?  ?  ?
?   ?   ?  ?
?  ? ??



??? [!!] Install the base system ??
?   ?  ?  ?
?   ?   Debootstrap warning?  ?
?   ? Warning: See the log for details ?  ?
? Extracting zlib1g.?  ?  ?
?   ?   ?

[Touch-packages] [Bug 1719579] Re: [Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save

** Changed in: ubuntu-power-systems
   Status: Triaged => Fix Released

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

Title:
  [Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in
  /var/tmp folder using virsh save

Status in The Ubuntu-power-systems project:
  Fix Released
Status in apparmor package in Ubuntu:
  Invalid
Status in libvirt package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #1 - SEETEENA THOUFEEK  - 2017-01-17 
00:09:16 ==
  Bala, Please mail me the machine information.

  == Comment: #3 - SEETEENA THOUFEEK  - 2017-01-17 
02:14:06 ==
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on 
'/var/tmp/bala'
  2017-01-16 12:09:37.707+: 7024: info : 
virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on 
'/var/tmp/bala' to '0:0'
  2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 
: failed to restore save state label on /var/tmp/bala
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : 
Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala)
  2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca62b00
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff4ca535c0
  2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 
7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with 
ret=-1
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 
: prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 
rerr=0x3fffa59be3c0
  2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : 
Encode length as 172
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 
offset=0
  2017-01-16 12:09:37.707+: 7024: info : 
virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: 
client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 
serial=4
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 
tx=0x100133d2590
  2017-01-16 12:09:37.707+: 7024: debug : 
virNetServerClientCalculateHandleMode:192 : mode=3
  2017-01-16 12:09:37.707+: 7024: info : virEventPollUpdateHandle:152 : 
EVENT_POLL_UPDATE_HANDLE: watch=417 events=3
  2017-01-16 12:09:37.707+: 7024: debug : virEventPollInterruptLocked:727 : 
Interrupting
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x3fff7c002c10
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133caea0
  2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d23c0
  .
  2017-01-16 12:14:28.445+: 7019: info : qemuMonitorJSONIOProcessLine:201 : 
QEMU_MONITOR_RECV_EVENT: mon=0x3fff94004d90 event={"timestamp": {"seconds": 
1484568868, "microseconds": 444620}, "event": "MIGRATION", "data": {"status": 
"failed"}}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorJSONIOProcessEvent:147 
: mon=0x3fff94004d90 obj=0x100133b5670
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1762 : 
object=0x100133a8000
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133a8000 type=0 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToStringOne:1691 : 
object=0x100133d2a80 type=2 gen=0x100133d1160
  2017-01-16 12:14:28.445+: 7019: debug : virJSONValueToString:1795 : 
result={"status":"failed"}
  2017-01-16 12:14:28.445+: 7019: debug : qemuMonitorEmitEvent:1218 : 
mon=0x3fff94004d90 event=MIGRATION
  2017-01-16 12:14:28.445+: 7019: info : virObjectRef:296 : OBJECT_REF: 
obj=0x3fff94004d90
  2017-01-16 12:14:28.445+: 7019: debug : qemuProcessHandleEvent:629 : 
vm=0x3fff4ca535c0
  2017-01-16 12:14:28.445+: 7019: info : virObjectNew:202 : OBJECT_NEW: 
obj=0x100133d2870 classname=virDomainQemuMonitorEvent
  2017-01-16 12:14:28.445+: 7019: debug : virObjectEventNew:645 : 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:259 : OBJECT_UNREF: 
obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: info : virObjectUnref:261 : 
OBJECT_DISPOSE: obj=0x100133d2870
  2017-01-16 12:14:28.445+: 7019: debug : 
virDomainQemuMonitorEventDispose:477 : obj=0x100133d2870

[Touch-packages] [Bug 1746495] Re: ibus-ui-gtk3 crashed with signal 5

*** This bug is a duplicate of bug 1747416 ***
https://bugs.launchpad.net/bugs/1747416

** This bug is no longer a duplicate of bug 1742571
   ibus-ui-gtk3 (5) g_settings_set_property → object_set_property → 
g_object_new_internal → g_object_new_valist → g_object_new
** This bug has been marked a duplicate of bug 1747416
   ibus-ui-gtk3 abrt on missing org.freedesktop.ibus.panel.emoji schemas

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

Title:
  ibus-ui-gtk3 crashed with signal 5

Status in ibus package in Ubuntu:
  New

Bug description:
  ibus-ui-gtk3 crashed with signal 5
  System after login(boot)

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu1
  ProcVersionSignature: Ubuntu 4.14.0-3.4-generic 4.14.0-rc6
  Uname: Linux 4.14.0-3-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Wed Jan 31 09:18:57 2018
  ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
  InstallationDate: Installed on 2016-08-02 (546 days ago)
  InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160727)
  ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
  Signal: 5
  SourcePackage: ibus
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_object_new () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ()
  Title: ibus-ui-gtk3 crashed with signal 5
  UpgradeStatus: Upgraded to bionic on 2017-11-24 (67 days ago)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo vboxsf

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

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

[Touch-packages] [Bug 1737618] Re: ibus not working in Ubuntu wayland session: traps: ibus-ui-gtk3[1565] general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in libX11.so.6.3.0[7fd420440000+1340

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.

** Changed in: ibus (Ubuntu)
   Importance: Undecided => High

** Changed in: ibus (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  ibus not working in Ubuntu wayland session:  traps: ibus-ui-gtk3[1565]
  general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in
  libX11.so.6.3.0[7fd42044+134000]

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  ibus is not loading neither the applet appearing in Gnome Shell
  wayland session in Ubuntu 17.10. These are the error messages I can
  find:

  :~$ cat /var/log/kern.log |grep ibus*
  Dec 11 02:47:32 HP-LAPTOP kernel: [  356.188579] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled
  Dec 11 05:26:54 HP-LAPTOP kernel: [   77.136259] traps: ibus-ui-gtk3[1565] 
general protection ip:7fd4204dd253 sp:7ffd74de90b0 error:0 in 
libX11.so.6.3.0[7fd42044+134000]
  Dec 11 05:54:19 HP-LAPTOP kernel: [  138.126513] traps: ibus-ui-gtk3[2277] 
general protection ip:7f4b7a06b253 sp:7fffe3c94860 error:0 in 
libX11.so.6.3.0[7f4b79fce000+134000]
  Dec 12 00:39:20 HP-LAPTOP kernel: [ 1355.581927] SGI XFS with ACLs, security 
attributes, realtime, no debug enabled

  I tried changing input method using im-config to xim and it did not
  yield any positive results. Also, I remember one time, there was a
  segmentation fault happened with ibus which I cannot reproduce again
  on this system.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ibus-wayland 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: ndiswrapper
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 12 02:20:20 2017
  InstallationDate: Installed on 2017-11-22 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1742571] Re: ibus-ui-gtk3 (5) g_settings_set_property → object_set_property → g_object_new_internal → g_object_new_valist → g_object_new